Activate MTD for an authorised SaaS tenant | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/activate-mtd-for-an-authorised-saas-tenant Publisher: Pixie Technologies LLC MTD - HMRC Compliant Module · How-to guide Activate MTD for an authorised SaaS tenant Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Follow this guide to use the existing SaaS tenant module lifecycle so install.php runs inside the tenant runtime without direct database commands. Audience: Pixie CRM SaaS administrators and tenant administrators; Module v1.0.0; Code-backed; Where to goSaaS tenant → Setup → Modules / tenant Tax Centre Before you startRequired access: Authorised tenant module administration plus the MTD permission needed for the tax action. Work on the correct tenant and taxpayer profile. Reconcile the underlying Accounting & Bookkeeping (https://pixiecrm.com/help-centre/category/accounting-bookkeeping) records before relying on prepared tax totals. What you’ll accomplish Use the existing SaaS tenant module lifecycle so install.php runs inside the tenant runtime without direct database commands. 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 Pixie CRM 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 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 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 - 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. - 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. Accounting interlinkFor transaction creation, tax mappings, banking, reconciliation, journals, reports and source-document corrections, use the Accounting & Bookkeeping Help Centre (https://pixiecrm.com/help-centre/category/accounting-bookkeeping). Correct the bookkeeping source first; do not type replacement totals into MTD merely to clear an error. Related guides Accounting & BookkeepingOpen related guidance (https://pixiecrm.com/help-centre/category/accounting-bookkeeping)All MTD - HMRC Compliant guidesOpen related guidance (https://pixiecrm.com/help-centre/category/mtd-hmrc-compliant)Client PortalOpen related guidance (https://pixiecrm.com/help-centre/category/client-portal)Data, privacy & securityOpen related guidance (https://pixiecrm.com/help-centre/category/data-privacy-security)