Most MTD ITSA guidance answers the question of what records to keep at the schematic level. Keep digital records of income and expenses. Keep them for the retention period. Use HMRC-compatible software. Done.

That leaves the operational evidence layer underspecified. What happens when HMRC opens an enquiry six years after the year in question? Which records do they ask for? What does an MTD-compliant audit trail actually look like in practice? When is a phone photo enough? When is a bank feed enough? When does cash blow up?

This page answers those questions. It is the evidence-discipline page, complementing rather than re-walking the high-level MTD record-keeping overview and the digital-link mechanic for spreadsheet-plus-bridging users covered in our spreadsheets and bridging software page.

What counts as a digital record, in four categories

House position §19.16 splits the answer into four categories.

Accepted unambiguously:

  • App-captured receipt photographs with date stamp and software audit trail (the photo is taken inside the MTD software, not on the phone camera roll).
  • Bank-feed CSV or API extracts read directly into the software (auto-categorised by the software, then reviewed and confirmed by the landlord or accountant).
  • Accounting-software entries originated within the software (a manual journal entry with appropriate detail).
  • Spreadsheet cells where the value is derived by formula or cell reference from a source transaction, and the workbook is preserved with the audit trail (per the digital-link rule).

Accepted with caveats:

  • Photographs of paper receipts taken outside the MTD software, then uploaded. Acceptable on goodwill but weaker at enquiry; recreate via app-capture where possible.
  • Email-attached invoices from suppliers, forwarded into the software's inbox-capture function. Acceptable; the email metadata provides a partial audit trail.
  • Cash transactions paired with digitised receipts (photo) plus a corresponding bank withdrawal entry. Acceptable; the chain runs cash-out → photographed receipt → categorised expense, all in the digital record.

Not accepted:

  • Shoeboxed paper receipts without digitisation. The MTD obligation is for electronic records.
  • Unstamped photographs without source software audit trail (just phone snaps with no metadata or linkage).
  • Written notes from memory at year-end reconstructing what happened during the year.
  • Verbal explanations of transactions without supporting documentation.

Marginal cases:

  • Bank statements downloaded as PDFs and held as PDF files (with no software ingestion). Marginal: the PDF is a digital file, but it is not a digital record in the MTD sense (no audit trail, no per-transaction categorisation). Treat as supplementary evidence to a proper digital record, not as the record itself.
  • Receipts photographed via a third-party app (e.g. a generic OCR tool) that does not integrate with the MTD software. Marginal: the photo plus OCR output is more than a phone snap, but the audit trail is in a different system. Bridge via CSV export from the OCR tool into the MTD software with a formulaic link.

Receipt capture mechanics

The clean pattern: paper receipt arrives, you open your MTD software, the software's receipt-capture function opens the phone camera, you photograph the receipt, the software's OCR extracts the date, amount, supplier, and suggests a category. You confirm or adjust the category, save, and the receipt sits in the software's archive linked to the transaction it relates to.

Two operational notes:

  • Don't batch-photograph at week-end or month-end. The MTD requirement is for contemporaneous records (FA 2017 Sch A1 paragraph 8). Best practice is to photograph each receipt at the point of transaction, in the moment, with the software's capture function. A weekly batch is operationally acceptable; a monthly batch is on the boundary; an annual batch (the year-end shoebox style) does not pass.
  • The original paper can be discarded once captured. HMRC explicitly accepts that the digital record supersedes the paper. This is a meaningful operational change from pre-MTD practice (where paper was the primary record and the spreadsheet was supplementary).

Bank feeds: the auto-categorisation discipline

Bank-feed integrations are the most powerful productivity feature of MTD software. They pull every transaction from the connected bank account into the software in real time, suggest a category for each, and let you confirm or adjust.

