Few words in retirement plan administration should trigger more anxiety than: “We changed payroll providers.”
Because payroll changes are never just payroll changes.
To HR, it’s a software conversion. To finance, it’s an operational upgrade. To your retirement plan team? It’s the moment everyone should start checking for exits.
Retirement plans live and die by payroll data. Deferral elections. Compensation definitions. Loan repayments. Match calculations. Eligibility tracking. Catch-up contributions. Roth sources. Auto-enrollment percentages. Every one of those depends on payroll feeding accurate information at the right time.
And when payroll changes, bad things happen.
Deferral elections don’t transfer correctly. Compensation codes get remapped improperly. Bonus pay gets treated differently. Loan deductions vanish. Catch-up contributions stop tracking. New hires fail to feed into eligibility reports. Payroll dates shift, breaking deposit timing expectations.
The best part? Nobody notices immediately.
Instead, errors quietly compound for months until a participant asks why their deductions look wrong, an audit uncovers the problem, or testing fails spectacularly.
Then comes the vendor blame Olympics.
Payroll says they implemented what they were told. Recordkeeper says the file specs weren’t followed. TPA says they assumed the data was accurate. The plan sponsor gets to write the correction checks.
This is why payroll changes should be treated like fiduciary events, not administrative housekeeping.
Before changing providers, sponsors should confirm file mapping, compensation treatment, eligibility coding, loan processing, source handling, payroll calendar timing, and parallel testing. After implementation, they should audit the first several payrolls like their sanity depends on it.
Because it does.
The most expensive retirement plan errors are rarely caused by malicious behavior or incompetence.
They’re caused by someone saying, “It’s just payroll.”
