Accounting Software for Making Tax Digital: The Annual Trap

31 January. Once per year, once per working life as a sole trader. Every major accounting software product built before 2019 was optimised around that single date: produce a year-end summary, hand it to your accountant or software tool, file, and forget until the following December. That workflow is not being replaced by Making Tax Digital. It is being supplemented by four additional deadlines per year. And most of the accounting software being sold to you right now for MTD was still fundamentally designed for a world where one annual moment mattered.

Under MTD for Income Tax Self Assessment, which applies to sole traders with income above £50,000 from April 2026 and income above £30,000 from April 2027, you will file on 5 August, 5 November, 5 February, 5 May, and 31 January. Five moments per year. Annual accounting software was built for one. That gap is where sole traders lose time, miss context, and discover that "compatible" and "useful" are not the same word.

The Annual Accounting Habit and Why It Persists

The UK small business accounting software market developed around a straightforward cycle: spend a year running your business, collect your receipts and invoices, reconcile everything in January, file your Self Assessment return. QuickBooks, Sage, FreeAgent, Xero: all built their core products for this rhythm. Their earliest customers were sole traders and small businesses who wanted to know, once a year, whether they had made money. Monthly bank reconciliation was useful but not essential. Quarterly profit estimates were an accountant's tool. Year-end reports were the product.

When HMRC introduced Making Tax Digital for VAT in April 2019, software vendors responded by adding API connections to existing products. The quarterly VAT return had already existed; the software now submitted it digitally rather than via the old portal. The interface barely changed. The same pattern is repeating with MTD for Income Tax. The vendors have built HMRC API connections. The underlying product, in most cases, is still an annual accounting tool. The quarterly submission is a feature. The year-end remains the event.

This is not a cynical framing. It is a description of what you see when you open the dashboards of the most widely marketed MTD accounting software products in 2026. The headline figure is income for the current tax year. The primary report is a year-to-date profit and loss. The notification system sends one meaningful alert per year.

What "MTD Compatible" Actually Guarantees

HMRC maintains a public list of software products that have passed its MTD compatibility testing. More than 200 products appear on that list. As explored in HMRC Compatible Software: What the Label Cannot Tell You, HMRC's compatibility testing measures one specific thing: whether the software can communicate with HMRC's MTD API and transmit data in the required format.

It does not measure ease of use. It does not test whether the categorisation system maps to HMRC's nine self-employment expense codes. It does not assess whether the quarterly workflow is intuitive for a plumber filing their own returns without professional support. It does not check whether the software generates a quarterly profit estimate, which is the figure that tells a self-employed courier how much to set aside before 5 August arrives.

Compatibility means the data leaves the software and reaches HMRC intact. The 200-product list is a quality floor, not a quality ranking.

The distinction matters because choosing accounting software for Making Tax Digital is, for most sole traders, a five-year or longer commitment. The transaction history you accumulate, the expense categories you establish, the quarterly records you file: all create friction against switching mid-mandate. The software you choose before April 2026 will define how you work every quarter for the life of the obligation. Choosing one that treats quarterly reporting as a bolt-on means accepting that bolt-on experience four times per year, indefinitely. As Best Accounting Software for Making Tax Digital: The Exit Test explored, leaving a software system after two or three years of MTD records is technically possible but practically painful for most sole traders.

The Five Events Your Software Needs to Handle

The original Self Assessment regime had one filing event per year. MTD ITSA creates five:

• Quarter 1 (6 April to 5 July): income and expenditure summary due by 5 August
• Quarter 2 (6 July to 5 October): due by 5 November
• Quarter 3 (6 October to 5 January): due by 5 February
• Quarter 4 (6 January to 5 April): due by 5 May
• End of Period Statement: the final annual declaration, due by 31 January

The 31 January deadline still exists. It is now the fifth of five events, not the only one. Q1 to Q4 submissions are provisional estimates of income and expenditure for each three-month period. The End of Period Statement is where you confirm the full year's figures, add any adjustments, and finalise your tax position.

Annual accounting software treats the End of Period Statement as the main event and Q1 to Q4 as minor preparatory steps. The software's core dashboards, primary reports, and notification systems are oriented toward January. A quarterly deadline in August is, in that framing, an administrative interruption rather than a primary obligation.

The consequence for a self-employed electrician is that the software tells them, in considerable detail, how last tax year went. It tells them far less clearly how the current quarter is progressing. Quarter-to-date income is often buried several screens deep, if it exists at all. There is no automatic reminder on 15 July that the Q1 deadline is three weeks away, unless the vendor specifically built one. The estimated tax liability for the current quarter, the number that tells a builder how much to transfer to savings, is a calculation the builder performs manually.

