Glossary
Parallel Payroll Run
A parallel payroll run is a migration control in which the old and new payroll systems process the same pay cycle at once, so the employer can compare every result and confirm the new provider is accurate before switching over fully, usually across one to three cycles.
Reviewed by Teamed's in-house employment-law team·Last updated 28 July 2026
Also known as: parallel pay run, payroll parallel testing
What is Parallel Payroll Run?
A parallel payroll run is a way to move safely from one payroll provider to another. Instead of switching in one step, the outgoing and incoming systems both process the same real pay cycle. The live run still pays people, and the parallel run is checked against it line by line.
The point is to catch differences before they reach employees. Reviewers compare gross pay, tax, pension, benefits and deductions across both systems, not just the final net figure. Any gap exposes a setup or calculation error in the new system while there is still time to fix it.
Parallel running is standard practice for larger or multi-country moves, where a single missed rule can affect many people. It is usually run for one to three cycles and covers awkward cases, such as leavers, new starters and back pay, because those are where hidden errors tend to appear.
Why run two payroll systems at the same time?
To prove the new system is right before you depend on it. Running both across the same cycle lets you compare outputs against a known, working baseline. If the numbers match across gross pay, tax and deductions, you can switch with confidence. If they do not, you find out before employees are affected.
How long should a parallel run last?
Long enough to see the payroll behave normally, which usually means one to three full cycles. A single cycle may miss quarterly or period-end events, so more than one is common for complex payrolls. The aim is to cover the situations that expose errors, not simply to repeat an identical run.
What gets compared during a parallel run?
Every component of pay, not just the net amount. Reviewers check gross pay, income tax, social contributions, pension, benefits and each deduction across both systems, then look closely at edge cases like new starters, leavers, back pay and country-specific rules. A match on net pay alone can hide two errors that cancel out.
Key facts
- Parallel-run best practice
- Payroll migration guidance recommends running at least two full parallel cycles and comparing every element, gross pay, tax, pensions and deductions, line by line before the legacy system is retired.Source: IRIS Software Group· verified 2026-07-28
Frequently asked questions
Does a parallel run mean employees get paid twice?
No. Only the live system actually pays people. The parallel system processes the same cycle for comparison only, and its output is never sent to employee bank accounts. Keeping that separation clear is one of the main controls when planning a parallel run, so no duplicate payment can escape.Is a parallel run always necessary when changing provider?
Not always, but it is strongly advised for anything beyond a small, single-country payroll. The more employees, countries and pay rules involved, the higher the chance a configuration error slips through, and the more a parallel run is worth the extra cost during the switch.How much does a parallel run add to the switch?
It adds cost, because the same cycle is processed twice and the results have to be reviewed in detail. That temporary expense buys assurance: it is far cheaper to correct an error found in a parallel run than to fix wrong payments and filings after go-live.
Related terms
Note
Glossary
Have a global hiring question?
Ask a real person, or run the numbers yourself with the free calculators.
Ask how Teamed manages a payroll migrationLast verified 2026-07-28