What belongs in a meaningful payroll service-level agreement?
A headline about “99.9% accuracy” says little unless the contract defines how accuracy is measured, which errors count, what the employer had to supply and what happens after a mistake. For payroll, process commitments and evidence of control are usually more useful than a decorative percentage.
The nine clauses to negotiate
| Clause | Specify explicitly |
|---|---|
| Pay calendar | Cut-offs, draft delivery, employer approval, filing and bank deadlines |
| Inputs and customer duties | Format, data owners, approvals, treatment of missing or late changes |
| Included processing | Frequencies, headcount basis, PAYE entities, pension and statutory tasks |
| Exceptions | Number of correction cycles, emergency changes and off-cycle pricing |
| Quality review | Variance checks, sign-off evidence, handling of discrepancies |
| Communication | Support hours, channel, priority definitions and escalation route |
| Data security | Contractual processor terms, access, incident route, retention and subprocessors |
| Continuity | Cover for key staff, systems failure and alternative processing plan |
| Exit | Data export format, handover support, notice periods, corrections and return/deletion |
Define late changes before they happen
Suppose a manager supplies an unapproved commission amendment after the cut-off. The SLA should say whether the change enters the current run, needs an authorised override or is handled later. It should record who makes that decision and whether additional fees apply. The answer cannot safely be “we always fix everything instantly”.
Useful service evidence
Ask for an anonymised draft payroll pack, sample exception log, input template, audit trail and sign-off record. A prospective provider should be able to show how it deals with a rejection from HMRC or an incorrect pension output, as well as ordinary payroll days.
HMRC's FPS/EPS reporting guidance explains important reporting requirements, including the normal on-or-before-payday FPS rule. The contract should identify which party performs each reporting action while recognising the employer's retained legal responsibilities.
Data terms are not an optional annex
Where a controller engages a processor, ICO guidance explains the need for documented contractual terms. The payroll SLA and data-processing agreement should describe consistent security and breach processes, not conflicting obligations.
A usable negotiation order
Agree the pay-run timetable and service scope first. Next validate quality checks and staffing/continuity. Then reconcile the prices and exception rules. Finally review the legal agreement and data-processing terms with appropriate advisers. Legal wording cannot rescue an operational schedule that never had enough time for approval.
Review the operating model, security checklist and provider scorecard before asking for a formal proposal. Send an initial non-sensitive brief if you'd like your service requirements scoped.