What HMRC actually means by digital links under MTD

A spreadsheet is digital. So is a figure pasted into an online box. But those two facts do not, by themselves, establish that a bookkeeping process meets Making Tax Digital requirements.

The important question is how information travels from the records you keep to the software that prepares and submits it. A digital link lets the systems transfer data electronically, without someone recreating the figures along the way.

There is also an important legal distinction: the detailed digital-link wording often quoted online comes from MTD for VAT. Income Tax has its own rules. Understanding both prevents a useful principle from becoming an inaccurate blanket claim.

What is a digital link?

For VAT, HMRC defines a digital link as an electronic transfer or exchange of data between software programs, products or applications. Examples include linked spreadsheet cells, CSV imports and exports, and API transfers.

HMRC explicitly says that using cut and paste or copy and paste to move information is not a digital link for this purpose. The detail is in VAT Notice 700/22, section 3.2.1.

The principle is practical: the next stage receives data from the previous stage electronically, instead of relying on a person to reproduce a number accurately.

It does not mean the whole process must run without a human pressing a button. A user-triggered export or upload can still transfer the data electronically.

How does this relate to MTD for Income Tax?

Income Tax obligations come from the Income Tax (Digital Obligations) Regulations 2026 and the relevant HMRC directions. Those govern compatible software, digital records, updates and returns.

HMRC’s Income Tax software guidance expressly allows products that connect to records already held in spreadsheets. It calls these bridging products. It also allows more than one product where the combination works together to meet the person’s obligations. Read HMRC’s explanation of bridging software.

For an Income Tax workflow, electronic imports, exports and supported connections are the sensible way to preserve the relationship between records and submissions. Do not assume that manually typing an annual total into a portal is an equivalent solution.

However, do not treat every paragraph of a VAT notice as if it were legislation governing Income Tax. The reporting detail, permitted simplifications and tax-return process differ. Ask your provider how the actual Income Tax workflow meets the relevant requirements.

Excel is not banned

A spreadsheet can be part of a suitable MTD setup. What matters is the records it holds and how the chosen software uses them.

For example, your workbook might contain one row per transaction, with dates, descriptions, amounts and categories. Formulas can calculate category totals. A compatible product then imports or reads the relevant data and prepares the submission.

The spreadsheet need not look like a large accounting package. It does need to be consistent enough that the right records reach the right place.

Putting a PDF of a handwritten cashbook on your computer is different. It gives you an electronic copy of a document, but not necessarily the structured transaction records needed by the reporting software.

What common transfers mean in practice

Use this table to discuss the process with your provider. It is not a claim that every workflow, in every tax regime, has identical legal requirements.

Worked example: the monthly workbook

Ben is a self-employed consultant who keeps an Excel cashbook. His transaction rows include a date, description, income or expense amount, and category. A summary sheet calculates the totals.

At quarter end, he exports the relevant records and imports the file into his MTD software. He checks the date range, mapping and totals, then reviews the cumulative update before submitting.

There are several separate checks here. The electronic transfer reduces the risk of retyping errors. The mapping review checks that a payment column has not been treated as income. Reconciliation checks that the export included all the intended rows.

Now imagine Ben discovers that the summary formula stops at row 200 but his records extend to row 230. The transfer can be perfectly electronic and still produce an incomplete result.

A digital link protects the movement of information. It does not guarantee the source data or formulas are correct.

Can you still make corrections?

Yes. Digital record keeping does not mean errors become permanent.

Correct the underlying record in the appropriate system, keeping an explanation where useful. Then use the supported process to update the summary or submission. Avoid maintaining an unexplained “correct total” separately from the transactions that supposedly produce it.

For Income Tax, cumulative updates can incorporate earlier record corrections during the year. Further changes after the fourth update may require it to be resent. See HMRC’s quarterly correction guidance.

Tax adjustments are another distinct task. They may be needed when moving from bookkeeping figures to the final annual tax position. Follow the relevant adjustment process rather than treating every legitimate adjustment as a broken link.

What evidence should you retain?

You should be able to explain where the reported figures came from. In practice, retain the source records, relevant import files, supporting documents and submission acknowledgements.

For a self-employed person, the usual business record-retention period is at least five years after the relevant 31 January filing deadline. HMRC explains how long to keep business records.

There is no need to invent a special “digital compliance audit” certificate for every upload. The useful objective is a clear, reproducible trail from the records to the reported amounts, with corrections that can be understood.

Where Avona.app fits

Avona.app’s bridging workflow is designed to import spreadsheet information and prepare MTD updates without asking you to retype totals. The self-service price is £15/month.

Use a representative workbook to check the import. Confirm the dates and columns, compare the totals and review any suggestions from Avona AI. If you maintain the source workbook separately, agree which version is authoritative and how future corrections will be handled.

You can keep a familiar spreadsheet routine. The goal is to give it a dependable route into the software that handles your MTD obligations.