Making Tax Digital for VAT: which client return is built on a broken digital journey?

The VAT return can be submitted on time and still depend on a fragile chain of copied totals, undocumented adjustments and spreadsheets that nobody can reconcile to the ledger. Making Tax Digital for VAT now covers VAT-registered businesses unless an exemption applies; it requires specified digital records, functional compatible software and digital links where information moves between components of the electronic account. The commercial opportunity in 2026 is not to “sign clients up”—HMRC automatically enrols new VAT registrations. It is to find where the data journey fails before the next return or enquiry, then repair one entity and period. This reading shows how an accountant or systems adviser can package a paid VAT data-health review, distinguish acceptable manual entry from prohibited manual transfers inside the digital journey, and build a recurring exception-control service. It also connects this mature obligation to the 2026 rollout of MTD for Income Tax without pretending the two regimes have identical records, thresholds or submission cycles.

Making Tax Digital for VAT requires VAT-registered businesses in scope to keep specified records digitally within functional compatible software and submit VAT returns through the HMRC API. The electronic account may span several products, but information that remains part of it must move through digital links rather than manual copying between software components.

The underlying VAT rules still determine tax point, value, rate, schemes and adjustments. MTD governs the record and submission path; it does not make an incorrect tax treatment correct because software transmitted it successfully.

Digital records include designatory business information and prescribed details of supplies made and received, together with scheme-specific information and the VAT account needed for the return. Original invoices and other supporting documents may still need retention. A scanned document or bank feed is useful only when the required fields and treatment reach the electronic account accurately.

The review should trace sample transactions across sales, purchase, import, reverse-charge and adjustment flows relevant to the client. It records where data originates, who changes it and what evidence supports the return value.

A spreadsheet can form part of functional compatible software when it is connected appropriately to the tools that submit the return. The problem arises when data that remains part of the electronic account is manually copied or retyped between software products. Manual entry from an original source document into the first digital record is a different step.

The architecture map should identify exports, imports, formulas, bridging software and user interventions. “We use a spreadsheet” is neither proof of failure nor proof of compliance; the actual transfer and record purpose decide.

A paid review should reconstruct one VAT period, map the software and digital links, sample high-consequence transactions, reconcile adjustments and issue a correction plan with owners. It should end with a defensible data journey, known exceptions and the next control date—not a generic software recommendation or a promise that HMRC will accept every tax treatment.

The first purchase can focus on one entity and return over ten working days. The accountant distinguishes data-transfer faults, source-record gaps and technical VAT questions. Where disclosure or correction is needed, scope and professional responsibility are agreed separately.

Adjustments should be supported, dated and linked to the return calculation so another competent reviewer can understand their source and treatment. A manual journal may be legitimate, but an unexplained balancing figure that bypasses transaction evidence weakens both MTD traceability and VAT assurance. Recurring adjustments deserve controlled templates and approval.

The exception register records import VAT, partial exemption, fuel scale, bad debt, error correction and other client-specific items. It identifies calculation owner, evidence, period and reversal or recurrence rule.

A software migration, connector update or chart-of-accounts change should be tested against a closed period before it becomes the live VAT journey. The client should reconcile opening balances, tax codes, digital transfers and return boxes, preserve the former evidence and assign responsibility for any difference rather than discover it at filing.

The change record names systems, versions, mapped fields, test population, expected outcome and approval. A successful API connection proves transmission, not that the underlying tax data survived migration correctly.

A buying window appears when a client changes software, acquires an entity, brings bookkeeping in-house, adds imports, uses new VAT schemes or repeatedly submits unexplained adjustments. An HMRC query or failed reconciliation sharpens urgency, but the offer should diagnose the data chain rather than use penalties as a generic fear message.

Accountants can identify triggers inside their own portfolio; software implementers and finance networks provide referrals; search, webinars, email and targeted calls can reach businesses between systems. Qualification establishes filing frequency, software stack, transaction complexity and access to records.

MTD for Income Tax began for qualifying sole traders and landlords above £50,000 from 6 April 2026, with lower thresholds planned for 2027 and 2028. Existing VAT digital records may provide useful infrastructure, but the income-tax regime has different eligibility, records and updates. Accountants should assess overlap without selling one configuration as universal.

This creates a portfolio conversation: which clients already have trustworthy digital source data, which depend on quarterly repair, and which software can support both obligations? The VAT review becomes evidence for a broader decision, not a forced cross-sell.

The recurring service should review exceptions, test digital links after system changes, reconcile return movements and maintain evidence for material adjustments. It earns a recurring fee where transaction volume and change justify active assurance. It is not a monthly charge for pressing submit or a guarantee against errors, enquiries or penalties.

The rhythm can follow each VAT period, with deeper testing after acquisitions, new schemes or integrations. Reporting should show which issue recurred, which control prevented it and what remains outside the accountant’s scope.

The offer is ready when the partner can define a VAT client cohort, reconstruct one period, separate systems work from tax advice and maintain controls within filing deadlines. GetFishNet’s free eligibility test checks the trigger, evidence, first-purchase value and recurring capacity before recommending acquisition channels.

The opportunity is not the existence of MTD; it is the cost of an unreliable data chain. If the partner cannot access source records or influence the bookkeeping process, the campaign should narrow or stop rather than promise transformation.

Authorities cited: HM Revenue & Customs; UK Legislation. Dated references remain in the private source register.