If you're a UK sole trader or landlord who also happens to write code — and a lot of freelance developers are exactly that — you've probably noticed HMRC's Making Tax Digital for Income Tax Self Assessment (MTD ITSA) creeping into your admin this year. It's live for anyone with qualifying self-employment or property income above £50,000, and it changes something that used to be a once-a-year chore into a quarterly one.
The first deadline (7 August 2026, covering the 6 April–5 July quarter) has already passed for most people in scope. The next one — 7 November 2026, covering 6 July–5 October — is the one actually worth planning for now, because it's the first time the "quarterly habit" either sticks or doesn't.
The deadline math is simple, the formula isn't obvious
HMRC's rule is: the 7th of the second month after the quarter ends. That gives you four fixed dates for a standard tax-year quarter split:
- Q1 (6 Apr–5 Jul) → 7 August
- Q2 (6 Jul–5 Oct) → 7 November
- Q3 (6 Oct–5 Jan) → 7 February
- Q4 (6 Jan–5 Apr) → 7 May
You can elect calendar-quarter alignment instead at sign-up, but once you've picked, you're locked into it for the year — so if you're scripting reminders or calendar events, build them from your actual elected quarter type, not the tax-year default.
What "a quarterly update" actually is
This trips people up: it is not a detailed ledger submission. HMRC wants a digital summary — categorised totals of income and expenses for the three-month period, submitted through MTD-compatible software via API. No receipts, no line-by-line transaction list, no supporting documents at this stage. That's a deliberate design choice to keep the quarterly burden light; the detail only matters at the year-end final declaration.
For anyone maintaining their own tracking (a spreadsheet, a small internal tool, a script pulling from a bank feed), the practical implication is that your categorisation scheme matters more than your transaction-level detail. If your expense categories don't map cleanly onto HMRC's self-employment categories (ask yourself: can I produce "total turnover" and "total expenses by type" for this quarter in one query?), you'll be doing manual reclassification work every quarter instead of once a year. Worth fixing before Q2 data entry, not after.
The penalty system has a soft landing — for now
For the 2026/27 tax year, there are no penalty points for a late quarterly submission. That changes from April 2027: each missed deadline after that earns a point, four points trigger a £200 fine, and every subsequent missed deadline after that adds another £200. Points expire after 24 months of on-time compliance. So right now there's real room to get the workflow right without a financial penalty attached to getting it wrong — which is exactly the window to build (or fix) the automation rather than wait.
One practical note on timing
Submission is via API, and the sensible deadline to target isn't 23:59 on 7 November — it's a day or two earlier. API load spikes near statutory deadlines are a known pattern with HMRC's systems (MTD VAT saw the same thing), and "the portal was slow" is not a defence that holds up well in a compliance context.
If you want the fuller walkthrough of the submission process and the HMRC-recognised software options, finance-journal.co.uk has a detailed guide to the MTD ITSA quarterly submission process that covers the mechanics end to end.
Top comments (0)