Spreadsheets Plus Bridging Software for MTD ITSA: The Digital-Link Mechanics

A landlord running on a longstanding spreadsheet often resists swapping to a full SaaS accounting suite for MTD ITSA, and the resistance is reasonable. Their spreadsheet works, the data flow is familiar, the back-history is intact, and the migration cost (data cleanup, retraining, paying for a subscription) is meaningful relative to the underlying compliance need.

The good news: spreadsheet-plus-bridging is a permitted MTD ITSA route. The catch: every data transfer between cells, sheets, the bridging tool, and HMRC's API must satisfy the digital-link rule. This page walks the rule, the mechanics, the spreadsheet column discipline, a compliant-versus-non-compliant worked example, the choice of bridging vendor, and the question of when staying on a spreadsheet still makes sense versus when a full SaaS suite saves the friction.

What HMRC actually allows

House position §19.6 confirms that MTD ITSA permits HMRC-recognised compatible software, with two valid forms: a full accounting-suite product (Xero, FreeAgent, QuickBooks, etc) that handles record-keeping and submission together, or a spreadsheet paired with HMRC-recognised bridging software that handles only the submission step. House position §19.14 covers the spreadsheet-plus-bridging route specifically, adopting HMRC's digital-link rule from MTD for VAT (notice 700/22) into the MTD ITSA context.

The legal anchor is FA 2017 Sch A1 paragraph 8, which obliges the taxpayer to keep records in electronic form. The phrase "electronic form" does not specify any particular software; what HMRC has insisted on (through notice 700/22 originally and now via §19.14 for ITSA) is that data moves between systems digitally rather than by hand.

The acceptable forms of digital link, per HMRC and §19.14, are:

• Cell references and formulae within a workbook (including across sheets and across linked workbooks).
• CSV or XML exports from one tool, ingested by another tool without manual edit.
• API transfers between systems.
• Automated extracts via script.
• Bank-feed integrations that import transactions directly into the spreadsheet or accounting tool.

The unacceptable forms are:

• Copy-paste, cut-paste, paste-special-values.
• Manual re-keying of a number from one location to another.
• Reading a figure from a screen and typing it elsewhere (screen-reading).
• Editing a CSV by hand between export and import.

That distinction (formulaic versus manual) is the single most important compliance discipline for a spreadsheet-power-user landlord under MTD ITSA.

What bridging software actually does

Bridging software is a thin API conduit. It does not store your records, it does not perform bookkeeping, and it does not categorise transactions on your behalf. What it does:

1. Reads a defined range of your spreadsheet (or accepts a CSV export).
2. Maps each spreadsheet column to a corresponding HMRC MTD ITSA API field (income line, premises running costs, repairs, finance charges, etc).
3. Authenticates against your Government Gateway credentials.
4. Submits the quarterly update via the MTD ITSA API endpoint.
5. Returns a confirmation receipt and writes an audit trail.

The data flow is linear: spreadsheet → bridging tool → Government Gateway authentication → HMRC API → confirmation. The bridging tool is the translator at the API boundary; your spreadsheet remains the system of record for everything else.

Pricing for bridging software ranges from free or near-free for the simplest tools (typically with limits on the number of submissions or property count) up to roughly £50 to £150 per year for vendors targeting landlords specifically. Bridging is cheaper than full SaaS accounting because the vendor is doing much less work.

Spreadsheet column discipline: mapping to SA105 categories

The discipline that converts a working spreadsheet into an MTD-ready spreadsheet is the column structure. Each row is a transaction; each column captures one attribute of that transaction. The columns that matter for MTD ITSA, mapped to the SA105 categories the API expects, are:

• Date (transaction date, not bank-clearance date)
• Property reference (or address, or short code)
• Counterparty (tenant, supplier, agent, etc)
• Category (one of: gross rental income, premises running costs, repairs and maintenance, finance charges, legal-management-and-professional fees, cost of services, other property expenses)
• Amount (gross, in pounds and pence)
• VAT (where applicable, typically only for commercial property landlords)
• Notes (a short description, useful for audit trail)

