Parallel payroll: import the legacy register, compare with a tolerance, and sign off each cycle

Run the old payroll system and TRANXACT side by side: import the legacy register for each cycle, compare it with the TRANXACT run category by category and employee by employee within a tolerance, and sign off or reject the cycle. Readiness says when two cycles in a row — adjacent pay periods of the same pay group — are signed off for go-live, and which period is missing when they are not.

Onde encontrar

• HRMS › Payroll › Parallel Payroll › Legacy Payroll Registers and Parallel Payroll Comparisons.
• Payroll Administrator imports registers and compares; GL Interface Administrator, Financial Controller and Payroll Administrator sign off; Payroll Auditor reads. HR Auditor does not see parallel payroll.

1. Import the legacy register

1. Legacy Payroll Registers › Import (Template beside it gives the layout): a CSV, text or Excel file, at most 20,000 rows, one register per cycle.
2. Columns are recognised by common names: register or cycle, legacy_system, period_start, period_end, pay_date, record_type, employee_no, gross, net, taxes, fed_tax, fica, state_tax, local_tax, deductions, benefits, employer_taxes, employer_benefits, leave_accrual_hours, liabilities; GL rows with gl_account, debit, credit; allocation rows with dimension, dimension_code and amount.
3. The result says how many rows and employees, and which employees were not found in TRANXACT. Rows shows what was read.

2. Compare

1. On the register choose Compare with a payroll run: the TRANXACT payroll run (calculated, approved, posted or paid), GL output from interface (empty: the posted payroll journal), Tolerance (amount) — default <0.01> — Tolerance (% of legacy) and the Cycle number.
2. A difference within the larger of the two tolerances counts as a match. “<PPC000003> (cycle <2>): <4> variance(s) outside tolerance.”
3. On Parallel Payroll Comparisons, By category shows gross, net, each tax, deductions, benefits, employer costs, leave accrued, liabilities, labor allocations and GL output; Variances lists the employees outside tolerance.

3. Sign off

• Sign off the cycle; a Note is needed when variances remain — say why they are accepted. Reject needs a note too.
• Readiness needs two cycles signed off in a row: regular runs of the same pay group for adjacent pay periods — the pay group’s next pay period on its calendar, or else the period that starts the day after the previous one ends. Off-cycle runs, and cycles of another pay group, do not make a row.
• Ready: “<2> consecutive parallel cycles signed off (<2026-01-01> to <2026-01-15> (<BW>), <2026-01-16> to <2026-01-31> (<BW>)): ready for go-live”.
• Not ready, the missing period is named: “<1> of 2 consecutive parallel cycles signed off (<2> signed off, not in a row); missing between <PPC000001> and <PPC000003>: pay period <2> (<2026-01-16> to <2026-01-31>) has no signed-off comparison”. Where that period was compared but not signed off, the line says so: “<PPC000002> is compared, not signed off”.
• Import and compare the missing period, then sign it off, and readiness counts the row. The console of the GL interface shows the same line.