How Bookkeepers Can Stop Chasing Receipts from Clients

If you bookkeep for more than a handful of clients, you already know: the single biggest non-billable cost in the practice is receipt chasing. The third email asking the contractor for the Home Depot receipts from March. The phone call to the realtor about that mysterious $487 charge from a parking garage. The Slack thread with the dentist that ends with a screenshot of his car's center console.

This is not a moral failing of clients. They are not bad at this on purpose. The work of remembering to send receipts is genuinely hard for someone whose attention is elsewhere — running a business, closing deals, fixing teeth. The pattern doesn't get fixed by harder reminders. It gets fixed by changing the geometry of where receipts go.

This piece is a playbook for setting up a receipt-capture workflow that survives without your monthly intervention. The goal is to do the work once, with the client, at the start of the engagement, and never have to chase a receipt again.

Why your clients aren't sending them

The default workflow most bookkeepers inherit looks something like this: "Send me your receipts at the end of the month." The client agrees. The month ends. Twenty-eight days later, you remind them. Three days after that, they send a partial batch. Two days after that, you ask for the rest. Eight days after that, they send the rest. You spend two more days categorizing.

The reason this doesn't work has nothing to do with the client's intentions. It's that the request batches the work. Asking someone to remember and physically gather a month of receipts at the end of the month is a 90-minute task on top of running their business. The brain rationally avoids 90-minute tasks. So they get pushed.

The workflow that works flips this: the client captures each receipt the moment it happens, in seconds, with zero categorization on their side, and never thinks about it again. The bookkeeper sees them appear in a shared inbox throughout the month. At month-end, you reconcile what's there. Nothing to chase, because nothing got batched.

The "their problem to set up once" model

The leverage point is the onboarding conversation. Spend 15 minutes the first week setting up the capture, and then the system runs itself. Here is the script that works for most clients:

1. You set them up with a dedicated email address and phone number. They save the phone number in their contacts as "Books" or similar. They forward email receipts to the email address by setting one Gmail rule (you provide the instructions).
2. For paper receipts at the register, they text a photo to the phone number. Two seconds, no app to open.
3. For the next month, that's all they do. You see everything appear in a shared inbox in near real time.
4. If they're using a tool that supports it, set up a home-screen camera shortcut on their phone so the in-person capture is one tap from the home screen.

That's the whole conversation. Total client time investment: 15 minutes upfront, then less than 10 seconds per receipt. No app to install. No login to remember. No batch to gather. The receipt-by-receipt cognitive load is so low that even resistant clients tend to adopt it.

Why this works when "use an app" doesn't

Receipt-capture apps have been around for a decade and most clients don't use them. Not because the apps are bad — they're often quite good — but because they require:

• Going to the app store, finding the right app among lookalikes.
• Creating an account with another username and password.
• Learning the interface (categories, books, projects, splits).
• Opening the app at the moment of capture, which is exactly when they're least likely to open an app.
• Logging in again whenever the session expires.

Every one of those steps is a hurdle that drops adoption. Most clients clear two and quit. Email and SMS clear zero hurdles because the client already has email and SMS open all day. The capture method has to live in the tools the client already uses, not in a new tool you're asking them to learn.

The shared-inbox model: you see what they see

The professional version of this is a shared workspace where you, as the bookkeeper, can see your client's receipts as they arrive, ask questions inline, and reconcile against bank statements. The client sees the same inbox — not a different system — so when you ask "what was this charge for?" they answer on the same receipt, not in a separate email thread that loses context.

Two patterns differentiate this from email-forwarding-to-a-folder:

• Per-receipt comment threads. Open a receipt, ask "client-billable?" or "business purpose?", the client replies inline, the answer lives with the receipt forever. No more cross-referencing email threads to substantiation notes at year-end.
• Standard follow-up questions by receipt type. Meals always need "who attended" and "business purpose." Travel needs "purpose" and "dates." Vehicle expenses need "miles" and "destination." A system that surfaces these by default catches the substantiation gaps the IRS will ask about — before they become substantiation gaps.

The combined effect is that year-end stops being a forensic exercise. Every receipt already has its category, its book, its substantiation note. The export becomes a one-click affair.

Bank reconciliation as the safety net

Even with perfect client discipline, charges slip through. The client uses a debit card on a quick supply run and forgets to text the receipt. A subscription renews quietly and there's no email confirmation. A travel charge gets routed to a personal credit card and then expensed later.

Monthly bank reconciliation catches these. You drop the client's statement (CSV or PDF) into the workspace, the system matches each transaction to the right receipt, and you see immediately what doesn't match. "Three charges with no receipt — can you check these?" is a much shorter and more bounded ask than "send me your receipts for the month."

The reconciliation also catches the things the client wouldn't think to mention: fraudulent charges, duplicates, recurring subscriptions they forgot about. These are the conversations clients value — the ones where you're surfacing problems they didn't know they had — not the conversations where you're nagging them for paperwork.

Pricing the practice differently

Bookkeepers who run on a chase-and-categorize model price by the hour because they have no way to make the work shorter. Bookkeepers who run on a capture-as-it-happens model bill flat fees because the work is genuinely the same predictable size each month. Flat fees mean higher effective hourly rate, more clients per FTE, and a calmer practice.

The shift from hourly to flat isn't just a billing change. It's a service-design change. You're no longer selling "I'll wade through your receipts." You're selling "Your books are continuously clean, and we close every month within five business days." That's a fundamentally different value proposition, and it commands a different price.

A practice that does $80K/year on 25 clients at chase-and-categorize hourly billing can plausibly do $120K/year on 30 clients at flat-fee monthly billing, with less stress, because the capture work is done by the clients themselves. The math is straightforward once the workflow is in place.

The clients this doesn't work for (and what to do)

Some clients won't text a photo. Some won't set up a Gmail rule. Some are deeply skeptical of "another app" even when it isn't an app. For these clients, three options:

• Be the capture for them. Get statement-level data through bank reconciliation and accept that you'll have undocumented expenses for small charges. Your fee reflects this. Not ideal, but workable for clients who pay you well enough.
• Use a family member as the conduit. The spouse who runs the office often does this happily. Set them up instead of the principal; receipts flow through them.
• Fire the client. Half-joking. If a client costs more in non-billable chasing than they generate in revenue, that client is a loss leader. Either raise the fee to cover it, or let them find someone else. Practices that don't do this hit a stress ceiling that limits growth.

The bigger picture for your practice

Bookkeeping as a profession is shifting. AI handles categorization. Bank feeds reduce data entry. The historical bookkeeping job — sorting paper, keying in numbers, reconciling by hand — is becoming a smaller fraction of the value. The work that grows in value is the advisory work: spotting trends, asking the right questions, preventing problems before they become disasters.

Advisory work requires clean, current data. Clean current data requires capture-at-source. Capture-at-source requires a workflow your clients actually adopt. So the receipt-capture workflow isn't just an operational improvement — it's the foundation of moving your practice up the value chain.

The bookkeeper who chases receipts is a clerk. The bookkeeper who builds the system so receipts don't need chasing is an advisor. The first one bills by the hour. The second one bills by the relationship. Same person, two very different careers.