Changing payroll providers looks like an HR and finance project: new software, new pay calendars, new direct-deposit files. For a company that sponsors a 401(k), it is also a fiduciary event. Every deferral, match, loan repayment and compensation figure your plan relies on originates in payroll, and a payroll conversion is the single moment when all of those feeds are rebuilt at once. When the mapping is wrong, the errors repeat every pay period until someone notices — often the auditor, the testing firm, or an employee looking at a statement.
This guide walks plan sponsors through what to settle before the switch, what to test on the first payrolls, and what to reconcile afterward so the conversion does not turn into a correction project.
Why a Payroll Change Is a Fiduciary Issue, Not Just a Systems Issue
ERISA requires the plan to be operated according to its written terms and requires participant contributions to reach the trust as soon as they can reasonably be segregated from company assets. Payroll is where both obligations are actually carried out. The new provider does not know your plan document; it knows only the earning codes, deduction codes and file layouts someone gives it. If the definition of compensation, the eligibility rules or the remittance timing are configured incorrectly, the plan is out of compliance from the first check date — even though no one at your company changed a plan decision.
That is why a payroll conversion belongs on the plan committee’s radar, not only the controller’s. The same gap between plan document and plan operations that causes most compliance failures is easiest to open during a system change.
How Payroll Conversions Go Wrong
- Earning codes mapped to the wrong compensation bucket — bonuses, commissions, overtime or fringe items treated as plan compensation when the document excludes them, or excluded when the document includes them.
- Deferral elections that don’t carry over — percentages entered as flat dollars, Roth elections loaded as pre-tax, or elections dropped for employees on leave.
- Loan repayments lost — repayment deductions not recreated, so loans quietly fall behind schedule.
- New-hire and eligibility flags reset — hire dates, rehire dates or hours history not converted, which breaks entry-date and auto-enrollment logic.
- Remittance timing slips — the new provider’s funding file or the sponsor’s approval step adds days, and deposits arrive later than your established pattern.
- Year-to-date totals split — two systems each report part of the year, and nobody combines them for limits, testing or the census.
Before the Switch: Six Things to Settle
1. Pull the plan’s definition of compensation
Start from the adoption agreement, not from the old payroll setup. Identify which pay types count for deferrals, which count for employer contributions (they can differ), and any exclusions. Then build an earning-code map that sends every new code to the correct bucket. If the old system was wrong, the conversion is your chance to stop repeating the error — and to flag it for correction.
2. Convert every deferral election exactly as made
Export current elections from the old system and the recordkeeper, and confirm each employee’s pre-tax and Roth percentages or amounts match. Pay special attention to employees who recently changed elections, are on leave, or are subject to catch-up contribution rules that affect whether contributions must be designated Roth.
3. Recreate loan repayment deductions
Get the recordkeeper’s active loan list with repayment amounts and confirm each one is set up in the new payroll before the first check date. A missed repayment cycle can push a loan toward default without the participant doing anything wrong.
4. Carry over hire, rehire and service history
The plan’s eligibility and entry-date rules depend on dates and hours payroll may not convert by default. Make sure original hire dates, rehire dates, terminations and hours history come across, especially for part-time and variable-hour employees.
5. Rebuild the recordkeeper data feed
The contribution file layout changes when payroll changes. Agree on the file format with the recordkeeper, decide who submits it, and test it before go-live. Confirm the new feed sends the employee data fields the recordkeeper needs, not just dollar amounts.
6. Write down the new remittance timeline
Document each step from payday to deposit: when the file is generated, who approves funding, and when money reaches the trust. Compare it with your historical pattern. If the new process is slower, fix the process rather than accepting later deposits — late deferral deposits are the most common ERISA error for a reason.
After the Switch: Test the First Payrolls
Do not wait for year-end. On the first two or three payrolls in the new system, reconcile a sample of employees line by line: gross pay, plan compensation, deferral, match, loan repayment, and the amount the recordkeeper actually received. Include at least one employee from each tricky group — hourly with overtime, commissioned, bonus-eligible, Roth deferrers, loan holders and recent hires. Any variance found here is a mapping problem that will repeat until fixed.
This is the same discipline described in our guide to reconciling payroll and recordkeeper data, applied at the moment it matters most.
An 8-Step Sponsor Self-Check
- Is there a written earning-code map tied to the plan document’s compensation definition?
- Did someone outside payroll review that map?
- Were all deferral elections, including Roth designations, verified against the recordkeeper?
- Is every active loan repayment set up in the new system?
- Did hire, rehire, termination and hours history convert?
- Has the new contribution file been accepted by the recordkeeper without manual fixes?
- Is the payday-to-deposit timeline documented and no slower than before?
- Will year-end census, limit checks and testing combine data from both systems?
Where Sponsors Get Hurt
- Assuming the new payroll provider “handles the 401(k)” when its contract covers only processing deductions you configure.
- Discovering a compensation mismatch during testing, after it has repeated across many pay periods.
- Missed deferral elections that require a corrective contribution — see correcting a missed deferral election.
- A census built from only the new system, leaving out early-year pay and terminated employees.
- Participant data sent over insecure channels during the conversion, a risk covered in our 401(k) cybersecurity guide.
What You Can Delegate and What You Can’t
Choosing a payroll provider is a business decision. Making the plan run correctly through that change is a fiduciary one. A 3(16) plan administrator can review the earning-code map against the plan document, coordinate the recordkeeper feed, monitor remittance timing, and reconcile the first payrolls. What only the employer can supply is the payroll data itself: accurate hire dates, pay types and approvals. If you are changing recordkeepers at the same time, the work compounds; our mid-year provider transition checklist covers that side.
A Partner That Accepts the Responsibility
Most providers will help with a conversion and then point back to the sponsor when something is mapped wrong. Admin316 takes a different position. In addition to serving as your 3(16) administrator, Admin316 accepts appointment as the plan’s ERISA 402(a) named fiduciary — a role most providers decline — so oversight of plan operations through events like a payroll change sits with a fiduciary who has formally accepted it.
If a payroll change is on your calendar, review the plan side before the first check date. Book a conversation with Admin316 and we will walk through your compensation definition, data feed and remittance process with you.
