Employee Expense Policy Template (UK)

What this template is for

This is a working structure for a UK small business expense policy, built for teams of two to fifteen people rather than large organisations with dedicated finance functions. It assumes you want something a new starter can read in five minutes and use immediately, not a document that needs a training session to understand.

Copy the clause headings below, fill in your own numbers and category list, and cut anything that doesn't apply to your business. A shorter accurate policy beats a longer one copied wholesale from somewhere else, because unused clauses just create confusion about whether they're actually in force.

As with any policy touching expenses, treat this as a starting draft to check against current HMRC guidance and, if you have one, your accountant — this is not tax advice and rules do change.

Clause 1: Scope and who it applies to

State plainly which roles the policy covers and which types of spend it includes — typically all company card spend and all reimbursed personal spend, but excluding payroll, pension contributions, and any spend already covered by a separate contract (like a company car scheme, if you have one).

If you have contractors or freelancers who also incur costs on your behalf, decide explicitly whether this policy applies to them or whether their arrangement is covered instead by their contract terms, and say so — leaving it ambiguous is where disputes tend to start.

• Applies to: all employees and [named contractor categories, if any].
• Covers: company card transactions and reimbursed personal expenditure.
• Excludes: payroll, benefits already contracted separately, and anything pre-approved under a separate written agreement.

Clause 2: Categories of allowable spend

List the categories you expect to see — travel, subsistence while travelling, client entertainment, small equipment and software, training — and for each one give a one-line description of what's in and out. This is more useful than a blanket statement like 'reasonable business expenses' because 'reasonable' means something different to everyone until you've written examples down.

For any category you want to actively discourage or cap, such as client entertainment, state the cap or the rule directly in this clause rather than leaving it to be inferred from the approval thresholds elsewhere.

1. Travel — train, bus, taxi where reasonable, and mileage for own-vehicle business journeys.
2. Subsistence — meals while travelling for work on a full day away from the usual workplace.
3. Client entertainment — capped per head, pre-approval required above the cap.
4. Equipment and software — small purchases within the no-approval band, larger ones need sign-off.
5. Training and professional development — pre-approval always required.

Clause 3: Approval thresholds

Set out your bands here — no-approval, approval-required, founder-only — using the method described in our companion guide on creating a team spending policy: look at recent transaction values, find where routine spend sits, and set the no-approval ceiling just above it. State clearly whether approval must happen before the purchase or can follow within a set number of days.

Be explicit about what happens to a claim that exceeds the relevant band without prior approval: most small businesses choose to still pay it once, with a direct conversation about the process, rather than refusing outright and damaging trust over a first-time process error — but say in the policy which approach you're taking, so it isn't decided ad hoc each time.

Clause 4: Evidence and submission requirements

Require a receipt or invoice for every claim above a low de minimis amount, a one-sentence business purpose, and the date and category. State where evidence should be submitted — attached directly to the transaction in your banking or expense tool is strongly preferable to emailed photos, which get lost.

Set a submission deadline, such as within the same month or within thirty days, and say what happens to late claims. A firm but human rule — late claims are still considered but flagged, repeated lateness gets a direct conversation — tends to work better in a small team than an automatic refusal, which can feel disproportionate for a first offence.

• Receipt or invoice required above [small de minimis amount].
• One-sentence business purpose on every claim, no exceptions.
• Submit within [30] days of the transaction date.
• Evidence attached directly to the transaction, not emailed separately.

Clause 5: Mileage and subsistence

For mileage, require a simple log of date, journey, purpose and miles, and state that reimbursement follows the rate set out in current HMRC guidance on business travel mileage for employees, checked at the time of claim rather than fixed in this document. This keeps the policy accurate even when rates change.

For subsistence, define what counts as a reasonable meal cost while travelling and refer to current HMRC guidance on expenses and benefits for the underlying tax treatment, particularly if you're considering a scale-rate approach rather than reimbursing actual receipted costs — that distinction has tax implications worth checking with an accountant before you commit to one method.

Clause 6: The approval and payment process

Describe the actual mechanics: how a claim is submitted, who reviews it, what tool is used, and the typical turnaround time for reimbursement once approved. Naming a specific turnaround — say, reimbursed within the next payroll run or within ten working days — removes a common source of quiet frustration in small teams where reimbursement timing is otherwise vague.

If you use a company card for some spend and reimbursement for the rest, say clearly which categories go through which route, since mixing the two without guidance leads to people defaulting to whichever is easiest for them rather than whichever is right for the purchase.

Clause 7: Leavers and disputed claims

State that all outstanding claims must be submitted before or on the employee's last working day, and that any company card or account access is removed on or before that date — not some time afterwards. This clause is frequently missing from small-business policies and is exactly the gap that causes problems when someone leaves on bad terms.

For disputed claims — where the approver questions whether a purchase was legitimate business spend — set out a simple two-step process: a direct conversation first, and if unresolved, a decision by the founder that is final and recorded in writing. Avoid leaving disputes to linger unresolved, since that erodes trust in the whole policy faster than almost anything else.

Remove card access and shared account logins on the leaver's last day, not the following week — this is a control gap that's easy to overlook in a small team where things move fast.

Putting it together and issuing it

Once the clauses are filled in, keep the whole document to one or two pages if at all possible — length is the enemy of a policy actually being read. Share it directly with each team member, talk through the thresholds and categories briefly in person or on a call, and store it somewhere permanently accessible rather than only sending it once by email.

Plan to revisit it after the first full quarter of real use. Real claims nearly always surface a category or edge case the draft didn't anticipate, and it's far better to patch the policy after three months than to leave a known gap unaddressed for a year.