Updated July 2026
How to get clients to actually send their receipts
Every bookkeeper has this client. Perfectly nice, pays on time, and every single month the receipts turn up late, blurry, or not at all. The instinct is to blame them. The fix is almost always on your side of the fence, because clients don't sabotage a system, they just quietly fail the ones that ask too much.
First, audit the friction
Count the steps between "client is holding a receipt" and "receipt is with you." A portal login is three steps before the first useful one: find the email with the password, reset the password, find the upload button. An app is worse: install, sign in, allow notifications. Every step loses a slice of your clients, and the ones you lose are exactly the ones who were marginal to begin with.
The empirical ranking, from what practitioners report over and over: a link that opens straight into an upload box beats email attachments, which beat a shared folder, which beats any portal, which beats any app. If your current system requires a password, that password is where your receipts go to die.
Give them one tiny job
The winning instruction is one sentence: "When you get a receipt, send it here." Not "log in monthly and reconcile your uploads." Not "categorize it as travel or meals." One action, doable in the checkout line, from a phone, in under ten seconds. Sorting, renaming, and filing are your problem, or your software's. The moment they become the client's problem, the client stops.
Reminders get opened when they come from you
Automated nudges from a noreply@ address get ignored; the same words sent under your own name get answered. Clients respond to the human they pay, not to the robot the human bought. Whatever tooling you use, the reminder should carry your name, point at the specific gap ("the 3 Amazon charges from March 12-18"), and give the cutoff. Vague asks ("please send any outstanding receipts") get vague results.
We keep a set of ready-to-steal polite, firm and final reminder templates. The escalation matters more than the wording does.
Use a cutoff, and let consequences do the chasing
An escalation ladder that works without drama:
- Day 1 of the month: one short ask listing exactly what's missing, with the upload link.
- Day 7: the firm version. Same list, plus the cutoff date and what happens after it.
- Cutoff day: the final one. "Anything that arrives after today books to Ask My Accountant or owner's draw, and we true it up next quarter."
The third email is the one that changes behaviour, because it moves the cost of a missing receipt off your evenings and onto their tax position, which is where it belongs. You'll send it twice per client, maybe three times, ever.
What doesn't work
Longer emails. Portals with more features. A monthly Zoom walkthrough of the portal. Threatening to fire the client, which you won't do and they know it. And doing nothing, which is the most expensive of all. Bookkeepers who actually track it put the chase at hours per client, every month-end.
If you'd rather not run the ladder by hand
The ladder above is the whole workflow Sorted Receipts runs so you don't have to remember to. One link per client with no password in the way, arrivals filed into the right month by themselves, a flag when a monthly vendor goes quiet, and the polite-then-firm emails going out in your name up to your cutoff. $8/mo flat. Worth saying though: the ladder works perfectly well with plain email and a shared folder. The principles are free.
Questions people search
How do I ask a client for receipts without nagging?
Name the specific gap, make delivery one click, set a cutoff and say what happens at it. Specific, easy and bounded reads as professional. "Just checking in again" reads as nagging.
Should I make clients use a receipt app?
Only if they already wanted one. For everyone else an app is friction, and friction is why you're chasing. A link that opens straight into an upload box has the highest compliance of anything practitioners report.
What do I do about receipts that never arrive?
Book it to a holding account per your cutoff policy, tell the client which transactions are affected, and move on. A predictable consequence beats a heroic chase, and it trains next month.