MTD for Income Tax: the 2026/27 quarterly deadlines, and how a practice actually keeps a whole client book on track

Most of what's written about Making Tax Digital for Income Tax (MTD ITSA) explains the rules. If you run a UK practice, you already know the rules. What nobody writes about — and what will quietly cost small practices the most time and margin — is the operational problem: how you move an entire book of sole-traders and landlords through four HMRC update deadlines a year, every year, and know on any given Tuesday exactly who's turning into a deadline-week problem.

This article gives you the real dates, the arithmetic of the workload, and a practice-side process you can run without a monthly platform bill. It's written from the practitioner's chair, not the textbook.

Not tax or legal advice. Dates and thresholds below are taken from published GOV.UK / HMRC "Making Tax Digital for Income Tax" guidance current at the time of writing. GOV.UK is the authority — verify there before you rely on anything. Not affiliated with HMRC. AI-assisted, reviewed before publication.

The four 2026/27 quarterly deadlines (and the year-end tax return)

MTD ITSA is mandatory from 6 April 2026 for individuals with qualifying income (self-employment plus UK property, gross) over £50,000. Those clients must keep digital records and send HMRC cumulative quarterly updates, then file the 2026/27 tax return through MTD-compatible software.

For the 2026/27 cycle, the deadlines are:

| Quarter | Period covered | Submit by | |---|---|---| | Q1 | 6 Apr – 5 Jul 2026 | 7 August 2026 | | Q2 | 6 Apr – 5 Oct 2026 | 7 November 2026 | | Q3 | 6 Apr 2026 – 5 Jan 2027 | 7 February 2027 | | Q4 | 6 Apr 2026 – 5 Apr 2027 | 7 May 2027 | | Final declaration / tax return | 2026/27 tax year | 31 January 2028 |

Two things that matter operationally and are easy to miss:

1. Quarterly updates are cumulative within the year. For standard update periods, Q2 is not just July to October; it covers 6 April to 5 October.
2. The 2026/27 tax return is due 31 January 2028 through MTD-compatible software. HMRC's developer materials still refer to a "final declaration"; GOV.UK public guidance frames this as submitting the tax return.
3. There is a 2026/27 penalty easement for quarterly updates. HMRC says no penalty points apply for late quarterly updates during 2026/27, but those updates still need to be sent before the tax return can be submitted. Late tax returns and late payments remain penalty-bearing.

And the regime doesn't stop at £50k. The phasing widens your in-scope book over three years:

• £50,000+ mandated from April 2026
• £30,000+ from April 2027
• £20,000+ from April 2028

So whatever process you build for 2026/27, you'll be running it on a bigger book in 2027/28 and bigger again in 2028/29. This is the single most important planning fact in the whole regime: it's not a one-off migration, it's a permanent, growing, recurring cycle.

The real problem isn't the filing. It's the chase.

Here's the part the rule-summaries skip. Your MTD-compatible software handles the submission — that's a solved problem, and there's plenty of choice. What no filing software gives you well is the answer to the practice-side question:

Across my whole book, who is at risk before the next deadline — right now, today?

