Britixo CRMBritixo CRMEnterprise Help Centre
Ctrl K
MTD - HMRC Compliant Module · How-to guide

Understand agent OAuth versus client-agent authorisation

Distinguish software OAuth from the separate legal HMRC relationship between an agent and each client. 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.

Audience: Administrators, taxpayers, accountants and authorised agentsModule v1.0.0Code-backed
Jump to steps
Where to goTax Centre → Settings → Profiles & HMRC authority
Before you startRequired access: Manage HMRC connection permission plus the relevant taxpayer/agent authority. Work on the correct tenant and taxpayer profile. Reconcile the underlying Accounting & Bookkeeping records before relying on prepared tax totals.

What you’ll accomplish

Distinguish software OAuth from the separate legal HMRC relationship between an agent and each client. 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

  1. Go to Tax Centre → Settings → Profiles & HMRC authority.
  2. Verify you are working on the correct taxpayer profile and tenant before you understand agent oauth versus client-agent authorisation.
  3. Follow the on-screen workflow for understand agent oauth versus client-agent authorisation and keep the underlying Accounting records unchanged unless a genuine bookkeeping correction is required.
  4. Check any blocker or warning before continuing; a blocker must not be bypassed by manually re-keying tax totals.
  5. Keep client approval, professional review and HMRC authority requirements separate and complete each one that applies to the filing mode.
  6. Use the Audit Trail and frozen snapshot details to verify what was prepared, approved and submitted.

Checks before you continue

Taxpayer profileAlways verify the correct profile, tax regime and masked identifiers before preparing or submitting.
Tenant contextTax records, HMRC authority and audit history must stay inside the current Britixo tenant/runtime.
Accounting sourceSource tax figures must come through the verified Accounting digital-link adapter with transaction lineage.
Approval stateThe exact frozen snapshot must carry the approvals required by its filing mode before HMRC submission.

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.
  • Agent OAuth authorises the software connection only; the supplied v1.0.0 module does not create the legal HMRC client-agent relationship. Establish/verify that relationship separately through the appropriate HMRC process.
Accounting interlinkFor transaction creation, tax mappings, banking, reconciliation, journals, reports and source-document corrections, use the Accounting & Bookkeeping Help Centre. Correct the bookkeeping source first; do not type replacement totals into MTD merely to clear an error.
Accounting & BookkeepingOpen related guidanceAll MTD - HMRC Compliant guidesOpen related guidance