Clients are already sending you receipts on WhatsApp
If you work with UK small businesses, this has probably already happened to you: a client photographs a fuel receipt at the petrol station and sends it straight to your WhatsApp, because that is the app they already have open. No portal, no login, no thinking about it. It is the fastest route from their pocket to your inbox, and clients default to it whether or not it is part of your official process.
This is not a fringe behaviour. WhatsApp is the everyday messaging app for a large share of UK small business owners and sole traders, and it is often the same channel they use to text you about a late payment or ask when their VAT return is due. For a client who barely tolerates their accounting software, WhatsApp feels effortless in a way a client portal never will.
Why this creates a real problem for your practice
The convenience for the client comes at a cost for you. A photo dropped into a WhatsApp thread has no structure. It arrives without a client reference, without a category, and without any link to your practice's document management system. If three clients all send receipts to the same personal number over the same week, someone in your team has to manually sort, save, and file every single one before it is any use to the bookkeeping process.
There are also practical limits that matter more the bigger your client base gets:
- No audit trail. WhatsApp threads are not part of your practice's record-keeping system, which creates a gap for MTD digital record requirements, particularly for the non-standard formats an informal confirmation like this can end up being treated as.
- No searchability at scale. Finding a specific receipt from three months ago in a personal chat thread is painful once you have more than a handful of clients doing this.
- Personal number dependency. If receipts are landing on an individual team member's phone, that becomes a single point of failure the moment they are on leave or leave the practice.
- No extraction. Someone still has to manually read the amount, date, and VAT off every image and key it into the ledger.
None of this means WhatsApp receipt submission is a bad instinct on the client's part. It means the practice needs a channel that matches that same low-friction habit but actually produces usable, structured data.
What a WhatsApp-based workflow looks like today
Some practices have tried to formalise this rather than fight it. A common pattern is a dedicated WhatsApp Business number, separate from any individual's personal phone, used only for receipt and invoice submission. Clients are told explicitly: send receipts here, not to your usual contact.
This solves the personal-number problem but not the structure problem. Someone on the team still has to open each image, extract the numbers, and file it correctly. For a very small client base, that might be tolerable. For a practice managing thirty or fifty clients, it becomes an unpaid data entry function bolted onto an already stretched team, which is the point at which practices start looking at a scalable receipt workflow instead.
The friction-free alternative: meet clients where they already are, without the manual sorting
The genuine insight in the WhatsApp habit is the same one behind paperless receipt management done well: clients want to submit a receipt the moment they think of it, with zero setup. Email does almost exactly the same job, and every client already has an email address they know how to use, whether or not they use WhatsApp.
Receiptflow's email-in feature is built around that same instinct. A client forwards a receipt to a dedicated address the moment it arrives in their inbox, or takes a photo and emails it there and then. There is no app to download, no login, no new habit to build beyond one they already have. The difference from a WhatsApp thread is what happens next: the receipt is automatically extracted, coded, and made available in your workflow, rather than sitting as an image waiting for someone to key it in by hand.
For practices weighing up whether to formalise a WhatsApp channel or move clients to something with structure built in, the honest comparison is this: WhatsApp solves the client's convenience problem and creates a data problem for you. Email-in solves both at once, with the same near-zero effort for the client.
Making the switch without losing the convenience clients like
If your practice already has clients sending receipts over WhatsApp, moving them to a structured alternative works best as a small ask, not a big process change. Tell the client exactly what to do differently: forward the receipt to this email address instead of texting it, and nothing else about how they work changes. Most clients will adopt this without resistance, because the effort on their side is identical.
The practices that get the most value from this switch are usually the ones dealing with high receipt volumes from trade and construction clients, hospitality clients, or anyone submitting several receipts a week rather than a handful a month. For those clients, the manual sorting cost of an informal WhatsApp channel adds up fast, and a structured, automatically extracted alternative, the same one behind building a receipt scanning service into your practice, pays for itself within a few weeks of reduced admin time.
Try Receiptflow's email-in feature and give clients a friction-free submission method that does not leave you sorting images by hand.
