How to stop chasing clients for receipts (templates included)
Chasing clients for receipts is the month-end ritual every bookkeeping firm knows: the bank feed is reconciled except for the charges nobody can prove, and someone writes another email that begins "just following up".
The chasing fails for a structural reason, not a behavioural one. You are asking the client to do a search, remember what the charge was, find which inbox got the receipt, download the PDF, send it to the right place. Every step is a place to stop. The fix is not a firmer reminder. It is removing the search from the request.
This post gives you the workflow that removes it, and the exact emails to send when you still have to ask.
Why chasing fails
A document request looks like a message but lands like homework. "Can you send the receipt for the £46.20 charge on the 12th?" requires the client to figure out what the charge was, guess which mailbox received the confirmation, search for it, and forward it. Six steps, three of them judgment calls.
That is why polite reminders produce nothing. The client is not refusing; they are deferring a task with unclear edges. Multiply that by every unexplained line and you get the monthly chase cycle.
The one rule that fixes most of it
Give every client exactly one place receipts go, and put it in writing before you need it. Not email-or-text-or-upload. One channel. The moment a client has to choose where a receipt goes, some of them choose "later".
The best channel is the one that requires no action at all. In order of least friction:
- Nothing at all. The receipts are already in their inbox. Most receipts arrive by email. If the client's inbox is connected to your workflow, the receipts collect themselves and chasing becomes the exception, not the routine. (This is what Receipt Pair does: the client connects Gmail or any IMAP inbox once, read-only, and receipts pair to bank charges automatically.)
- A dedicated forwarding address. One address, theirs, memorable, that accepts any forwarded receipt. No login, no app, no portal. The client forwards; matching happens on your side.
- A camera. For paper receipts, a phone photo beats a scanner beats a drawer full of thermal paper. The photo should land in the same place as everything else.
What does not work: a portal the client visits twice a year, a shared folder with unclear naming, or "just email them to me" across three different staff inboxes.
Work from the missing list, not from memory
Generic requests get generic responses. "Please send your receipts" asks the client to decide what counts. An itemized list does the deciding for them: date, merchant, amount, one line each.
Build the list from the bank feed, every charge with no receipt attached, and send that. A client who can see "12 Sep · Adobe · £46.20" can search their inbox for one merchant instead of reconstructing a month. The list is also your paper trail: what was asked, when, and what is still open.
The chase emails, at three levels
Steal these. They work because each one is shorter than the task it requests, names specific items, and states a consequence that is real.
Level 1: the monthly list (send on a fixed date, every month):
Subject: {Firm}: {N} receipts needed for {Month}
Hi {Name},
Month-end is coming up and these charges are still missing receipts:
{date · merchant · amount, one per line}
Easiest way: forward the receipt emails to {inbound address}, or reply to this email with the PDFs. If a charge genuinely has no receipt, just reply "no receipt" next to it and I'll note it.
Deadline: {date}. Anything in by then makes this month's close.
Thanks,
{Accountant}
Level 2: the reminder (72 hours later, only to non-responders):
Subject: Still open: {N} receipts for {Month}
Hi {Name},
Still missing {N} receipts, listed below again. If the receipts are in your inbox, searching the merchant name usually finds them in under a minute (Gmail's search operators help here).
{remaining lines}
If any of these had no receipt (cash, or a portal-only vendor), tell me which and I'll mark them closed.
{Accountant}
Level 3: the close-out (after the deadline):
Subject: Closing {Month}, last call on {N} receipts
Hi {Name},
I'm closing {Month} on {date}. These {N} charges will go in the books without receipts unless they arrive by then:
{remaining lines}
No receipt means the expense may not hold up in an audit and the VAT may not be reclaimable. I'd rather have the paper than the risk. Forward them to {inbound address} or reply here.
{Accountant}
Three things make these work where "just bumping this" fails: the list is specific, the reply path is one step, and the consequence is stated plainly instead of implied.
When chasing is still needed
Some receipts will never arrive by email: cash purchases, vendors who only publish invoices inside their own portal, the paper receipt from the till. For those, the templates above still apply, but the long-term fix is shrinking the chase set, not perfecting the chase. Every receipt that arrives automatically is a line that never needs a reminder.
The measure to watch is the size of the missing list, not the number of emails sent. When the list is short, the chasing is a five-minute task. When the list is the whole month's spend, no template will save you.
What this looks like with a system
Receipt Pair is built around exactly this loop. The bank feed supplies the list, every charge, matched or not. The client's inbox supplies the receipts, connected once, searched continuously, including history. Whatever is left unmatched is the missing report: one line per charge, exportable, chaseable. The templates above are built into the workflow as a copy-ready email per missing item.
Chasing stops being a monthly negotiation and becomes a short list with a deadline. Which is what it should have been all along.