The discipline to apply:

  • Connect the bank feed at least one quarter before the mandate date. Bank-feed integrations typically have a setup latency (the bank's open-banking handshake can take days to weeks to authorise; the historical-transaction backfill can take longer).
  • Review every auto-categorisation before submitting the quarterly update. The algorithm is good but not infallible. Mortgage interest is a particular trap (banks describe mortgage payments inconsistently; the software sometimes categorises mortgage payments as "loan" rather than "finance costs").
  • Reject the auto-categorisation when wrong. Do not accept it and rely on adjusting at year-end. The quarterly update is the submission; the year-end is the reconciliation, not the place to undo quarterly errors.
  • Pair every transaction with supporting documentation. A bank-feed entry on its own is not sufficient evidence (it shows the cash movement); the invoice or receipt is the categorisation evidence.

The quarter-boundary timing question:

A tenant pays rent on 5 April. The payment relates to the April-to-July let period. Under property cash basis (the default for unincorporated landlords under FA 2017), the rent is income in the quarter the cash arrives. 5 April lands in Q4 of the prior tax year; 7 April lands in Q1 of the new tax year. The MTD quarterly update reflects whichever quarter the payment hit the bank.

Landlords on the accruals basis (a minority, typically those above the £150,000 turnover threshold or who elect into accruals) accrue the rent to the period it relates to, not the period it was received. The MTD update reflects the accruals position. Software handles the basis-choice differently; verify your software is set to the correct basis at setup.

The cash-receipt edge case

Cash is the operational edge case. A tenant pays a deposit refund in cash. A contractor accepts cash for a small repair. A managing agent reimburses petty expenses in cash.

The discipline:

  • Write a receipt for the cash transaction (or accept the contractor's hand-written receipt).
  • Photograph the receipt via the MTD software's capture function immediately.
  • Record the cash withdrawal (or deposit) on the bank-feed side as a separate entry, categorised as cash movement.
  • Record the categorised expense (or income) on the cash side, linked to the photographed receipt.

This pattern (cash out, photographed receipt, categorised entry) creates the audit trail HMRC expects. The cash transaction itself remains legal and acceptable; what changes under MTD is the evidence chain that must surround it.

Landlords whose pre-MTD practice was to handle small cash transactions informally (without receipts, without tracking) must change the practice. The change is not in what counts as taxable; the change is in what HMRC requires you to be able to evidence.

Want this checked against your specific situation?

Drop your email and a one-line summary. We reply within 24 hours, no phone call needed.

Seven-year retention

TMA 1970 s.12B sets the statutory retention minimum at five years from the 31 January submission deadline (which equates to six years from the end of the tax year of assessment for self-employed and landlord taxpayers). House position §19.16 adopts a seven-year target as the practical retention floor, recognising that:

  • HMRC's discovery time limits run to four years (standard), six years (careless), or twenty years (deliberate).
  • Post-cessation expenses can be claimed within seven years under ITTOIA 2005 s.354 / ITA 2007 s.125 (covered in our mid-year cessation page).
  • Late-arriving invoices and post-year-end adjustments routinely emerge twelve to eighteen months after the year in question.

A landlord retaining records for seven years from year-end (so 2026/27 records retained until April 2034) sits comfortably outside the careless-behaviour window and accommodates post-cessation tail items.

The retention can be in:

  • The MTD software's archive (the cleanest route; preserves the audit trail natively).
  • A cloud backup (OneDrive, Google Drive, Dropbox business; acceptable provided the file metadata and software-export logs are preserved alongside the figures).
  • A self-hosted archive (a network drive at home, with backups), provided regular integrity checks and an off-site backup hold against device failure.

Active subscriptions to MTD software during the retention period are expensive over seven years; many vendors now offer a read-only archive plan at a fraction of the active price, which is the cleanest route for post-cessation retention.

What HMRC actually asks for in an enquiry

An MTD ITSA enquiry under TMA 1970 s.9A typically opens with a written notice listing the documents requested. The standard set includes:

  • The digital records for the year under enquiry (typically exported as PDF or CSV).
  • The corresponding bank statements (PDF downloads from the bank, covering the period).
  • Sample invoices and receipts for the larger expense lines or unusual items.
  • The software audit trail (logs of entries, edits, submissions, with timestamps).
  • A reconciliation between the quarterly updates submitted and the final-declaration figures.
  • Explanations for any unusual transactions (large one-off payments, transactions with related parties, items the software auto-categorised differently from your final position).

The response window is set by the notice (typically thirty to sixty days). HMRC's compliance handbook covers the standard mechanic; an experienced ASA-engaged accountant handles the response on the landlord's behalf where the authorisation is in place.

Where the records are sound, the enquiry is closed quickly with a no-change or small-adjustment outcome. Where the records are weak, the enquiry extends, additional information notices follow, the discovery rules may extend back-years, and the penalties for inadequate records (FA 2007 Sch 24, up to £3,000 per offence) come into scope.

The discipline that holds at enquiry is the discipline that was applied during the year: contemporaneous capture, formulaic links, software-audited entries, supplementary documentation paired with bank-feed transactions, cash transactions properly digitised. Year-end retrospective tidying does not produce records that survive an enquiry six years later.

Joint-owner records, software portals, and cross-niche edges

Joint owners share the property but not the records. Each spouse's MTD ITSA records are theirs separately, even if held in the same software subscription. The software segregates by user account; each spouse logs in with their own credentials, sees their own slice of the shared property's data, and submits their own quarterly updates. At enquiry, HMRC requests records for the specific taxpayer under enquiry; the software exports the relevant subset.

This pattern is covered in more depth in our joint-owner quarterly filing page, which walks the two-parallel-cycle architecture and the shared-source-data-with-split-derivations bookkeeping pattern.

Software-portal storage versus local backup: the practical position is both. The MTD software's archive is the primary record (with the audit trail intact); a periodic cloud backup is the secondary insurance. Relying solely on the software vendor's continued existence over a seven-year period is a single-point-of-failure risk; relying solely on a local backup loses the audit trail. The two together create the redundancy HMRC's enquiry process can probe from either direction.

For landlords also subject to other digital record obligations (tenancy paperwork under the Renters' Rights Act 2025, gas safety certificates, EICR, EPC, the landlord database registration, deposit protection certificates), the operational simplest pattern is one digital archive folder structure spanning all categories. The MTD records (financial) and the housing-regulation records (legal/operational) come from different statutory sources but live operationally together in many landlord setups.

Where this page sits

This page is the evidence-and-audit-trail layer of MTD ITSA digital records. It does not cover:

For the broader MTD ITSA context, the bucket overview is the starting point.

Source authority for the positions on this page: house position §19.16 (Wave 4 digital-records evidence extension, locked 2026-05-23) and §19.14 (digital-link rule); TMA 1970 s.12B (5-year statutory retention minimum); FA 2017 Sch A1 paragraph 8 (digital-records obligation); HMRC notice 700/22 (digital-records framework); HMRC Compliance Handbook (enquiry mechanics); FA 2007 Sch 24 (inadequate-records penalties); ITTOIA 2005 s.354 (post-cessation expenses, 7-year window).