Use MTD - HMRC Compliant across Britixo SaaS tenants
Activate the same reusable module through each authorised tenant runtime while keeping data in the active tenant database. 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
Activate the same reusable module through each authorised tenant runtime while keeping data in the active tenant database. 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 the authorised tenant through the existing Britixo SaaS tenant runtime.
- Install/activate the shared module through the supported tenant module lifecycle.
- Check the runtime database is the tenant database before creating tax profiles or connections.
- Create taxpayer profiles and HMRC authority only inside the intended tenant.
- Use the tenant Tax Centre; never copy OAuth tokens, taxpayer identifiers or filing records between tenant databases.
- Repeat the same lifecycle independently for each tenant that is entitled to use the module.
Checks before you continue
Technical basis for this guidance
This guide was checked against install.php; helpers/mtd_hmrc_helper.php; models/Mtd_hmrc_model.php; mtd_hmrc_compliant.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.
- Every module-owned tax query is intended to run in the current tenant context; do not use a browser-supplied tenant ID as authority for cross-tenant access.
