Managing employee expenses is one of the odder parts of a UK bookkeeper's job, because you are responsible for the quality of records you do not directly control. Your client's employees submit their own receipts, on their own schedule, with their own standards for what counts as a legible photo. You are the one who has to make it all reconcile.
The temptation is to treat this as an unsolvable people problem: employees will always be messy, chasing will always be part of the job. It is not unsolvable. It is a process design problem, and it responds to the same fixes that make any other receipt workflow scalable: clear expectations, low friction, and automation for the parts that do not need a human.
Why this workflow is harder than client-submitted receipts
When you deal directly with a client's own business receipts, you have one relationship to manage and one person to educate. Employee expenses multiply that by however many staff a client has, each with their own habits, their own understanding (or lack of it) of what HMRC requires, and no direct relationship with you at all.
That last point matters more than it seems. An employee submitting a fuel receipt to their line manager for reimbursement has no reason to think about VAT treatment, P11D implications, or what "a legible copy" actually means for audit purposes. That is not their job. It is yours, once the expense claim reaches your desk, usually as a shoebox, a spreadsheet, or a stream of forwarded emails with no consistent format.
Set expectations before you set up any tooling
Before introducing any new capture process, get clarity from the client on two things: what counts as a valid business expense under their own policy, and what HMRC requires for the specific expense categories their staff claim most (mileage, subsistence, and equipment being the most common). Without this, automation just speeds up the collection of records that still need manual correction later.
This is also the point to check what your actual expense management software needs to support for the categories this client's staff claim most. Once that is clear, put it in writing, even briefly, for the client to circulate to their team. A short one-page policy covering what needs a receipt, what the submission deadline is, and what format is acceptable removes most of the ambiguity that causes late or unusable submissions in the first place.
Give employees the lowest-friction capture method available
Employees are not going to log into a new portal to submit a coffee receipt, and expecting them to is where most attempted process fixes fail. The submission method has to fit into how they already work: forwarding an email, or snapping a photo on their phone, with no app download, no account creation, and no training required.
This is the same principle behind why a low-friction, paperless submission channel works for client-submitted receipts generally, and it applies even more strongly here, because employees have less at stake in getting it right than the business owner does. The lower the friction, the higher the compliance, without you having to chase anyone.
Automate the extraction, keep the judgement calls human
Once receipts arrive, whatever channel they come through, the extraction and initial categorisation should be automatic. A bookkeeper's time is better spent reviewing the transactions that need a judgement call, mixed personal and business use, an unusually high claim, a receipt with no clear VAT breakdown, than retyping every line from every receipt.
This matters specifically for employee expenses because the review burden is different from ordinary business expenses. You are not just checking whether an expense is legitimate for the business; you are also checking whether it is correctly treated for the employee, since some categories (certain benefits, for example) have P11D or payrolling implications that a straightforward business purchase would not.
Handle the recurring problem categories deliberately
A handful of expense types cause a disproportionate share of the back-and-forth. Handling each of these with a clear rule, agreed with the client in advance, removes most of the friction at source.
Mileage. Set a clear rate and require a simple log (date, purpose, mileage) alongside any fuel receipts, rather than trying to reconstruct journeys after the fact from a fuel card statement. A dedicated mileage and travel review process is worth building once this category grows beyond the occasional claim.
Subsistence and meals. Agree a threshold above which a itemised receipt is required versus a simple total, since staff will otherwise submit whatever they happen to have, a card slip with no detail, which is not sufficient on its own.
Equipment and small purchases. Set a value threshold for what needs pre-approval versus what can be claimed after the fact, so employees are not submitting purchases the client never intended to reimburse.
Subscriptions and recurring costs. These are easy to miss because they do not generate a fresh receipt each month. Flag them for a one-off setup so they are captured automatically going forward rather than chased manually each cycle.
What this looks like once it is running properly
A well-run employee expense process should not need a bookkeeper chasing anyone by the third or fourth month. Receipts arrive through the low-friction channel, extraction and categorisation happen automatically, and the bookkeeper's review time concentrates entirely on the transactions that genuinely need judgement.
The measure of success is not zero exceptions. It is that chasing becomes the rare occurrence rather than the default, and the time you spend on this part of the client relationship shifts from data entry to the kind of review that actually protects the client from a compliance issue, the same outcome going paperless on expense claims generally is meant to deliver.
Use Receiptflow to give client employees a simple receipt capture workflow, no app or login required, and see how much of the chasing disappears once submission stops being the bottleneck.
