Finance Index
How do you write an expense policy that's clear enough to follow without asking finance?
Reference guide to expense policy people follow, including card controls, policy design, employee spend workflows, receipt capture, and reconciliation.
Write it short (two to four pages), organized by situation rather than by clause ("traveling," "taking a client to dinner," "working from home"), with dollar guidance and worked examples instead of adjectives like "reasonable." Then enforce it in the expense tool - limits and flags at submission - so the policy is experienced as guardrails, not as an audit surprise three weeks later.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| How do you write | Write it short (two to four pages), organized by situation rather than by clause ("traveling," "taking a client to dinner," "working from home"), with dollar guidance and worked examples instead of adjectives like "reasonable." Then enforce it in the expense tool. | Keeps evidence clear and reduces control risk. |
| Per-category limits | Hybrid: hard caps where abuse concentrates (lodging nightly rates, meal limits), guidelines with required justification in between, and city-indexing (or GSA-rate referencing) for travel-heavy companies where one national number is wrong everywhere. | Helps finance decide what to do next. |
| Related terms | Principles produce better behavior in high-trust, senior teams and ambiguity everywhere else - "like it's yours" means different things to different wallets. | Keeps spend tied to policy, ownership, and review. |
| Control point | Encode limits as submission-time validations, require receipts by threshold automatically, flag policy exceptions to the approver with the violation named, and block the few absolute prohibitions outright. | Keeps spend tied to policy, ownership, and review. |
| Employees say the policy | A table: situation -> what's covered -> limit -> what you need (receipt, approval) - plus where to ask questions. | Keeps spend tied to policy, ownership, and review. |
Per-category limits - hard caps, guidelines, or city-indexed allowances?
Hybrid: hard caps where abuse concentrates (lodging nightly rates, meal limits), guidelines with required justification in between, and city-indexing (or GSA-rate referencing) for travel-heavy companies where one national number is wrong everywhere.
Principles-based ("spend it like it's yours") vs rules-based policy?
Principles produce better behavior in high-trust, senior teams and ambiguity everywhere else - "like it's yours" means different things to different wallets. The working pattern: a principles preamble that sets tone, rules for the few categories where variance hurts, and visible, consistent enforcement - which matters more than which philosophy you chose.
How do I embed policy into the expense tool?
Encode limits as submission-time validations, require receipts by threshold automatically, flag policy exceptions to the approver with the violation named, and block the few absolute prohibitions outright. Every rule caught at submission is an audit finding that never existed.
Employees say the policy is impossible to find and impossible to read - what does a one-page summary look like?
A table: situation -> what's covered -> limit -> what you need (receipt, approval) - plus where to ask questions. Link it from the expense tool itself; a policy that lives three clicks from the moment of need doesn't exist operationally.
What belongs in the gray-areas section?
The questions finance answers every month: alcohol (when, with whom), tipping norms, seat upgrades, spousal travel, home-office equipment, client gifts and their tax limits, mixing personal travel with business trips. Answering them in writing converts a recurring judgment call into a lookup.
How should policy handle remote employees without creating a benefits problem?
Define specific covered items with caps (equipment, internet contribution if you offer one), distinguish reimbursable business expenses from stipends - flat allowances without substantiation are generally taxable wages - and apply one standard for all remote staff rather than negotiating individually.
Our policy was written in 2018 and enforcement is selective - how do we relaunch with credibility?
Rewrite short, announce honestly what changed and why, grant amnesty for past practice, and start enforcement consistently from a stated date - including for leadership, visibly. Credibility comes from the first month of even-handed application, not from the relaunch memo.
Stampli perspective
Stampli's design principle is that policy works best as workflow: Expense Cards carry finance-defined guardrails - limits by cardholder, merchant category, or vendor - set before spend happens, and mobile receipt prompts enforce documentation at the moment of purchase. The policy document then describes what the system already enforces, which is the only kind of policy that stays credible.