Creating Expense Policies That Actually Work
How to write expense policies that provide clarity and control without creating bureaucratic overhead or making people feel mistrusted.
Bad expense policies create one of two problems: either they’re so vague that people don’t know what’s acceptable, or so detailed that they create bureaucratic overhead and make everyone feel like children. Good expense policies find the middle ground—clear enough to guide decisions, flexible enough to accommodate judgment.
Why You Need an Expense Policy
Clarity. People shouldn’t have to guess what’s okay. Is a $100 client dinner acceptable? Can they expense a $30/month productivity app? Clear policies answer these questions.
Consistency. Without a policy, expense decisions are arbitrary. One manager approves everything, another rejects everything. Policies create fairness.
Protection. Policies protect the company from abuse and protect employees from accusations. Clear rules mean clear expectations.
Efficiency. When rules are clear, approvals are faster. No back-and-forth about whether something is allowed.
The Core Principles
Before writing specific rules, establish principles:
Principle 1: Act Like an Owner
Would you spend this money if it were coming out of your own pocket? This single principle handles 80% of cases.
Principle 2: Business Purpose Required
Every expense should have a clear business reason. “I wanted it” isn’t a business reason. “It makes me more productive” is—if true.
Principle 3: Reasonable and Appropriate
Expenses should be reasonable for the situation. A $50 lunch meeting is reasonable. A $500 lunch meeting needs justification.
Principle 4: When in Doubt, Ask
If you’re not sure, ask before spending. It’s easier to get approval than forgiveness.
What to Include in Your Policy
1. Expense Categories and Guidelines
Cover the major categories with specific guidance:
Software and Subscriptions
•
Pre-approval required for tools over $X/month
•
Must check if company already has similar tool
•
Annual contracts require manager approval
•
Security review required for tools handling sensitive data
Travel
•
Booking lead time expectations
•
Flight class by duration
•
Hotel nightly rate caps by city tier
•
Ground transportation guidelines
•
Trip approval requirements
Meals and Entertainment
•
Client meal per-person caps
•
Team meal guidelines
•
Alcohol policy (covered or not, limits)
•
Entertainment (events, tickets) approval requirements
Professional Development
•
Conference and course budgets
•
Book and learning material policies
•
Certification reimbursement
Equipment and Supplies
•
Home office setup allowance
•
Equipment refresh policies
•
Office supplies guidelines
2. Approval Requirements
Be specific about what needs approval and from whom:
Amount
Approval Required
Under $100
No approval
$100-500
Manager
$500-2,000
Director/VP
Over $2,000
Finance/CEO
Adjust thresholds based on company stage and culture.
3. Documentation Requirements
Specify what documentation is needed:
•
Receipts required for expenses over $25
•
Business purpose description for meals and entertainment
•
Attendee list for group expenses
•
Approval documentation for pre-approved items
4. Submission and Reimbursement
Cover the mechanics:
•
How to submit expenses (app, email, form)
•
Deadline for submission (e.g., within 30 days)
•
Expected reimbursement timeline
•
What happens with late submissions
5. Non-Reimbursable Expenses
List what’s explicitly not covered:
•
Personal items
•
Commuting costs (unless travel for work)
•
Fines and penalties
•
Political contributions
•
Personal entertainment
•
Family member expenses
6. Corporate Card Guidelines
If you issue cards:
•
Card is company property
•
Personal use prohibited
•
Lost card reporting procedure
•
Spending limits by role
Sample Policy Sections
Travel Policy Example
Air Travel:
•
Economy class for flights under 6 hours
•
Premium economy or business class optional for flights over 6 hours, with manager approval
•
Book at least 14 days in advance when possible
•
Use preferred airline for points accumulation when price difference is less than 20%
Hotels:
•
Standard room at business-class hotels
•
Nightly rate caps: Tier 1 cities (NYC, SF, London) $300; Tier 2 cities $200; Other $150
•
Exceptions require pre-approval
•
Extended stays (5+ nights) may warrant apartment rental
Ground Transportation:
•
Public transit or rideshare preferred
•
Rental cars for trips where cost-effective or necessary
•
No premium/luxury vehicles without justification
Per Diem vs. Actuals:
•
Option A: Per diem of $75/day for meals and incidentals
•
Option B: Actual expenses with $100/day cap
•
Choose one approach and stick with it
Meals and Entertainment Example
Client Meals:
•
Reasonable restaurants appropriate to the client relationship
•
Per-person cap: $75 lunch, $125 dinner
•
Alcohol: limited to 2 drinks per person, not to exceed 30% of total bill
•
Business purpose and attendee names required
Team Meals:
•
Team lunches/dinners: $40 per person cap
•
Manager approval required for 10+ people
•
Celebrations (launches, milestones): $60 per person with director approval
Individual Meals:
•
Working meals during travel: reasonable actuals
•
Local working meals: generally not reimbursable unless working late (after 8pm)
Software Policy Example
Pre-Approved Tools:
•
Productivity suite (Google Workspace, Notion, Slack) - standard
•
Design tools for designers (Figma) - standard
•
Development tools for engineers (GitHub, etc.) - standard
New Tool Requests:
•
Under $20/month: Manager approval, IT notification
•
$20-100/month: Manager approval, IT security review
•
Over $100/month: Director approval, IT security review, procurement review
Requirements:
•
Check existing tools first (we may already have it)
•
SSO/SAML required for tools handling company data
•
No tools storing sensitive customer data without security approval
Common Mistakes in Expense Policies
Too Vague
Bad: “Expenses should be reasonable.”
Better: “Expenses should be reasonable for the business purpose. Client dinners under $75/person don’t require justification. Above that, include a note explaining the context.”
Too Detailed
Bad: A 50-page document covering every possible scenario.
Better: Clear principles plus guidelines for common categories. Accept that judgment is required for edge cases.
Too Restrictive
Bad: Requiring VP approval for a $50 purchase.
Better: Set thresholds that balance control with operational efficiency.
No Enforcement
Bad: Having policies but never reviewing compliance.
Better: Regular audits, consistent enforcement, clear consequences.
One-Size-Fits-All
Bad: Same policy for a 5-person startup and 500-person company.
Better: Policies that match your stage, culture, and trust level.
Communicating the Policy
A policy no one knows about is useless.
Make It Accessible
•
Post in company wiki/handbook
•
Link from expense submission tool
•
Include in onboarding
Explain the Why
•
Don’t just list rules
•
Explain the reasoning
•
Help people understand the principles
Train Managers
•
Managers are the front line of policy enforcement
•
Make sure they understand and apply consistently
Announce Changes
•
When policies change, communicate clearly
•
Give people time to adjust
Enforcement
Light Touch Approach
For most companies, especially early stage:
•
Review expenses monthly
•
Flag patterns, not individual items
•
Have conversations before consequences
•
Trust but verify
When to Escalate
Some situations warrant direct action:
•
Obvious personal expenses on company card
•
Fraudulent receipts or claims
•
Pattern of policy violations after coaching
•
Expenses without business purpose
Consequences
Graduated response:
1.
Coaching conversation
2.
Written warning
3.
Removal of card/spending privileges
4.
Termination (for fraud or repeated violations)
Document everything. Be consistent.
Evolving Your Policy
When to Update
•
After significant company growth (thresholds may need adjustment)
•
After acquisition or merger
•
When patterns of confusion emerge
•
When business model changes
•
Annually as part of policy review
How to Update
•
Gather feedback from managers and employees
•
Review common edge cases and questions
•
Benchmark against similar companies
•
Get input from finance and legal
•
Communicate changes clearly
Key Takeaways
•
Good expense policies balance clarity with flexibility
•
Lead with principles, follow with specific guidelines
•
Set appropriate thresholds—not so low they create overhead, not so high they enable abuse
•
Document common categories clearly but accept that judgment handles edge cases
•
Communicate the policy and explain the reasoning
•
Enforce consistently—policies without enforcement are suggestions
•
Update as the company grows and circumstances change
•
Trust your team by default; policies are guardrails, not micromanagement
Put your context to work.
Keep your project’s decisions, next steps and proof together as your agents work.
Explore the agent workflow →