Around 30.3 million people are paid through PAYE in the UK each month, and every employer running that payroll has to register with HMRC before the first payday, even a company whose only worker is its single director [1] [2]. Payroll is a legal duty from the moment a business hires, and "payroll as a service" is the umbrella term for the different ways a business can meet that duty without doing everything by hand.
The phrase covers more than one delivery model, which is where confusion starts. It is used for a fully managed service, for cloud payroll software, and increasingly for an embedded payroll engine that another platform calls through an API. These models sit at very different points on the scale of control, cost and responsibility.
This article explains what payroll as a service means, the three delivery models behind the term, the employer duties any of them has to cover, and the point that trips up most buyers: where legal responsibility sits when payroll is outsourced. It is written for software platforms and businesses deciding how to deliver or consume UK payroll.
Key takeaways
- Payroll as a service spans three models: a fully managed service, cloud software, and an embedded API engine.
- Every UK employer must register with HMRC before the first payday and operate PAYE, whichever model it uses [2] [3].
- Legal responsibility for payroll accuracy stays with the employer even when the work is outsourced [4].
- Auto-enrolment is an ongoing duty that recalculates on every payrun and re-enrols staff every three years [5].
- An embedded engine lets a platform deliver full UK payroll inside its own product, rather than handing the job to a third party.
What payroll as a service actually means
At its simplest, payroll as a service means a business does not build and maintain its own payroll capability from scratch. Instead it consumes payroll as an ongoing service that someone else keeps compliant with HMRC's changing rules. The value is that tax bands, National Insurance thresholds and statutory pay rates all change at least once a year, and a service absorbs those updates so the business does not have to [6] [7].
Where the term gets slippery is in how the service is delivered, because three distinct models all wear the same label.
The three delivery models
The table below sets out the three models, who runs the payroll in each, and where the model sits on the control-versus-effort scale. The distinction matters because the same phrase can describe a hands-off managed service or a hands-on API integration.
| Model | Who runs the payroll | Best suited to |
|---|---|---|
| Managed service | A third-party provider runs it end to end | Businesses that want payroll off their plate entirely |
| Cloud software | The business runs it in-house using the software | Employers and bureaux wanting control with automation |
| Embedded API engine | Another platform runs it inside its own product | HR, ERP and fintech platforms offering payroll as a feature |
A managed service takes the whole process off the business, which hands over the effort but also the day-to-day control. Cloud software keeps the process in-house, giving the business control while automating the calculation and filing. An embedded engine inverts the model again: the payroll runs inside a host platform through an API, so the host's users get payroll as a native feature without ever seeing the underlying engine. Moonworkers packages its engine for the second and third of these through its SME payroll software and its HMRC-recognised payroll API.
Why the term shifted towards embedding
For years, payroll as a service meant either a managed bureau or a piece of software. The shift has been towards embedding, driven by platforms that want to offer payroll without becoming payroll companies. The wider market for API-based and embedded payroll has grown quickly on the back of this demand, as accounting systems, HR platforms and fintech products increasingly build payroll directly into their core applications rather than sending users elsewhere [8].
HMRC has encouraged this direction. Its stated strategy is to release richer APIs and support third-party innovation, continuing the approach that delivered Real Time Information through close work with software developers [9]. The result is that "payroll as a service" now often means a compliance engine other software calls, not a bureau a business phones. A developer evaluating that route can start from the public API documentation and a sandbox rather than a sales process.
The employer duties any payroll service has to cover
Whatever the model, the underlying legal duties are fixed by HMRC and do not change. A payroll service earns its keep by covering all of them correctly, so it is worth being precise about what "all of them" includes.
PAYE, RTI and paying HMRC
Every employer normally has to operate PAYE, HMRC's system for collecting Income Tax and National Insurance from employment, and must register before the first payday [3] [2]. On each payrun the service records pay, calculates deductions, and reports them to HMRC in a Full Payment Submission on or before the day the employee is paid [10]. It then has to account for what is owed and pay HMRC by the monthly deadline [11].
The calculation itself carries real money. For the 2026-27 tax year, employer National Insurance is charged at 15% on earnings above the £5,000 Secondary Threshold, so a single employee on £30,000 generates roughly £3,750 in employer National Insurance before any relief, a figure the service has to compute correctly on every run [7]. An error there is not a rounding issue but a direct cost or an underpayment to HMRC, which is why the accuracy of the engine matters as much as the convenience of the service.
Because filing RTI is mandatory and time-bound, this is the part a service must handle automatically rather than leaving as a manual step. Software that submits RTI must be HMRC-recognised, which confirms it meets HMRC's specifications for the Full Payment Submission and other returns [12]. The service also has to run year-end reporting and keep records available to HMRC on request, and it must handle deductions such as student loans, taking 9% of earnings above the relevant plan threshold [4] [13]. Accountancy firms delivering this across many clients typically rely on a multi-client payroll platform so each scheme files correctly every month.
Auto-enrolment and its ongoing nature
Payroll does not stop at tax. Every UK employer must put eligible staff into a workplace pension and contribute to it, a duty known as automatic enrolment [14]. This is not a one-off setup: once staff are enrolled, the employer must calculate and pay both its own and the worker's contributions for as long as each person remains an active member, which means the assessment recalculates on every payrun, including on part-period earnings [5].
The duty also renews. Every three years the employer must re-enrol eligible staff who previously left or opted out, on the anniversary of its duties start date [5]. A payroll service that treats auto-enrolment as a background feature rather than a live calculation on every run will eventually miss an assessment, which is why the pension step has to sit inside the payroll engine alongside the tax calculation [15].
What outsourcing does, and does not, transfer
The most important thing to understand about payroll as a service is what it does not do: it does not move the legal responsibility off the employer. HMRC is explicit that a business which outsources its payroll still has obligations for operating PAYE, and the liability for deducting and paying the right tax and National Insurance rests with the employer where it has not taken reasonable care [4].
This has two practical consequences. First, the employer has to exercise due diligence over any provider it uses, keeping documentation of how the provider works and considering whether its processes create any exposure [4]. HMRC even publishes guidance to help businesses spot the signs of payroll provider fraud, a reminder that handing payroll over is not the same as handing over accountability [16]. Second, because the buck stops with the employer, transparency matters: a service where the employer can see exactly what was calculated and filed is safer than one where the figures disappear into a black box. A business issuing the occasional payslip can keep that visibility with an instant payslip generator rather than losing sight of the numbers.
Managed service versus embeddable engine
The two ends of the payroll-as-a-service spectrum, a managed service and an embeddable engine, are close to opposites, and confusing them leads to the wrong choice.
A managed service is the hand-it-over model. The provider runs the whole process, and the business supplies data and receives outputs. It suits a business that wants payroll entirely off its plate and is comfortable with less direct control over timing and detail. An embeddable engine is the build-it-in model. The API is the payroll product, and another platform calls it from inside its own interface so its users get payroll as a native feature without seeing the engine behind it. This is the model a growing number of HR, ERP and fintech platforms choose, because it lets them offer full UK payroll, PAYE, National Insurance, RTI and auto-enrolment, without building the compliance logic themselves [9].
The pricing models differ too. A managed service usually charges for the labour of running payroll, while an engine is typically priced per payslip, so the cost scales with payroll activity rather than with seats or headcount, which is set out on the Moonworkers pricing page. The deeper technical picture of how a platform integrates an engine is covered in the companion guides to the payroll REST API and the RTI API.
Choosing a payroll as a service model
The right model depends on how much control a business or platform wants to keep and what it is trying to build. A single business that simply needs its own payroll run well is best served by cloud software or, for very occasional needs, an on-demand payslip. A software platform that wants payroll to be one of its own features needs an embeddable engine, because a managed service cannot be built into another product.
The deciding question for a platform is whether it is buying a service to consume or an engine to embed. A managed service and cloud software both leave the payroll product in someone else's hands, which is correct for an employer but wrong for a platform that wants payroll to be part of its own offering. For that platform, the embedded engine is the only model that fits, and reading the distinction correctly at the outset avoids a costly change of direction later. A single-person business at the other end of the scale can meet its duty with sole-trader payroll without taking on a full platform.
Conclusion
Payroll as a service is not one thing. It is a spectrum running from a fully managed service, through cloud software, to an embedded engine that other platforms build on, and the models differ most in who holds control and how the service is priced. What does not change across the spectrum is the set of duties underneath: register before the first payday, operate PAYE, file RTI on time, run auto-enrolment on every payrun, and keep records, all while the legal responsibility stays with the employer.
The direction of travel is towards embedding, as more platforms decide that payroll should be a native feature of their product rather than a job handed to a third party. That shift rewards engines that are HMRC-recognised as a baseline and then judged on the criteria that actually matter: transparency, developer access, and a compliance layer that runs correctly on every payrun without being asked.
Frequently asked questions
What does payroll as a service mean?
Payroll as a service means consuming payroll as an ongoing service kept compliant by someone else, rather than building and maintaining the capability in-house. The term covers three models: a fully managed service where a provider runs everything, cloud software the business runs itself, and an embedded API engine that another platform calls inside its own product [8]. All three exist to absorb the annual changes to tax, National Insurance and statutory pay so the business does not have to track them [7].
Does outsourcing payroll remove the employer's legal responsibility?
No. HMRC is clear that a business which outsources payroll still has obligations for operating PAYE, and the liability for deducting and paying the correct tax and National Insurance remains with the employer where it has not taken reasonable care [4]. The employer should keep documentation of how any provider works and monitor its processes. Outsourcing moves the effort, not the accountability.
What is the difference between a managed payroll service and a payroll engine?
A managed service runs the whole payroll process on the business's behalf, so the business supplies data and receives outputs while the provider keeps control of the detail. A payroll engine is a piece of software that performs the calculations and filings, and an embeddable engine exposes that through an API so another platform can build payroll into its own product [9]. A managed service is something a business consumes; an engine is something a platform builds on.
Does a payroll service handle auto-enrolment as well as tax?
A complete payroll service must handle both, because auto-enrolment is a legal duty for every UK employer alongside PAYE. Eligible staff must be enrolled in a workplace pension, contributions calculated and paid on every payrun, and staff re-enrolled every three years [5]. Because the assessment recalculates each pay period, the pension step needs to sit inside the same engine that runs the tax calculation rather than being bolted on separately [14].
