Run the MTD HMRC Production go-live checklist
Verify Accounting digital linkage, HMRC subscriptions, fraud headers, OAuth, declarations, permissions and controlled live testing before Production filing. 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
Verify Accounting digital linkage, HMRC subscriptions, fraud headers, OAuth, declarations, permissions and controlled live testing before Production filing. 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
- Prove the exact Accounting adapter and transaction-level digital links in staging.
- Complete HMRC Sandbox endpoint testing for every supported filing workflow.
- Validate all required fraud-prevention headers.
- Configure Production client ID, secret, encryption key, redirect URI and vendor public IP securely.
- Verify the required HMRC Production API subscriptions/approval are in place.
- Configure exact current taxpayer/agent declaration wording before enabling final declaration.
- Test taxpayer and agent OAuth, client approval, professional approval, submission locks and audit evidence.
- Perform a controlled Production acceptance filing only under the approved operational plan.
Checks before you continue
Technical basis for this guidance
This guide was checked against libraries/Mtd_hmrc_config.php; libraries/Mtd_hmrc_gateway.php; docs/HMRC_PRODUCTION_GATE.md; README.md. 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.
