Install and activate the MTD - HMRC Compliant Module
Install the reusable module through the normal Britixo module lifecycle without modifying Accounting or CRM core files. 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
Install the reusable module through the normal Britixo module lifecycle without modifying Accounting or CRM core files. 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 Setup → Modules in the Britixo administrator area for the current master or tenant runtime.
- Upload the installable ZIP with the single mtd_hmrc_compliant/ module root.
- Install and activate the module through the native module lifecycle so install.php runs with the current database prefix.
- Go to the new MTD - HMRC Compliant Module menu and confirm the Overview page loads.
- Check the Accounting & digital link panel; do not attempt a filing if Accounting cannot be proven active.
- Assign only the permissions needed by the staff who will prepare, review, approve or submit tax data.
- Configure HMRC application values in the protected deployment environment before starting OAuth.
Checks before you continue
Technical basis for this guidance
This guide was checked against mtd_hmrc_compliant.php; controllers/Mtd_hmrc_compliant.php; views/admin/settings.php; install.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.
