How to Create a Team Spending Policy

Why the policy comes before the product

It is tempting to solve team spending by opening an account and ordering a card for everyone, because that feels like progress. The trouble is that a card without rules just moves the decision about what is acceptable spending from 'before the purchase' to 'after the statement arrives', which is the worst possible time to have that conversation. A policy fixes the sequence: agree the rules, then choose the tool that enforces them.

Founders who skip this step tend to discover the gap only when something goes wrong — a large purchase nobody signed off, a subscription nobody remembers approving, or a disagreement about whether a client dinner was reasonable. None of these are card problems. They are policy problems that a card cannot fix on its own.

This guide sets out how to build that policy from scratch for a team of two to ten people, with wording you can adapt directly, before you look at any specific expense card or business account.

What a spending policy actually needs to cover

A working policy answers five questions clearly enough that nobody has to ask you: who can spend, on what, up to how much, with what evidence, and what happens if they get it wrong. Everything else is detail. Resist the urge to write a long document that tries to anticipate every category of purchase — a short policy that people actually read beats a long one that sits in a drive nobody opens.

Structure it as short numbered clauses rather than prose. Each clause should be testable: someone should be able to read it and know immediately whether a specific purchase complies, without needing to interpret intent.

1. Scope — which roles and which types of spend the policy covers (e.g. all company card and reimbursed spend, excluding payroll and rent).
2. Thresholds — the value bands and what approval, if any, applies at each band.
3. Approval route — who approves, how (message, form, sign-off in the accounting tool), and how quickly.
4. Evidence — what has to be kept for each band, and where it is stored.
5. Prohibited spend — a short, explicit list of what the company will never reimburse or authorise.
6. Leaver process — what happens to access and outstanding claims when someone leaves.
7. Review point — when the policy itself gets revisited.

Setting approval thresholds in bands

Most small teams do better with three bands than with a single limit. A no-approval band covers routine, low-value purchases — think stationery, small software subscriptions, minor site materials — where requiring sign-off would just create friction without reducing risk. An approval band covers everything above that up to a level the founder is comfortable delegating, requiring a named approver's sign-off before or shortly after the purchase. A founder-only band covers anything larger, unusual, or recurring in a way that changes the cost base, such as a new annual contract.

Where you set the numbers depends on your cash position and your risk tolerance, not on what other businesses do. A useful starting method is to look at your last three months of small purchases, find the value below which 90% of transactions fall, and set that as your no-approval ceiling. Set the founder-only band at a level where getting it wrong would meaningfully affect the month's cash position.

Revisit the bands as the business grows. A no-approval limit that made sense with one employee often needs tightening, not loosening, once three or four people can spend independently, simply because the combined exposure is larger even if no individual purchase is.

• No-approval band: routine, low-value, pre-agreed categories only.
• Approval band: needs a named sign-off, ideally before the purchase or within 24 hours after.
• Founder-only band: new contracts, anything recurring, anything outside agreed categories.
• Review bands whenever headcount or card count changes.

Evidence and record-keeping without becoming an admin burden

Evidence requirements should scale with value. For small purchases, a photo of the receipt attached to the transaction in whatever system you use is enough — do not ask for anything more, or people will stop bothering and you'll end up with worse records than if you'd asked for less. For larger purchases, ask for the underlying invoice, the business purpose in a sentence, and if relevant a purchase order or approval reference.

Keep evidence attached to the transaction rather than filed separately, because separated evidence has a habit of never being matched back up. Most business banking and card tools now let you attach a photo or file directly to a transaction line, which is worth using even if your bookkeeping is otherwise simple.

VAT treatment is a bookkeeping and tax matter, not something this policy should try to resolve on the page — the practical instruction for staff is simply 'always get a proper VAT receipt, not just a card slip', and leave the reclaim mechanics to whoever does your books or your accountant, checked against current guidance on GOV.UK.

Mileage, subsistence and other recurring categories

