Provide the VAT digital-link adapter contract
Supply the nine VAT totals plus transaction-level source manifest through the verified Accounting integration hook. 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
Supply the nine VAT totals plus transaction-level source manifest through the verified Accounting integration hook. 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
- Verify the Accounting module is active in the same runtime database.
- Implement the documented mtd_hmrc_accounting_vat_summary integration hook in the verified Accounting integration layer.
- Return all nine HMRC VAT values expected by the MTD adapter.
- Return source_manifest as transaction-level digital lineage; totals without lineage remain blocked.
- Use Accounting records and mappings as the source; do not re-key VAT totals manually into the MTD module.
- Prepare a VAT snapshot and verify the compliance result no longer reports DIGITAL_LINEAGE_MISSING.
Checks before you continue
Technical basis for this guidance
This guide was checked against libraries/Mtd_accounting_adapter.php; libraries/Mtd_tax_compliance_engine.php; docs/ACCOUNTING_ADAPTER_CONTRACT.md. 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.