
Foundations
Part of Payroll software in England: what PAYE, pension duties and UK business counts show a supplier
How to scope the payroll software market size in England
Learn how to scope the payroll software market size in England: define the customer base, use ONS and PAYE evidence and build labelled ranges.
No official dataset gives the payroll software market size in England as a current revenue total. A credible estimate therefore needs several labelled measures, not one figure borrowed from a commercial forecast or scaled from an unrelated UK statistic.
What to take away
- No official dataset gives a current England revenue total, so a credible estimate needs several labelled measures.
- Decide scope firstcustomers, outsourced payroll, bundled functions, employer sizes and free products all change the answer.
- ONS business counts show market structure, not payroll software buyers, because VAT-only firms and outsourcing distort the total.
- England's employer count comes from the regional tables, not from scaling the UK total by an average price.
- HMRC recognition measures supply, not active licences, England revenue or product quality.
- Automatic enrolment duties tie pension assessment to every pay cycle, shaping what a product must do.
- Build low, central and high cases from observed contract values, then reconcile them with stratified customer research.
Decide what belongs in the market
Payroll software can mean an employer application, a bureau platform used for many clients, an enterprise payroll module, HMRC's free tool, or software supplied with a managed service. Pricing may be per employee, per payslip, per employer, per payroll run or part of a wider HR package.
Before counting anything, record these scope decisions:
- Which geography rule appliescustomer headquarters, worker location or billing address.
- Whether the estimate covers customers, suppliers or both.
- Which models countemployer applications, bureau platforms, enterprise modules, HMRC's free tool or software supplied with a managed service.
- Whether outsourced payroll is included.
- Whether bundled HR functions and free products are included.
- Whether subscriptions, implementation work and managed processing are counted separately, and which pricing basis applies.
Scope decisions before counting
- Customers, suppliers or both in England
- Outsourced payroll revenue included
- Pension, HR, time and payment functions
- Employee and employer sizes covered
- Free products and internal systems
- Calendar or tax year used
Those choices can change the answer substantially. Keep software subscriptions, implementation work and managed processing as separate lines.
Geography needs a rule too. A supplier can sit outside England and serve English employers, while a bureau can process everything remotely. Choose customer headquarters, worker location or billing address, then say which.
Use ONS data to size the customer base
The ONS UK business: activity, size and location release reported 2.73 million VAT and/or PAYE businesses across the UK in March 2025. Its underlying dataset supports regional and employment-size analysis.
That total is not a payroll-software customer count. VAT-only organisations may have no employees, one enterprise can operate several local units, and employers may outsource payroll or use a bundled system. Extract the England tables and PAYE-relevant size bands, then describe them as an upper-market structure indicator, not buyers.
England's share sits in the regional tables of the same release, not in a scaled UK total.
Map the compliance perimeter
HMRC says employers running payroll themselves normally report employee payments and deductions on or before payday. That report is usually a Full Payment Submission. Its payroll software guidance says software must report PAYE information online unless the employer is exempt, and explains functional differences such as pension deductions, payslips and varied pay periods.
The HMRC-recognised software list shows free and paid products able to report PAYE online. It measures recognised supply, not active licences, England revenue or product quality. HMRC expressly does not recommend one supplier over another. Names on the list change, so check the current list rather than a review site.
Automatic enrolment adds recurring workflow. The Pensions Regulator says an employer must assess ages and earnings and maintain contributions whenever it runs payroll. Its payroll-process guidance advises checking whether software supports automatic enrolment and the chosen pension arrangement.
Ongoing duties cover age and earnings checks, contribution calculations, opt in and opt out events, and record keeping. Each one lands inside a pay run.
Data protection sits inside the same perimeter. ICO controller and processor guidance decides who determines purpose and means, not whether a contract label matches the facts, and it applies to every supplier counted in the estimate.
Commercial models, each with a buyer in mind
Buyer example
- Employer subscription
- a 12-person agency paying weekly and monthly
- Bureau platform
- a practice running 400 client payrolls
- Enterprise module
- a 4,000-employee group with several PAYE schemes
- Managed payroll
- a care group with heavy exception volumes
- Embedded payroll
- a sector platform adding payroll to its own product
What to test
- Employer subscription
- margin after onboarding and payday support
- Bureau platform
- batch work, client separation, exception queues
- Enterprise module
- integrations, configuration, change testing
- Managed payroll
- who supplies data, files, releases pay, corrects errors
- Embedded payroll
- one map of data, filing, failures and support
Where the real product gaps are
The gaps sit between systems and people: migration of historical pay and pension data, rejected pension files, opt out handling and correcting an FPS after payday.
Build ranges from observed buying data
Segment England employers by headcount, payroll frequency and operating model. For each segment, measure the proportion using paid standalone software, a wider suite, a bureau or an internal system. Multiply validated customer counts by observed annual contract values, keeping setup and service fees apart.
Publish low, central and high cases with every assumption, each carrying its vintage, inputs and uncertainty. Verify prices from contracts or current supplier pages, churn from cohorts rather than anecdotes, and employer counts from the same ONS edition. A useful estimate is reproducible and decision-specific.
Add a separate supply-side view if competitive density matters. Count current entries on the recognised-software page by product category only after cleaning supplier and product names; the list carries products from suppliers such as Sage, Xero, IRIS, BrightPay and QuickBooks, and one supplier can list several products. The page can change between observations, so do not infer sales, capacity or England coverage from a listing.
Finally, reconcile the estimate with customer research. Ask a stratified sample what they actually paid, which functions were bundled and whether fees cover software, advice or processing. Report response count and recruitment method.
Before you act
- Define whether customers, suppliers or both must be in England.
- Decide if outsourced payroll and bundled HR functions count.
- Extract England tables and PAYE-relevant size bands from ONS data.
- Keep software subscriptions, implementation work and managed processing separate.
- Verify prices from contracts or current supplier pages.
- Reconcile the estimate with a stratified sample of actual buyers.
Common questions
Why is there no single headline figure for the England payroll software market?
No official dataset supplies a current revenue total for payroll software bought by organisations in England. A credible estimate therefore needs several labelled measures, not one figure borrowed from a commercial forecast or scaled from an unrelated UK statistic.
What does the HMRC-recognised software list actually measure?
It shows free and paid products able to report PAYE online. It measures recognised supply, not active licences, England revenue or product quality, and HMRC expressly does not recommend one supplier over another. One supplier can list several products, and the page can change between observations.
How should a reader build market ranges from observed buying data?
Segment England employers by headcount, payroll frequency and operating model. For each segment, measure the proportion using paid standalone software, a wider suite, a bureau or an internal system. Multiply validated customer counts by observed annual contract values, keeping setup and service fees apart, then publish low, central and high cases with every assumption.



