How to Stop Chasing Employees for Receipts

Why you're chasing receipts in the first place

If you find yourself sending the same message every month — 'can you send me the receipt for that £40 you spent on Tuesday' — the problem usually isn't the person you're chasing. It's that your process asks them to remember and produce evidence at a point in time (usually your bookkeeping day) that has nothing to do with when the purchase actually happened. Memory of a specific receipt fades within days, and the physical or digital copy is easy to lose once it's separated from the moment of purchase.

The fix is not a firmer message or a stricter deadline on its own — those just make the chase feel worse for both sides without changing when evidence gets captured. The fix is moving the capture point back to the purchase itself, so there's nothing left to chase later.

This matters because receipt chasing has a cost beyond your own time: it signals that the expense process is loose, which tends to make people less careful about what they buy and how they describe it, not more.

Capture at the point of purchase, not at reconciliation

The single highest-leverage change most small teams can make is requiring the receipt photo to be attached to the transaction immediately, using whatever banking or card app is already in the purchaser's pocket. Most current UK business banking apps, including debit expense card products like Tide's, let a cardholder snap a photo of the receipt straight onto the transaction line seconds after paying.

This works because it turns receipt capture into a two-second extension of the purchase itself, rather than a separate admin task competing with everything else on someone's to-do list later in the month. It also means the evidence is already attached to the right transaction, so nobody has to match receipts to statement lines afterwards.

If your current setup doesn't support this — for example, you're using shared reimbursement with no card at all — consider whether that's actually the right mechanism for your team, since reimbursement inherently separates the purchase from the record-keeping in a way that makes chasing more likely.

Set a short, fixed submission window

An open-ended policy — submit your receipts whenever — guarantees a backlog, because there's no natural deadline pulling people to act. Replace it with a short, fixed window: receipts attached within 48 hours of purchase, or claims submitted by the last day of the month, whichever suits your rhythm. Shorter windows tend to work better than longer ones, because a 48-hour deadline still overlaps with the purchase being fresh in memory, while a 30-day deadline does not.

State the window clearly in your policy and repeat it verbally when someone joins the team — a rule that exists only in a document nobody rereads has the same effect as no rule at all.

Build one predictable monthly reconciliation day

Pick a fixed date each month to reconcile the team's spending against submitted evidence, and protect that time the same way you'd protect a client meeting. On that day, pull the statement, check every line has attached evidence, and message anyone with a gap immediately rather than letting it roll forward.

The predictability matters more than the exact date chosen. When people know reconciliation happens on, say, the 3rd of every month, gaps get flagged quickly while the purchase is still recent enough for a fast, low-friction answer, rather than three months later when nobody remembers the context.

1. Pull the statement or export from your banking/expense tool.
2. Match every line to attached evidence.
3. Flag gaps and message the purchaser directly, same day.
4. Note any recurring pattern (same person, same category) for a quick conversation.
5. File the reconciled month and move on — don't let it roll into next month unresolved.

Why chasing feels personal even when it isn't

A repeated message asking for a receipt can start to feel like an accusation, even when you don't mean it that way, and that discomfort is often why founders put off chasing until several transactions have piled up — which only makes the eventual conversation feel bigger. Keeping the first follow-up quick, specific and low-drama ('just need the receipt for Tuesday's £40 train ticket, no rush but by Friday please') keeps it feeling like routine admin rather than scrutiny.

If the same person is consistently the one you're chasing, that's worth a short direct conversation outside the transaction itself — not to assign blame, but to understand whether the process genuinely doesn't fit how they work, and to fix that rather than repeating the same reminder every month indefinitely.

A pattern of missing receipts from one person is a process signal before it's a conduct issue. Ask what's making it hard for them, first.

When the mechanism itself is the problem

If you're reimbursing employees who pay from their own accounts, you're relying on them to keep and later produce evidence for a purchase that, from their point of view, is already settled and paid for. That inherent lag is a structural reason reimbursement generates more chasing than a company card does, regardless of how good your policy wording is.

Switching some or all spend to a business debit expense card, where each purchase is immediately visible on the business account and evidence can be attached at the same moment, removes a lot of the chasing at its source rather than managing it after the fact. This is a mechanism decision, though, and should follow from your policy and cash position rather than being adopted purely to solve chasing — see our comparison of expense cards versus reimbursement for the full trade-offs.

Escalation without drama

For a first missed receipt, a friendly direct message is enough — treat it as completely normal, because it is. If the same person misses two or three in a row, have a short conversation about what's making the current process difficult for them specifically, since the answer is often something fixable, like the tool being awkward to use on their phone or the deadline clashing with a busy part of their week.

Reserve a firmer written reminder, referencing the policy directly, for a genuinely repeated pattern after that conversation has already happened once. Jumping straight to a formal tone over a single missed receipt tends to damage trust in the relationship far more than the missing receipt itself ever would.

What good looks like after three months

If the changes above are working, your monthly reconciliation day should take a fraction of the time it used to, because most transactions already have evidence attached by the time you look. The messages you do send should be occasional and specific rather than a recurring generic chase sent to the whole team.

If you're still chasing the same people for the same reasons after three months of a fixed window and point-of-purchase capture, treat that as a signal to revisit the mechanism itself, not just to repeat the reminder with more urgency.