Payroll Bureau Services: A Complete Guide
More than 60% of UK businesses now outsource some or all of their payroll, according to industry research, and the employer National Insurance rate rose to 15% from 6 April 2026 [1]. Those two facts sit behind a steady shift towards payroll bureau services: as the cost and complexity of running a compliant payroll climb, more employers hand the work to a specialist rather than absorb it in-house.
A payroll bureau processes wages, deductions and HMRC submissions on behalf of other businesses. It is one of several ways to run UK payroll, and it is often confused with fully managed outsourcing, with cloud payroll software, and with the accountant who files a company's annual accounts. Each of those is a distinct arrangement with different responsibilities and a different price.
This guide sets out what payroll bureau services actually cover, how they are priced, who remains liable to HMRC when payroll is outsourced, and the point at which a bureau arrangement starts to make financial sense. It is written for business owners weighing up the option and for accountants considering whether to run a bureau of their own.
Key takeaways
- A payroll bureau processes payroll and files Real Time Information with HMRC on behalf of client businesses, usually charging per payslip or per employee per month.
- A bureau service is not the same as fully managed payroll: the client typically keeps some in-house control and supplies the underlying data each pay period.
- The employer, not the bureau, remains legally accountable to HMRC for the accuracy of payroll and the payment of PAYE and National Insurance [5].
- Late Full Payment Submissions attract monthly penalties from £100 to £400 depending on headcount [3].
- Modern bureaux increasingly run on an HMRC-recognised payroll engine that handles many clients through one integration, replacing per-client desktop installations.
What payroll bureau services are
A payroll bureau is an external provider that runs payroll for other organisations. Each pay period, the client sends the bureau the raw inputs (hours worked, starters, leavers, salary changes, bonuses, absence), and the bureau calculates gross-to-net pay, produces payslips, files the required returns with HMRC, and tells the employer what to pay each worker and what to remit to the tax authority [1]. The bureau operates the machinery; the employer supplies the data and signs off the result.
That division of labour is what distinguishes a bureau from a fully managed service. A bureau leaves the employer holding the employment relationship and the source data, and takes on the processing and filing. It suits organisations that want to keep control of their payroll data and approvals while removing the technical burden of calculation and compliance [6].
Payroll bureau services are typically delivered by accountancy firms, specialist payroll companies, or software platforms that offer a bureau layer. The common thread is that one provider runs many client payrolls from a single operation, which is why bureau economics depend heavily on the software underneath. Accountancy practices that want to add payroll to their offering can do so through a multi-client payroll dashboard rather than installing separate software for each client.
Bureau service versus fully managed payroll
The terms "payroll bureau" and "outsourced payroll" are often used interchangeably, but they describe different levels of delegation. Understanding the difference matters because it changes who does what each month and how much the service costs [4].
| Feature | Payroll bureau | Fully managed payroll |
|---|---|---|
| Who holds the payroll data | The employer | The provider |
| Who supplies inputs each period | The employer sends hours and changes | The provider gathers and maintains them |
| Payslip production | The bureau | The provider |
| RTI filing to HMRC | The bureau, under the employer's PAYE reference | The provider, under the employer's PAYE reference |
| Employee queries | Handled in-house | Often handled by the provider |
| Typical cost | Lower, processing only | Higher, full administration |
A bureau processes what it is given and files it correctly. A fully managed service additionally answers employee questions, chases missing timesheets, manages pension correspondence and takes on more of the administrative overhead [1]. Neither model changes the underlying legal position: both file under the employer's own Employer PAYE Reference, and both leave the employer accountable to HMRC [9].
What a bureau does each pay period
The bureau's core job is to turn a set of inputs into a compliant payroll run. In a typical monthly cycle, the employer submits changes, the bureau calculates pay and deductions, the employer approves, and the bureau files with HMRC and issues payslips [2]. The sequence is repeated every pay period, whether weekly, fortnightly or monthly.
Within that cycle, the bureau calculates income tax under the correct tax code, employee and employer National Insurance, pension contributions, student loan deductions and any statutory payments due [6]. It then produces a Full Payment Submission on or before payday and, where relevant, an Employer Payment Summary to reclaim statutory pay or declare a nil liability [7]. The output the employer receives is a set of payslips, a summary of what to pay staff, and a figure to remit to HMRC by the 22nd of the following tax month [15].
What a payroll bureau handles under HMRC rules
The value of a bureau lies in its command of the HMRC framework. Payroll is not simply arithmetic; it is a regulated process with strict deadlines, defined submission formats and financial penalties for error. A competent bureau absorbs that complexity so the client does not have to.
RTI submissions: FPS and EPS
Real Time Information is the reporting regime under which every UK employer tells HMRC about payments and deductions on or before each payday [2]. The Full Payment Submission is the primary return: it reports gross pay, income tax, National Insurance, student loan deductions and statutory payments for every employee paid in the period [6]. A bureau files this under the client's PAYE reference, which is what allows HMRC to treat the bureau's submission as discharging the employer's obligation [9].
The Employer Payment Summary is the secondary return, filed by the 19th of the following tax month to claim reductions such as statutory pay recovery, Employment Allowance or a nil declaration when no employees were paid [7]. Missing these deadlines carries a real cost. HMRC charges monthly late-filing penalties on a sliding scale, and a bureau that files reliably is buying its clients out of that exposure [3].
| Number of employees | Monthly late-filing penalty |
|---|---|
| 1 to 9 | £100 |
| 10 to 49 | £200 |
| 50 to 249 | £300 |
| 250 or more | £400 |
Any bureau or platform filing RTI at scale must be HMRC Recognised, which is the baseline requirement for submitting Full Payment Submissions through recognised software rather than a differentiator between providers [2]. A fuller walk-through of the filing calendar sits in the guide to the running PAYE payroll checklist.
Statutory deductions and payments
A bureau applies the correct 2026-27 thresholds to every calculation. Income tax runs on a Personal Allowance of £12,570 with a basic rate of 20% up to £50,270, and employer National Insurance is charged at 15% above the Secondary Threshold of £5,000 a year [10]. Getting the category letters right matters too, because employees under 21, apprentices under 25 and veterans in their first year of civilian work attract a 0% employer rate up to £50,270 [10].
Statutory payments are a frequent source of error for employers who process payroll manually. From 6 April 2026, Statutory Sick Pay is due from the first day of sickness at £123.25 a week or 80% of average weekly earnings if lower, and the previous Lower Earnings Limit qualifying condition has been removed [12]. Family-related payments such as Statutory Maternity Pay run at £194.32 a week from week seven [17]. A bureau tracks these rates and applies small employers' relief where the client qualifies. The changes to sick pay are covered in more depth in the article on SSP reform from April 2026.
Student loan deductions add another layer. A bureau applies the right repayment plan (Plan 1 at £26,900, Plan 2 at £29,385, Plan 4 at £33,795, all at 9% above threshold) and deducts any postgraduate loan first [18]. Errors here are common because there is no Plan 3 and the thresholds differ by nation, so the calculation is easy to get wrong without software that encodes the rules.
Auto-enrolment and pensions
Workplace pension duties fall on the employer, not the bureau, but a bureau administers them within the payroll run. Every employer must assess its workforce, enrol eligible jobholders into a qualifying scheme, deduct contributions and file declarations with The Pensions Regulator [13]. A bureau calculates the contributions each period and passes the pension data to the chosen scheme.
Where the client uses a master trust such as NEST, Smart Pension or The People's Pension, the bureau integrates the contribution file into the pay run so that deductions and uploads stay in step [13]. This is one of the areas where a bureau saves the most administrative time, because auto-enrolment assessment has to be repeated every pay period as employees cross age and earnings thresholds. The Employment Allowance, worth up to a set amount off the employer National Insurance bill, is also claimed through the payroll and a bureau will apply it where the client is eligible [14].
How payroll bureau services are priced
Pricing is where bureau services diverge most sharply from other payroll options. There is no single market rate, and the headline figure often hides the true cost once frequency and extras are added. Understanding the two dominant models is the key to comparing quotes fairly.
Per-payslip versus per-employee models
The two common structures are a charge per payslip produced and a charge per employee per month. The distinction seems minor until pay frequency enters the picture, at which point the two models can produce very different bills for the same workforce [1].
| Pricing model | How it is charged | Best suited to |
|---|---|---|
| Per payslip | A fixed fee for each payslip generated | Businesses with fluctuating headcount or seasonal staff |
| Per employee per month | A monthly fee for each employee on the payroll | Businesses with stable headcount paid monthly |
| Tiered or banded | A fixed fee covering a range of employees | Growing businesses wanting predictable cost |
The trap in per-payslip pricing appears with weekly payrolls. A team of 10 paid weekly generates roughly 43 payslips a month, so a per-payslip fee is multiplied by every run, not every head [2]. For a monthly payroll, per payslip and per employee amount to the same thing. For a weekly payroll, per-employee pricing is usually cheaper, and per-payslip pricing rewards businesses whose headcount rises and falls with the season. Employers comparing options should map the model against their own pay frequency before signing, and can read a fuller breakdown of the trade-offs on the page covering Moonworkers pricing.
What sits inside a bureau fee
A quoted rate rarely covers everything. A low headline fee often includes only payslip production and RTI filing, with additional services charged on top [6]. Before comparing two bureaux, an employer needs to know which of the following are inside the fee and which are extra.
Common inclusions and add-ons are: payslip production and RTI filing (usually core), pension contribution uploads and auto-enrolment assessment (sometimes core, sometimes extra), BACS payment of net wages to staff (often an add-on), production of P60s at year end and P45s for leavers [19], P11D reporting of benefits in kind, and one-off setup or migration fees when a new client is onboarded. The Apprenticeship Levy, payable at 0.5% by employers with a pay bill above £3,000,000, is declared through the same EPS the bureau already files, so large clients should confirm it is handled [16].
For an employer that only needs the occasional payslip rather than a full ongoing service, a bureau relationship can be overkill. A single compliant payslip can be produced through an instant payslip generator without the commitment of a monthly contract.
Compliance and accountability when payroll is outsourced
The most misunderstood aspect of using a payroll bureau is where legal responsibility sits. Outsourcing the work does not outsource the liability, and getting this wrong exposes an employer to penalties it may assume the bureau is carrying.
The employer keeps the liability
HMRC is explicit that accountability cannot be delegated. Any liabilities arising from mistakes made by a third party remain with the employer, who is expected to treat the outsourced process as if it were run in-house and to carry out enough checks to be satisfied with the decisions the bureau is making [5]. If a bureau miscalculates and underpays PAYE, HMRC pursues the employer, not the bureau.
That does not make a bureau pointless; it makes provider selection important. Payment made by a payroll agent discharges the employer's liability only when the agent files under the employer's own PAYE reference and discloses the details correctly to HMRC [9]. A reliable bureau reduces the practical risk of error to near zero, but the employer should still review the numbers each period rather than approving blind [6].
Reporting an outsourcing arrangement to HMRC
Employers can, and in some cases should, tell HMRC about a payroll outsourcing arrangement using an online form [4]. This is separate from the authorisation that lets a bureau act as an agent. A bureau operating as a formal agent registers through the PAYE for Agents online service, which gives it access to file and view client PAYE records under a controlled authorisation [8].
The distinction between an agent and an unauthorised processor matters for data access and for the audit trail HMRC expects. An authorised agent appears in HMRC's records against the client; an informal processor does not [8]. Businesses should confirm which arrangement their bureau operates, because it affects who can speak to HMRC on the company's behalf and how a dispute would be resolved [4].
When payroll bureau services make sense
A bureau is not the right answer for every business. The case for one strengthens as payroll grows in size, frequency or complexity, and weakens for the smallest and simplest employers who can run a compliant payroll themselves with software.
Signs a business has outgrown manual payroll
Certain triggers reliably indicate that manual or spreadsheet-based payroll has become a liability. The clearest is a growing headcount combined with multiple pay frequencies, because each additional variable multiplies the chance of a filing error [2]. A business paying weekly and monthly staff, running auto-enrolment, and handling statutory pay is operating close to the limit of what a non-specialist can manage without mistakes [13].
Other signals include repeated late FPS submissions and the penalties that follow, difficulty keeping pace with rate changes such as the 15% employer National Insurance rate or the day-one Statutory Sick Pay rules, and the opportunity cost of an owner or office manager spending hours each month on payroll rather than on the business [10]. At that point, the fee for a bureau or for capable software is usually lower than the cost of the errors and the time [3]. Smaller businesses that want to keep payroll in-house can instead move to dedicated UK payroll software that automates the same compliance work.
The accountant-run bureau model
For accountancy practices, running a bureau is a service line rather than a cost. Clients already trust the firm with their accounts, and payroll is a natural extension that generates recurring monthly revenue [1]. The economics depend entirely on the software: a practice running 50 client payrolls through 50 separate desktop installations spends most of its margin on administration, whereas a practice running the same 50 clients through one multi-client platform scales cleanly [8].
This is where the technology under the bureau matters most. A modern bureau platform lets an accountant manage many employers from a single dashboard, with per-client approval workflows and a single integration to HMRC, rather than repeating the same setup for every client [6]. Practices building or scaling a bureau can evaluate an accountant payroll platform designed for multi-client management, and developers building bureau tooling of their own can embed the same compliance engine through an HMRC-recognised payroll API.
Choosing a payroll bureau or bureau platform
Because HMRC recognition is a baseline that every serious provider holds, the criteria that actually separate bureaux lie elsewhere. The most useful questions are about pricing transparency, the software underneath, and the division of responsibility. An employer should ask whether the fee is per payslip or per employee, what the fee includes and excludes, whether the provider files as an authorised agent, and how errors are corrected [4].
For a business choosing between a traditional bureau and running payroll in-house on software, the decision often comes down to control and volume. Software keeps the data and the approvals inside the business and suits employers who want to run their own payroll with the compliance automated. A bureau suits those who would rather delegate the processing entirely [1]. A growing number of providers now blur the line, offering a platform that an employer can run directly or hand to an accountant, with the same HMRC-recognised engine serving both [2].
Conclusion
Payroll bureau services occupy a middle ground between running payroll entirely in-house and handing the whole function to a fully managed provider. They remove the technical burden of calculation and filing while leaving the employer in control of the data and, crucially, still accountable to HMRC for the result. That accountability is the single fact most employers underestimate, and it is the reason provider reliability matters more than headline price.
As employer costs rise and the compliance framework grows, the practical question is shifting from whether to get help with payroll to what shape that help should take. The answer increasingly points to software rather than service: an HMRC-recognised engine that an employer can run directly, or that an accountant can operate across many clients from one dashboard, is displacing the per-client installations that defined the traditional bureau. The direction of travel is towards fewer moving parts, one integration to HMRC, and compliance handled by the engine rather than by hand.
FAQs
Is a payroll bureau the same as outsourcing payroll?
Not quite. A payroll bureau processes payroll and files with HMRC using data the employer supplies each period, so the employer keeps some in-house control. Fully outsourced or managed payroll hands the whole function, including data gathering and employee queries, to the provider. A bureau is a partial form of outsourcing rather than a complete one.
Who is responsible if a payroll bureau makes a mistake?
The employer. HMRC is clear that accountability cannot be outsourced, so any liability arising from a bureau's error remains with the business whose PAYE reference the return was filed under. A reliable bureau reduces the risk to almost nothing, but the employer should still review each payroll run before approving it rather than signing off without checking.
How much do payroll bureau services cost in the UK?
Bureaux charge either per payslip produced or per employee per month, and the right model depends on pay frequency. Per-employee pricing usually works out cheaper for weekly payrolls, while the two models cost the same for monthly payrolls. Setup fees, BACS payments, pension uploads and year-end forms are often charged on top of the core processing fee, so it pays to confirm what is included.
Can an accountant run payroll as a bureau service?
Yes, and many do. Payroll is a natural extension of an accountancy practice and generates recurring monthly revenue. The economics depend on the software: running many clients through a single multi-client platform with one HMRC integration is far more profitable than maintaining separate installations for each client, which is why bureau platforms are built around multi-employer management.