Mileage and subsistence are the two categories that generate the most repeated questions, and the policy's job is not to quote rates but to point people to the current, correct source and to state your process. For mileage, direct staff to keep a simple log — date, journey, purpose, miles — and confirm you pay at the rate set out in current HMRC guidance on mileage for business travel, rather than writing a number into the policy that will go stale.

For subsistence — meals while travelling for work — set a simple rule about what counts as reasonable (for example, a modest meal when away from the usual workplace for a full day) and again point to current HMRC guidance on expenses and benefits rather than fixing a cash figure that may not track allowable rates over time.

The discipline here is the same in both cases: write the process, not the number, so the policy does not need rewriting every time a rate changes.

Fraud controls that are proportionate to a small team

Fraud controls for a two- or three-person team are not about mistrust; they are about not putting any one person in a position where a mistake or a bad day is invisible until the damage is done. The simplest control is separation of duties: the person who approves a purchase should not also be the only person who can reconcile it and mark it as resolved, even if that means the founder occasionally does the second check personally.

A second useful control is a standing rule that no single transaction above the founder-only threshold gets waved through verbally — it has to leave a written trace, even a one-line message, before the money moves. This is not bureaucracy; it is the difference between a decision you can reconstruct later and one you have to guess at.

Finally, review statements monthly rather than trusting that receipts submitted equal receipts accurate. A short monthly check against the bank or card statement catches the gap between what was claimed and what was actually spent, which is where most small-business expense problems are eventually found.

None of this assumes anyone is dishonest. It assumes people are busy, and busy people make errors that are much cheaper to catch in month one than in month twelve.

The monthly reconciliation routine

Pick a fixed day each month — the same day every time — to reconcile team spending. The routine itself can be short: pull the statement, match each line to a stored receipt or evidence entry, flag anything without evidence, and follow up directly with whoever made the purchase rather than letting it roll into next month unresolved.

Keep a simple running note of anything unusual, even if it's resolved quickly, so that patterns are visible over time — a recurring subscription nobody remembers signing up to, or a category of spend that's crept up, is much easier to spot across six months of notes than from memory.

This routine is what actually keeps a policy alive. A document without a monthly habit behind it decays within a couple of quarters; a short habit with a rough document behind it works for years.

Rolling the policy out without sounding bureaucratic

For a team of two or three, roll-out does not need a meeting agenda or a signed acknowledgement form. A short, direct conversation — here's what you can spend without asking, here's what needs a quick message first, here's what's off-limits, here's what happens if you're not sure — covers it, backed by the one-page document as a reference rather than a rulebook to be memorised.

Frame it as making their life easier, because it genuinely does: a clear no-approval band means people stop having to ask permission for a £4 purchase, and a clear approval route means they're never left guessing whether something needs sign-off. Most resistance to spending policies comes from vague, inconsistently applied rules, not from clear ones.

Put the policy somewhere everyone can find it without asking — pinned in the team chat, in the same folder as other basic company documents — and mention it again briefly whenever someone new joins or a threshold changes.

When to bring in a card or account, and how to choose

Once the policy exists, choosing a mechanism becomes a much narrower question: do you need pre-loaded control per employee, occasional reimbursement, or short-term credit, and does your business structure even allow the option you're considering. A business account with debit expense cards, such as Tide, gives each person a card tied to the business's own funds with no borrowing involved, which suits teams that want spending visibility without extending credit.

A business credit card, such as one from Capital on Tap, adds short-term credit and individual employee cards but is only available to limited companies and usually requires a personal guarantee from a director, which is a real commitment worth weighing carefully rather than glossing over. Neither option removes the need for the policy you've just written — they only make it easier or harder to enforce.

Check current features, fees and eligibility directly on the provider's site before deciding, since terms change. This site may earn a payment if you go on to use either provider, which is disclosed here for transparency and should not influence which one, if either, suits your policy.