HMRC software compatibility should be checked for the exact tax service and functions the business needs. Verify the current official listing and the provider’s supported workflow, including whether a separate bridging or submission component is required.
Compatibility for VAT does not automatically mean compatibility for MTD for Income Tax. Review supported activities, agent access and export options before committing to a reporting process.
Name the exact HMRC service required
Start with the tax and function the business needs to perform. MTD for VAT, MTD for Income Tax, payroll reporting and other services are not interchangeable compatibility claims. Record the taxpayer type, income sources and reporting periods involved. A product advertised broadly as 'HMRC compatible' may support one function while requiring another module or product for the rest of the business's obligations.
HMRC's Income Tax software guidance explains the need for suitable digital records, quarterly submissions and completion of the annual return with other relevant income. It recognises different product combinations and provides a current finder. Recognition is not a recommendation of a supplier, and the selected workflow still needs to fit the user's circumstances. Check the exact product and supported functions rather than relying only on the provider's brand name. [1]
Verify the current listing and release
Use the official finder and the provider's current documentation to establish whether the required function is available now. Distinguish a released feature from an announced development or an old screenshot. Record the product name, version or service tier where relevant and the date checked. If an accountant will submit, confirm that the agent workflow is supported as well as the individual's direct-use option.
Ask the provider to demonstrate the actual submission path using a suitable non-live example or documentation. Identify any registration, authorisation or setup needed before use. A successful login to a bookkeeping package does not prove that the correct HMRC service has been connected. Keep the setup steps visible in the implementation plan so compatibility is translated into a working process before the reporting deadline.
Check all income sources and tasks
List the business and other income information needed for the annual return and confirm how each will be handled. A tool that sends trading updates may not, on its own, cover every part of a landlord's or sole trader's wider return. If another product completes the final stage, identify it and confirm the handover. Do not assume that four successful updates prove the annual workflow is complete.
Review supported accounting periods, multiple activities and any relevant special circumstances. Ask a precise question rather than accepting a general assurance that the software is suitable for 'small businesses'. Keep the response with the selection record. The provider and agent should be working from the same facts, particularly where the person has property income, another trade or information outside the normal quarterly records.
Understand bridging and multiple-product arrangements
Where bridging software is proposed, identify the records it connects to and the submissions it can make. Confirm that the full combination meets the applicable requirements and preserves the necessary data connections. A spreadsheet can remain part of a supported workflow, but simply purchasing a bridge does not correct incomplete records or an unsuitable transfer process between tools.
Assign one clear product and operator to each submission task under the applicable rules. Avoid parallel systems each sending an update for the same business because both teams believe they are responsible. Document how corrections and year-end information move through the arrangement. The more tools involved, the more important it is to define the authoritative record and reconcile the figures at each handover.
Validate the operational fit before committing
Check costs, permissions, record exports and support alongside compatibility. Test a representative transaction and its correction through the proposed workflow. Confirm that the business or agent can retrieve submission acknowledgements and supporting records. Technical recognition does not establish that staff can use the product reliably, that the service tier includes the needed function or that the archive will remain accessible after cancellation.
Use Choosing accounting software for a small business for the broader software-selection process and Making Tax Digital readiness review to discuss compatibility within a digital reporting setup. State the exact tax service, activities and functions required. A focused review can then confirm the supported route and outstanding setup tasks without implying that an official listing guarantees the accuracy of the business's records or future submissions.
Recheck compatibility and the workflow when the provider changes its product, the business adds an income source or an adviser takes over. Keep the original decision and the updated conclusion dated. This helps distinguish a genuine change in supported functionality from a setup problem or an assumption that was never verified in the first place.
Illustrative scenario
A landlord already uses a VAT-capable product for another activity. They check the current Income Tax functionality and required setup rather than assuming the existing subscription covers the new obligation.
Preparation checklist
- Identify the tax service
- Check the official listing
- Confirm required features
- Test the complete workflow
Frequently asked questions
Does VAT compatibility establish MTD for Income Tax compatibility?
No. Check the exact tax service and required functions separately, including the current product or module used for each.
Does HMRC recognition guarantee the software suits my records?
No. It is a compatibility check, not a personalised recommendation or assurance that the business's data and workflow are correct.
Can a bridging tool solve incomplete bookkeeping automatically?
No. It connects records for supported tasks. The underlying records, data links, review and reporting responsibilities still need to meet the applicable requirements.
When should compatibility be checked again?
When products, service tiers, business activities or advisers change, and when a new reporting function is required. Keep the date and scope of each check.
Official sources
Sources checked: 8 September 2026. Check the linked guidance for subsequent changes.
General information only. The appropriate action depends on your circumstances and the applicable jurisdiction.
Report a correction