Every accountant knows the January scramble.
Then January arrives, and you are phoning, emailing, and sometimes sorting through a shoebox of receipts before the 31 January deadline. You spend October hoping. November nudging. December chasing properly.
It is a rough few weeks. Most practices get through it on goodwill, overtime, and strong coffee. But it happens once a year.
Making Tax Digital for Income Tax changes that.
From 6 April 2026, this applies to sole traders and landlords registered for Self Assessment. They now have to file quarterly updates too, not just the annual return. The rule kicks in if your qualifying income is over £50,000, based on the 2024-25 tax year.
The 2025-26 return is still due on 31 January 2027, running alongside the new quarterly cycle. For the full phase-in across all three thresholds, read the MTD income tax timeline. And the annual return does not disappear.
Four fixed dates a year, not one January
The quarterly updates land on 7 August, 7 November, 7 February and 7 May. It is four fixed filing dates a year, owed to HMRC, for every client in scope, without end. That is not a loose target.
A job like that is not a once-a-year scramble any more. You can staff it, schedule it, measure it, and improve it, the same way you already run payroll or VAT returns. It repeats on a fixed calendar. It carries a real penalty for missing it. It has a clear output.
The habits that got you through one January will not survive four Augusts, Novembers, Februaries and Mays in a row. A habit built for one push a year now has to work four times, back to back. There is no long autumn run-up left to hide the slippage in.
What the workload really looks like
Do the maths on a mid-sized practice.
A client with a trade and a rental property files separately for each, eight quarterly submissions a year instead of four. One client with a single trade means four quarterly updates plus the year-end return, instead of one annual cycle.
At practice scale those totals climb fast, and they sit on top of your existing January Self Assessment peak, not instead of it. We work through the full staffing maths, client book to deadline spikes, in our capacity piece.
A workload that size cannot run on a partner remembering to chase someone about their fuel receipts. Four times a year, on the same four dates, for every client in scope, you need a clear process. Who is due. Who has been chased. Who has replied, sorted, checked, filed.
What it costs to leave this unmanaged
HMRC's penalty system for missed quarterly updates runs on points. One point per missed submission. A £200 penalty once a client reaches four points. Points only clear after 24 months with no further miss.
For 2026-27, HMRC is running a soft landing.
No penalty points apply for a late quarterly update in that first year. But late-return and late-payment penalties on the annual side still apply as normal.
That gives you a year to build the chase process properly, before points start counting for real. It is not a reason to leave it until year two.
Map the chase process, step by step
Some of this work a machine can do reliably. Some of it needs a person's judgement. Every practice needs a check between the two.
An agent can work out who is due, from the client list, income sources, and the fixed deadline calendar. It sends the first, second and third reminder on schedule, through the channel each client reads. It also takes a first pass at sorting bank transactions and uploaded receipts into standard categories.
An AI agent is a computer worker that does one job for you. We build them, run them, and check their work every month.
Always needs a person: deciding whether an odd transaction is business or personal. Chasing a client who has gone quiet after three automated reminders needs a phone call and a relationship, not another email. Signing off the quarterly update before it reaches HMRC.
The check in between: every transaction an agent sorts gets checked, against a sample or a threshold, before you trust it. Reminders that go unanswered move up to a named person at a fixed point, not forever. Software can spit out a number. That does not make the number right.
And the process reports on itself. Refreshed before each of the four deadlines, not discovered during deadline week. Which clients cleared on the first reminder. Which needed a phone call. Which needed all three.
That last part, the report, is what turns four deadlines a year from four annual panics into something you can see coming. It is the same idea behind our Reports service. We track trends over time, not judge each month alone. Problems show up before they become a missed filing, not after. We agree the thresholds up front.
We are not tax advisers
BlooSprout builds and runs the practical machinery behind work like record chasing. We are not tax advisers, and nothing here is tax advice.
For the current rules on scope, thresholds and deadlines, read HMRC's own guidance on making tax digital for income tax. It is worth reading directly before you set your process around it. We do.
Build the process before the first deadline finds the gaps
Some practices will feel MTD as a burden. Those will be the ones still running record chasing as a January habit, stretched thin across four dates a year.
Others will not feel it that way. Those are the ones who mapped the process once. They decided what to automate, where a person needs to check it, and who owns the chasing when a client goes quiet. Before 7 August arrives and tells them anyway.
We will look at your process. We will not sell you a tax opinion. You already know where your own chase process leaks. Bring that to the call.