Making Tax Digital for Income Tax Is Live: What Your Software Must Do

A landlord with three rental properties in Manchester doesn’t think of herself as a software buyer. She thinks of herself as someone who fills in a tax return once a year, usually in January, usually later than planned. From April 2026, that habit stops working. If her rental and self-employment income together crosses £50,000, HM Revenue & Customs expects quarterly digital updates instead of one annual form, and the update has to come from software that keeps her records digitally from the moment a transaction happens.

Records kept digitally from the moment a transaction happens: that’s where most of the confusion sits. Businesses assume Making Tax Digital for Income Tax (MTD ITSA) is a filing change. It’s a record-keeping change first, and a filing change second. If your software, or your client’s software, still relies on a spreadsheet someone updates from memory on a Sunday night, that workflow is the part that needs to change, not just the form at the end.

Who has to comply, and when

HMRC’s staged rollout is set by income, not by business type:

Income here is turnover, not profit. A landlord with £52,000 in rent and heavy mortgage interest still falls into the £50,000 band. Anyone close to a threshold this year should assume they’ll be in scope the following year and build accordingly, rather than wait for a letter from HMRC to confirm it.

What “digital records” actually requires

The rule that catches people off guard is HMRC’s digital links requirement. You’re allowed to keep records in a spreadsheet. You’re not allowed to move numbers between systems by retyping them or copying and pasting. A formula that pulls a total from one spreadsheet tab to another counts as a digital link. A person reading a number off a bank statement and typing it into a different spreadsheet does not.

In practice, this pushes three groups toward different solutions:

Sole traders and landlords with simple finances can often stay on a spreadsheet, provided they add what HMRC calls bridging software: a small tool that reads the spreadsheet and submits the quarterly update through the API, without a human retyping anything in between.

Businesses already on accounting software need that software to support MTD ITSA specifically, not just general bookkeeping. Being able to generate an invoice or track expenses isn’t the same as being able to submit a quarterly update and a Final Declaration through HMRC’s system.

Anyone running custom software, a property management tool built in-house, a freelance invoicing app, a niche system for a specific trade, has to decide whether to build the HMRC connection into that existing tool or route the numbers into a recognized platform instead.

HMRC keeps a public list of software recognized for Making Tax Digital, and Xero, QuickBooks, and Sage all appear on it, alongside a longer tail of smaller providers. For most small businesses, one of these three ends up doing the actual quarterly submission, even when the day-to-day bookkeeping happens somewhere else.

Where Xero, QuickBooks, and Sage actually differ

The three platforms aren’t interchangeable, and the differences matter more once quarterly deadlines are involved rather than an annual one.

None of these figures are a substitute for checking your specific bank and plan, since feed coverage and pricing tiers shift often. The point of the comparison is architectural: if you or your developer need to build something around the accounting data, a client portal, a dashboard, an automated reconciliation step, Xero’s API is usually the one that gets you there with the least friction.

Bank feeds do more work than people expect

A large share of the manual retyping that breaks digital links happens at the bank-statement stage. Someone downloads a CSV, opens it, and types selected lines into their bookkeeping spreadsheet. Open Banking feeds remove that step entirely: transactions flow from the bank into Xero, QuickBooks, or Sage automatically, categorized and dated, with no human copy-paste in the chain.

For businesses that take payments online rather than just receiving them, Stripe sits in the same category. Its settlement and payout data can feed directly into accounting software, so the money that lands in a bank account already carries a reference back to the original sale. Faster Payments transfers work the same way through most UK banks’ own feeds. None of this is exotic technology. It’s the plumbing that MTD ITSA is quietly forcing businesses to finally connect, because the alternative, someone typing numbers twice, is exactly what the rule exists to stop.

What changes if you build or maintain software for this market

If you run a proptech tool, a practice management system, or any custom software that touches UK self-employment or rental income, the compliance burden isn’t on your users. It’s on your engineering backlog.

The features that tend to get missed until a client asks for them:

• A working connection to HMRC’s Making Tax Digital API, tested against HMRC’s own sandbox before going live, not assumed to work because it looks similar to a general accounting integration.
• Handling for a failed or late submission: a queue, a retry, and a clear record of what was sent and when, because “it probably went through” isn’t an acceptable answer to a tax authority.
• An audit trail showing where each figure in a quarterly update originated, since a digital link that can’t be traced back to its source transaction defeats the purpose of the rule.
• A sensible way to split income and expenses across multiple properties or businesses, since each one typically needs its own End of Period Statement.

We’ve built the underlying pattern here before, even outside a tax context. For a lending business, we built a client portal that syncs loan balances, repayments, and account status with the company’s banking partner in real time, so staff stopped retyping numbers between the bank’s system and the internal ledger. That’s the same shape of problem MTD’s digital links rule is solving for: data should move through an API or a live feed, not through someone’s fingers twice. Whether the destination is a bank’s core system or HMRC’s submission endpoint, the engineering work looks similar: map the fields, handle the failures, and log everything so a mismatch is traceable rather than mysterious.

Fixed-price projects at Pazl, including custom finance and bookkeeping software, typically start around $3,300 (≈€3,000), with a six-month warranty on whatever gets delivered. An HMRC integration for an existing piece of software is scoped after we’ve looked at what you’re already running. The effort depends heavily on whether your data already lives in a structured system or is still scattered across spreadsheets and one person’s inbox.

A note on AI-assisted bookkeeping and cross-border data

Some bookkeeping tools now use AI to auto-categorize transactions before they reach a quarterly update, useful for cutting down manual tagging, but worth a moment of caution if the output ends up processed by or shared with an accountant or client based in the EU. The UK isn’t automatically bound by the EU AI Act, but a UK business using an AI system whose output crosses into the EU can end up in a gray area depending on how that data is used downstream. This isn’t a reason to avoid AI-assisted categorization. It’s a reason to know where your data goes after the tool produces its output, and to get a straight answer from a lawyer rather than a blog post if EU exposure looks likely.

FAQ

Do I have to switch to Xero, QuickBooks, or Sage, or can I keep my spreadsheet? You can keep the spreadsheet as long as it’s connected to HMRC through bridging software with no manual retyping in between. For anyone managing more than a handful of transactions a month, switching to a connected platform is usually less work in practice than maintaining a spreadsheet-and-bridge setup correctly.

What happens if I miss a quarterly deadline? HMRC applies a points-based penalty system for late submissions under MTD ITSA, where missed deadlines accumulate points before a fine is triggered. The exact detail depends on your circumstances, so check HMRC’s own guidance for your specific case rather than assuming a fixed grace period.

My income is just under one of the thresholds right now, do I need to act yet? If you’re within a few thousand pounds of