This is not hypothetical. Accountants who worked with sole traders through the MTD ITSA pilot programmes have reported this experience consistently: the software submits quarterly data correctly. It does not help sole traders understand what they are submitting or manage the rhythm with any confidence.

What Quarterly-First Accounting Software Actually Looks Like

A smaller number of software products, including some newer entrants built specifically for the MTD era, treat the quarter as the primary unit of work rather than the year. The differences are visible immediately in the interface.

A quarterly-native dashboard shows the current quarter by default. The headline figures are quarter-to-date income and quarter-to-date expenses, with a simple estimated tax liability for the quarter. The tax year view exists but is not the home screen. You see where you are now, not where you were nine months ago.

Quarter-on-quarter comparison is a standard report, not a custom one you assemble yourself. For a builder whose income varies significantly between summer and winter quarters, comparing Q1 of this year against Q1 of last year is practical context that changes how they plan. Annual-first software surfaces this at year-end. Quarterly-first software surfaces it in August, when the summer figures are still fresh and the pattern still useful.

Deadline reminders are genuinely quarterly. The software sends a notification two weeks before each of the four quarterly deadlines, not a single December reminder about 31 January. If a vendor cannot show you screenshots of four distinct quarterly deadline notifications per year, the reminder system was not designed for the MTD rhythm.

Categorisation uses HMRC's self-employment expense codes as a first-class feature. The nine categories HMRC applies to sole trader expenses, including travel, clothing, office costs, premises, and staff costs, appear in the interface by name rather than buried in a chart of accounts designed for limited companies. Miscategorised expenses can attract HMRC compliance enquiries. Miscategorising consistently over four quarters per year for five years compounds the exposure considerably.

None of these features require unusual engineering. They reflect choices about what the software treats as the primary task. Annual-first products made their choices in a different era and have added MTD compliance as a layer. Quarterly-first products started from the obligation and built outward.

The Test to Run Before You Commit

The HMRC compatibility list tells you which products can submit your data. These questions tell you which ones were built for your actual working pattern:

What is the default view when you log in? If the software opens to a year-to-date summary rather than a quarter-to-date view, it was designed for annual accounts. Worth knowing before you pay 12 months of subscription and navigate four quarters of friction.

Does the software show a quarterly tax estimate? The figure that lets you set money aside before each deadline. If you have to calculate it yourself from raw income and expense figures, the software is leaving the most practically important work to you.

Can the vendor demonstrate the quarterly submission in three steps? A product demo that spends 40 minutes on invoicing and bank feeds, then shows the quarterly submission as a brief final slide, is showing you where the development investment actually went.

What do the quarterly reminders look like? Ask for screenshots. Four distinct quarterly reminders per year plus one End of Period Statement reminder is the baseline for genuine MTD support. A single year-end notification confirms an annual product orientation.

How does the software distinguish Q1 to Q4 from the End of Period Statement? Quarterly submissions are provisional estimates. The End of Period Statement is the final declaration. Software that treats them identically in the interface has not engaged carefully with what MTD ITSA actually requires.

As covered in Sole Trader Accounting Software: Price It by the Hour, the true cost of accounting software is not the monthly subscription. It is the subscription fee plus the time you spend navigating a system that was not built for your actual workflow. A quarterly-native product that takes 20 minutes per quarter costs less in practice than an annual-first product where you spend 90 minutes reorienting every three months.

A Rhythm, Not an Event

The appeal of annual Self Assessment was its compactness: one significant effort per year, then leave it alone. Making Tax Digital removes that pattern. The mandate is a rhythm, four times per year, with a fifth event to close the loop. The accounting software it demands is software that acknowledges that rhythm in its daily interface rather than layering quarterly obligations onto annual architecture.

HMRC has not built that software for free, and the reasons for that absence are examined in Free Tax Return Software: The Government Tool HMRC Never Built. The 200-plus products on the compatibility list range from genuinely quarterly-native tools to annual packages with a submit button appended. The MTD compatibility badge does not distinguish between them.

What distinguishes them is whether they treat 5 August, 5 November, 5 February, and 5 May as primary deadlines alongside 31 January, or as minor calendar interruptions in a product built for year-end. For a sole trader filing without an accountant, that distinction defines the quality of the next five years of tax administration.

If you are selecting accounting software for Making Tax Digital before April 2026, prioritise the quarterly experience over the annual one. The annual experience is broadly similar across most products. The quarterly experience is where the gap between designed-for-MTD and bolted-on-MTD becomes apparent, four times per year, every year, until the mandate changes.