Mid-Year Acquisition Parallel Payroll Variance
Meridian Health Services runs Infor CloudSuite HCM payroll for 1,850 employees across three pay groups: weekly (620), biweekly (1,010), and monthly (220). It acquired Northside Clinic, adding 220 weekly employees who previously used a legacy system with union shift differentials. During the second parallel run, gross-to-net variance is 4.7%. Symptoms include 31 employees with negative net pay, overtime premium excluded from the shift-differential taxable base for 64 employees, 14 employees in two states with a reciprocal tax agreement showing duplicate state withholding, and a weekly calendar showing 27 pay periods instead of 26. The payroll manager wants to go live in three weeks because the legacy contract expires. The HRIS team has one payroll analyst and no dedicated tax specialist. The union has threatened a grievance if shift differentials are underpaid. Leadership asks whether to delay, phase, or proceed with manual workarounds.
1. How should the team rank the root causes, and what go-live recommendation follows?
Read the worked answer
Rank by financial exposure, legal risk, and employee impact, not by ease of fix. First, the 27-period weekly calendar is a structural defect: every weekly calculation, deduction arrears threshold, and accrual proration depends on it. Second, duplicate state withholding is a compliance issue with penalty exposure. Third, negative net pay affects real employees and creates wage-payment risk. Fourth, shift-differential taxable-base mapping is a configuration error in earnings/accumulator order, not a data error. The correct recommendation is a phased go-live: hold the weekly group until the calendar and reciprocal-tax setup are corrected and two clean parallel cycles show variance below 0.5% with zero negative net pay. Move biweekly and monthly only if their control totals are clean. Proceeding with manual workarounds in three weeks concentrates risk in the highest-volume, most union-sensitive group and leaves no capacity to fix defects discovered after cutover.
2. Design the reconciliation and control routine the payroll analyst should run before cutover.
Read the worked answer
The analyst needs a repeatable three-level reconciliation, not a one-time comparison. Level one: record-count and control-total reconciliation by pay group, comparing employee count, total gross, total taxes, total deductions, and total net between legacy and Infor Payroll. Level two: employee-level variance analysis with reason codes tied to configuration objects: pay calendar, earnings mapping, accumulator sequence, tax reciprocity, deduction arrears, and retro pay. Level three: exception reports for negative net, zero net, duplicate tax records, and employees with no withholding. Set tolerance: aggregate variance at or below 0.5% and no unexplained employee variance above $25. Require sign-off from payroll operations, HRIS, and finance. Retain the reconciliation evidence for audit. The analyst should also test a terminated employee, a mid-period hire, a retro shift-differential adjustment, and a reciprocal-tax employee. These cases exercise the failure modes the parallel run revealed and are more diagnostic than another full-cycle comparison.
3. What employee-communication and retro-pay approach should accompany the cutover?
Read the worked answer
Communication should be segmented by impact. Employees with negative net pay need individual outreach before the live run, not a generic memo: explain the cause, confirm the corrected amount, and provide a payroll contact. Union-represented employees need a joint communication with the union steward covering shift-differential correction and the retro calculation method. The retro-pay approach should use the corrected earnings and accumulator setup, calculate by pay period, and show gross-to-net detail for each affected period. Do not net retro amounts against current deductions without a documented arrears policy. If the legacy contract expires, run the weekly group on legacy for one or two extra cycles under a short extension; this is cheaper than a failed cutover. Publish a cutover FAQ with dates, payslip access, and escalation. Track call volume and correction requests daily for the first two pay cycles to detect systemic issues early.