The portal problem nobody wants to say out loud
Every practice that has rolled out a client portal has had the same experience. The portal gets built, the client gets an onboarding email with login instructions, and within a few months, half the client base has forgotten their password, stopped checking the portal, and gone back to whatever they were doing before, usually emailing receipts directly to their bookkeeper or letting them pile up until the accountant asks.
This is not a reflection on the client's diligence. It is a predictable outcome of asking someone to build a new habit around a tool they only touch a few times a month. A client submitting receipts is not thinking about their accounting workflow. They are thinking about getting back to running their business, and anything that adds a step gets skipped or deferred.
Why email-in works when portals do not
Email-in receipt submission sidesteps the adoption problem entirely, because it asks the client to do something they already do dozens of times a day: send an email. There is no new login to remember, no app to download, and no portal interface to learn. A client forwards a receipt to a dedicated address the moment it lands in their inbox, or photographs a paper receipt and emails it there and then, using the exact same motion they would use to forward anything else.
The practical effect is that receipt submission stops competing with everything else on a client's to-do list. It becomes something that happens in the moment, rather than a task that gets batched up and forgotten until the accountant chases it, the same low-friction principle behind paperless receipt management done well.
How email-in receipt capture actually works
The mechanics are simple by design, which is precisely the point:
- The client is given a dedicated email address, unique to their practice relationship, either to forward supplier invoices to directly or to email photos of paper receipts.
- The receipt arrives and is automatically extracted. Rather than sitting in an inbox as an attachment waiting for someone to open it, the system reads the document and pulls out supplier, date, amount, and VAT automatically, the kind of accuracy worth putting on any checklist for choosing a receipt scanning tool.
- The extracted data is checked and coded. Confident extractions post straight through; anything the system is uncertain about is flagged for a quick human check rather than guessed at.
- The receipt and its data become available in the practice's workflow, ready for reconciliation, without anyone having manually typed a single figure, and available as evidence the moment a digital receipts audit is run across the client base.
From the client's side, steps two through four are invisible. All they experience is forwarding an email, the same as they would to a colleague.
Why this reduces receipt chasing more than any reminder system
A huge share of the admin burden in a bookkeeping practice is not the processing of receipts once they arrive, it is chasing clients to send them in the first place. Reminder emails, phone calls, and end-of-month scrambles are all symptoms of a submission process with too much friction for the client to bother with consistently.
Email-in does not eliminate the need for any reminders, but it removes the biggest reason clients delay: not knowing where to send something or having to stop and log into a system they rarely use, the same friction point that makes MTD-ready client receipt habits so hard to establish through a portal alone. When the answer to "where does this receipt go" is simply "forward it, like you would anything else", clients submit closer to the point of purchase, rather than saving up a backlog to deal with all at once.
Setting this up without disrupting how clients already work
Rolling out email-in submission works best framed as a small, specific change rather than a new system to learn. Tell clients exactly one thing: forward your receipts and invoices to this address instead of wherever you have been sending them, or instead of holding onto them until your next meeting. Nothing else about their routine needs to change.
For clients already in the habit of emailing receipts directly to their bookkeeper's personal inbox, this is a genuinely trivial switch, just a different address to send to. For clients used to a shoebox or a folder of paper receipts, it is a slightly bigger habit change, but still far smaller than learning a portal, since photographing and emailing a receipt is something almost every client already knows how to do from using their phone for anything else, the same low-friction entry point covered in onboarding a paper-based client to digital receipts.
Where Receiptflow fits
Receiptflow's email-in feature is built around this exact principle: meet the client where they already are, rather than asking them to come to you. Receipts forwarded or photographed and emailed are extracted and coded automatically, with no client-side app, login, or training required. For practices that have tried a portal and watched adoption fade after the first few months, email-in tends to be the version of digital receipt capture that clients actually keep using, because it never asked them to change how they work in the first place. It's also worth folding into any receipt management SLA you set with clients, and it fits naturally alongside managing employee expense receipts for clients running a small team.
Try Receiptflow's email-in feature and see the adoption difference for yourself.
