Self-service, bureau, enterprise module, managed service or embedded payroll, compared by buyer

A payroll product's revenue model affects its support workload, compliance exposure and customer promise. Charging per employee is only one choice. The more important distinction is whether the supplier sells a tool, runs payroll, enables a bureau or embeds a component in another platform.

Model	Primary buyer	Possible revenue unit	Main operating pressure
Employer software	Small or mid-sized employer	Base subscription plus employees	Usability and deadline support
Bureau platform	Accountant or payroll provider	Employers, employees or runs	Multi-client controls and throughput
Enterprise module	Larger organisation	Contract, modules and implementation	Configuration, integration and assurance
Managed payroll	Employer outsourcing the process	Employees, runs or service tier	Service delivery and responsibility boundaries
Embedded payroll	HR, finance or vertical platform	Usage, licence or revenue share	API reliability and shared accountability

Employer self-service software

This model helps an employer calculate pay and report PAYE. HMRC's find payroll software page shows that buyers must compare more than online reporting, including payslips, pension support and different pay periods. A low entry price may attract small employers, but onboarding, late-payday questions and tax-year updates can make support expensive.

Use headcount bands carefully. The buyer may add casual workers, directors or several pay frequencies without moving neatly into a new employee tier.

Bureau software

A bureau product serves organisations processing payroll for multiple clients. Its value can rest on permissions, batch actions, client-level audit records and exception management. The HMRC-recognised product directory includes products described for bureau use, but recognition is not an endorsement or evidence of commercial performance.

Pricing should reflect workload drivers such as employer count, active employees, runs and filing complexity. A single client can create disproportionate work when records arrive late.

Enterprise payroll modules

Larger buyers may purchase payroll within human-capital or finance systems. Contracts can include implementation, integrations, service levels and change control. Revenue per customer may be higher, but procurement, migration and assurance take longer. Configurability also creates testing obligations whenever rules or connected systems change.

Managed payroll services

Here, the customer buys operational delivery as well as software access. The contract must state who approves data, releases payments, submits reports, handles employee queries and corrects errors. HMRC still describes the employer's reporting obligations, while outsourcing changes who performs tasks rather than erasing accountability.

Managed service margins depend on exception rates and support discipline. Do not price only from employee count if fragmented data and manual approvals drive effort.

Embedded and API models

An embedded provider supplies payroll capabilities inside another product. Distribution may improve, but fault ownership becomes harder to explain. API availability does not prove that the whole workflow meets HMRC requirements. The developer should map filing, calculation, identity, data storage and customer support responsibilities end to end.

Automatic enrolment must also fit the operating model. The Pensions Regulator's payroll-process guidance recommends ensuring payroll processes work with the pension arrangement.

Choose a model by observing paid use, not by selecting the highest theoretical recurring revenue. Compare gross margin after support, acquisition time, implementation cost, retention, correction work and regulatory maintenance. A viable offer makes its service boundary visible before the first payroll is run.

Model cash timing as well as headline price. Annual subscriptions may fund development earlier, whereas implementation-heavy contracts can depend on milestones and acceptance. A bureau deal might expand gradually as the practice migrates clients. Record when revenue is earned, when staff work occurs and what refund or service-credit exposure exists.

The decision need not be permanent. A supplier can start with a narrow employer tool and later create a bureau edition, but shared code does not make the operational models identical. Introduce a new model only after measuring its extra permissions, support, testing and contractual burden.