Almost 90% of digital tax returns in the UK are now filed through third-party software rather than direct government portals, and the number of software providers working with HM Revenue and Customs has risen to nearly 3,000 [1]. Every one of those payroll products that files Real Time Information has passed the same gate: HMRC recognition. With around 30.2 million people paid through PAYE in December 2025, the recognition scheme is the quiet mechanism that keeps that volume of data flowing correctly [2].
The phrase "HMRC-recognised" appears on almost every payroll product's marketing, yet what it actually certifies is widely misunderstood. It is not an endorsement, a quality ranking or a guarantee of good service. It is a technical confirmation that the software has been tested and can file PAYE information to HMRC in the correct format.
This explainer sets out exactly what HMRC recognition means, how a product earns it, what it does and does not cover, and why it should be treated as the starting point of a payroll decision rather than the finish line. It is written for employers choosing payroll software, accountants advising clients, and anyone who has seen the badge and wondered what sits behind it.
Key takeaways
- HMRC recognition confirms that payroll software has been tested to file Real Time Information such as the FPS and EPS correctly, nothing more [3].
- HMRC uses the term "recognised", not "approved" or "certified", and cannot recommend one product over another [4].
- Developers apply to HMRC's Software Developer Support Team, which aims to respond within six weeks and continues to monitor live data quality after recognition [5].
- The free HMRC tool is capped at nine employees and does not produce payslips, so most employers need commercial recognised software [6].
- Recognition is the baseline every serious product meets; developer experience, statutory coverage and pricing are what actually separate them.
What HMRC recognition actually certifies
HMRC recognition is a confirmation that a piece of software can report PAYE information to HMRC online in the required format. HMRC will accept forms and returns sent using any commercial product on its recognised list [3]. The scheme exists so that employers can trust that a product will produce submissions HMRC systems will accept, and so that HMRC receives clean, correctly structured data.
The precise wording matters. HMRC uses "recognised", not "approved" or "accredited". The distinction is deliberate: recognition means the software passed HMRC's technical tests, but HMRC does not endorse the product, cannot recommend one over another, and is not responsible for any problems an employer has with software they have bought [4]. A product that describes itself as "HMRC-approved" or "HMRC-certified" is using language HMRC itself avoids.
What recognition is tested against
Recognition is awarded against HMRC's published technical specifications for the relevant tax year. The core of this is the Real Time Information specification, which defines exactly how a Full Payment Submission and an Employer Payment Summary must be structured for HMRC's systems to accept them [7]. PAYE recognition can cover more than one strand: alongside RTI, it can extend to Expenses and Benefits (EXB) reporting, with each strand assessed on its own terms [5].
| Element | What recognition confirms |
|---|---|
| RTI submissions | The software builds and sends the FPS and EPS in the correct format [[7]](https://www.gov.uk/government/publications/real-time-information-internet-submissions-2025-to-2026-technical-specifications) |
| Data structure | Submissions match HMRC's data item specification and pass validation [[3]](https://www.gov.uk/guidance/find-payroll-software-that-is-recognised-by-hmrc) |
| Ongoing quality | HMRC monitors live-environment data errors after recognition is granted [[5]](https://www.gov.uk/guidance/paye-recognition-for-payroll-software-developers) |
Recognition therefore certifies the reporting mechanism. It does not certify the wider quality of the product, its user interface, its support, or how well it calculates figures beyond what the submission validation checks. Those remain the buyer's job to assess.
How software becomes HMRC-recognised
The recognition process runs between HMRC and the software developer, not the employer. A developer applies to HMRC's Software Developer Support Team, which replies with instructions and then reviews the application, aiming to respond within six weeks [5]. The product is tested against the technical specification, and where HMRC identifies gaps, it seeks a commitment from the developer to make changes before awarding recognition [3].
Recognition is not a one-off certificate that lasts forever. HMRC has a responsibility to ensure software on the recognised list remains fit for purpose, and the award for any PAYE strand is subject to ongoing assessment of the data issues and errors a product actually submits in the live environment [5]. A product that starts sending malformed data can face scrutiny. This ongoing monitoring is why recognition is a meaningful signal, even though it is a floor rather than a ceiling. A modern HMRC-recognised payroll API is designed to keep passing that live-data assessment automatically as rates and specifications change each April.
Why every serious product holds it
Because filing RTI is mandatory for virtually every employer, recognition is effectively a requirement to operate in the UK payroll market. Employers must report payroll data to HMRC on or before each payday under Real Time Information, and the only way to do that at scale is through recognised commercial software or HMRC's own free tool [8]. As a result, every credible payroll product carries the badge. That is precisely why recognition cannot be a differentiator: it is the price of entry. Employers comparing payroll software should treat the badge as confirmed on both sides and focus on what differs.
The free tool sets the floor
HMRC publishes its own free payroll application, Basic PAYE Tools, for the smallest employers. It is genuinely free and genuinely recognised, which makes it the true baseline any paid product has to justify itself against. Its limits, however, are significant.
| Feature | HMRC Basic PAYE Tools | Typical commercial recognised software |
|---|---|---|
| Employee cap | Up to 9 employees [[6]](https://www.gov.uk/basic-paye-tools) | No practical cap |
| Payslips | Not produced [[9]](https://www.gov.uk/government/publications/basic-paye-tools-user-guide/basic-paye-tools-user-guide) | Produced automatically |
| Auto-enrolment assessment | Not performed | Performed each pay run |
| Non-PAYE deductions | Not recorded, for example attachment of earnings [[9]](https://www.gov.uk/government/publications/basic-paye-tools-user-guide/basic-paye-tools-user-guide) | Handled |
| Agent and bureau use | Not designed for it [[9]](https://www.gov.uk/government/publications/basic-paye-tools-user-guide/basic-paye-tools-user-guide) | Built for multiple clients |
The free tool is designed for businesses with fewer than 10 employees, does not produce payslips, and does not assess auto-enrolment or record deductions unrelated to PAYE such as an attachment of earnings [6][9]. For any employer that has more than nine staff, needs payslips, or must run pension assessment, it is not a workable option. This is the gap commercial recognised software fills, and it is where the real comparison between products begins. Accountants running payroll across many client schemes need software built for that, since the free tool is explicitly not designed for agents or bureaux [9], which is why they turn to a dedicated payroll bureau platform.
Why recognition matters: the cost of getting filing wrong
Recognition matters because incorrect or late filing carries real penalties, and recognised software is built to avoid both. Under RTI, an employer must file a Full Payment Submission on or before each payday [8]. Late filing attracts automatic penalties that scale with the size of the payroll.
| Employees in the PAYE scheme | Monthly late-filing penalty |
|---|---|
| 1 to 9 | £100 |
| 10 to 49 | £200 |
| 50 to 249 | £300 |
| 250 or more | £400 |
Where a failure continues beyond three months, HMRC may add a further penalty of 5% of the tax and Class 1 National Insurance that the missing return should have shown [10]. Recognised software that files the submission automatically at the end of a pay run removes the manual step that produces most late filings. It also keeps the calculation current: for the 2026-27 tax year that means applying employer National Insurance at 15% above the £5,000 Secondary Threshold [11] and income tax across the correct bands [12], without the employer reconfiguring anything each April.
What recognition does not tell a buyer
Because recognition is a floor, it is silent on the factors that actually separate one product from another. It says nothing about how well the software handles Scottish tax, directors on an annual National Insurance basis, or the newest statutory payments. It says nothing about support quality, reliability at month-end, or whether the product locks the buyer into a wider accounting or HR ecosystem. And it says nothing about pricing model, where a per-payslip approach scales with payroll activity rather than headcount. These are the questions a buyer should ask once recognition is confirmed. For a fuller technical view of what a complete engine handles, this guide to the UK payroll API covers the statutory surface in detail.
How to verify a product is genuinely recognised
Because "HMRC-recognised" carries weight, it pays to confirm a claim rather than take marketing copy at face value. HMRC maintains a single public list of recognised payroll software on GOV.UK, and any genuine product appears there [3]. The list separates free products from paid ones, and it flags the free software recognised for businesses with fewer than 10 employees [4]. Checking a product against that list is the most reliable verification available, because it comes directly from HMRC rather than from the vendor.
A few practical checks help a buyer read the list correctly. First, the recognised name may differ from a marketing brand, so the underlying product name is what to search for. Second, recognition is tied to a tax year's specification, so a product should reflect current-year compliance rather than a badge earned several years ago and left unchanged [7]. Third, the language matters: a product describing itself as "recognised" is using HMRC's own term, while "approved" or "certified" signals a vendor stretching the wording HMRC deliberately avoids [4].
For an employer, this verification takes minutes and removes a whole class of risk. Filing PAYE is not an area where an unrecognised or out-of-date product is worth the saving, given that HMRC accepts returns only from software that meets its specification [8]. Confirming recognition first, then evaluating coverage, pricing and support, is the sequence that keeps a payroll decision on solid ground.
Where recognition is heading
The recognition scheme sits inside a larger shift. HMRC has committed to an API-first approach to digital delivery, with an ambition for most interactions to be digital by 2030, and it explicitly wants a thriving, innovative software market rather than a single government portal doing everything [1][13]. The rise from around 600 to nearly 3,000 third-party providers is the direct result of that strategy [1].
For employers and developers, the practical consequence is that recognised software is increasingly the primary channel to HMRC, not an alternative to a manual one. As payroll becomes something platforms embed rather than a standalone product every business logs into separately, recognition remains the gate each of those embedded engines must pass. Occasional or one-off needs can still be met by lighter recognised options such as an instant payslip generator, while businesses running regular payroll rely on a full recognised engine.
Conclusion
HMRC recognition is best understood as a technical pass mark, not a seal of approval. It confirms that software can file Real Time Information correctly, that it has been tested against HMRC's specification, and that HMRC continues to watch the quality of the data it sends. It does not rank products, endorse them, or guarantee anything about their wider quality. Every serious UK payroll product holds it, which is exactly why it should be the first box a buyer ticks and then moves past.
The more useful questions come after the badge is confirmed: how completely the software covers UK statutory rules, how it prices, whether it ties the buyer into a wider ecosystem, and how well it fits the way the business or platform actually runs payroll. As HMRC pushes towards a digital-first, API-led future, recognition will stay essential and stay invisible, the floor that lets everything built on top of it be trusted.
Frequently asked questions
Is HMRC-recognised the same as HMRC-approved?
No. HMRC uses the term "recognised", which means the software has passed HMRC's technical tests for filing PAYE information online [3]. HMRC does not "approve", "accredit" or "certify" payroll products, and it cannot recommend one over another or take responsibility for problems with software an employer has bought [4]. A product marketed as "HMRC-approved" is using language HMRC itself does not use.
Does an employer legally have to use HMRC-recognised software?
An employer must report payroll to HMRC through Real Time Information on or before each payday, and in practice that requires recognised software or HMRC's free tool [8]. There is no separate legal duty to use a recognised commercial product specifically, but any software used to file RTI has to meet HMRC's specification, which is what recognition confirms [7]. For employers with more than nine staff, a recognised commercial product is effectively the only workable route.
Is the free HMRC payroll tool enough for a small business?
For the very smallest employers it can be, but its limits are strict. Basic PAYE Tools is capped at nine employees, does not produce payslips, and does not assess auto-enrolment or record non-PAYE deductions [6][9]. A business that expects to grow beyond nine staff, needs to issue payslips, or has automatic enrolment duties will need commercial recognised software instead.
How long does HMRC recognition last?
Recognition is not a permanent certificate. HMRC aims to respond to a developer's application within six weeks, and once granted, the award remains subject to ongoing assessment of the data errors a product submits in the live environment [5]. Software is also expected to keep pace with each year's updated specification, so recognition reflects continuing compliance rather than a single point in time.
