Most businesses that believe they are MTD compliant are compliant in one narrow sense: they submit VAT returns through software that connects to HMRC’s API. What many have not checked is whether the data behind that submission meets the digital links rule, which governs how information moves from the point it enters the business through to the moment it reaches HMRC.
The digital links rule is where MTD compliance most commonly breaks down. A business can be filing through recognised software and still be non-compliant if any part of its data journey involves a manual transfer, a copy-paste, or a rekeyed figure.
This post explains what the rule requires, where businesses fall short, and what genuinely compliant software looks like underneath the submission layer.
What the Digital Links Rule Requires
HMRC’s MTD legislation requires that where data is transferred, converted, or merged between software programs, the transfer must use a digital link. A digital link is any electronic transfer of data that does not require human intervention to move the data from one place to another.
The rule applies to the entire data journey, not just the final submission. From the point a transaction is first recorded, through any processing, consolidation, or summarisation, to the moment the VAT return figure is submitted to HMRC, every transfer must be digital.
HMRC provides examples of what qualifies as a digital link. Emailing a CSV file that is then imported into another system qualifies. An API connection between two software products qualifies. A formula-linked spreadsheet where data flows automatically between cells or sheets qualifies, provided no manual intervention occurs in that transfer.
What does not qualify is equally specific. Copying a figure from one spreadsheet and typing it into another does not qualify. Printing a report and rekeying the totals into a different system does not qualify. Any point in the data journey where a human reads a number and enters it somewhere else breaks the digital link, regardless of how accurate that entry is.
Where Businesses Most Commonly Break the Link
The digital links rule is not complicated in principle. In practice, many businesses have data journeys with multiple systems, legacy processes, and manual steps that were built before MTD existed and have not been reviewed against the new requirement.
Multi-system record-keeping is the most common failure point. A business that records sales in one system, purchases in another, and then consolidates figures in a spreadsheet for VAT purposes has a data journey with potential manual steps between each stage. If the consolidation involves copying figures rather than an automated transfer, the link is broken.
Spreadsheet-based VAT workings create the same problem. Many businesses use spreadsheets to apply partial exemption calculations, apportion input tax, or adjust figures before submission. If those workings involve manually entering figures from the accounting system into the spreadsheet, the link does not exist at that point, regardless of what happens after.
Branch or location consolidation introduces the issue at scale. A business with multiple sites collecting transaction data locally and then submitting a single group VAT return needs a digital link across every consolidation step. If branch managers email figures to head office and those figures are manually entered into the main system, every one of those transfers breaks the rule.
Bridging software with manual input is another common failure. Bridging software creates a digital link between a spreadsheet and HMRC’s API. But if the figures in that spreadsheet were manually entered from another source, the digital link begins at the spreadsheet, not at the point of original transaction capture. Everything before the spreadsheet is outside the digital chain.
What Genuinely Compliant Software Looks Like
A system that genuinely meets the digital links rule does not have manual transfer points in its data journey. Transactions enter the system once, at the point they occur, and every subsequent step, including summarisation, consolidation, calculation, and submission, happens within or between systems connected by automated digital links.
Single system record-keeping removes the transfer problem entirely. When sales, purchases, payments, and adjustments are all recorded in one platform, there is no inter-system transfer to worry about. The VAT position is calculated from the records already in the system, and the return is generated and submitted from the same environment.
Automated consolidation handles multi-location businesses correctly. Where a business has branches or multiple entities contributing to a single VAT return, the consolidation step needs to happen automatically within the platform, not through a manual collection and rekeying process. The digital link must extend to each contributing location.
In-system VAT workings keep partial exemption calculations and other adjustments within the compliant data chain. If adjustments are made inside the accounting platform using configurable rules rather than in an external spreadsheet, those adjustments are part of the digital record rather than a break in it.
API-connected third-party tools can be part of a compliant chain if the connection is fully automated. A point-of-sale system that pushes sales data to an accounting platform via API, with no manual step in between, maintains the digital link. The key question to ask of any connected tool is whether data moves automatically or whether a human carries it across.
The Audit Implications of a Broken Digital Link
HMRC has powers to inspect MTD records and assess whether the digital links rule has been followed. An investigation triggered by a VAT discrepancy or a compliance review can require a business to demonstrate that its data journey meets the standard.
A business that cannot show an unbroken digital chain from transaction capture to submission faces two problems. The first is the compliance failure itself, which carries penalty exposure depending on whether HMRC classifies the failure as careless or deliberate. The second is the inability to produce a clean audit trail, which makes the investigation longer and more disruptive regardless of the outcome.
Software that maintains a complete, timestamped record of every transaction and every transfer within the system provides the audit trail that makes this kind of review straightforward. Software that relies on external spreadsheets or manual consolidation steps cannot produce the same clarity.
Monesize Core and the Digital Links Rule
Monesize Core records transactions at the point they enter the system and maintains them within a single platform through every subsequent step. Sales recorded in the Sales module, purchases in the Purchases module, and payments processed through the Accounting module all contribute to the VAT position without any manual transfer between systems.
For businesses with branch structures, Monesize Core’s branch model captures transaction data at the location level and consolidates it automatically within the platform. The VAT return draws from every contributing branch without a manual collection step, and the digital link is maintained across the entire data journey.
VAT workings, including partial exemption calculations where applicable, are handled within the Accounting module rather than in external spreadsheets. The calculation sits inside the compliant data chain, not outside it.
Every transaction, adjustment, and submission is recorded in the Activity Logs module with a full timestamp and user attribution. If HMRC ever asks a business using Monesize Core to demonstrate its digital link compliance, the complete record is in the platform, organised and retrievable without reconstruction.
The HMRC module manages the MTD API connection and handles submission directly. There is no bridging tool, no manual export, and no intermediate step between the VAT position calculated in the platform and the return received by HMRC.
ALSO READ: QuickBooks Advanced vs Monesize Core: The Operations Gap
Reviewing Your Current Digital Link Compliance
If your business has not formally mapped its data journey against the digital links rule, the process is straightforward. Start from the point a transaction first enters your records and follow every step through to the VAT return submission. At each point where data moves from one place to another, ask whether that transfer is automatic or whether a human carries the data across.
Any manual transfer is a gap. The question then is whether that gap can be closed within your current system or whether closing it requires a different platform.
For businesses that find gaps, the urgency depends on their current situation. Businesses already within MTD for VAT are operating with those gaps now. Businesses approaching MTD for Income Tax have time to resolve them before the first quarterly submission is due, but that window closes faster than most expect.
The Digital Link Is Not a Filing Feature
MTD compliance is not achieved at the point of submission. It is achieved or not achieved throughout the period, in how transactions are recorded, how data moves between systems, and how the figures that reach HMRC are produced.
Software that connects to HMRC’s API handles the last step. Software that maintains a complete, unbroken digital chain from transaction to submission handles all of them.
See Monesize Core’s Immutable Audit Trail
Monesize Core maintains an unbroken digital link from transaction capture to HMRC submission, with a complete audit trail behind every figure. No manual transfers, no bridging tools, no gaps in the chain.
See how it works end to end. Request a demo.