MTD Receipt Capture Requirements UK: What Software Needs | Receiptflow
What Receipt Capture Software Needs to Do for MTD Compliance: A UK Practice Guide
Tanvir Alam•Aug 26, 2026•8 min read•Tax & Compliance
MTD digital record rules require transaction data to enter your software once and travel digitally from there, which means receipt capture software has to extract and post data without anyone retyping it.
MTD receipt capture requirements UK come down to one question most practices never ask directly: does a photo of a receipt on a client's phone actually count as a digital record, or does it only count once someone in your office has done something with it?
The answer determines whether your firm is compliant or quietly exposed, and it's one of the clearer patterns to emerge from what practices actually learned in MTD's first year. This guide isn't another explainer of what Making Tax Digital is. It's about what HMRC's digital record rules specifically demand of receipt and expense data, what counts, what doesn't, and where the paper-to-software gap creates real risk for practices managing dozens of clients at once.
What HMRC's Digital Record Rules Actually Require
For every business transaction, HMRC requires three pieces of data held digitally: the date, the amount, and the category of income or expense. That's the baseline. The bigger compliance requirement sits behind it: once that data exists digitally, it has to move through your systems via a digital link, with no manual re-typing at any point in the chain.
This is the part practices underestimate. A digital link means data transfers electronically between software, whether that's an API connection, an export-import file, or a formula between spreadsheet cells. What breaks the chain is a person reading a figure off one screen and typing it into another. Do that, and the record stops being a compliant digital record from that point forward, regardless of how it started.
For businesses with combined self-employment and property income over £50,000 in the 2024/25 tax year, MTD for Income Tax has applied since 6 April 2026. Records have to be kept for at least five years after the submission deadline for that tax year, so a 2026/27 record needs to survive until 31 January 2033 at the earliest.
That retention window matters for receipt data specifically. A blurry photo saved to a phone's camera roll with no metadata attached isn't much use five years from now when HMRC asks for evidence behind a claimed expense.
MTD for Income Tax also runs on a quarterly cycle: four updates a year, each pulling from the same digital records, which gets considerably harder to manage once you're coordinating quarterly submissions across a full client list rather than a single filer. That means the compliance test isn't a once-a-year check on your record keeping, it's a running requirement your capture workflow has to pass every quarter without anyone stepping in to patch gaps manually. A practice that gets away with a manual workaround in one quarter is still exposed the next, because the underlying process hasn't changed.
What Counts as a Digital Record (and What Doesn't)
Here's the part that surprises a lot of clients: HMRC does not require anyone to scan or photograph paper receipts. The paper document itself never has to be digitised. What has to be digital is the transaction data extracted from it, the date, amount and category, entered into MTD-compatible software.
So a scanned invoice, a photo of a receipt, an electronic spreadsheet row, or data pulled through OCR software all count as digital records, provided the content requirements are met and the data connects to your submission software through an unbroken digital link.
What doesn't count:
A paper receipt sitting in a shoebox with nothing recorded about it anywhere
A figure a client reads out over the phone that your team types into a spreadsheet, then someone else retypes into your bookkeeping software
A photo of a receipt stored on a phone that never gets its data extracted into a proper record
Data copied from one spreadsheet into another by hand, with numbers changed or corrected along the way
The underlying paper receipt can be thrown away once the digital record is created and the client understands you may still want it kept for expense evidence. But the digital record has to be accurate, complete, and untouched by manual re-entry once it exists.
The Paper Receipt Problem: Where Practices Get Caught Out
Think about the actual workflow at a mid-sized practice. A sole trader client hands over a carrier bag of till receipts at the end of the quarter. Someone junior sorts through them, types the date, amount and expense category into a spreadsheet or directly into the practice's software.
That first entry, done by a human reading a paper receipt and keying the data in, is legitimate. It's the point where the digital record is created. The risk shows up afterwards: if that data then gets copied into a different system for the actual MTD submission, and anyone retypes rather than exports or syncs it, the digital link has broken.
That exposure starts at the point of onboarding, which is why getting the process right when you register clients for MTD for Income Tax in the first place matters as much as the ongoing capture workflow. Multiply the retyping risk across forty clients doing quarterly submissions and the exposure isn't one transposition error. It's a structural gap in the workflow that HMRC can flag during a compliance check, because the digital link either exists end to end or it doesn't.
The fix isn't asking clients to stop bringing in paper receipts. Most won't, and MTD doesn't require them to. The fix is making sure that once a receipt's data is captured, it travels through every downstream system digitally, with nobody retyping figures at any stage.
What Receipt Capture Software Needs to Do to Be MTD-Ready
This is where the software choice actually matters, and it's a narrower question than most vendor pages make it sound, especially given how much the receipt scanning market has changed since the earliest OCR tools. A tool that photographs receipts nicely isn't automatically MTD-ready. To close the compliance gap described above, receipt capture software needs to:
Extract structured data at the point of capture. OCR should pull the date, amount, VAT, and supplier directly from the image, not just store the image as a file. That structured extraction is what turns a photo into a digital record in HMRC's terms.
Post that data with a genuine digital link, not an export someone has to touch. If your team has to open a CSV, review it, and manually key figures into your practice software, the chain is broken. The data needs to move via API or direct sync, with human review limited to approving categorisation, not retyping numbers.
Keep an audit trail from receipt to submission. If HMRC asks how a figure in a quarterly update was derived, you should be able to trace it back to the original receipt image and the extraction that produced it, with a timestamp showing when the record was created.
Support the retention period without extra work. Five years minimum means the software needs to store both the source image and the structured data reliably, not rely on a client's phone storage or an inbox that gets cleared out.
Flag categorisation for review rather than guessing silently. Category is one of the three required fields. Software that assigns a category with no visibility into how, or lets errors through unchecked, creates the same risk as manual keying: a record that looks digital but isn't reliably accurate.
Handle multiple clients without the workflow changing per client. A practice with forty clients on forty different habits, some emailing photos, some dropping paper in the post, some forwarding supplier invoices, needs one capture process that produces the same compliant digital record regardless of how the receipt arrived. Software that only works cleanly for the client who already emails tidy PDFs isn't solving the actual problem.
Receiptflow was built around this exact chain: capture, extract, sync, without a manual retyping step anywhere between a client's photo and your practice software. That's not a feature list, it's the specific thing MTD's digital link rule requires of receipt data. If you are still shortlisting tools, our receipt scanning software checklist covers the ten points worth testing before you commit to any of them, MTD compliance included. Vendor stability is worth weighing too, as practices who'd built workflows around AutoEntry found out when Sage's acquisition of AutoEntry reshaped the product roadmap under them.
A Practical Checklist for Choosing MTD-Ready Receipt Software
Before signing up for any receipt capture tool, ask whether it can answer yes to each of these:
Does the data sync into your bookkeeping software automatically, without a manual export-import step?
Can you trace any submitted figure back to its original receipt image?
Are date, amount, and category all captured and editable without needing to be retyped elsewhere?
Is the audit trail retained for at least five years without extra configuration?
Does it integrate with the software your firm actually uses for quarterly submissions, not just a generic export?
If the answer to any of these is no, or it depends on how you set it up, that's a compliance gap worth closing before it becomes an HMRC finding rather than after.
Getting the receipt workflow right isn't a nice-to-have ahead of a client's MTD deadline, it's the part of compliance that's easiest to get quietly wrong and hardest to unwind after the fact.
Does HMRC require accountants to scan every client receipt?
No. HMRC requires digital records of the transaction data, date, amount and category, but does not require the paper receipt itself to be scanned or photographed.
Can a spreadsheet be used for MTD digital records?
Yes, provided it captures date, amount and category for each transaction and connects to compatible software through a digital link rather than retyped data.
What happens if a client submits a paper receipt that gets manually keyed in?
The first entry from paper is legitimate, but any later manual retyping of that data into another system breaks the required digital link.
How long do digital receipt records need to be kept under MTD?
At least five years after the submission deadline for the relevant tax year.
Is a photo of a receipt on a phone enough to be MTD compliant?
Only once the transaction data has been extracted into a proper digital record; the image alone does not meet HMRC's content requirements.
What is a digital link under MTD?
An electronic transfer of data between software with no manual retyping of figures at any point in the chain.
