Understand central HMRC app credentials and tenant OAuth
Keep Britixo application credentials under controlled deployment configuration while each taxpayer or agent grants their own HMRC authority. 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
Keep Britixo application credentials under controlled deployment configuration while each taxpayer or agent grants their own HMRC authority. 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 SaaS tenant → Setup → Modules / tenant Tax Centre.
- Verify you are working on the correct taxpayer profile and tenant before you understand central hmrc app credentials and tenant oauth.
- Follow the on-screen workflow for understand central hmrc app credentials and tenant oauth and keep the underlying Accounting records unchanged unless a genuine bookkeeping correction is required.
- Check any blocker or warning before continuing; a blocker must not be bypassed by manually re-keying tax totals.
- Keep client approval, professional review and HMRC authority requirements separate and complete each one that applies to the filing mode.
- Use the Audit Trail and frozen snapshot details to verify what was prepared, approved and submitted.
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.