Deactivate or replace the MTD module safely
Deactivate or replace code without deleting historic tax records; preserve filings, approvals, audit evidence and Accounting data. 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
Deactivate or replace code without deleting historic tax records; preserve filings, approvals, audit evidence and Accounting data. 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
- Export/record the release checksum and current module version before replacement.
- Use the native module replacement/deactivation process; do not run direct DROP/DELETE database commands.
- Do not delete mtd_* history merely because the PHP module is deactivated.
- After replacement, reactivate so the idempotent installer can ensure required module-owned schema exists.
- Check profiles, encrypted connections, obligations, snapshots, approvals, submissions and audit events remain present for the tenant.
- Re-run Accounting readiness and HMRC Sandbox/Production health checks before the next filing.
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.