What is a payroll parallel run?
A payroll parallel run processes the same payroll population and pay period through the new payroll solution and an agreed comparison baseline. The results are then reconciled to identify differences and prove readiness before the new system becomes the live payroll.
Why parallel runs matter
Payroll defects can be difficult to identify from configuration testing alone. A parallel run exposes the combined effect of employee data, pay rules, integrations, calendars and processing.
Before the parallel run
Define the population, pay period, data freeze rules, comparison fields, variance tolerances, owners and sign-off criteria before running the comparison.
Parallel run checklist
- Agree population and payroll period
- Define comparison baseline
- Confirm data freeze and cut-off
- Define control totals and comparison fields
- Set variance tolerances
- Assign variance owners
- Run and reconcile payroll
- Investigate material variances
- Retest corrections
- Obtain formal sign-off
How to reconcile the results
Start with control totals and then move to employee-level investigation. Compare employee counts, gross pay, deductions, statutory amounts, net pay, employer costs and finance outputs where relevant.
Variance analysis
Do not focus only on a match percentage. A small number of high-value exceptions can be more important than a high overall match rate.
- Compare employee counts and key totals
- Compare gross pay
- Compare deductions and statutory amounts
- Compare net pay
- Compare employer costs
- Compare finance postings
- Classify material variances
- Document expected differences
- Track defects separately
- Retain reconciliation evidence
Go/no-go criteria
A strong go/no-go decision considers whether material variances are explained, critical defects are resolved or accepted, and Payroll has signed off.
Common parallel-run mistakes
Common problems include comparing different populations, uncontrolled data changes, treating every variance as a defect, and leaving reconciliation until the end of the project.
Frequently asked questions
How many parallel runs should a payroll project complete?
There is no universal number. It depends on complexity, risk, payroll frequency, countries, data quality and solution stability.
What is a good payroll parallel-run match rate?
There is no single percentage that guarantees readiness. Materiality and explainability matter more than an arbitrary match rate.
Should every employee be compared?
The full agreed population should normally be covered at control-total level, with employee-level investigation according to the approved reconciliation method.
When should parallel runs happen?
They normally occur after configuration and integrations are stable enough to produce meaningful payroll results, while planning should begin much earlier.
Put the guidance into practice.
The Enterprise Payroll Implementation Toolkit gives you editable project, risk, testing, parallel-run, communication and go-live workbooks.
Explore the Payroll Toolkit