Provide the Income Tax digital-link adapter contract
Supply cumulative or annual business totals and source lineage for the selected HMRC business source. 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 cumulative or annual business totals and source lineage for the selected HMRC business source. 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 Accounting is active and the HMRC business source has been synchronised.
- Implement the documented mtd_hmrc_accounting_income_tax_summary integration hook for the verified Accounting build.
- Use business type, Business ID, tax year, period end and submission type supplied by the MTD module.
- Return the HMRC business payload plus source_manifest transaction lineage.
- Keep self-employment, UK property and foreign property sources separate by Business ID.
- Prepare a snapshot and resolve any digital-lineage blocker before approval.
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.