What to include in a payroll RFP template
The template below covers the ten sections a UK payroll outsourcing RFP should address. Each section includes what to cover, why it matters, and the key items to specify. You do not need every item in every section; adapt the depth to match your complexity. If you have not written an RFP before, do not let the length put you off. You are essentially answering two questions: what does your payroll look like, and what do you need a provider to do with it?
1. Introduction and background
This section sets the context. It tells providers who you are, why you are going to market, and how the process will work.
- About your organisation: sector, structure, number of legal entities, number of employees
- Why you are issuing the RFP: new to outsourcing, switching payroll provider, business growth, compliance concerns
- Confidentiality statement: how proposal information will be treated
- Timeline overview: key dates from RFP issue through to decision
- Named contact for clarification questions during the response period
Tip: keep this section brief and factual. Providers need context, not a company history. A paragraph on your organisation and a paragraph on the procurement reason is enough.
2. Company and payroll profile
This is where you give providers the detail they need to quote accurately. The more specific you are here, the more useful the proposals you receive.
- Total headcount and payroll headcount (they may differ if you have contractors or workers on a separate arrangement)
- Number of PAYE schemes and legal entities
- Pay frequencies: weekly, fortnightly, four-weekly, monthly, or a mix
- Number of pay groups
- Worker types: salaried, hourly, zero-hours, agency workers, directors, expatriates
- Current payroll system or provider (and why you are moving)
- Integration landscape: your HR system, time and attendance, pensions platform, accounting software, ERP
- Complexity factors: multiple sites, shift patterns, overtime rules, commission structures, benefits-in-kind, salary sacrifice schemes, Construction Industry Scheme (CIS) if applicable
- International payroll needs, if any
Tip: if you are unsure about some of these details, gather them before issuing the RFP. Gaps in your payroll profile are the single most common reason for inaccurate quotes.
3. Scope of services required
Tell providers exactly what you need them to do. Be specific: "payroll processing" means different things to different providers.
- Processing: gross-to-net calculations, statutory deductions, statutory payments (SSP, SMP, ShPP, SPP, SAP, Statutory Parental Bereavement Pay, Statutory Neonatal Care Pay), student loan deductions, attachment of earnings orders
- HMRC compliance: Real Time Information submissions (FPS and EPS), year-end processing (P60 production, final submissions), P11D and P11D(b) if applicable
- Pensions: auto-enrolment assessment, opt-in and opt-out processing, pension scheme submissions, cyclical re-enrolment
- Payments: BACS processing for net pay, HMRC payments, pension provider payments, third-party deductions
- Payslips: generation and distribution (online portal, paper, or both)
- Reporting: standard reports, custom reports, management information, dashboards, cost centre reporting
- Employee and manager self-service: portal access, mobile access, payslip retrieval, P60 access, personal detail updates
- Ad-hoc services: out-of-cycle payments, leavers processing, settlement agreements, redundancy calculations
- Year-end: P60 production and distribution, P11D support, PAYE Settlement Agreement (PSA) support if applicable
- Query handling: how employee and manager queries are managed, response time expectations, escalation paths
What to ask: for each service area, ask providers to confirm whether it is included in the standard PEPM rate or priced as an additional charge. This is where hidden costs surface.
4. Technology and integration
This section ensures the provider's platform works with your existing systems and meets your security requirements.
- Platform model: cloud-based, on-premise, or hybrid
- Integration requirements with your named systems (specify each by name)
- API availability and documentation
- Data migration approach and responsibilities
- Reporting and analytics capabilities: standard, custom, real-time
- HMRC connectivity for RTI submissions
- Security and data protection: ISO 27001 certification, data residency (where your data is stored and processed), encryption standards (at rest and in transit), access controls, penetration testing schedule
- GDPR compliance and willingness to enter a Data Processing Agreement as processor under UK GDPR
5. Implementation and transition
Implementation is where most post-contract problems originate. A detailed implementation section in your RFP protects you by forcing providers to explain their approach before you commit.
- Proposed implementation methodology and timeline
- Key milestones: data migration, user acceptance testing, parallel run, first live run
- Parallel running approach: how many pay cycles will run in parallel, what constitutes a successful parallel run
- Data migration responsibilities: who extracts data from the outgoing system, who validates it, what format is required
- Project management: will you have a dedicated project manager, a governance structure, a steering group
- Training for your team: administrators, managers, employees
- TUPE considerations, if staff are transferring from a current outsource provider (the Transfer of Undertakings (Protection of Employment) Regulations 2006 may apply where an organised grouping of employees is dedicated to your payroll)
- Risk mitigation: what happens if the first live pay run fails
- Cut-over timing preferences: post year-end is common because it avoids mid-year complications, but your operational needs may differ
In our experience, the most common cause of implementation delays is incomplete or inaccurate data from the outgoing system. Your RFP should ask providers how they handle data quality issues during migration. Our guide to payroll implementation covers the full process from project kick-off to first live run.
6. Service levels and governance
Service level agreements define what "good" looks like once the service is running. Without them, you have no objective basis for managing performance.
- Proposed SLA structure: processing accuracy percentage, query response times, payslip availability timing relative to pay date
- Error handling and remediation process: what happens when something goes wrong, who is responsible for corrections, what are the timescales
- Escalation procedure: named contacts, escalation tiers, response commitments at each tier
- Account management model: dedicated account manager, shared team, or named contacts
- Regular service reviews: frequency, format, attendees, management information provided
- Continuous improvement approach: how the provider identifies and implements process improvements
- Disaster recovery and business continuity: recovery point and recovery time objectives, testing schedule
7. Pricing
The pricing section is where comparability matters most. If you do not specify the format, providers will present pricing however suits them, making meaningful comparison very difficult.
Ask providers to break their pricing into:
- PEPM (per employee per month) rate: and a clear statement of what is and is not included
- Implementation fee: broken down by component (project management, data migration, parallel running, training)
- Year-end charges: if separate from the PEPM
- Ad-hoc and out-of-cycle charges: per-event pricing for leavers, settlements, additional pay runs
- Pension administration charges: if priced separately
- Query and helpdesk charges: if priced separately
- Volume-based thresholds: any discount tiers or price changes as headcount grows or shrinks
- Price escalation mechanism: fixed for how long, index-linked, annual review
- Contract length options: one, three, and five year pricing where available
- Payment terms
Important: ask each provider to confirm explicitly which services are included in the headline PEPM and which attract additional charges. This is the single most effective way to make pricing genuinely comparable. For context on what payroll outsourcing typically costs in the UK, see our guide to payroll outsourcing costs.
8. Compliance and accreditation
This section helps you assess the provider's credentials and risk profile.
- HMRC recognition for payroll software
- ISO 27001 certification (information security management)
- ISAE 3402 Type II or SOC 2 report (independent assurance over controls)
- ISAE 3000 (broader assurance standard)
- CIPP membership and whether payroll staff hold CIPP qualifications
- GDPR Data Processing Agreement readiness
- Insurance: professional indemnity cover and cyber liability cover
- Client references: request references from organisations of a similar size and complexity
- Financial stability: latest filed accounts or a credit reference
9. Contract and exit terms
Exit planning is often an afterthought, but it should not be. Your ability to leave a provider cleanly affects your negotiating position throughout the relationship.
- Standard contract length and notice period
- Data ownership and portability: confirm you own your data and specify the format and timeline for data return on exit
- Exit process: data handover, transition support, charges for exit assistance, timeline from notice to final handover
- Termination for cause: what constitutes a material breach and what remedies are available
- Intellectual property: who owns any custom configurations, reports, or processes developed during the relationship
- TUPE obligations on exit, if the provider's staff are embedded in your operations
10. Response instructions
Clear response instructions ensure you receive comparable documents, not a mix of slide decks, brochures and spreadsheets.
- Submission deadline (date and time)
- Required format: specify the structure and file format you want
- Named contact for questions during the response period
- Whether you are sharing your evaluation criteria and weighting
- Presentation and demo expectations: will you invite shortlisted providers to present, and if so, when
- Decision timeline: when you expect to notify providers of the outcome
Tip: set a reasonable response window. Two to three weeks is typical for a UK payroll RFP. Shorter than two weeks and you risk incomplete responses; longer than four weeks and you lose momentum.