Sizing the payroll software market with ONS and PAYE evidence instead of a headline figure

No official dataset supplies a current revenue total for payroll software bought by organisations in England. A credible market estimate therefore needs several labelled measures, not one figure borrowed from a commercial forecast or scaled from an unrelated UK statistic.

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:

• whether customers, suppliers or both must be in England;
• whether outsourced payroll revenue is included;
• whether pension, HR, time-recording and payment functions count;
• the employee and employer sizes covered;
• whether free products and internal systems are in scope;
• the calendar or tax year used.

Those choices can change the answer substantially. Keep software subscriptions, implementation work and managed processing as separate lines.

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.

Map the compliance perimeter

HMRC says employers running payroll themselves normally report employee payments and deductions on or before payday. 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.

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.

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. 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. It need not pretend that an official England revenue total exists.

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. One supplier can list several products, and the page can change between observations. 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. This check can expose double counting that a spreadsheet alone will miss.