A summary sheet rolls up by category and by quarter, driven entirely by formulae (SUMIFS, FILTER, or pivot-table equivalents). The bridging tool reads either the transactions sheet filtered by quarter, or the rolled-up summary, depending on the vendor's preference.

Joint-owner spreadsheets add an ownership-share column (50/50, 70/30, or whatever the beneficial-interest split is) and a derived "your share" column driven by =Amount * Share. The bridging tool then reads the your-share column rather than the gross amount. This pattern keeps the underlying source clean while producing per-owner figures correctly.

A compliant versus non-compliant worked example

Take Khan, a landlord with two BTLs in Reading and Slough, who runs his bookkeeping on an Excel workbook he built himself in 2018.

Compliant flow:

• Sheet 1 (Transactions): line-by-line entries for every rent receipt and every expense. Columns: Date, Property, Counterparty, Category, Amount, Notes.
• Sheet 2 (Quarterly Summary): formulae like =SUMIFS(Transactions!E:E, Transactions!D:D, "Repairs and maintenance", Transactions!A:A, ">="&DATE(2026,4,6), Transactions!A:A, "<="&DATE(2026,7,5)) that roll up Q1 totals by category.
• Sheet 3 (Bridging Export): formulaic references to Sheet 2, formatted in the column order the bridging vendor requires. Khan exports this sheet as CSV at quarter-end and imports into the bridging tool.
• Bridging tool reads the CSV, validates, submits via the MTD ITSA API. Submission receipt logged.

Every step in that flow is a digital link. The CSV export is deterministic (File > Save As CSV with no edit between export and import). The formulae in Sheets 2 and 3 are unambiguous digital links from the source data. The bridging tool's API transfer to HMRC is the final digital link.

Non-compliant flow:

• Sheet 1: same line-by-line transactions.
• Quarterly summary: Khan opens the file at quarter-end, looks at the autosum in the status bar for each category, and types the four quarterly totals into a new "Q1 totals" sheet by hand.
• Khan emails the Q1 totals to his bookkeeper, who types the numbers into the bridging tool's web form.

The hand-typing in step two is manual re-keying. The web-form data entry in step three is screen-reading plus manual entry. Both break the digital-link rule. The submitted figure might match what the transactions show, but the path it took to get there is non-compliant under §19.14.

The fix on Khan's workbook is trivial: replace the typed quarterly totals with =SUMIFS(...) formulae, and have the bookkeeper export the summary as CSV and feed it to the bridging tool directly. Same numbers, same submission, compliant data flow.

Common pitfalls to avoid

The patterns we see most often in landlord spreadsheets that need fixing before April 2026:

• A "summary" sheet that someone updated monthly by typing totals from the transactions sheet. Replace every typed cell with a formula.
• Copy-paste of last-month's structure into next-month's tab, with figures overwritten. Replace with structured formulae that reference dynamic ranges.
• Manual VAT splits where the spreadsheet has a gross figure and the VAT is derived by mental arithmetic. Replace with an explicit VAT column and formulaic gross / net derivations.
• Sheets that load data from a bank statement by manual entry. Replace with a bank-feed integration (where the bank supports it) or a deterministic CSV import from the bank's online portal.
• Spreadsheets stored on a personal laptop with no backup. Move to a cloud-hosted location (OneDrive, Google Drive, Dropbox business) so the digital-record obligation under FA 2017 Sch A1 paragraph 8 plus the 7-year retention under TMA 1970 s.12B both hold.

None of these fixes require a software change. They are spreadsheet discipline corrections, performed once, and held thereafter.

Choosing bridging software (without naming names)

The gov.uk MTD ITSA compatible-software list is the authoritative source for which bridging vendors are HMRC-recognised. The list filter for "spreadsheet bridging" or "Excel" identifies the products built for the spreadsheet-power-user landlord.

Evaluation criteria worth applying:

