Outsource Payroll Company guide
Stage a Parallel Payroll Run Before Switching Providers
Published

A parallel-run plan that freezes the inputs, reconciles both providers at the employee and tax level, and sets a pass rule before the cutover decision.
Payroll handoff readiness check
Use this table before a provider or Filipino payroll support worker receives access.
| Work area | Ready to hand off when | Owner check |
|---|---|---|
| Comparison period | the period is closed, representative, and has clean source records | owner accepts the period and the employee population |
| Frozen inputs | both systems receive the same files and the pull date is recorded | owner confirms no late input changed one side |
| Reconciliation | gross, deductions, net, bank, tax, and ledger lines are compared by employee | owner reviews every variance above the tolerance |
| Pass rule | acceptable and blocking differences are defined in advance | owner signs the pass or fail decision |
| Cutover and rollback | a rollback point and trigger are documented with named callers | owner confirms the old provider remains available through transition |
Choose the comparison period
A parallel run compares the old and new payroll providers using the same employee population and the same inputs. Pick a closed period with clean source records, not a month already full of exceptions. Include a mix of pay types, deductions, and tax jurisdictions that the new provider will handle. A simple period with no variance proves very little. The comparison should be hard enough to expose a real difference.
Write the pass rule before either system runs. Decide which differences are acceptable, which require explanation, and which stop the cutover. Set a tolerance for rounding and a separate rule for tax, garnishment, and bank amounts. Name who can approve an exception and who signs the final comparison. A rule written after the results invites the team to explain away a failure.
Run both systems from the same inputs
Freeze the input set for both systems at the same point in the cycle. Use the same timesheets, rate changes, deduction elections, and one-time payments. Record the file names and the date each input was pulled. If one system receives a later correction, the comparison is no longer parallel. Keep the frozen set with the reconciliation so a reviewer can reproduce the run.
Run both systems without letting one correct the other's inputs. The new provider may have a different validation rule, but it should receive the same source data. Log every manual adjustment made during the run and the reason. A manual fix that exists only in the new system is a hidden difference. The comparison should show what the provider does with identical facts.
Reconcile at the employee and tax level
Reconcile at the employee level first, then at the totals. Compare gross wages, each deduction, employer contributions, net pay, and the bank amount for every employee. A total that matches can still hide two employees with offsetting errors. Use a unique employee key that both systems share and keep the mapping visible. Investigate every difference rather than netting it against another employee.
Then reconcile the tax and filing outputs. Compare taxable wages, withholding, employer taxes, and the jurisdiction totals the provider will report. Check the general ledger mapping for wages, taxes, and benefits. If the new provider groups accounts differently, record the mapping decision before cutover. A payroll that pays correctly but files or posts incorrectly is not a successful parallel run.
Disposition every variance
Give every variance a disposition: provider error, input error, mapping difference, or accepted policy change. Attach the evidence and the owner who decided. Do not close a variance as a rounding difference unless the pass rule allows it. If the same variance appears for many employees, treat it as one systemic issue with a single repair. The disposition log is the story of whether the new provider is ready.
Share the log with the provider before the cutover decision. Ask for a written response to each provider-side item and a date for the fix. If a fix will arrive after the first live run, document the workaround and the owner who will watch it. Do not accept a verbal assurance as closure. The decision to cut over should rest on resolved evidence, not on optimism.
Cut over with a rollback plan
Set a cutover date with a rollback point that is still early enough to run payroll the old way. Define the trigger for rollback, such as an unresolved tax difference or a failed bank file. Confirm that the old provider will keep the data available through the agreed transition period. Tell the payroll owner, the bank, and the finance team who can call the rollback. A plan without a trigger becomes a debate during the worst possible week.
After the first live run, compare it with the parallel baseline and review the exceptions with the same discipline. Keep the old provider's final files and the new provider's first files together. Record what the parallel run missed and add that check to the next transition. A cutover is complete only when the first live payroll, the tax filing, and the ledger all reconcile. The parallel run is the rehearsal, not the finish line.
Document the mapping decisions finance must own
Payroll affects the ledger through wages, taxes, benefits, accruals, and sometimes department allocations. Record the account, cost center, and department mapping for each pay component in both systems. Name the finance owner who accepts a changed mapping and the date of the decision. Test one journal entry from each provider and compare the debits and credits. A payroll provider should not silently decide how the employer reports labor costs.
Keep the mapping workbook with the parallel-run evidence and give it a version number. Update it before the first live run if finance changes an account or a reporting unit. Reconcile the first live journal against the parallel baseline and record any difference. If a mapping change is needed after cutover, treat it as a new decision with an owner and a retroactive correction plan. The mapping is part of the payroll system, not an afterthought for accounting.
Agree on who owns the old system
During the transition, someone must keep the old provider account, data, and support path usable. Name that person and a backup in the cutover plan. Confirm that the old provider will not close access on the cutover date before the first live run is verified. Record the last day of access and the data export plan. A rollback is impossible if the old system is already gone.
Copy-ready brief
Payroll support role brief
Replace the tool names and owner details, then use this list in a provider call or job brief.
- Role: Payroll provider transition analyst
- First task lane: Freeze inputs, assemble the employee-level reconciliation, and maintain the variance log
- Tools: Old and new payroll systems, register extracts, bank file, tax reports, ledger mapping
- Access: Read-only access to both systems and write access to the transition workbook
- Daily output: Variance entries with evidence, disposition, owner, and next action
- Stop rules: No cutover sign-off while a blocking tax, bank, or ledger variance remains open
- Owner review: Payroll owner approves the pass rule, the variance dispositions, and the rollback decision
Questions from payroll buyers
Can a total reconciliation replace employee-level checks?
No. Two employee errors can offset and make the total look correct. Reconcile by employee first, then use totals as a second check.
What is a reasonable pass rule?
One that defines rounding tolerance, blocking categories such as tax or bank differences, the approver for exceptions, and the evidence required before cutover.
Should the old provider stay available after cutover?
Yes, for the agreed transition period. Keep final files and access available long enough to support a rollback or a later question.
Sources
- IRS Publication 15 (Circular E)Withholding and reporting context for comparing two payroll providers.
- DOL Wage and Hour DivisionWage payment and recordkeeping resources for the comparison population.
- SBA: Buy or sell a businessTransition planning context for small-business systems and records.
- NIST Cybersecurity Framework 2.0Access and vendor-change controls during a payroll system transition.