Technology, implementation and cost
4. Technology and integration
The platform matters, but it matters less than the people and the processes behind it. That said, there are baseline capabilities you should expect and integration requirements you need to confirm early.
Reporting is often where technology differences become most visible day to day. You need a platform that gives you the reports you actually use: payroll summaries, cost-centre breakdowns, pension contributions, variance reports, statutory payment tracking. Ask to see sample reports. If the standard reporting suite doesn't meet your needs, ask about custom reporting capability and whether it costs extra.
Integration with your existing systems is worth testing during the evaluation, not after you've signed. The most common integrations are HR software, time and attendance, pensions, and accounting. Ask whether the provider offers pre-built integrations, API access, or file-based data exchange. Pre-built integrations reduce implementation risk; APIs give you flexibility; file-based exchange is the fallback.
HMRC connectivity should be automated. RTI submissions, auto-enrolment, and year-end reporting should all flow directly from the platform without manual intervention. Ask whether legislative updates (tax codes, NI thresholds, statutory rates) are applied automatically and when they're typically available relative to the new tax year.
Employee self-service is increasingly standard: digital payslips, P60 access, personal detail updates, and holiday or absence requests. Ask what employees can do themselves and what still requires your team's involvement.
5. Implementation and transition
Implementation is where the quality of a provider's operation is tested for the first time, and it's where many relationships go wrong. A provider that runs payroll brilliantly for existing clients but has a chaotic onboarding process will give you a difficult start that colours everything after it.
A good implementation process follows a clear structure: discovery (understanding your payroll, your data, your processes), data migration (transferring employee records, pay history, year-to-date figures), configuration (setting up pay elements, deductions, reporting structures), parallel running (processing payroll on both old and new systems simultaneously to verify accuracy), go-live, and post-go-live support.
Ask this: "How many parallel runs do you recommend, and who manages them? What's your process if the first live pay run has errors?" The answers tell you how much the provider has thought about risk.
Dedicated project management makes a significant difference. Ask whether you'll have a named project manager for the implementation, or whether it's handled by the same team that will run your ongoing payroll. Both models can work, but you should know which you're getting.
Data migration deserves specific attention. How far back will historical data be migrated? In what format do they need your data? What validation checks do they run? In our experience, the most common cause of implementation delays is incomplete or poorly structured data from the outgoing provider, so it's worth establishing early what validation checks the new provider runs and how exceptions are handled. For a full walkthrough of what to expect, see our guide to payroll implementation.
TUPE considerations. If you currently have an in-house payroll team and you're outsourcing the function for the first time, the Transfer of Undertakings (Protection of Employment) Regulations 2006 may apply. TUPE can require your existing payroll staff to transfer to the new provider on their current terms and conditions. This isn't always the case (it depends on whether there's an "organised grouping of employees" principally dedicated to the payroll function), but it needs to be assessed early in the process. ACAS and legislation.gov.uk provide detailed guidance. Raise this with your provider and your legal team before you get to contract stage.
6. Pricing transparency
Cost matters, but the headline per-employee-per-month (PEPM) rate tells you surprisingly little on its own. What's included in that rate, and what's charged as an extra, can vary enormously between providers.
What's typically included in a standard PEPM rate: gross-to-net processing, payslip generation (digital and/or printed), RTI submissions to HMRC, pension auto-enrolment administration, and standard reporting.
What's often charged separately:
| Common extra |
Why it matters |
| Implementation/setup fee |
Usually the largest single charge in year one |
| Year-end processing (P60s, P11Ds) |
Happens every year; should be budgeted for |
| Ad-hoc or additional pay runs |
Bonus runs, off-cycle corrections |
| Bespoke reporting |
Beyond the standard report suite |
| Employee query handling |
Some providers charge per query above a threshold |
| Pension submission to the provider |
Filing, not just calculation |
| BACS payment processing |
If the provider makes payments on your behalf |
| P11D preparation and submission |
Benefits in kind reporting |
Ask this: "Give me a full breakdown of every charge I'd pay in a typical 12-month period, including year-end, for an organisation of our size and complexity." Then compare that total across providers, not just the PEPM rate.
Contract length and notice. Most UK managed payroll contracts run for one to three years, with three to six months' notice required for termination. Ask whether there's an initial minimum term before the notice period applies, and whether the contract auto-renews. Price escalation clauses are also worth checking: is the PEPM rate fixed for the contract term, or does it increase annually (and if so, by how much and linked to what)?
For a deeper breakdown of cost structures, see our full guide to payroll outsourcing costs. And when you're ready to formalise the comparison, our payroll RFP template is designed to surface these costs consistently across providers.