Consider the arithmetic. Four quarterly updates plus one year-end tax return is roughly five submission events per in-scope client, per year. A practice with 300 qualifying clients is therefore tracking and chasing on the order of 1,200 quarterly updates a year, plus year-end returns. (That's an illustrative calculation from the deadline structure, not a claim about any particular practice — run your own number: in-scope clients × 4, then add year-end work.)

That's not "file once and forget." It's the same "have you sent your records yet?" conversation, with dozens of people, four times a year, growing each April. By hand, from memory, it doesn't scale — and the failure mode is silent until the week of the deadline.

Why "in progress" is the status that hurts you

When 7 August 2026 arrives, the clients who hurt the quarter won't be the ones flagged Not started — you're already watching those. The ones who hurt you are sitting in In progress. It feels safe. It looks fine on a spreadsheet. It tells you nothing about whether the client has actually moved.

A genuine at-risk list is the intersection of four conditions:

1. In scope for the current cycle (qualifying income over the relevant threshold).
2. Not ready — records or sign-off still outstanding.
3. Deadline close — the meaning of "not ready" changes entirely depending on whether you're 90 days out or 30.
4. Not yet on compatible software, live. Software setup is the long pole. "Chosen but not live" three weeks out is a red flag, not a green one.

A spreadsheet can hold those four columns. What it can't do is watch them for you and surface the handful of clients who tripped all four conditions this week. That watching is the job.

A practice-side process you can run every quarter

The fix is boring, repeatable, and works backwards from each submit-by date. The point is to never be filing on deadline day.

Segment the book two ways, once. By scope band (in scope now / 2027 / 2028 / under) and by readiness. Do this once and maintain it; don't rebuild it every quarter.

Run a T-minus cadence per deadline:

• T-minus 4 weeks (the period has just closed): send the first request to every in-scope client who isn't Ready. Prioritise anyone still on no/unchosen software — that's the long pole.
• T-minus 2 weeks: send a second nudge. Mark records as they arrive; update what you're still waiting on so the next message is accurate. Phone anyone showing At risk.
• T-minus 1 week: prepare and sign off figures for clients whose records are in; submit through your compatible software as they're signed off; final calls to stragglers.
• Deadline week: submit the remainder with comfortable margin; confirm every in-scope client is Ready for this quarter.
• Immediately after: reset readiness for the next quarter and take a backup snapshot.

Assign roles, even in a small team: a lead/principal for threshold decisions, at-risk escalations, fee conversations and sign-off; a preparer for figures and submission; an admin/first-chaser for running the worklist and logging what's arrived. In a sole-practitioner shop, those three hats are just three sections of your personal checklist.

Standardise the chase email. Writing it fresh every time, for every client, four times a year, is where the hours vanish. The same calm template — with the correct deadline date and the specific records you're waiting on merged in — does the job and protects your tone when you're under pressure.

Have the fee conversation before Q1, not after. Five touchpoints a year versus one annual return is a real change in workload. The increase holds far better when you itemise the extra work (four updates prepared and submitted, year-end finalisation, deadline reminders, software-setup help) rather than saying "fees are going up" — and when you raise it before the client has felt the extra chasing, not after.

The honest note on software

Be clear with yourself about the division of labour. Your MTD-compatible software does the filing and the figures — keep using it for exactly that. The cloud practice-management platforms (you'll know the names) also solve the tracking and chasing as part of a wider hosted workflow, with your clients' financial data held on their servers. That's a recurring cost and a data-handling responsibility, and for a sole-practitioner or a small team it may be more than this specific job needs.

The gap that's left — and the one most practices will feel acutely in August 2026 — is practice-side tracking plus client comms: who's at risk, and the words to chase them. That gap can be filled without a subscription and without sending client figures to a hosted platform.

Where to start this week

You don't need to buy anything to begin. You need to know where you actually stand.

[SCREENSHOT: the Chase Engine readiness dashboard — next-deadline countdown, in-scope / ready / at-risk counts, and the chase queue.]

We built a free MTD for Income Tax Readiness Checker that does exactly that: answer a few sharp questions about your client book, your software position and your quarterly process, and get an honest 0–100 readiness score, your specific gaps ordered by severity, and a live countdown to 7 August 2026 — computed entirely in your browser. No login, no email required to see your score, and nothing leaves your device.

→ Run the free Readiness Checker (2 minutes, in-browser)

If the checker shows the gaps are real, the MTD ITSA Chase Engine is the fix for them: a single-page, client-side tool that segments your whole book by threshold and readiness, encodes these four 2026/27 cumulative-update deadlines with live countdowns, flags every at-risk client, and drafts the chase email per client — for a one-off £149 (founding price for the first 100 practices, then £199), with a 30-day money-back guarantee and the Quarterly Cycle SOP and comms scripts included.

→ See everything the Chase Engine does

Whatever you use, build the process before the period you're chasing — not during it. The first deadline doesn't move.

Not tax or legal advice. The Chase Engine and the free checker are practice-management and client-communication tools; they do not submit to HMRC or calculate tax. Verify all dates and thresholds on GOV.UK. Not affiliated with HMRC. AI-assisted content, reviewed before release.