Customer work, connected.

Help & supportMyAccount
MTD - HMRC Compliant Module · How-to guide

Connect an accountant or agent OAuth authority

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Connect an authorised agent context to Pixie CRM without storing Government Gateway credentials.

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

Connect an authorised agent context to Pixie CRM without storing Government Gateway credentials. 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 the required taxpayer profile under Tax Centre → Settings.
  2. Select Connect agent, not Connect taxpayer.
  3. Complete HMRC OAuth using the authorised agent context.
  4. Remember that this only authorises Pixie CRM software to use that agent context; it does not create the legal client-agent relationship.
  5. Check the client has separately authorised the agent for the required HMRC service before filing on the client’s behalf.
  6. Keep client approval and professional review evidence on the frozen return before any agent submission.

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 Pixie CRM 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

  • Pixie CRM 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 Pixie CRM.
  • 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.

Search the platform, integrations and practical Help Centre guides.

Press Esc to close.Browse every page