Making Tax Digital for Income Tax (MTD for ITSA) is not really a quarterly filing problem. It is a bookkeeping hygiene problem.
If your income and expenses are consistently captured, categorised and evidenced, the quarterly update is just an export and a submission. If your bookkeeping lives in a half-updated spreadsheet and a bank login, quarterly updates become four new fire drills a year.
The short version
- Quarterly updates are only as reliable as your transaction categorisation, so automate capture and coding first, then worry about submission.
- If you are staying in spreadsheets, treat “bridging” as submission only, you still need a controlled chart of categories and a repeatable close process.
- Bank rules are powerful but brittle, so build for misclassifications, duplicates and feed gaps with reviews and exception queues.
- n8n is useful around the edges, for example chasing missing receipts and pushing exceptions to Slack or email, but you still need an accounting system of record.
Who needs to do MTD for Income Tax, and when?
HMRC’s start dates are tied to your qualifying income on your Self Assessment tax return. If your 2024 to 2025 return shows qualifying income over £50,000, you are in from 6 April 2026. If it is over £30,000, you are in from 6 April 2027. HMRC also set out a later cohort over £20,000 from 6 April 2028. All of this is in HMRC guidance and the quarterly update direction, not in accounting software marketing pages. See HMRC’s "Before you use this guide" and the quarterly update direction for the thresholds and scope: GOV.UK: Use Making Tax Digital for Income Tax, before you use this guide and GOV.UK: Making Tax Digital for Income Tax, Quarterly update direction.
A few practical details that matter operationally:
- You submit quarterly updates of income and expenses using compatible software. HMRC does not provide the software.
- Quarterly updates are on fixed periods and deadlines. HMRC publishes the standard deadlines as 7 August, 7 November, 7 February and 7 May, and confirms you can submit any time from the end of the period to the deadline: GOV.UK: Send quarterly updates.
- HMRC stated they will not apply penalty points for late quarterly updates in the first year (2026 to 2027). That is helpful for bedding in processes, but it is not a reason to stay manual: GOV.UK: Send quarterly updates.
If you are an ops lead or a founder, the key question is not “are we eligible yet”. It is “how much of our income and spend is already structured enough to report without heroics”.
What actually gets sent in a quarterly update?
Most advice online blurs three different things: digital records, quarterly updates, and the year end finalisation.
Under MTD for Income Tax, you keep digital records of your business income and expenses, and you send HMRC quarterly updates that summarise those categories. The quarterly update direction sets out that the quarterly update is made up of totals by category, based on your digital records, rather than a full set of accounts: GOV.UK: Making Tax Digital for Income Tax, Quarterly update direction.
Two implications for your systems:
- Your categorisation needs to be predictable. If you recode transactions differently each quarter, your numbers will jump around. That increases review time and creates awkward conversations with your accountant.
- Quarterly updates are per income source. HMRC’s software finder and vendor guides focus on self-employment and property. In real businesses this often means you have more than one “bucket” to keep tidy, even if you are one person: GOV.UK: Find software that works with Making Tax Digital for Income Tax.
The mechanism is boring, and that is good: your feed brings in transactions, you apply rules, you attach evidence where needed, you reconcile, then you submit totals.
Spreadsheet plus bridging, or full software?
If you are currently on Google Sheets or Excel, you have two sensible routes.
Route A: Spreadsheet bookkeeping plus bridging submission
Bridging software connects your spreadsheet totals to HMRC, without moving your day to day bookkeeping into a full accounting platform.
This can work well when:
- You have simple income and expense lines.
- You do not need invoicing, VAT workflows, multi-currency, approval flows, or project accounting.
- You can enforce a consistent sheet structure and categories.
The trade off is that you must be disciplined. A spreadsheet does not stop you from:
- using inconsistent categories,
- double counting,
- editing historical periods,
- or losing the audit trail for who changed what and why.
HMRC’s own stance is software-agnostic, but clear about compatibility: use the GOV.UK software finder for submission.
Route B: Full bookkeeping software plus built-in MTD submission
Xero, QuickBooks Online and FreeAgent all position themselves as MTD-capable, and they focus on the benefits of bank feeds and automation.
This works well when:
- you want bank feeds, rules, invoice capture, and a proper ledger,
- you need collaboration with an accountant or bookkeeper,
- you need an audit trail,
- you have multiple income streams or property plus trade.
Vendors publish their MTD for Income Tax pages and help articles, but you should still verify compatibility on HMRC’s list because product variants and eligibility can differ: Xero UK: MTD software for VAT and Income Tax and QuickBooks: your MTD filing cycle in QuickBooks.
A decision framework you can run this week
Use this simple scoring. If you score 2 or more “yes”, spreadsheets are usually a false economy.
| Question | Yes means you should favour full software |
|---|---|
| Do you need bank rules to scale categorisation? | You need a ledger that can apply and audit rules |
| Do you have more than one income source in scope (trade plus property)? | You need separation and reporting by activity |
| Do you have staff or an accountant collaborating monthly? | You need permissions and audit trails |
| Do you often chase receipts after the fact? | You need capture workflows and exception queues |
| Do you regularly reclassify transactions at year end? | You need controlled adjustments and notes |
If you stay on Sheets or Excel, treat it as software engineering. Lock down formats, control versions, and do not rely on “everyone remembers how we do it”.
What should you automate first for MTD ITSA?
The mistake we see is people starting at the end: picking the submission tool first.
Start with the steps that create reliable data.
1) Bank feeds, and what happens when they stop
Bank feeds are your primary source of truth for “did money actually move”. If the feed breaks, your quarterly update becomes a scramble.
Whatever platform you choose, define:
- who checks the feed weekly,
- what “missing days” means (for example: no new transactions since last Tuesday),
- and what the fallback is (CSV import, or manual entry, depending on tool).
This is not glamorous, but it is where most systems fail quietly.
2) Receipt capture, with an exception queue
Receipt capture is not about OCR magic. It is about building a workflow that makes missing evidence visible.
In practice, you want an exceptions list like:
- card transaction over a threshold without an attachment,
- supplier name that looks like a personal purchase,
- repeated “misc” categories.
You can build that exceptions list inside your accounting platform, or you can build it outside and push it to someone to fix.
3) Categorisation rules, and their failure modes
Bank rules are powerful, but they are easy to over-trust.
Common failure modes:
- Substring matches catch the wrong merchant. A rule for “Amazon” can miscode AWS, Kindle, Marketplace and refunds differently.
- Card processor descriptors change. A supplier moves from Stripe to Adyen, and your rule no longer matches.
- Duplicate creation when you retry imports or integrations. If you import the same CSV twice, rules happily recode both sets.
To make rules safe, you need:
- a small set of rules that cover common spend,
- a monthly review of uncategorised and “other”,
- and a way to track rule changes.
Can n8n help, and where does it bite?
n8n is good at connecting tools you already run. In an MTD context, it is most useful around the bookkeeping system, not instead of it. For example:
- Pull a list of uncategorised transactions from Xero or QuickBooks on a schedule.
- Email or Slack the person responsible with a deep link to fix them.
- Watch a Google Drive folder for new receipts, and post a reminder if a receipt exists but no matching transaction is found.
If you build these flows, you need to be honest about limits.
Rate limits and retries
Both accounting platforms and automation platforms have rate limits.
- Xero documents API limits and global minute limits in their developer FAQ: Xero Developer: limits FAQs.
- Intuit documents QuickBooks Online API call limits and throttles: Intuit Developer: limits and throttles.
- n8n’s own docs show that when a node hits a rate limit it errors, and you should handle it with retry settings or a wait and loop pattern: n8n docs: handle rate limits.
In production, a naive “Retry on fail” can create duplicates. A workflow that fails after creating an invoice but before tagging it will retry and create a second invoice.
The fix is idempotency. You store a stable external ID and check for it before creating anything. If your tool does not give you that concept, you build one in your own store.
Ownership and maintenance
If you automate around bookkeeping, decide who owns it:
- Who updates bank rules when merchant descriptors change?
- Who handles failures when an API credential expires?
- Who reviews duplicates?
If the answer is “the founder”, it will not last.
Swarm Labs built a product called Time Hive that logs every automation run and estimates hours saved. For MTD automation, that kind of logging matters because you want to know which workflows are failing, and whether the automation is actually reducing admin or just moving it around.
A workable quarterly process (and what to check each month)
Quarterly updates feel heavy when you treat them as quarterly work.
Instead, run a monthly close, then your quarterly update is just the sum of three clean months.
Here is a practical checklist.
Monthly, 30 to 60 minutes
- Confirm bank feed is current.
- Reconcile new transactions.
- Clear uncategorised items.
- Attach receipts for transactions that need evidence.
- Review the “rules caught this” list for obvious miscodes.
Quarterly, 30 minutes
- Lock the quarter (or at least stop editing it casually).
- Run a sanity check report: income and top 10 expense categories.
- Submit the quarterly update through your chosen compatible software.
The point is consistency. HMRC explicitly allows you to submit within the window after the period ends, up to the deadline, so you can align this with your existing monthly ops rhythm: GOV.UK: Send quarterly updates.
If you are currently spreadsheet-based, this is where most teams fail. Without a disciplined monthly close, your spreadsheet becomes a moving target and quarterly totals become a negotiation.
Setting up MTD ITSA automation without making a mess
If you want this to be low effort by the time the £30,000 threshold applies from 6 April 2027, treat 2026 to 2027 as the bedding-in year. HMRC explicitly positioned the first year as a lighter-touch period on quarterly update penalties, which is a useful window to fix your process before it is enforced: GOV.UK: Send quarterly updates.
What we implement for clients is usually:
- Choose the system of record (Xero, QuickBooks Online, or FreeAgent) based on how you actually run money.
- Set up bank feeds and rule sets conservatively.
- Put receipt capture into a single, enforced habit.
- Add automations around exceptions and reminders, often with n8n.
- Instrument it so you can see failures and duplicates early.
If you want to sanity-check what you have now, start with our services pages and the integration patterns we build in /integrations/. The tooling matters, but the operating model matters more.
If you want MTD quarterly updates to be boring
Swarm Labs is a UK software studio in Manchester. We set up MTD for Income Tax bookkeeping automation and then keep it maintained with monthly optimisation, so your quarterly updates come from clean, reconciled data rather than late nights.
If you want help choosing between spreadsheet plus bridging versus Xero, QuickBooks Online or FreeAgent, and putting n8n around the edges safely, talk to us about your integration.
Sources
- GOV.UK: Use Making Tax Digital for Income Tax, Before you use this guide
- GOV.UK: Use Making Tax Digital for Income Tax, Send quarterly updates
- GOV.UK: Making Tax Digital for Income Tax, Quarterly update direction
- GOV.UK: Find software that works with Making Tax Digital for Income Tax
- Xero: MTD Software for VAT and Income Tax
- Intuit QuickBooks: Your MTD filing cycle in QuickBooks
- Xero Developer: Limits FAQs
- Intuit Developer: QuickBooks Online API limits and throttles
- n8n docs (GitHub): Handle rate limits