Public MTD guidance & client-action review

Find the MTD point a client will misunderstand before it becomes partner time.

QuarterReady checks the public journey against current HMRC rules, follows the next action and builds one client-ready fix. Internal operations are only assessed when a firm chooses to work with us and provides the necessary access.

Current HMRC sourcesNamed pages and datesPublic scope stated clearly
436,000+first quarterly updates submitted by 12 August 2026HMRC source
September 2026HMRC begins staged sign-up for people required to use MTD in 2026–27 who have not signed up themselvesHMRC source
7 Novembernext quarterly-update deadline for standard and calendar periodsHMRC source

The focused public-page review

Show the evidence. Fix one point properly.

Each finding is limited to the pages checked. If a page or internal process was not inspected, it is marked as unknown—not scored as a failure.

01

Accuracy & freshness

Dates, thresholds, terminology and time-sensitive claims checked against current HMRC guidance.

02

Client questions answered

Whether a visitor can identify their likely start year, what changes and what to prepare.

03

Action path

Links, next steps, data requested and the point where a client reaches the right person.

04

Change control

Source, checked date, owner, expiry trigger and the items that still need the firm to confirm.

What a client sees

A decision record, not a generic website critique.

Anonymised review · firm package page checked · HMRC baseline rechecked 29 August 2026

Terminology

Specific, reproducible issue

The package page repeatedly uses “HMRC Approved Software”; HMRC describes products as compatible or recognised and does not recommend providers.

Client taskStatusReview action
Understand software statusMislabelledUse compatible or recognised
Identify likely start yearPartialAdd the staged cohort check
Compare packagesToo earlyCheck likely cohort first
Know the supported routeFirm to confirmName the service boundary

Editable starter scenario

How much manual chasing could sit behind the next deadline?

The figures below are example assumptions, not a benchmark. Replace all six with the firm's own portfolio and team data.

Modelled result

50team hours each quarter
84clients in the chase pool
£2,772quarterly handling cost
Four-quarter view202 hours · £11,088

Based on 210 modelled in-scope clients. Excludes software setup, review, correction and partner escalation time.

Where commissioned work begins

Turn the public fix into a working client-readiness system.

The free review does not reveal or replace this layer. It needs the firm's actual client data, service decisions, software routes and ownership rules.

01

Cohort register

One client list showing likely start year, income sources, exemption route and sign-up status.

02

Readiness evidence

Software, record method, authorisation, bookkeeper and missing-information status in one place.

03

Chase & exceptions

Dated requests, ownership, reminders and a clear route for clients who do not fit the standard path.

04

Partner view

Who is ready, waiting or blocked before each quarterly deadline, with the next action named.

Release method

Five checks before a client link is shared.

  1. 01

    Scope

    Name the exact pages, searches and actions included in the check.

  2. 02

    Reproduce

    Confirm the wording or link again before making a claim.

  3. 03

    Compare

    Test it against current HMRC language and the client task it is meant to support.

  4. 04

    Build

    Supply the corrected copy, client check or action path—not a list of vague suggestions.

  5. 05

    Control

    Add sources, a checked date, an owner and the trigger for the next review.

Start with evidence

One useful correction before any commercial conversation.

QuarterReady provides independent, source-linked MTD communication and readiness reviews for UK accountancy firms. Public reviews assess only the pages named; internal systems are reviewed only with the firm’s permission and access.

If a review is wrong or misses a relevant page, it is corrected. If the fix is useful and a firm wants help installing and testing it, that is a separate conversation.