A company expense policy should cover what employees can spend money on, the limits and approvals for each category, how and when to submit receipts, how reimbursements are paid, and what happens when the rules are broken. A good one is short, specific and easy to follow, so people actually read it. This guide breaks down every section to include, with plain-language examples you can adapt, and shows how to enforce the policy automatically instead of policing every receipt by hand.
Why a written expense policy matters
Without a written policy, every purchase becomes a judgment call and every reimbursement becomes an argument. People guess at what is allowed, spend inconsistently, and finance ends up litigating each questionable charge after the money is gone. A clear policy sets expectations up front: employees know what they can buy and how to get paid back, and finance has a rule to point to instead of a case-by-case debate. It also matters at tax time, because the IRS treats reimbursements made under an accountable plan differently from those that are not, and a written policy is part of showing you run one.
What every expense policy should include
1. What the company will and will not pay for
List the categories the business reimburses (travel, lodging, meals, software, office supplies, client entertainment) and, just as important, what it will not (personal items, alcohol beyond stated limits, fines, first-class upgrades). Be concrete. A line like "reasonable meals while traveling" invites disputes; "meals while traveling, up to $60 per day" does not.
2. Spending limits by category
Set clear dollar limits so people do not have to guess. For example: hotels up to $250 per night in most cities, meals up to $60 per day, any single purchase over $500 requires pre-approval. Limits do two jobs: they cap spend, and they remove the awkwardness of an employee wondering whether a purchase is acceptable.
3. Approval rules
Spell out who approves what and when. A common structure: anything under a small threshold needs no pre-approval, purchases above it need a manager's sign-off first, and large or unusual spend needs finance. Say whether approval happens before or after the purchase, because "ask first" and "explain later" are very different policies and mixing them up causes most of the friction.
4. Receipt requirements
State exactly what counts as a valid receipt, when it is due, and the threshold below which one is not required. For example: an itemized receipt for every purchase over $25, submitted within 15 days. Itemized matters, because a credit card slip shows the total but not what was bought, and the detail is what proves the expense was legitimate and coded correctly.
5. How to submit expenses
Tell people the mechanics: which tool to use, how to attach receipts, what information to include, and the deadline. The easier this is, the more compliant people are. Policies fail not because employees are dishonest but because submitting is annoying, so they procrastinate and details get lost. Capturing receipts at the moment of purchase, from a phone, beats a monthly scramble every time.
6. Reimbursement timing and method
Say how quickly approved expenses are paid back and how (typically with payroll or a direct deposit). People plan around this, especially when they front travel costs personally, so a clear "reimbursed within one pay cycle of approval" prevents a lot of quiet resentment.
7. Company cards, if you issue them
If some employees carry company cards, cover them explicitly: what the card may be used for, that personal use is prohibited, and that a receipt is still required for every charge. A card is not a substitute for a receipt; reconciliation still needs the detail behind each transaction.
8. Consequences for violations
State plainly what happens when the policy is not followed: a late or missing receipt may delay reimbursement, out-of-policy spend may not be reimbursed at all, and repeated or deliberate abuse is a disciplinary matter. You are not trying to be punitive; you are removing ambiguity so the rare bad case is handled by a rule rather than an improvised confrontation.
A short example you can adapt
Here is the compact version many small companies use as a starting point:
- We reimburse reasonable, documented business expenses: travel, lodging, meals, software and supplies.
- Meals: up to $60 per day while traveling. Lodging: up to $250 per night. Anything over $500 needs pre-approval from your manager.
- Submit an itemized receipt for every expense over $25 within 15 days, through our expense tool.
- Approved expenses are reimbursed within one pay cycle.
- Personal charges on company cards are prohibited. Out-of-policy spend may not be reimbursed.
Adapt the numbers to your business, but keep the structure: categories, limits, approvals, receipts, timing, consequences.
How to enforce a policy without policing every receipt
A policy nobody enforces is a suggestion. But enforcing it by hand, checking each receipt against each limit, is exactly the tedious work that makes finance dread the close. The better approach builds the rules into the system so violations are caught automatically as spend happens. When a charge exceeds a category limit, it gets flagged. When a receipt is missing, the employee is reminded while they still remember the purchase. When something needs approval, it routes to the right person before it clears.
That is the idea behind expense policy software: the policy stops living in a PDF nobody opens and starts running on every transaction. Pair it with an expense approval workflow that routes sign-offs automatically, and enforcement becomes a background process rather than a monthly audit. Finance reviews the exceptions the system flags instead of re-checking every compliant charge by hand.
The short version
A company expense policy should tell employees what they can spend on, the limits and approvals per category, how and when to submit receipts, how fast they get reimbursed, the rules for company cards, and the consequences for breaking the policy. Keep it short and specific so people read it. Then enforce it automatically: flag out-of-policy charges and missing receipts as they happen, so the rules hold without anyone policing every line. Expenditure checks each charge against your policy on the cards you already use, never moves or holds your money, and is software and insight, not tax or accounting advice.