Review the append-only MTD audit trail
Follow this guide to use the module Audit page to inspect connection, preparation, approval, submission and other recorded tax events. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
What you’ll accomplish
Use the module Audit page to inspect connection, preparation, approval, submission and other recorded tax events. The MTD module stores tax profiles, HMRC authority, obligations, frozen filing snapshots, approvals and audit evidence, while Accounting remains the primary financial record system.
Follow these steps
- Go to Tax Centre → Approvals / Audit Trail.
- Verify you are working on the correct taxpayer profile and tenant before you review the append-only mtd audit trail.
- Follow the on-screen workflow for review the append-only mtd audit trail and keep the underlying Accounting records unchanged unless a genuine bookkeeping correction is required.
- Check any blocker or warning before continuing; a blocker must not be bypassed by manually re-keying tax totals.
- Keep client approval, professional review and HMRC authority requirements separate and complete each one that applies to the filing mode.
- Use the Audit Trail and frozen snapshot details to verify what was prepared, approved and submitted.
Checks before you continue
Technical basis for this guidance
This guide was checked against libraries/Mtd_approval_service.php; models/Mtd_hmrc_model.php; views/admin/approvals.php; views/admin/audit.php. The user instructions describe only behaviour exposed or enforced by the supplied module. Internal secrets, encrypted token values and database identifiers are intentionally not shown to ordinary users.
Compliance and operational boundaries
- Britixo Accounting & Bookkeeping remains the authoritative ledger; the MTD module is a tax preparation/submission layer.
- Government Gateway usernames and passwords must never be entered into or stored by Britixo.
- A tax filing must not proceed when transaction-level digital lineage cannot be proven.
