Connect a taxpayer to HMRC
Follow this guide to start the taxpayer OAuth journey from a profile and return to Britixo with a tenant-bound HMRC connection. 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
Start the taxpayer OAuth journey from a profile and return to Britixo with a tenant-bound HMRC connection. 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 → Settings and find the required taxpayer profile.
- Select Connect taxpayer.
- Britixo creates a short-lived OAuth state and redirects the browser to the configured HMRC authorisation endpoint.
- The taxpayer signs in directly with HMRC and grants the requested software authority; do not enter Government Gateway credentials into Britixo.
- HMRC returns the browser to the registered callback route.
- Britixo exchanges the authorisation code server-side, encrypts the token material and binds the connection to the current tenant/profile.
- Return to the Tax Centre and run the relevant VAT or Income Tax sync to verify the connection.
Checks before you continue
Technical basis for this guidance
This guide was checked against controllers/Mtd_hmrc_oauth.php; libraries/Mtd_hmrc_oauth_service.php; libraries/Mtd_hmrc_crypto.php; libraries/Mtd_hmrc_fraud_header_service.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.
