A provider change reset plan settings more often than sponsors realize, and the result is a plan that is operated one way while the signed plan document says another. A conversion team loads the recordkeeper’s standard configuration, nobody compares it to your document, and months later a participant, an auditor or the DOL notices that eligibility, match, vesting or compensation rules do not match what the plan actually says. That is an operational failure, and it is a fiduciary problem rather than a clerical one, because the plan must be run according to its terms.
This post covers the specific event of a conversion or provider switch resetting settings. For the broader topic of documents and notices drifting apart, see our guide on a plan document and operations mismatch. Here we focus on how the reset happens, how to catch it, and how to correct it.
Why a Provider Change Is a Fiduciary Event, Not an IT Project
The plan document is the controlling instrument. A recordkeeper’s system is only a tool that is supposed to implement it. When a new provider loads default settings, the system can start applying rules your document never adopted, and the sponsor remains responsible for the outcome.
1. Defaults are built for the average plan, not yours
Onboarding templates assume common choices. If your plan uses a different eligibility rule, a custom match formula, a particular vesting schedule or a specific definition of pay, a default setting can quietly override it.
2. The conversion team is not reading your document
Implementation staff typically work from a questionnaire or the old provider’s data feed. Unless someone ties each setting back to the document language, the questionnaire answers become the new operating rules.
3. Responsibility does not transfer with the data
Moving to a new provider does not move the duty to follow the plan terms. Our overview of switching 401(k) providers mid-year covers the transition risks that make this review essential.
Where Resets Typically Show Up
Settings that tend to drift after a conversion include:
- Eligibility and entry date rules, including any exclusions for classes of employees (see 401(k) eligibility and entry dates)
- Match formula, caps and any last-day or hours conditions
- Definition of compensation used for deferrals and employer contributions (see compensation definition errors)
- Vesting schedule and the service-crediting method
- Automatic enrollment percentage, escalation and default investment
- Loan limits, hardship rules and in-service distribution availability
- Forfeiture handling and how forfeitures are used
How to Catch the Mismatch
Do not wait for a participant complaint. A structured comparison finds problems while they are still small.
1. Pull the controlling documents
Gather the adoption agreement, basic plan document, every amendment, and the most recent SPD and any modifications. Our guide to SPDs and summaries of material modifications explains how those fit together.
2. Build a setting-by-setting map
Create a table with three columns: the document provision, the old provider’s configuration, and the new provider’s configuration. Any row where the new setting differs from the document is a candidate failure.
3. Test with real participants, not just settings
Select a sample of employees across hire dates, pay types and status changes. Recalculate their eligibility, deferrals, match and vesting by hand from the document and compare to what the system produced.
4. Reconcile the feed and the roster
Use the recordkeeper roster, including terminated participants with balances, as your population. Our resource on participant data reconciliation shows how to line up payroll, recordkeeper and plan records.
5. Review notices and disclosures sent after the change
If the new provider generated enrollment, safe harbor or default investment notices from reset settings, those notices may now describe terms the plan does not contain. Compare them to the document.
An 8-Step Self-Check After Any Conversion
- Identify the effective date of the conversion and the first payroll processed on the new system.
- Obtain the new provider’s full configuration report, not a summary.
- Tie every configuration item to specific document language.
- Flag every difference and classify it as a system error or a possible undocumented plan change.
- Recalculate a sample of participants for eligibility, contributions and vesting.
- Check whether any participant was excluded, included late or paid incorrectly.
- Review notices, forms and portal language for accuracy.
- Record findings, owners and evidence in writing for the plan file.
How to Cure and Correct the Mismatch
Correction follows a general sequence. The right method depends on the type of failure, your plan year and the amounts involved, so confirm specifics with your document provider and ERISA counsel.
1. Fix the setting first
Have the provider reconfigure the system to match the document and confirm the change in writing. Stopping the ongoing error comes before measuring the past.
2. Decide whether the document or the practice should win
Sometimes the reset reveals that the new practice is actually what the sponsor would prefer. Changing the plan is a settlor decision made by amendment, not by system default, and a prospective amendment does not erase past noncompliance. Where the practice is plainly outside the document, the usual path is to correct to the document’s terms.
3. Quantify the affected participants and amounts
Determine who was affected, for how long, and what they should have received or contributed, including earnings. Document the method so it can be reviewed.
4. Select the correction pathway
Operational failures are generally addressed through self-correction where available, or through the IRS correction program. Late or missing money may also raise fiduciary correction questions. Read our guides on administrative error correction, fixing plan failures under EPCRS and the Voluntary Fiduciary Correction Program to see how the options differ.
5. Re-run testing if the error touched contributions
Misapplied eligibility or compensation can change the results of nondiscrimination testing. Recompute before filing.
Where Sponsors Get Hurt
- Assuming the new provider verified the configuration against the document, when it only loaded a questionnaire.
- Discovering the issue at audit time, after years of compounding errors. See the audit readiness checklist.
- Correcting the system but never calculating make-up amounts for past participants.
- Amending the document after the fact to match the error without evaluating the effect on prior years.
- Leaving no written record, so the plan file cannot show prudent process.
What You Can Delegate and What You Cannot
A 3(16) administrator can run the comparison, reconcile the data, calculate corrections and keep the evidence trail. Our 3(16) plan administration service handles that day-to-day implementation. What cannot be delegated away is the settlor’s decision to change plan terms, and the employer-only data a provider cannot see, such as intended eligibility classes, ownership and family relationships, and the true definition of pay the company meant to adopt. Those inputs must come from you. For a fuller picture of how the roles divide, see 3(16), 3(21), 3(38) and 402(a) fiduciary roles.
Put Someone Formally in Charge of Following the Document
The recurring cause of this problem is that nobody was formally accountable for tying system settings to the document during the switch. Admin316 accepts formal appointment as your ERISA 402(a) named fiduciary, something most providers decline. Combined with 3(16) administration, that means a named party owns the plan’s operation against its written terms through every provider change. Learn more about 402(a) fiduciary services, then book a conversation with Admin316 to review whether your plan is operating the way your document says.

