Should You Unbundle Your 401(k) TPA and Recordkeeper?
A practical guide for plan sponsors comparing unbundle 401k TPA recordkeeper: decision criteria, due diligence questions, costs, service, implementation, and review.
Unbundling a 401(k) TPA and recordkeeper can be worthwhile when a committee has a specific service, pricing, or flexibility problem it can manage; it is not a shortcut around oversight.
Choosing a retirement-plan service model is a buyer decision with operational and fiduciary consequences. A 401(k) allows employees to contribute part of wages to individual accounts, and employers may also contribute.[1] The committee’s task is to evaluate the delivery model against the plan it actually operates—not against a generic promise of simplicity, choice, or savings.
At a glance
- Core question: What arrangement best supports this plan’s operations and governance?
- Focus: Compare the current pain point with the added transition, integration, and governance work of separate providers. Ask who owns every exception, correction, and participant escalation.
- Reading path: define the model, compare evidence, then implement and review the decision.
Define the decision before comparing providers
A third-party administrator and a recordkeeper may perform related but distinct work. Separating them can allow a plan to select specialist capabilities, while also creating more handoffs that must be defined and tested. The sponsor remains responsible for a prudent process when hiring and monitoring providers.[2] A provider relationship should be described in terms of functions: who receives payroll data, who reconciles deposits, who applies plan terms, who answers participants, who prepares reports, who supports testing or corrections, and who has discretion. Titles alone do not decide fiduciary status; the DOL explains that discretion in plan administration or asset management can create fiduciary status.[2]
Start with a one-page operating profile. List participant count and workforce patterns, payroll systems and frequencies, plan features, recurring exceptions, investment governance, committee capacity, and the service failures the plan is trying to solve. Then identify non-negotiables. Examples include reliable contribution processing, support for the plan’s eligibility rules, usable reporting, clear escalation, and a transition plan that does not interrupt participant service.
Compare the model, not just the presentation
| Lens | What to examine | Useful evidence |
|---|---|---|
| Scope | Which functions are included, excluded, or delegated? | Responsibility matrix and contract schedule |
| Cost | How are provider, investment, transaction, and change fees described? | Fee exhibit with assumptions and triggers |
| Service | Who owns recurring work and exceptions? | Service calendar, escalation path, sample reports |
| Control | What can the committee change without a full conversion? | Implementation and change-management plan |
Compare the current pain point with the added transition, integration, and governance work of separate providers. Ask who owns every exception, correction, and participant escalation. Ask every finalist to respond to the same fact pattern and to state assumptions. Comparable answers are more valuable than polished but differently scoped proposals. DOL guidance notes that surveying providers with the same information can help a fiduciary make and document a meaningful comparison.[2]
Do not treat a vendor’s standard workflow as proof that it fits your plan. Ask for a walkthrough using a real but de-identified scenario: a payroll correction, an eligibility question, a participant loan or distribution request, an annual review, and an unexpected data-file failure. The walkthrough reveals handoffs, timing, ownership, and whether the proposed service model can handle your ordinary exceptions.
Implement with a documented, proportionate process
Set evaluation criteria before presentations begin. A practical committee can use a shared requirements document, a response template, a scoring rubric, a record of questions and clarifications, and meeting minutes that explain the decision. This does not mean every decision requires the same length of project. It means the process should be capable of showing why the selected approach addressed the plan’s needs, fees, and risks.
Decision flow
- Map data: identify payroll fields, owners, and timing.
- Compare gaps: compare provider mappings, controls, and exceptions.
- Test handoff: test the handoff before relying on production data.
- Reconcile: reconcile results and retain exception evidence.
Move forward only when the committee can explain the evidence, owner, and next review point for the decision.
Practical buyer checklist
| Workstream | Questions to ask | Decision record |
|---|---|---|
| Operations | Who owns each file, exception, and participant escalation? | Named owner, timing, and escalation route |
| Fees | What is included, what changes the price, and who pays? | Comparable fee schedule and assumptions |
| Transition | What data, notices, testing, and blackout planning are required? | Milestones, dependencies, and contingency owner |
| Monitoring | Which measures show service and controls are working? | Review calendar, scorecard, and action log |
Review the decision after selection
Selection is not the end of oversight. The DOL says fiduciaries should act prudently, follow plan documents when consistent with ERISA, and pay only reasonable plan expenses.[2] Build a review calendar that distinguishes routine service monitoring from a broader market check. Review unresolved exceptions, missed service commitments, participant experience, reporting quality, fee changes, and whether the provider is performing the functions promised in the agreement.
Keep a concise file: the original requirements, proposals or benchmark evidence, questions, scorecard, meeting notes, contract terms, and follow-up actions. The record should show a reasoned process, including why a lower-cost option was not chosen if it lacked needed capability. It should also show when a narrow issue was handled through negotiation or corrective action instead of a full market process.
Questions that expose hidden assumptions
- Which plan task is most likely to fail during a busy payroll or year-end period, and who owns the recovery?
- What data must move between parties, how is it validated, and how are errors communicated?
- What services are standard, which are project-based, and what event triggers an additional charge?
- Which decisions stay with the committee, and which functions are performed with discretion?
- What evidence will be available at the next review to show whether the arrangement is working?
Before closing the file, assign an owner to each open item and a date for confirming it. That small discipline prevents an evaluation from becoming a collection of opinions rather than a usable governance record.
Takeaway
The best provider decision is a documented match between the plan’s needs and a service model the committee can understand, monitor, and improve. Use a common scope, comparable evidence, a clear fee view, and named owners for every handoff. This article is general educational information, not legal, tax, investment, or fiduciary advice; review plan documents and obtain advice suited to your circumstances before making a provider or plan-administration decision.
References
- [1] Internal Revenue Service, 401(k) plans. https://www.irs.gov/retirement-plans/401k-plans
- [2] U.S. Department of Labor, Employee Benefits Security Administration, Meeting Your Fiduciary Responsibilities. https://www.dol.gov/agencies/ebsa/about-ebsa/our-activities/resource-center/publications/meeting-your-fiduciary-responsibilities
Discuss your plan with Yang's Pension Consulting
Decision pathway
Use this page to frame the decision, collect the plan documents and operating facts that matter, and then confirm the facts with the appropriate plan, tax, actuarial, legal, or compliance professional.
- Define: identify the plan terms, workforce facts, and timing involved.
- Compare: separate operational choices from questions that require professional analysis.
- Implement: document the approved approach and align payroll, providers, and communications.
- Review: revisit the process when plan design, workforce, or rules change.
Try a related planning aid: Fee and Service Benchmark Worksheet.
Continue learning
Compare interfaces and accountability, not only price
Bundled and unbundled arrangements can both support a plan. The key question is whether the sponsor can clearly identify who receives payroll data, performs recordkeeping, applies plan terms, tests results, handles corrections, and owns each exception during normal operations and transitions.
What to document before acting
Map the data flow, system of record, contract boundaries, compensation disclosures, service-level commitments, cybersecurity responsibilities, implementation timeline, blackout/participant communications, and escalation paths before changing a provider model.
How to use the evidence
Start with the written plan and the current service agreement rather than relying on a prior email, a payroll default, or a vendor label. Compare the operative terms with the current payroll configuration and provider report. If they disagree, pause the change, identify the source record that controls, and document the resolution before the next processing cycle.
A useful review file answers four questions: what fact was confirmed, who confirmed it, what action was taken, and when the result will be checked again. That record gives the sponsor, its providers, and any reviewer a shared basis for resolving future exceptions without reconstructing decisions from memory.
Before releasing a change, run one normal example and one edge case through the proposed workflow. Compare the expected output with the plan terms, confirm who receives the result, and define a stop-and-escalate point for incomplete data. After release, perform a short reconciliation and retain the sign-off with the underlying report.
Implementation checkpoint
- Confirm the written terms: identify the plan provision and effective date that govern the decision.
- Reconcile operating data: compare payroll, provider, and participant records before finalizing an action.
- Assign an exception owner: document who resolves a mismatch and how the correction is reviewed.
- Retain the decision record: keep the inputs, approvals, provider communications, and follow-up evidence together.
Important boundary: Unbundling is not inherently cheaper or more prudent. The sponsor still must select and monitor providers prudently and manage handoffs.
Reference
- Official source: https://www.ecfr.gov/current/title-29/subtitle-B/chapter-XXV/subchapter-F/part-2550/section-2550.408b-2
