Research brief · Published
Parallel-run evidence during payroll provider transitions
A study design for measuring whether a parallel payroll run produced enough employee-level, tax, and ledger evidence to support a provider cutover decision.

Research finding
Score input identity, employee-level pay, tax and filing, and ledger mapping as separate layers.
Methodology
This brief triangulates the headline measure against official Philippine government, regulatory, development, and labor sources. It translates evidence into an operating control and separates context from recommendations.
| Measure | Interpretation |
|---|---|
| 4 reconciliation layers checked before cutover. | Context signal for planning, not a promise about an individual worker or provider. |
| 4 source records | Primary source links are listed and numbered below for review. |
Key takeaways
- Score input identity, employee-level pay, tax and filing, and ledger mapping as separate layers.
- Block cutover on unresolved tax, bank, or ledger differences rather than a matching total.
- Record every manual adjustment because a fix that exists on one side is a hidden variance.
- Require a written disposition and owner for each variance above the agreed tolerance.
- Confirm rollback access and a trigger before treating the parallel run as complete.
Comparison design
This study asks whether a parallel payroll run produced enough evidence to support a cutover decision. The population is every employee and pay component included in the comparison period. The unit is one reconciliation layer: frozen inputs, employee pay, tax and filing, and ledger mapping. The design treats a matching total as insufficient because offsetting errors can hide inside it. Results describe the evidence available for this transition, not a guarantee that either provider is accurate.
Input identity
Input identity is met when both systems receive the same source files for the same period. Record the file names, pull dates, and the person who froze the set. Check that no late correction was applied to one side only. If an input had to be changed for a valid reason, log the change and apply it to both systems. A comparison with different inputs measures the inputs as much as the providers, so this layer must be scored first.
Employee-level reconciliation
Reconcile gross wages, each deduction, employer contributions, net pay, and the bank amount for every employee. Use a shared employee key and keep the mapping visible. Investigate a difference even when the total matches, because two employees can offset each other. Record the evidence for each resolved variance. This layer is met only when every employee is either matched within tolerance or has an approved disposition.
Tax and filing reconciliation
Compare taxable wages, withholding, employer taxes, and jurisdiction totals. Check the returns and deposits the provider will produce, not only the employee pay amounts. Record any difference in taxability, jurisdiction assignment, or rounding. A payroll that pays correctly but files incorrectly is not ready for cutover. The tax layer should be reviewed with someone who understands the employer's registration footprint and filing calendar.
Ledger mapping
Check how each provider maps wages, taxes, benefits, and accruals to the general ledger. Record the account, department, and cost center for a sample of transactions. A provider may use a different grouping that is acceptable only if finance agrees and the mapping is documented. Compare the total debits and credits as well as the individual lines. The ledger layer is met when finance can post the result without a manual reclassification that no one owns.
Variance disposition
Give every variance a disposition: provider error, input error, mapping difference, or accepted policy change. Record the evidence, the owner, and the decision date. Do not close a variance as rounding unless the pass rule allows that tolerance. Group repeated differences into one systemic issue with a single repair. The disposition log is the evidence that the cutover decision was based on resolved facts rather than a hopeful review.
Pass rule and sign-off
The pass rule should be written before the run and should name blocking categories. Record who can approve an exception and who signs the final decision. A pass rule that changes after the results is not a control. Include the tax and ledger layers in the sign-off, not only employee pay. The sign-off should reference the frozen input set and the variance log so a later reviewer can reconstruct the decision.
Rollback readiness
Confirm that the old provider remains available through the transition period and that its final files are retained. Define the trigger for rollback and the people who can call it. Test that the old system can still process a payroll if the new one fails. A rollback plan that depends on a former employee or an expired account is not usable. Record the access check and the date it was performed.
Sampling and limitations
If the employee population is large, sample by pay group, jurisdiction, and pay type, and record the frame and selection rule. Include employees with garnishments, benefits, and off-cycle payments. This design measures reconciliation evidence, not the legal accuracy of either provider's tax treatment. It depends on complete extracts and a stable mapping. A missing layer should be reported as unverified rather than treated as a pass.
Decision and retest
Use the result to decide whether to cut over, delay, or run another parallel period. Name the blocking layers and the repairs required before the next attempt. Retest with the same pass rule and a comparable population. Report the result by layer so a strong employee-pay result cannot hide a weak tax or ledger result. A transition is complete only when the first live payroll and its filings reconcile to the baseline.
Input freeze evidence
Record the exact files, extract dates, and row counts used for both systems. Store a hash or a read-only copy so a later reviewer can prove the inputs did not change. Note any manual adjustment made after the freeze and apply it to both sides or exclude the employee from the comparison. An input freeze without evidence is only a promise. The freeze is the foundation for every other layer.
Exception approval
Define who can approve a variance disposition and what evidence they must see. Record the approver, date, and reason for every exception above the tolerance. A provider account manager should not be the only person who decides that a tax difference is acceptable. The employer owns the risk, so the employer's payroll or finance owner should sign. Approval without evidence is a delay, not a resolution.
Employee communication
Decide what employees will be told if the transition changes a pay date, a deduction, or a portal. Prepare the message before cutover and keep it consistent with the first live run. Record who approves the message and when it will be sent. A smooth parallel run does not guarantee a smooth employee experience if the communication is improvised. Include the support contact and the expected response time.
Reporting format
Report the result by reconciliation layer, with counts of matched, accepted, and unresolved items. Show the blocking variances and their owners separately. Include the pass rule and the date it was approved. Avoid a single readiness percentage because a strong employee-pay result can hide an unresolved tax or ledger issue. The report should support a clear cutover, delay, or rollback decision.
Repair options
If input identity fails, fix the freeze and rerun the affected employees. If employee pay differs, inspect the provider configuration and the source data before changing either. If tax or ledger mapping differs, involve the owner who can accept the accounting treatment. Choose one repair per blocking layer and rerun the comparison. Do not cut over with an open blocking variance just to meet a planned date.
Post-cutover check
Compare the first live payroll with the parallel baseline at the employee, tax, and ledger layers. Record any new variance and assign an owner before the next cycle. Confirm that the old provider's final files and access are still available during the transition. Review the first filing and the first journal entry. A cutover is complete only when the live evidence matches the baseline or has an approved disposition.
Retest design
If the team runs another parallel period, keep the same pass rule and a comparable population. Add any check that would have caught the prior miss. Report the result by layer and show which variances remain open. Do not change the tolerance to make the result pass. The retest should prove that the repair works, not that the team can produce a cleaner-looking report.
Data protection during the run
A parallel run creates extra copies of payroll data in two systems and often in spreadsheets. Limit the comparison files to the fields the reconciliation needs, store them in an approved location, and remove them when the decision is complete. Record who has access to both systems. Do not send a full employee extract through email to resolve a single variance. The transition is a high-risk period for data sprawl, so the evidence plan should include a deletion date.
Vendor responsibility
Write down which provider is responsible for which task during the transition: file production, tax filing, bank communication, employee support, and error correction. A parallel run can reveal a gap that both providers assume the other will handle. Record the owner for each gap and the date the responsibility transfers. A cutover plan without this map can leave a live payroll item with no one accountable.
Sources
Prepare a parallel-run reconciliation
A Philippines-based payroll support specialist can freeze the input set, build the employee-level comparison, and maintain the variance log for review. Your authorized payroll owner and finance lead still approve the pass rule, the dispositions, and the cutover decision.
Review payroll preparation supportFAQs
Is a matching payroll total enough to approve cutover?
No. Offsetting employee errors can produce a matching total. The employee, tax, and ledger layers each need evidence.
What should trigger a rollback?
A blocking tax, bank, or ledger difference that cannot be resolved before the live run, or a failure of the new system to produce an acceptable file.
How long should the old provider remain available?
Through the agreed transition period and long enough to support a rollback or a later question. Confirm access before cutover, not after a failure.
For adjacent operating context, see Payroll Preparation and the payroll operations guide library.