Bank Feeds and MTD: How Automated Imports Help with Digital Record Keeping
Last updated: February 2026
Making Tax Digital for Income Tax requires you to keep digital records and submit quarterly updates through MTD-compatible software. Bank feeds are the most efficient way to get transaction data into that software. They pull your bank transactions automatically, removing manual data entry and reducing errors. But bank feeds alone do not satisfy HMRC’s digital record-keeping requirements. You still need to categorise every transaction, handle personal spending that appears in a business account, and make adjustments that bank feeds cannot capture. This article explains how to set up bank feeds, what they do well, and where you need to do the work yourself.
What bank feeds are and how they work
A bank feed is an automated connection between your bank account and your accounting software. Once set up, the feed imports your transactions — typically overnight — so that every payment in and out appears in your bookkeeping system without you typing anything. Most UK high street banks support bank feeds through Open Banking, a secure data-sharing framework regulated by the Financial Conduct Authority.
The feed imports raw data: the date, amount, payee or payer name, and a reference. It does not know whether a payment was for stock, travel, or a personal purchase. That distinction is your responsibility, and it is the part that turns raw bank data into the digital records HMRC expects under MTD.
Why bank feeds matter for MTD
From 6 April 2026, sole traders and landlords with qualifying income above £50,000 must keep digital records and submit quarterly updates to HMRC. Qualifying income means your combined gross self-employment and UK property income — total turnover, not profit after expenses. The MTD Income Tax rules require that your digital records include the date, amount, and category for each transaction.
Without bank feeds, you would need to enter every transaction manually into your software — potentially hundreds of entries per quarter. Bank feeds eliminate that data entry step. They ensure every transaction is captured and timestamped accurately, which is half of what HMRC needs. The other half — categorisation — still requires human input.
Setting up bank feeds: step by step
The process varies slightly between software providers, but follows the same general pattern across all MTD-compatible platforms. Here is how it works in Xero, which is one of the most widely used MTD software packages in the UK.
Step 1: Add your bank account in the software
In Xero, go to Accounting > Bank accounts > Add bank account. Search for your bank by name. Xero supports most UK banks including Barclays, HSBC, Lloyds, NatWest, Santander, Starling, Monzo and others. Select your bank from the list.
Step 2: Authorise the connection
You will be redirected to your bank’s own login page. Log in with your usual online banking credentials and authorise the connection. Under Open Banking rules, the bank will ask you to confirm which accounts you want to share data from. Select your business current account. You are not giving your software provider your banking password — the authorisation happens directly with your bank through a secure handshake.
Step 3: Set the import start date
Most bank feeds import up to 90 days of historical transactions. If you are setting up before the start of your first MTD quarter (6 April 2026 for Phase 1), set the import date to capture transactions from the start of the quarter. There is no benefit in importing older data unless you need it for other accounting purposes.
Step 4: Review the first import
Transactions typically appear within 24 hours of the initial connection. Check that the opening balance matches your bank statement. If it does, the feed is working correctly and will continue importing new transactions each business day.
Reconnection
Open Banking authorisations expire every 90 days under FCA rules. Your software will prompt you to reauthorise the connection. This takes about 60 seconds — log in to your bank, confirm the connection, and transactions resume. If you miss the reauthorisation window, the feed pauses but does not lose data. Once you reconnect, it catches up on any transactions from the gap period.
What you must do after transactions import
This is the critical part that many sole traders underestimate. A bank feed imports data. It does not create compliant records. You need to do three things with every imported transaction.
1. Categorise each transaction
Every transaction needs an accounting category: sales income, cost of goods, travel, office supplies, bank charges, rent received, and so on. Your software will suggest categories based on payee names and previous matches. For example, if you categorise a payment to Shell as “Motor expenses” once, the software will suggest the same category next time Shell appears. Over a few weeks, most recurring transactions match automatically.
New or one-off transactions still require manual categorisation. A quarterly update submitted to HMRC under MTD must report income and expenses by category. If you leave transactions uncategorised, your quarterly figures will be wrong.
2. Split or exclude personal transactions
If you use a single bank account for both business and personal spending — common among sole traders — the bank feed imports everything. Personal transactions such as grocery shopping, clothing, or household bills are not business expenses and must not appear in your MTD records. You have two options:
- Code personal items to drawings: categorise them as owner’s drawings (or “personal” in simplified systems), which excludes them from your income and expense figures
- Use a separate business bank account: this is the cleaner approach. A dedicated business account means every imported transaction is business-related, and you only need to categorise — not filter — each item
HMRC does not legally require sole traders to have a separate business bank account. But in practice, mixing personal and business transactions creates significant extra work at each quarterly update. A dedicated account with a clean bank feed is the single most effective thing you can do to reduce your MTD admin burden.
3. Match transactions to invoices or bills
If you raise sales invoices or enter supplier bills in your software, bank feed transactions need to be matched to those records. When a customer pays invoice #1042 for £1,200, the bank feed shows a £1,200 credit. You match that credit to the outstanding invoice, which marks it as paid and keeps your debtor records accurate. Most software suggests matches automatically when amounts correspond.
Worked example: a sole trader setting up bank feeds in Xero
Tom runs a plumbing business in Leeds with annual gross income of £62,000. He enters MTD Phase 1 from 6 April 2026. He uses Xero as his MTD software and banks with NatWest.
March 2026: Tom signs up for MTD ITSA through his HMRC online account. In Xero, he goes to Accounting > Bank accounts and adds his NatWest business current account. He is redirected to the NatWest login page, authorises the Open Banking connection, and selects his business account. Within 24 hours, Xero imports 90 days of transactions.
6 April – 5 July 2026 (Q1): During the quarter, Tom’s bank feed imports 187 transactions. These include:
- 68 customer payments totalling £15,400 (income)
- 14 payments to plumbing suppliers totalling £3,100 (cost of materials)
- 23 fuel purchases totalling £680 (motor expenses)
- 12 trade tool and equipment purchases totalling £890 (tools and equipment)
- 8 transfers and direct debits for insurance, phone and software totalling £420 (general admin)
- 62 personal transactions totalling £2,950 (coded to drawings — excluded from MTD figures)
Tom spends about 20 minutes each week reviewing and categorising new transactions. Xero’s bank rules handle recurring items automatically — NatWest fees always go to “Bank charges”, Shell payments always go to “Motor expenses”. He only needs to categorise genuinely new payees.
Late July 2026: Tom reviews his Q1 figures in Xero: £15,400 income, £5,090 expenses across the relevant categories. His accountant checks the numbers, confirms the categorisation looks correct, and submits the Q1 update to HMRC through Xero before the 7 August deadline. The bank feed gave Tom accurate, timestamped data for every transaction. His weekly categorisation work turned that data into compliant digital records.
Limitations of bank feeds
Bank feeds are excellent for capturing cash-basis transactions as they flow through your bank account. But they have genuine limitations that you need to understand.
No accruals
Bank feeds only capture transactions when money moves. If you invoice a customer on 28 June but they pay on 10 July, the income appears in Q2 rather than Q1 under a bank-feed-only approach. For sole traders using cash basis accounting (which most MTD users will), this is not a problem — you report income when received. But if you use accruals accounting, bank feeds alone will not give you the correct period allocation. You will need to raise invoices and bills separately and match bank transactions to them.
No cash transactions
Bank feeds only capture what goes through the bank. If you receive cash payments — common in trades, market stalls, and some service businesses — those transactions will not appear in your bank feed. You must enter cash income manually into your software. Failing to record cash income is not just an MTD compliance failure; it is tax evasion.
No adjustments or allowances
Capital allowances, loss relief, pension contributions, use-of-home allowances, and mileage claims do not flow through your bank account in a way that bank feeds can capture directly. These adjustments are made in the Final Declaration (due 31 January following the tax year end) or as journal entries in your software. Bank feeds handle the day-to-day transaction recording; year-end adjustments require separate work.
No VAT calculations
If you are also registered for MTD for VAT (mandatory above the £90,000 VAT threshold), bank feeds import gross amounts. Your software needs to know the VAT rate for each transaction to calculate the VAT element. This means you must set the correct VAT rate when categorising each transaction — the bank feed cannot determine whether a purchase included 20% VAT, 5% reduced rate, or was zero-rated.
Bank rules: making categorisation faster
Every major MTD software package includes a bank rules feature that learns from your categorisation patterns. In Xero, you can create explicit rules: “Any transaction with ‘SHELL’ in the payee name → categorise as Motor expenses at 20% VAT.” In FreeAgent, QuickBooks, and Sage, similar automation exists under different names (transaction rules, auto-categorisation, or bank feed rules).
After two or three months of categorising transactions, a well-configured set of bank rules will handle 70–80% of your transactions automatically. You then review and approve the suggestions rather than categorising from scratch. This is where the real time saving of bank feeds emerges — not just in the import, but in the progressively automated categorisation that follows.
Should you use a separate bank account?
Yes, if at all possible. Here is a practical comparison:
| Approach | Quarterly categorisation work | Risk of errors |
|---|---|---|
| Mixed personal/business account | Every transaction needs reviewing; personal items coded to drawings | Higher — personal expenses accidentally claimed as business costs |
| Dedicated business account | Only business transactions to categorise; no filtering needed | Lower — all imported transactions are genuinely business-related |
A basic business current account from a digital bank like Starling or Monzo costs nothing and takes minutes to open. The time saved at each quarterly update — and the reduced risk of errors in your MTD submissions — makes it worthwhile for virtually every sole trader.
Frequently asked questions
- Do bank feeds count as digital records for MTD?
- Not on their own. Bank feeds import raw transaction data, but HMRC requires each transaction to be categorised by type (income, specific expense categories). You must categorise every imported transaction before your records meet MTD requirements.
- What happens if my bank feed disconnects mid-quarter?
- No transactions are lost. When you reauthorise the connection, your software imports any transactions from the disconnection period. Open Banking authorisations expire every 90 days, so expect to reauthorise roughly four times per year. Your software will notify you when reauthorisation is needed.
- Can I use bank feeds with a personal bank account for MTD?
- Yes. HMRC does not require a separate business bank account. However, you must correctly identify and exclude personal transactions from your MTD records. Using a dedicated business account is strongly recommended to reduce this burden and minimise categorisation errors.
- Do I still need to keep receipts if I use bank feeds?
- Yes. Bank feeds provide evidence that a payment was made, but HMRC may ask for underlying documentation (receipts, invoices) to verify the nature and business purpose of a transaction. Keep receipts for at least five years after the 31 January filing deadline for the relevant tax year.
- Which banks support bank feeds in MTD software?
- Most UK banks support Open Banking feeds, including Barclays, HSBC, Lloyds, NatWest, Santander, Starling, Monzo, Tide, and most building societies. Check your specific software provider’s bank feed page for a full list of supported institutions.
Need help with MTD digital records?
Jack Ross Chartered Accountants helps sole traders and landlords set up bank feeds, configure their MTD software, and submit quarterly updates on time. As a certified Xero partner practice, we handle the technical setup so you can focus on running your business. Get in touch
