The One-Page Expense Policy Template for Small Teams (Copy, Paste, Done)

Most expense policy templates are written for a 500-person finance department. They run twelve pages, cover international per diems and corporate card tiers you'll never use, and sit untouched in a shared drive because nobody on a team of eight has time to read them. If you've been putting off writing an expense policy because every template feels like overkill, this one is for you.

A small business expense policy doesn't need to be long — it needs to be clear. The whole point is that your team knows what they can spend without asking, and you stop answering the same "can I expense this?" question every week. Below is a one-page expense policy template you can copy, fill in four numbers, and share today. No legal review, no finance team required.

Why a Small Team Needs a Policy at All

When it's just you and a few people, spending runs on vibes. Someone buys a tool, mentions it in Slack, and you say "sure." That works right up until it doesn't — until two people buy the same software, a client dinner comes in at triple what you expected, or someone waits three weeks to find out whether a $200 purchase will be reimbursed.

A policy fixes all of that with one document. It sets expectations before money is spent, so you're not making judgment calls after the fact. It also protects your team: when the rules are written down, nobody has to guess whether they'll get paid back, and nobody feels singled out when a purchase gets questioned. The rules apply to everyone equally because they're on paper.

And it saves you time. Every clear line in a policy is a question you never have to answer again.

The 6 Things Every Small-Team Policy Needs

Enterprise templates list a dozen components. For a team under 50, you need six. Skip the rest.

1. Scope — who the policy applies to and what counts as a business expense.
2. Categories and limits — what people can spend, and how much, without asking.
3. The approval line — the dollar amount above which a purchase needs a yes.
4. Documentation — what proof to keep (hint: a receipt photo, not the paper).
5. How to submit — the one way expenses get logged, so nothing slips through.
6. Reimbursement timing — when people get paid back, so they stop wondering.

That's the entire policy. Six sections, one page. Everything else enterprise templates add is noise for a team your size.

The Copy-Paste Expense Policy Template

Here it is. Replace the bracketed numbers with your own and you're done. Keep it in a shared doc your team can find in two clicks.

---

[Company Name] Expense Policy Last updated: [date]

1. Scope. This policy applies to everyone at [Company]. A business expense is any cost incurred directly to do your job or serve a client. When in doubt, ask before you buy.

2. What you can spend without asking (monthly, per person):

3. Approval line. Anything over $[300] needs one approval from [manager/you] before you buy. Under that, you're clear — just log it.

4. Documentation. Snap a photo of the receipt at the time of purchase. For meals, note who was there and why. No receipt needed under $[25] (but a card statement line helps).

5. How to submit. Log every expense in [X Pensi / your tool] within [7] days. One place, every time. If it's not logged, it didn't happen.

6. Reimbursement. Approved out-of-pocket expenses are paid back on the [next payroll run / within 10 business days].

Questions? Ask [name] before spending, not after.

---

That's a complete, usable expense policy. Fill in the brackets and it fits any team of 2 to 50.

The Four Numbers That Make or Break It

The template only works if the numbers fit your team. Set them too low and people route around the policy; set them too high and you lose the control. Here's how to pick them:

• Software limit: Look at what your team already spends per person on tools in a normal month, then round up slightly. If designers run ~$60 in subscriptions, set it at $75 so renewals are self-serve.
• Meal limit: A number that covers a normal working lunch or modest client dinner without a conversation. $40/meal fits most teams; coastal cities trend higher.
• Approval line: The threshold where you genuinely want a heads-up. For most small teams that's $300–$500. Below it, trust your people; above it, you want to know.
• Submission window: Short enough that receipts don't vanish, long enough to be realistic. Seven days is the sweet spot.

X Pensi lets you enforce these numbers automatically instead of policing them by hand. Set your category limits and approval line once, and every receipt your team snaps gets checked against the policy and rolled up against your budget in real time — so the policy isn't a document people forget, it's just how spending works. No chasing, no month-end surprises, no "wait, who approved this?"

Rolling It Out Without a Meeting

You don't need a company-wide sit-down. Post the policy once in your shared doc, drop a two-line summary in your team channel ("here's what you can spend without asking, here's the one approval rule"), and point to it when questions come up. Review it once a quarter and adjust the four numbers if they're consistently too tight or too loose.

The policy that gets followed is the one people can actually read. Keep it to a page, keep the language plain, and trust your team inside clear lines.

Put Your Policy on Autopilot

A written expense policy is step one. The real win is when the policy enforces itself — when limits, approvals, and receipt tracking happen automatically instead of landing on your plate. Stop losing money to messy expense tracking and manual approvals. Try X Pensi free — set your policy once, snap receipts from your phone, and watch spending stay inside the lines on its own.

---

Read next: How to Control Team Spending Without Micromanaging and The 7 Expense Categories Every Small Team Should Track.