Updated July 2026
How to get clients to actually send their receipts
Every bookkeeper has the client: perfectly nice, pays on time, and every month their receipts arrive late, blurry, or not at all. The instinct is to blame the client. The fix is almost always on your side of the fence — because clients don't fail systems maliciously, they fail systems 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 percentage of clients, and the clients 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 you make them 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, reference the specific gap ("the 3 Amazon charges from March 12–18"), and name the cutoff. Vague asks ("please send any outstanding receipts") produce vague results.
We keep a set of ready-to-steal polite, firm, and final reminder templates — the escalation matters more than the wording.
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 version — "anything that arrives after today books to Ask My Accountant / owner's draw and we true it up next quarter."
The third email is the one that changes behavior, because it moves the cost of missing receipts from your evenings onto their tax position — where it belongs. You'll send it twice, maybe three times per client, ever.
What doesn't work
Longer emails. Portals with more features. Monthly Zoom walkthroughs of the portal. Threatening to fire the client (you won't, and they know). And doing nothing, which quietly costs the most — practitioners who track it put the chase at hours per client per month at month-end.
If you'd rather not run the ladder by hand
This workflow is exactly what Sorted Receipts automates: each client gets one private upload link (no login, no app), arrivals are auto-sorted by month, vendor, and type, recurring vendors with a gap get flagged, and the polite-to-firm reminders go out under your name on your cutoff. Flat from $29/mo. But the ladder above works with plain email and a shared folder too — the principles are free.
Questions people search
How do I ask a client for receipts without nagging?
Name the specific gap, give one-click delivery, and set a cutoff with a stated consequence. Specific + easy + 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 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.