MTD bridging software: the safe choice that has quietly become the risky one
MTD bridging software feels like the cautious option. It lets a practice keep its clients on spreadsheets, submit the numbers HMRC now requires digitally, and avoid the disruption of moving anyone onto cloud accounting software. For VAT, that caution was reasonable for years. For MTD ITSA in 2026, it is worth saying plainly: bridging software is no longer the safe choice. It is the choice that defers a harder problem to a worse moment.
This is an opinion piece, and it is worth being upfront about that. The facts below are genuine. The conclusion drawn from them is a judgement call, and practices weighing this decision should treat it as one input, not the final word.
What bridging software was actually built to do
Bridging software has one job: take numbers that already exist somewhere else, a spreadsheet, usually, and submit them to HMRC in the digital format MTD requires, without the underlying records themselves needing to move anywhere. For MTD for VAT, where the requirement was largely about the final submission format and a digital link between records and return, that narrow job was enough for a lot of practices.
MTD ITSA asks for something structurally different, and this is where the gap starts to show, particularly for the non-standard receipt formats a spreadsheet was never built to capture consistently. Bridging software does not support the transaction-level record-keeping, categorised income and expense tracking, or end-of-period statements that MTD for Income Tax Self Assessment actually requires. It was built to bridge a gap between existing records and a submission format. It was not built to be the record-keeping system itself, and ITSA increasingly assumes the software doing the submitting is also doing at least some of the record-keeping.
Why the timeline makes this urgent rather than theoretical
Since 6 April 2026, sole traders and landlords with qualifying income above £50,000 must keep digital records and submit quarterly updates using HMRC-recognised software. Under HMRC's current published schedule, the threshold is due to drop to £30,000 from April 2027, and to £20,000 from April 2028, though this rollout timeline has shifted before and is worth reconfirming against HMRC's live guidance closer to each date. That is not a distant future scenario. It is a rolling expansion that is already pulling more of a typical practice's client base into scope every year.
In short: the client base bridging software was adequate for a year ago is shrinking every April as the income threshold drops, whether or not a practice has planned for it.
Every client who crosses a threshold needs a decision made about their record-keeping approach, and a practice that has not already worked out its default answer for that decision is making it reactively, client by client, under time pressure, rather than deliberately and in advance.
When bridging software genuinely still works
The honest case for bridging software has not disappeared entirely, and it is worth stating clearly rather than dismissing wholesale. For a client with very low transaction volume and a genuinely well-organised, consistently maintained spreadsheet, bridging software remains a compliant, workable option. Not every client needs cloud accounting software, and forcing a low-complexity client onto a full platform they do not need is its own kind of inefficiency.
A practical test for whether a client genuinely fits this profile: has their spreadsheet needed correction at the point of annual filing in each of the last two years? If the answer is no, and their transaction volume is genuinely low, bridging software is a defensible long-term choice for that specific client, not just a temporary stopgap. If the answer is yes even once, the qualifier does not apply, regardless of how low their volume appears on paper.
The qualifier matters: genuinely well-organised and consistently maintained, not organised well enough to have survived one year-end review. Quarterly submission under MTD ITSA punishes inconsistency in a way annual filing never did. A spreadsheet that gets tidied up once a year before the accountant looks at it is a different proposition from one that needs to be accurate four times a year on a fixed schedule.
Where bridging software becomes the harder problem, not the easier one
For any client above a low transaction threshold, or with income that is likely to cross the next MTD bracket within the next year or two, bridging software creates a specific, compounding risk: the practice ends up managing quarterly digital links from a manual spreadsheet process four times a year, every year, for every client on that setup, rather than solving the underlying record-keeping problem once.
Practices relying heavily on bridging software face growing operational risk as portfolios scale, and for practices managing larger client numbers, relying on spreadsheets creates a backlog problem once quarterly reporting is fully in swing across the client base. The failure mode is not dramatic. It is not a single missed deadline. It is a slow accumulation of quarterly submission overhead that never gets easier, because the underlying process was never actually upgraded, just bridged.
There is also a digital links requirement to keep in mind: bridging software must be digitally linked to whatever record-keeping software or spreadsheet it draws from, with no manual copy-and-paste step in between. In practice, that digital link is often the most fragile part of a bridging setup, breaking silently when a spreadsheet's structure changes, a formula gets edited, or a client renames a tab, all of which are exactly the kind of small changes that happen constantly in a spreadsheet nobody else is checking.
Bridging software vs proper digital records: a quick comparison
| Bridging software | Digital record-keeping | |
|---|---|---|
| What it actually does | Submits existing figures in HMRC's required format | Captures and categorises transactions from the point of entry |
| Best fit | Low-volume clients, disciplined spreadsheets | Most clients above minimal transaction volume |
| Quarterly submission effort | Manual review before every submission, four times a year | Largely automated once set up |
| Digital link fragility | High; breaks silently when spreadsheet structure changes | Not applicable; records are already digital and structured |
| Risk trajectory as thresholds fall | Increases every April as more clients come into scope | Decreases once records are already compliant |
The pattern worth noticing in that table is the last row. Bridging software's risk does not stay flat. It grows every time a threshold drops, because more of a practice's client base becomes exposed to the quarterly review burden bridging software was never designed to make light work of.
Having the conversation with clients still on bridging software
Moving a client off bridging software is a conversation practices often avoid because it sounds like extra work being imposed on the client for the practice's convenience. Framed honestly, it is the opposite: it is removing a recurring quarterly burden from both sides before a threshold change forces it under worse conditions.
A few things make that conversation land better. Lead with the client's own risk, not the practice's preference: a missed or inaccurate quarterly submission caused by a stale spreadsheet link is the client's compliance exposure as much as the practice's workload. Time the conversation around a natural moment, such as a threshold review or year-end, rather than raising it cold. And be specific about what changes for the client operationally: usually less manual admin on their side, not more, once receipts and transactions flow in automatically rather than needing to be entered into a spreadsheet by hand.
The decision a practice actually needs to make
The real question is not whether bridging software is technically compliant. For low-volume clients with disciplined records, it still is. The real question is whether a practice wants to keep making that assessment client by client, reactively, as each one crosses an income threshold, or whether it wants a default position now: which clients genuinely qualify for bridging as a long-term approach, and which ones are being kept on it out of inertia rather than a considered fit.
A practical way to draw that line: if a client's transaction volume, income trajectory, or record-keeping discipline makes it plausible they will need to move to proper digital record-keeping within the next two to three years anyway, moving them now, on the practice's own timeline rather than a scramble around a threshold date, is usually the lower-risk choice. Digital record capture through receipt forwarding and automated extraction removes most of the manual re-entry that made moving off spreadsheets feel disruptive in the first place, which narrows the gap between staying on bridging software and what genuinely MTD-compliant capture software needs to do.
Receiptflow keeps client records genuinely digital and MTD-ready from the point a receipt is captured, rather than bridged into compliance quarter by quarter. Start a free trial and see how it fits your MTD transition plan.
The bottom line
Bridging software is not wrong. It is a narrower tool than the MTD ITSA landscape now assumes, genuinely fit for a shrinking slice of low-volume, highly disciplined clients, and increasingly a source of quiet, compounding operational risk for everyone else still on it by default rather than by deliberate fit. The practices treating this as an active decision now, rather than an inherited default, are the ones who will not be making it under pressure when the next threshold drop pulls in another slice of their client base, a lesson MTD's first year already taught the practices paying attention.
Receiptflow gets clients onto genuinely digital records without the disruption bridging software was meant to avoid. See how it fits your practice.
