Managing MTD Quarterly Submissions for Multiple Clients: A Practice Workflow Guide

The operational reality of quarterly submissions across a client base

MTD quarterly submissions for multiple clients is not a compliance knowledge problem for most practices at this point. It is a workflow problem: the same four-times-a-year cycle, run simultaneously across every client in scope, without the natural slack an annual deadline used to provide. This is the practice-management side of that cycle, not what MTD is or why it applies, and it assumes your clients are already registered and connected rather than covering that step again here.

The quarterly structure at a glance

The 'figures reported' column is not a footnote. Each period covers only the months since the last update, but what actually gets reported each time is the running total for the tax year so far, which is the detail that most shapes how the whole workflow needs to run, since every submission after the first is built on top of everything that came before it.

The deadline structure that actually drives your calendar

Quarterly updates are due 7 August, 7 November, 7 February, and 7 May, each covering a period ending the previous month, plus the existing 31 January Final Declaration. Four submission points a year, evenly spread, replacing what used to be a single annual crunch with a recurring one.

In short: MTD does not reduce your total annual workload, it redistributes it into [four smaller, more frequent deadlines](https://receiptflow.co/blog/making-tax-digital-receipt-management-accountants), and a practice still running an annual-crunch operating rhythm against a quarterly obligation is the single biggest structural mismatch causing avoidable stress.

The cumulative basis trap: the detail that catches practices out

Each quarterly update reports running totals for the tax year to date, not figures for that quarter in isolation. A Q2 submission does not report Q2 alone; it reports the full year to date including Q1. This has a specific, practical consequence for a multi-client workflow: an error in an early quarter does not stay contained to that quarter's submission. It propagates forward into every subsequent submission until it is caught and corrected, because each one is built on the cumulative figure.

For a practice running dozens of clients through this cycle, this changes what 'catching an error early' actually means. A mistake in a Q1 submission that goes unnoticed until Q3 does not just need fixing in Q3. It potentially means the Q1 and Q2 submissions were also built on the wrong cumulative base, which is a meaningfully bigger correction than fixing a single quarter's figures.

Calendar quarters vs standard quarters

If a practice's bookkeeping naturally runs on calendar months, standard MTD quarters, running from the client's own accounting reference dates, are not the only option. Calendar quarterly periods can be elected in software instead, running 1 April to 30 June, 1 July to 30 September, and so on, with the same 7 August, 7 November, 7 February, 7 May submission deadlines. The election is made in software the first time a client submits, and once set for a tax year, applies to all four updates for that client.

For a practice managing many clients, standardising as many clients as sensibly possible onto the same quarter structure, calendar quarters specifically, where the client's own accounting timing allows it, meaningfully simplifies the workflow. Reviewing forty clients against forty different quarter start dates is a fundamentally harder scheduling problem than reviewing forty clients against one shared quarter structure.

A worked scenario: 40 clients, four deadlines

Take a practice with 40 clients in MTD ITSA scope. Spread evenly, that is roughly 10 clients whose data needs collecting, reviewed, and submitted in each of the four quarterly windows, but in practice the distribution is rarely even, because clients on the same accounting basis or with similar business patterns tend to cluster around the same review timing. Without deliberate scheduling, a practice can end up with 25 clients converging on the same few days before a single deadline, and five clients quietly forgotten until the following quarter's tracker review surfaces the gap.

The fix is not adding capacity to handle a bigger crunch. It is spreading the same 40 clients more evenly across the weeks available in each quarter, using the staggered collection approach below, so no single week absorbs a disproportionate share of the total workload.

Communicating the new cadence to clients

A meaningful share of the workflow burden originates with clients who have not internalised that quarterly means quarterly, not four smaller annual reminders. A client used to a single end-of-year data handover will, by default, try to apply that same rhythm to MTD unless the practice actively resets the expectation.

This is worth addressing directly and early, not left to be learned the hard way after a missed first-quarter deadline. A short, standard communication at the start of the client relationship's first MTD year, explaining the four dates, what is needed from them and by when, and what happens if data arrives late, sets the expectation once rather than requiring it to be re-explained ad hoc every quarter.

A quarter-by-quarter task checklist

A consistent internal checklist, run identically each quarter regardless of which one it is, removes the need to reconstruct the process from memory four times a year.

• Week 1 of the quarter's collection window: send the standard data request to all clients due that quarter, referencing the specific deadline date.
• Week 2: follow up individually with any client who has not yet responded, rather than a single blanket reminder to everyone.
• Final week before the internal deadline: complete bookkeeping for all responded clients; flag any still-outstanding client for direct escalation.
• Internal deadline (ahead of the 7th): all completed submissions reviewed; any client still missing data flagged as a specific risk, not a routine follow-up.
• HMRC deadline (the 7th): submissions filed; tracker updated to reflect the completed quarter before the next quarter's window opens.

Handling amendments and exceptions mid-year

Because of the cumulative basis, an amendment discovered after a quarter has already been submitted is not a contained, one-off correction. It needs to flow through into the next submission's cumulative figure, and the practice needs a clear record of what was amended, when, and why, both for its own audit trail and to explain the change if a client or HMRC ever queries a later quarter's numbers.

A simple discipline handles most of this: any amendment discovered after submission gets logged in the same tracker used for the core workflow, with a note on which subsequent quarter's figures it affects, rather than being corrected quietly in the background with no record of what changed or why.

Building a repeatable four-times-a-year cycle

Set an internal deadline ahead of the actual one

Finishing bookkeeping by mid-month, ahead of the 7th-of-the-following-month HMRC deadline, leaves genuine review time before submission, rather than submitting on the deadline itself with no buffer for catching an error. Last-minute submissions are consistently where mistakes creep into a rushed cumulative figure.

Stagger client data collection, do not batch it all at once

Requesting receipts and records from every client in the final week before a deadline recreates exactly the crunch MTD's quarterly structure was meant to spread out. A staggered collection schedule, opening the request window early in the quarter and following up progressively rather than in one push near the deadline, keeps the workload closer to genuinely level across the quarter.

Track submission status explicitly, per client, per quarter

A simple, shared tracker, client, quarter, data collected, bookkeeping complete, reviewed, submitted, removes the reliance on any individual team member's memory of where forty or more clients each stand at any given moment. This matters more under MTD's cadence than it did under an annual deadline, because the tracker has to be rebuilt and cleared four times a year, not once.

Use the first year's soft landing deliberately, not as a safety net to ignore

HMRC's current published guidance sets out a twelve-month soft landing on late-update penalty points for taxpayers joining MTD ITSA from April 2026, meaning late quarterly updates in the 2026/27 tax year are not expected to trigger penalty points, though the detail is worth reconfirming against HMRC's live guidance since this is actively-rolling-out policy. This is a one-off concession for the first year only, and the practical use of it is not relaxing the internal process because penalties are not yet biting. It is using the lower-stakes first year to genuinely stress-test and refine the workflow before the concession ends and the same process runs under real penalty risk.

Receiptflow keeps client receipt data MTD-ready ahead of each quarterly submission. Start a free trial and see how a consistent capture workflow removes most of the data-collection bottleneck described above.

Choosing tools that actually support this cadence

A tracking spreadsheet is a reasonable starting point, and for a smaller client list it may remain entirely sufficient, though it says nothing about whether the software each client actually submits through is the right fit for how your practice runs this cycle. As the client count grows, the limitation of a manually maintained tracker becomes less about whether it can technically hold the data and more about whether anyone reliably keeps it updated in real time, four times a year, without it becoming stale between deadlines.

The more durable fix is a receipt and document capture workflow that keeps client records genuinely current between deadlines, rather than data that only gets consolidated and reviewed in the days immediately before each submission. When client receipts and invoices are captured continuously as they occur, the quarterly submission becomes a review-and-file step against records that are already largely complete, rather than a data-collection sprint that starts from scratch each time the deadline approaches.

What a mature quarterly workflow looks like a year in

A practice that has genuinely adapted to the quarterly cycle, rather than just surviving four annual-style crunches a year, has three things in place: client data arriving continuously through the quarter rather than in a pre-deadline scramble, a shared tracker that makes status visible without anyone having to ask, and an internal deadline with real review time built in before the actual HMRC date. None of these are complicated individually. Together, they are the difference between MTD quarterly submissions becoming a manageable, repeatable rhythm and becoming four smaller versions of the old year-end crunch, four times more often.

The bottom line

Managing MTD quarterly submissions across a client base is fundamentally an operational scheduling problem, not a compliance knowledge one. The cumulative basis means errors compound forward if not caught quickly, standardising quarter structures where possible simplifies practice-wide scheduling, and a staggered, tracked collection process is what actually prevents four smaller crunches from replacing the single annual one MTD was meant to improve on.

Receiptflow keeps client receipt data MTD-ready ahead of each quarterly submission. See how it fits your practice workflow.