• HMRC-recognition: appears on the gov.uk MTD ITSA list specifically (not just the MTD VAT list).
• Spreadsheet format: handles Excel and Google Sheets, or only one of them (matters if you ever migrate).
• Property-level reporting: maps your columns to per-property figures correctly, especially if you have joint ownership splits.
• Pricing model: per-submission, per-quarter, or annual flat fee (annual flat fee is typically the cheapest for active landlords).
• Audit trail: maintains a submission log, retrieval of past submissions, ability to re-export the data flow for an HMRC enquiry.
• Support: a real-person support channel matters in the first one or two quarters as the workflow beds in.

We deliberately do not name specific vendors in this page, per §19.14, because the gov.uk register changes (vendors enter and leave the list as they obtain or lose certification, and product names change in mergers). The decision should be a snapshot of the current register, not a pointer to a name on an editorial page that might be stale.

When spreadsheet plus bridging is the right answer (and when it is not)

Spreadsheet plus bridging is the right answer when:

• Portfolio is small (one to three properties) and the existing spreadsheet works.
• The landlord's bookkeeping discipline is high (transactions entered weekly or monthly, not annually).
• The annual subscription cost of a full SaaS suite is meaningful relative to the rental profit.
• There are no joint-ownership complications that would benefit from a SaaS product's per-owner reporting.
• The landlord is comfortable with formulae and structured workbooks.

A full SaaS accounting product is the right answer when:

• Portfolio is larger (four or more properties), where the manual maintenance of category formulae and bank-feed reconciliation in a spreadsheet exceeds the SaaS subscription.
• The landlord has joint ownership and the SaaS product handles ownership splits automatically.
• The landlord uses a bookkeeper or accountant who needs simultaneous access to the records.
• The bookkeeping discipline historically has been weak, where a SaaS product's bank-feed-driven workflow imposes structure the landlord has not maintained voluntarily.
• The landlord values the consolidated view of rental P&L per property that SaaS products surface natively.

Our companion guide on choosing software by landlord scenario walks the scenario-led decision in more depth, with a five-question decision tree.

Pre-mandate testing protocol

In the run-up to 6 April 2026 (or to the April 2027 / April 2028 phased threshold drops), the protocol that catches issues before they bite is:

1. Audit the workbook. Open every formula and trace its source. Identify any cell where the value is typed rather than derived. Fix.
2. Confirm the CSV export is deterministic. Open the workbook in a different version of Excel (or Google Sheets) and verify the export produces an identical CSV. Some products handle locale (commas vs periods, date formats) inconsistently and corrupt the export.
3. Sign up with the chosen bridging vendor in pilot mode. The HMRC MTD ITSA pilot has been open since April 2025; many bridging vendors expose pilot-API connections for testing.
4. Run a parallel quarter. Take Q3 or Q4 of the 2025/26 tax year, run it through the spreadsheet, export, import to bridging, submit via the pilot. Verify the submission matches your spreadsheet figures.
5. Run a parallel year-end. Test the end-of-period statement and final declaration submissions as well as the quarterly update. The bridging tool typically handles all three; verify each independently.
6. Save the audit trail. Keep the bridging tool's confirmation log alongside the workbook. HMRC compliance enquiries reach back six years; the digital trail is your evidence base.

Landlords who run this protocol in autumn 2025 land in April 2026 with a tested workflow. Landlords who delay until February or March 2026 are running into the bridging vendors' busiest onboarding window with the least margin for fixing issues.

Where this page sits

This page is the operational digital-link mechanics page for landlords on the spreadsheet-plus-bridging route. It does not re-walk the strategic software-decision question (covered in our choosing software by scenario page), the headline MTD ITSA changes (covered in our bucket overview page), or the digital-records evidence discipline more broadly (covered in our digital records, receipts, and bank feeds page).

For joint owners with the spreadsheet route, the joint-owner mechanics are covered in our joint-owner quarterly filing page, where the per-owner share-derivation column pattern carries through to the bridging tool the same way.

Source authority for the positions on this page: house position §19.14 (Wave 4 digital-link extension, locked 2026-05-23) and §19.6 (software requirements); HMRC notice 700/22 (MTD for VAT digital-link rule, adapted to ITSA); gov.uk MTD ITSA compatible-software list; FA 2017 Sch A1 paragraph 8 (digital-records obligation); TMA 1970 s.12B (7-year retention).