MTD quarterly record-collection checklist

By Babagana Zannah, team lead · Published 6 August 2026 · Updated 6 August 2026

Babagana Zannah
Leads engineering teams; puts AI to work inside one of the UK's largest companies

An MTD quarterly record-collection checklist should control an operating cycle. It should not attempt to decide a client’s tax position. Its purpose is to request an approved set of records, reconcile what arrives, surface gaps and preserve a clear route to professional review.

Use this checklist for operational planning in a UK accountancy or bookkeeping practice. It is not tax, accounting or legal advice. It does not determine whether a client must use Making Tax Digital for Income Tax, which dates apply, whether records are complete, how transactions should be categorised or whether an update is ready to send.

Start with the live HMRC position

HMRC’s MTD for Income Tax overview describes a phased introduction based on qualifying income, as well as sign-up, software and authorisation steps. The page had been updated in July 2026 when this guide’s sources were checked. Use the live page for each client rather than treating this checklist as an eligibility test.

HMRC also states that quarterly updates are summaries of self-employment and property income and expenses, created from digital records. They are not tax returns. Its quarterly update guidance sets out periods, deadlines and what is sent. Those facts can change, so the responsible person should record the source and date used for the client-specific instruction.

1. Confirm scope and ownership

Before collection begins, record:

• the client and businesses covered;
• the applicable period;
• the client’s MTD position confirmed by an authorised person;
• the current workflow dates and source used to verify them;
• the compatible software and authoritative record source;
• who maintains the digital records;
• what the client must provide and through which route;
• who approves corrections and submission steps; and
• which circumstances stop routine collection.

If identity, business scope, authority, software or period is unclear, do not start a reminder sequence.

2. Assign roles before tasks

One person may hold several roles, but the responsibilities should remain explicit:

• Scope owner: confirms the client, businesses, period, obligations and agreed service.
• Collection owner: prepares approved requests and maintains the operational tracker.
• Reconciliation owner: checks approved locations and links returned material to the request.
• Professional reviewer: decides sufficiency, treatment, corrections and readiness for the next step.
• Submission owner: controls software submissions and related authorisation.
• Exception owner: handles disputes, access failures, security concerns and unclear replies.

ICAEW’s professional guidance for MTD for Income Tax services discusses service scope, client responsibilities and accuracy. Use its current guidance and the practice’s professional policies. A tracker status must not replace judgement assigned to a professional.

3. Create one cycle record

The cycle record should point to approved source systems rather than copying files or sensitive details. Include:

• client, business and engagement reference;
• period and confirmed workflow dates;
• instruction owner and confirmation date;
• required item or data category;
• approved recipient and return route;
• current state and last verified timestamp;
• next action, date and owner;
• exception or stop state;
• evidence reference for requests, replies and approvals; and
• final outcome with the person and time that authorised it.

Use factual states such as not requested, requested, partly received, received for reconciliation, ready for professional review, query raised, correction required, blocked and complete. Avoid a single status that could blur receipt, reconciliation, approval and submission.

4. Confirm the record inventory

HMRC’s digital-record guidance explains the information held in digital records and the continuing need to retain supporting records used to prepare a tax return. It also covers digital links where more than one software product is used.

The collection owner should turn the professional instruction into a precise inventory. For each item, record:

• the business and period;
• whether it already exists in an approved location;
• whether a digital record exists but needs reconciliation;
• whether supporting evidence is expected;
• who can decide that the item does not apply; and
• which later review depends on it.

Do not request “everything for the quarter” if a narrower approved list is available. Do not infer that a populated software field, bank feed or uploaded document is complete simply because it exists.

5. Plan backwards from the confirmed date

Once the responsible person confirms the relevant date, allow time for:

1. the client’s realistic response time and accessibility needs;
2. delivery failure and alternative-channel handling;
3. reconciliation across approved inboxes, portals and software;
4. follow-up for precise remaining gaps;
5. professional review and corrections;
6. exception handling and client questions;
7. software access and submission controls; and
8. a contingency margin set by the practice.

Keep the client’s requested response date separate from an HMRC deadline. HMRC’s agent toolkit advises agents to set expectations for record submission and tailor communications to client circumstances and digital capability. Use that principle when setting cadence and channels.

6. Send a verified, minimal request

Immediately before contact, check every requested item against all agreed sources. Remove anything received, marked not applicable by an authorised person or waiting for review.

The message should include:

• the engagement or period in terms the client recognises;
• the exact items still requested;
• the approved return route;
• the practice’s requested response date;
• how to report an unavailable, inapplicable or already-sent item; and
• a named route for questions and accessibility support.

The client reminder-email templates provide adaptable structures. The missing-document process covers pre-send verification and stop rules.

7. Reconcile responses before continuing

Pause the routine reminder for the affected request when any reply appears.

• Link an expected item to the approved location and mark it for reconciliation or review.
• Record a partial response and request only the remaining gap.
• Search approved locations when a client says an item was already sent.
• Give a “not applicable” statement to the person authorised to decide.
• Route questions, corrections and unclear content to a competent person.
• Stop and follow privacy or security procedures for unexpected sensitive information.
• Escalate complaints, disputes and vulnerabilities to the named owner.

Do not let a filename match or successful upload establish sufficiency, treatment or readiness to submit. Those are separate professional controls.

8. Keep collection, approval and submission distinct

Before any software submission, the authorised process should confirm the correct client, business and period; required reconciliation and review; resolution of exceptions; correct software and credentials; authority for the action; and how success, failure or uncertainty will be recorded.

If a write or submission fails, preserve the error evidence and return the task to its owner. Do not retry indefinitely or mark the cycle complete from an unverified response.

Copyable quarterly collection checklist

Scope and source

• Client, businesses and period confirmed.
• Current MTD position and dates checked against live HMRC guidance.
• Engagement responsibilities and approved channels confirmed.
• Collection, reconciliation, review, submission and exception owners named.
• One controlled cycle record created.
• Client-specific item list approved.

Request and response

• Existing software records and approved locations checked.
• Client response date kept separate from an HMRC deadline.
• Message contains only current gaps and the approved return route.
• Accessibility alternative and question route available.
• Routine reminders pause on a reply or exception.
• Partial, duplicate, unavailable and not-applicable responses have separate states.
• Received material is awaiting reconciliation or review, not automatically accepted.

Approval and close

• Operational collection and professional review remain separate.
• Software writes and submissions use explicit authorisation.
• Failed or uncertain actions do not become successful statuses.
• Requests, replies, decisions and final state are auditable.
• Retrospective measures use stable definitions and include human effort.

Sources and review status

Author: Babagana Zannah. Published 6 August 2026 and last updated 6 August 2026. Sources checked 6 August 2026. Next editorial review due 6 November 2026.

The following primary sources were re-opened on the source-check date. Recheck them sooner when HMRC or professional guidance changes.

• HMRC: Use MTD for Income Tax, before you use this guide
• HMRC: Use MTD for Income Tax, create digital records
• HMRC: Use MTD for Income Tax, send quarterly updates
• ICAEW: Professional standards for MTD for Income Tax services
• HMRC: Get ready for MTD, preparing your clients

Questions owners ask