It's April 2026. Making Tax Digital for Income Tax Self Assessment is live. You're in your practice, coffee in hand, and your self-employed client walks in carrying a shoebox. Inside: twelve months of paper bank statements, unsorted, some with coffee stains, others folded into origami. Your stomach drops.
Because you know what's coming. MTD for Income Tax means quarterly submissions. Digital record-keeping. A clear audit trail from source documents to HMRC. And here's your client, handing you the polar opposite of "digital."
The practical questions are real. What counts as a "digital record" under MTD? Is a PDF statement itself a digital record? Can a paper statement still be used? And when does HMRC's digital-link rule actually apply?
The important distinction is that a bank statement is normally a supporting document. The MTD digital record is the income or expense record created and stored in compatible software. HMRC's digital-link restriction applies when those digital records move between software products; it does not mean every source statement must arrive digitally or that the first record can never be entered from paper.
What Making Tax Digital Means for Bank Statements
Making Tax Digital for Income Tax is being introduced in stages. It applies from 6 April 2026 where qualifying income shown on the 2024–25 tax return was more than £50,000; from 6 April 2027 where qualifying income shown on the 2025–26 return was more than £30,000; and from 6 April 2028 where qualifying income shown on the 2026–27 return was more than £20,000. Exemptions and special circumstances can change the result, so check HMRC's eligibility guidance.
The MTD requirements that affect how you handle bank statements are:
- Digital record-keeping — Create and store records of self-employment and property income and expenses in software that works with Making Tax Digital for Income Tax.
- Quarterly updates — Send four in-year summaries from those digital records for each self-employment and property business.
- One annual tax return — Check the full-year figures, add other income, gains, reliefs and allowances, then submit the tax return through compatible software by the normal 31 January deadline.
- Digital links between products — If more than one software product is used for record keeping and submissions, transfer the existing digital records using an approved digital method rather than re-keying or copy-and-paste.
A PDF, CSV or paper statement may supply evidence for a transaction, but its file format does not decide compliance. What matters is that the relevant transaction record is created and stored accurately in compatible software, supporting documents or copies are retained, and any later movement of that digital record between products follows HMRC's digital-link rules.
Which Bank Statement Formats Are MTD-Compliant?
Different formats change the amount of processing work, not the legal status of the source document. The digital record still needs to be created in compatible software:
| Bank Statement Format | Role under MTD | Practical workflow |
|---|---|---|
| CSV download from online banking | Supporting source file | Import relevant rows into compatible record-keeping software, review and categorise them, and retain the statement or a copy. |
| PDF download from online banking | Supporting document | Extract and import the transactions, or enter them accurately into compatible software. Retain the PDF as supporting evidence. |
| Scanned paper statement (PDF) | Copy of a supporting document | Use the scan for extraction or entry, then create the transaction records in compatible software and retain the supporting evidence. |
| Paper statement (not digitised) | Valid supporting document | Create the corresponding digital records in compatible software. Scanning is optional, although it may reduce handling and transcription work. |
| Photograph of statement on phone | Potential supporting copy | Make sure it is complete, legible and retained. The actual income or expense records still belong in compatible software. |
The practical reality is that different UK banks offer different export capabilities, and your clients use different banks. Here's what you're dealing with:
The uneven landscape of UK bank export capabilities means most practices face a mix of formats every month: a Monzo CSV from one client, an HSBC PDF from another, a Nationwide PDF from a third, and a shoebox of paper statements from the client who still thinks the internet is a fad. Your MTD compliance system needs to handle all of them consistently.
The Digital Links Requirement: What Bookkeepers Need to Know
The digital-link rule matters when you use more than one product for MTD record keeping and submissions. It applies to the transfer of an existing digital record between software programs, or between parts of the same program. It is not a rule that every bank statement must begin life as a digital file.
What Counts as a Digital Link
- CSV, XML or spreadsheet import and export — move a file containing digital records and import it into the next product.
- Email or portable-device transfer — HMRC explicitly lists emailing a spreadsheet, or passing it on a storage device, as a digital link when the recipient imports the file rather than re-entering its contents.
- API or automated transfers — move records directly between products.
- Linked spreadsheet cells — formulas can carry a value between linked cells or sheets without manual re-entry.
What Breaks the Digital Link
- Re-keying an existing record — reading a digital record in one product and typing it again into the next product used in the MTD workflow.
- Copy-and-paste between products or unlinked cells — HMRC does not treat this as a digital link for moving an existing record.
- Emailing a file and then re-entering it — emailing the spreadsheet itself can be a digital link; opening it and manually recreating the records in another product is not.
Where BankScan AI fits: BankScan AI can turn a bank statement into a structured CSV or Excel file for review and import. If you import that file into compatible record-keeping software, it can reduce transcription effort and provide a file-based transfer. You still need to check the data and mapping, retain supporting evidence, use HMRC-recognised software for the required records and submissions, and preserve digital links if those records move between products later.
Your MTD Quarterly Submission Workflow for Bank Statements
⏱ Bank statement processing for MTD: minutes per client per quarterUnder MTD for Income Tax, the tax year is divided into quarterly periods, each requiring a summary submission of income and expenditure. Here's how to build a bank statement workflow that feeds each quarterly submission cleanly:
The Four MTD Quarterly Update Periods (Standard Accounting Date: 5 April Year-End)
| Quarter | Period | Submission Deadline | Bank Statements Needed |
|---|---|---|---|
| Q1 | 6 April – 5 July | 7 August | Records from 6 April through 5 July |
| Q2 | 6 April – 5 October | 7 November | Cumulative records through 5 October |
| Q3 | 6 April – 5 January | 7 February | Cumulative records through 5 January |
| Q4 | 6 April – 5 April | 7 May | Full tax-year records |
Note: Each update is cumulative from the start of the tax year. Calendar-period updates likewise cover 1 April through 30 June, 30 September, 31 December and 31 March. The tax return is a separate year-end obligation, normally due by 31 January after the tax year, and the same four 7th-of-the-month update deadlines apply.
Step-by-Step Quarterly Workflow
- Collect statements as the quarter progresses — Don't wait until the quarterly deadline to gather three months of statements. Ask clients to share their bank PDFs monthly, or grant you read-only access to their online banking if they're comfortable with that. The fewer statements you're chasing on deadline day, the smoother the submission.
- Prepare a consistent import file — Upload each month's statements to BankScan AI if you want automated extraction. Whether they arrive as CSVs, PDFs or scans, review the resulting Excel or CSV output before it becomes an accounting record.
- Import into your compatible record-keeping software — Map the file to the fields required by your chosen product, import it, and verify dates, amounts, descriptions and categories. Product capabilities and import formats vary.
- Review transactions against the quarter's activity — With all bank data imported and categorised, review for completeness. Check that all income sources and expense categories are captured. Flag any unusual transactions for client queries.
- Submit the quarterly update — Your compatible software sends the summary to HMRC. If separate record-keeping and submission products are used, make sure the existing digital records move between them using a permitted digital link.
- Store the records — Retain the digital income and expense records in compatible software for the statutory period. Also keep the original bank statements, reviewed extraction files and HMRC submission confirmations as supporting evidence.
Common MTD Bank Statement Pitfalls (and How to Avoid Them)
The theory of MTD compliance is straightforward. The practice is where things get messy. Here are the most common bank statement pitfalls UK bookkeepers encounter under MTD — and the practical fixes.
1. Missing Statements from Clients
It happens every quarter: the client who "can't find" their February statement, or the one who "thought you already had it." Under MTD, missing statements mean incomplete digital records, which means a submission that doesn't capture all income and expenditure. Fix: Set a monthly statement reminder (automated email or WhatsApp), and maintain a simple tracking sheet that shows which months' statements are received for each client. If a statement is genuinely unavailable from the client, request it directly from the bank — most UK banks can reissue statements on request.
2. Foreign Currency Accounts
Self-employed clients with overseas income — freelancers paid in USD, landlords with euro-denominated mortgages — present a currency conversion challenge under MTD. HMRC requires figures in GBP, and the exchange rate used must be consistent and documented. Fix: Extract the foreign currency transactions using BankScan AI (which preserves the original currency amounts), then apply HMRC's published monthly exchange rates or your client's chosen consistent rate. Document the rate source in the digital records.
3. Joint Accounts
When a client shares a bank account with a spouse or business partner, only the client's share of income and expenditure should appear in their MTD submission. Manual splitting of joint account transactions is tedious and error-prone. Fix: Process the full statement through BankScan AI to get all transactions in a spreadsheet, then tag transactions by owner. If the split is consistent (e.g., 50/50), use spreadsheet formulas to automate the apportionment and document the split methodology.
4. Legacy Bank Formats
Building society passbooks. Old-style bank statements with non-standard layouts. Statements from banks that merged years ago but still use legacy formatting. These exist, and they land on your desk during quarter-end. Fix: Scan them to a high-quality PDF and process through BankScan AI. The AI is trained on 22 UK bank formats including legacy variants like Virgin Money's inherited Clydesdale and Yorkshire Bank layouts. If a format genuinely can't be processed automatically, document the exception and process it as close to the MTD standard as possible — HMRC expects reasonable effort, not perfection.
5. Business and Personal Transactions Mixed in One Account
Many self-employed clients use a single bank account for both business and personal transactions. Under MTD, only business income and expenditure should be reported. Fix: Extract the full transaction history through BankScan AI, then use your accounting software's categorisation tools to tag business transactions. The extracted spreadsheet provides a complete audit trail showing which transactions were included and excluded — essential if HMRC ever queries the submission.
6. Client Onboarding with Historical Data
When a new self-employed client joins your practice mid-tax-year, you need to process months of historical bank statements for the MTD quarterly submissions they haven't yet made. Fix: Use BankScan AI's bulk upload to process multiple months of statements in one batch. Upload six PDFs at once and receive six separate Excel files, each correctly formatted and ready for import. This turns what would be two days of manual data entry into a 15-minute batch job.
Building Your MTD Bank Statement Compliance System
MTD compliance isn't a one-off exercise — it's a recurring system your practice runs every quarter, for every MTD-registered client. Here's what a sustainable system looks like:
MTD-Compliant System
- Supporting statements or copies retained
- Accurate records created in compatible software
- Imports reviewed and reconciled
- Digital links maintained between MTD products
- Full audit trail preserved
- Quarterly submissions on time, every time
- Current HMRC guidance checked
Non-Compliant System
- Supporting records missing or incomplete
- Required digital records not created
- Existing records re-keyed between products
- Digital links undocumented or broken
- Missing or incomplete audit trail
- Quarterly submissions rushed and error-prone
- Deadlines or HMRC notices ignored
The technology to reduce this work already exists. BankScan AI processes statements from major UK banks and building societies, including complex PDF layouts. It can produce a structured file for review and import into a bookkeeping workflow; the user's chosen compatible software and the way records move between products determine MTD compliance.
UK bookkeepers are already adapting their practices for MTD for Income Tax. A documented workflow for collecting evidence, creating accurate digital records, linking software and reviewing deadlines is more reliable than leaving the whole process until the quarterly submission window.
Prepare Bank Statements for Your Digital Workflow
Upload a UK bank statement — PDF, CSV or scan — and get a structured Excel or CSV file to review and import into your record-keeping workflow. Free first conversion.
Try BankScan AI Free →Frequently Asked Questions
Can I use PDF bank statements for Making Tax Digital?
You can use a PDF statement as a supporting document, but the PDF is not automatically the MTD digital record. The income or expense record must be created and stored in software that works with MTD for Income Tax. Manual entry from a source statement can create that first digital record; if the record is later transferred between software products, the transfer must use a digital link.
Do I need to keep paper bank statements after digitising them under MTD?
HMRC says you must continue to keep the original supporting records, or copies of them, used to prepare the tax return, including bank statements and invoices. Scanning can make processing easier, but creating an MTD digital record does not by itself remove the normal requirement to retain supporting evidence.
What counts as a digital link under MTD rules?
A digital link transfers an existing digital record between software products, or between parts of software, without manually re-entering the record. HMRC examples include linked spreadsheet cells, CSV or XML import and export, emailing or physically transferring a spreadsheet for import, automated transfers and APIs. Copy-and-paste or re-keying an existing record between products does not count. The rule is about moving digital records after they have been created, not whether the source bank statement arrived on paper or as a PDF.
Are CSV bank statement downloads MTD compliant?
A bank CSV is a useful source file, but no statement format is automatically compliant by itself. Import the relevant transactions into compatible record-keeping software, check and categorise them, and retain the supporting statement or a copy. If those digital records move to another product used for an HMRC submission, use one of HMRC's permitted digital-link methods.
How do I handle client bank statements that only come as paper?
Paper statements can remain supporting documents. The requirement is to create and store the relevant income and expense records in compatible software. You may enter them accurately into that software or scan and extract them first. Automation can reduce transcription effort and errors, but HMRC does not require every paper source document to be digitised before the first digital record is created.
What happens if my client's bank does not offer digital statements?
A bank does not need to provide digital statements for you to comply. Keep the paper statement or a copy and create the corresponding income and expense records in compatible software. Scanning and automated extraction are optional workflow choices, not a condition of MTD compliance.
Does BankScan AI work with MTD-compatible software?
BankScan AI produces CSV and Excel files designed for spreadsheet and accounting workflows. Check the field mapping and import support in your chosen product. BankScan AI output does not by itself prove MTD compliance: the digital records must be created and stored in compatible software, and any transfer between products used for HMRC submissions must follow HMRC's digital-link rules.
Last updated: 30 July 2026. Check HMRC's current digital-record guidance and MTD start-date guidance. Read our UK bank statement formats guide or browse all blog posts for UK accountants and bookkeepers.