If you have searched for Making Tax Digital compatible software, you have seen the phrase “HMRC recognised” used as a quality signal. Software providers display it prominently. Comparison sites filter by it. Accountants recommend choosing from the list.
What most businesses do not realise is that HMRC recognition is a technical accreditation, not an endorsement of the software’s quality, suitability, or completeness. A product on the recognised list has demonstrated that it can communicate with HMRC’s API. It has not been assessed for whether it maintains digital records correctly, calculates tax accurately, or fits the operational structure of your business.
Understanding what the label covers, and what it leaves open, is important for any business choosing software under MTD or replacing a system that is no longer fit for purpose.
What HMRC Recognition Actually Covers
HMRC operates a process through which software developers submit their products for testing against the MTD API. The testing confirms that the software can authenticate with HMRC’s systems, send the required data in the correct format, and receive the confirmation that a submission has been accepted.
That is the full scope of the accreditation. HMRC tests the connection. It does not audit the software’s internal logic, review how it calculates VAT or income tax, inspect whether its record-keeping meets the digital link requirement end to end, or assess whether it is appropriate for businesses of a particular size, structure, or industry.
HMRC publishes its list of recognised software products and updates it as new products complete the process. The list is long. At any given point it contains hundreds of products ranging from full enterprise platforms to lightweight bridging tools that do nothing except transmit a number from a spreadsheet to HMRC’s API.
Both of those categories appear on the same list with the same recognition status.
What HMRC Recognition Does Not Tell You
The gaps in what recognition covers are the areas where businesses make poor software decisions.
Record-keeping compliance is not assessed. MTD requires businesses to maintain digital records from the point of transaction capture through to submission, with an unbroken digital link. HMRC recognition confirms that the submission end of that chain works. It says nothing about whether the software actually maintains records in a way that meets the standard throughout the period.
A business using bridging software, for example, is on the recognised list. But if it is maintaining its underlying records in a spreadsheet and using the bridging tool only to transmit the final figures, the quality of those underlying records is entirely outside the scope of HMRC’s assessment.
Calculation accuracy is not verified. HMRC does not test whether the software’s VAT calculations, income tax estimates, or payroll figures are correct. It tests whether the software can send a number. Where that number comes from and whether it is right is the software provider’s responsibility, and by extension the taxpayer’s.
Suitability for your business structure is not considered. A sole trader with straightforward income and a single location has very different requirements from a mid-market business with multiple branches, complex VAT positions, partial exemption calculations, or group reporting obligations. HMRC recognition applies equally to both, which means the label provides no signal about whether a product handles the complexity your business actually has.
Ongoing compliance is not monitored. A product recognised at one point in time remains on the list unless it is actively removed. HMRC does not continuously re-test products to confirm they remain compliant as tax legislation changes, as the API evolves, or as the software itself is updated. A recognised product from several years ago may have had its MTD functionality deprioritised or discontinued without that change being reflected in the list.
The Bridging Software Problem
Bridging software deserves specific attention because it is widely used, appears on the recognised list, and is frequently misunderstood as a genuine compliance solution.
Bridging software connects a spreadsheet or legacy system to HMRC’s API, creating the digital link that MTD requires at the point of submission. HMRC accepted bridging software as a transitional measure to allow businesses to meet the initial MTD for VAT deadline without replacing their entire accounting system.
The problem is that bridging software addresses the submission requirement without addressing the record-keeping requirement. A business maintaining VAT records in Excel and using bridging software to submit them has a recognised digital link. It does not necessarily have digital records that meet MTD’s standard throughout the period, and the bridging tool itself provides no assurance about the quality or completeness of the underlying data.
Beyond compliance, bridging software adds a manual step to every submission cycle. The figures need to come from somewhere, be entered into the bridging tool, and then be submitted. That process introduces a point of human error that purpose-built software eliminates by generating the submission directly from the records it already holds.
For businesses approaching MTD for Income Tax, which requires quarterly submissions rather than quarterly VAT returns, the operational cost of that manual step multiplies. Four submissions per year per income source, each requiring the same manual extract and upload process, becomes a significant administrative burden.
What to Actually Verify When Choosing MTD Software
Given that HMRC recognition is a minimum bar rather than a quality standard, businesses evaluating MTD software should be asking questions the recognised list cannot answer.
Does the software maintain digital records natively? The digital link requirement runs from transaction capture to submission. Software that holds transactions in its own database and generates the submission from those records meets that requirement cleanly. Software that depends on importing or bridging from an external source creates a gap that needs to be assessed carefully.
Does the software handle your VAT position correctly? Standard rated, zero rated, exempt, and partially exempt supplies all need to be treated differently. If your business has a partial exemption calculation, the software needs to handle that methodology, not just apply a flat rate. HMRC recognition does not confirm this.
Can the software grow with your reporting obligations? MTD is expanding. A business that selects software for MTD for VAT today will face MTD for Income Tax or Corporation Tax in the future. Software that handles VAT submission but has no roadmap for the broader MTD programme leaves you facing another software decision when the next deadline arrives.
Does the submission trail produce a complete audit record? If HMRC queries a return, you need to be able to demonstrate where every figure came from. Software that produces a submission without an auditable record of the underlying calculations puts the business in a difficult position if that question is ever asked.
Is the provider actively maintaining MTD compliance? HMRC’s API evolves. Tax legislation changes. Software that was fully compliant at the point of recognition needs to be kept current. Ask whether the provider has a track record of updating the product as requirements change and whether those updates are included in the standard subscription.
The Difference Between Recognised and Ready
Recognition and readiness are not the same thing, and the distinction matters for businesses making a software decision under time pressure.
A recognised product is one that passed a technical test. A ready product is one that maintains your records correctly, calculates your tax position accurately, submits compliantly, scales with your business structure, and keeps pace with legislative change.
The first category is large. The second is smaller. Most businesses need the second and mistakenly use the first as a proxy for it.
For mid-market businesses with branch structures, complex VAT positions, or reporting obligations that span multiple frameworks, the gap between recognised and ready is widest. A lightweight tool that connects to HMRC’s API may be recognised, but it is not ready for an operation of that complexity.
Where Monesize Core Sits on This
Monesize Core connects to HMRC’s MTD API for VAT submission and is positioned for the broader MTD programme as Income Tax and Corporation Tax mandates come into force. That is the recognised part.
The ready part is what sits underneath. Digital records are maintained at the transaction level inside the platform. Every sale, purchase, payment, and adjustment is captured with the detail the MTD digital link requirement demands. The VAT return is generated from those records directly, not imported or bridged from an external source.
For businesses with multiple branches, Monesize Core aggregates transaction data across locations into a single compliant submission without manual consolidation. For businesses with complex VAT positions, the Accounting module handles standard, zero-rated, exempt, and partially exempt supplies within the same record-keeping structure.
The Activity Logs module maintains a complete audit trail behind every submission. If HMRC queries a return, the supporting record is in the platform, timestamped and attributable, not in a spreadsheet that needs to be reconstructed.
As HMRC’s MTD programme expands, Monesize Core’s modular architecture allows compliance to extend into new areas without replacing the underlying platform. The same system that handles MTD for VAT today handles the broader programme as it develops.
ALSO READ: Introducing Monesize Core: One Unified Platform for Enterprise Operations and Finance
Recognition Is the Start of the Conversation, Not the End
When a software provider tells you they are HMRC recognised, the right response is to treat that as confirmation they cleared the minimum bar, and then ask the questions that actually determine whether the software is right for your business.
The recognised list is a starting point for identifying products that can connect to HMRC’s systems. It is not a shortcut to selecting software that will handle your compliance obligations correctly, scale with your operation, or protect you if HMRC asks questions about your records.
Choose software that is both recognised and ready. The difference shows up every quarter.
See What HMRC-Ready Actually Looks Like
Monesize Core maintains digital records at the transaction level, submits directly through HMRC’s MTD API, and scales across branches and reporting frameworks without bridging tools or manual workarounds.
See the difference between recognised and ready. Request a demo.