How to Run a Digital Receipts Audit Across Your Client Base
Tanvir Alam•Sep 29, 2026•5 min read•Receipt Management
A structured digital receipts audit across a client base tests record-keeping compliance directly, rather than assuming it because no problem has surfaced yet.
Most practices assume their receipt workflow is compliant because nothing has gone wrong yet, not because anyone actually checked. That is a comfortable assumption right up until a client is selected for an HMRC enquiry and the digital records behind three years of returns turn out to have gaps nobody noticed.
A digital receipts audit tests that assumption directly. It does not need to be a major project. Done well, it is a structured review, similar in spirit to , that most practices can complete across their client base in a matter of weeks, and it consistently surfaces problems that were invisible until someone looked.
Receipt and record-keeping issues rarely announce themselves. A client whose digital records are 90% complete files their return the same way as a client whose records are fully complete, because the missing 10% only becomes visible when someone is specifically looking for it, an HMRC compliance check, a due diligence exercise ahead of a sale, or an audit like this one.
This is particularly true under Making Tax Digital, where the requirement is not just that records exist, but that they are kept digitally and linked correctly through the submission chain, and it is exactly where the non-standard receipt formats most guidance misses tend to hide. A client who has been submitting accurate figures can still be non-compliant on the digital record-keeping requirement itself if bridging or manual re-entry has broken that digital link somewhere along the way.
What a digital receipts audit should actually check
An audit worth running covers four areas, each testing a different failure mode.
Completeness. For a sample of transactions across a representative period, does a corresponding receipt or invoice actually exist in digital form? This catches the most basic gap: expenses claimed with no supporting document behind them, or the same document claimed twice under a different filename.
Digital continuity. For clients within MTD's scope, is the chain from original transaction to submitted figures maintained digitally throughout, or does it break at some point into a manual step (a spreadsheet retyped by hand, a paper record scanned after the fact but not properly linked)? This is the specific requirement generic record-keeping checks tend to miss.
Retention. Are records being kept for the required period, and are they actually retrievable, not just theoretically stored somewhere, but genuinely accessible if requested? A receipt saved to a folder nobody can find six months later fails this test just as badly as one that was never saved.
Quality and legibility. Are stored receipts actually legible, with the VAT and total amounts clearly visible, or are a meaningful proportion faded, cropped, or too low-resolution to stand up to scrutiny? This is a common gap with older scanned or photographed records that were captured before quality standards were tightened.
A practical method for running the audit
Auditing every transaction for every client is not realistic for most practices. A sampling approach gets useful, representative findings without the workload of a full review.
Segment the client base by risk. Start with clients who have higher transaction volumes, more complex expense categories (mixed-use vehicles, multiple income streams), or who moved onto digital record-keeping more recently, since these are where gaps are statistically more likely.
Pull a sample, not the whole ledger. For each client in scope, sample 15 to 20 transactions spread across different months and expense categories, rather than reviewing everything or clustering the sample in a single period.
Score each client against the four checks. A simple pass, partial, or fail rating against completeness, digital continuity, retention, and quality gives you a comparable picture across the client base, rather than a pile of unstructured notes.
Prioritise fixes by risk and effort. A client with several partial or fail ratings and a genuine enquiry risk (a complex return, a recent history of HMRC contact) should move to the top of your remediation list, ahead of a low-risk client with a single minor gap.
What to do once gaps are found
Finding a gap is the point of the audit, not a failure of it. The response should be proportionate and constructive rather than alarmist, since most gaps are fixable going forward even where past records cannot be recreated.
For clients with digital continuity failures, this usually means moving them onto a capture process that removes the manual step entirely, so the gap cannot recur. For clients with completeness or quality issues, it usually means a direct conversation about what "a usable receipt" actually looks like, since many clients genuinely do not know their current records fall short until it is pointed out with a specific example.
Making this a recurring check, not a one-off
An audit run once and never repeated only tells you where things stood on the day you looked. Building this into an annual or twice-yearly cycle, timed to sit before the busiest filing periods rather than during them, keeps the client base's records in a state you can defend if HMRC ever asks, rather than hoping they hold up, and it is worth writing that cadence into a receipt management SLA with clients so it does not depend on someone remembering to schedule it.
The practices that run this consistently tend to find fewer and fewer gaps over time, not because clients suddenly become more careful, but because the underlying capture process improves each time a gap gets fixed at the source rather than patched after the fact, along the lines set out in paperless receipt management done well.
A capture process that keeps the digital chain intact from receipt to submission removes most of what this audit exists to catch. See how Receiptflow keeps that chain unbroken, and start a free trial to test it against your own audit checklist.
FAQs
Common Questions with Clear Answers
Why should accountants audit their clients' digital receipt records?
Because compliance gaps rarely announce themselves; a client with mostly complete records looks the same as one with fully complete records until an HMRC check or a structured audit specifically looks for the gap.
What does a digital receipts audit check for?
Four things: completeness of supporting documents, whether the digital chain from transaction to submission stays unbroken under MTD, whether records are retained and genuinely retrievable, and whether stored receipts are legible enough to stand up to scrutiny.
Do accountants need to audit every client transaction?
No, a representative sample of 15 to 20 transactions per client, spread across different months and categories, gives a useful and comparable picture without the workload of reviewing an entire ledger.
How often should a digital receipts audit be run?
Building it into an annual or twice-yearly cycle, timed before the busiest filing periods, keeps client records defensible on an ongoing basis rather than only checking once and hoping nothing has changed since.
What is a digital continuity failure under MTD?
It happens when the chain from an original transaction to the submitted figures breaks into a manual step somewhere along the way, such as a spreadsheet retyped by hand, even if the final figures submitted are accurate.
