Retirement Plan Advisor, TPA, Recordkeeper, Custodian, and Actuary: Who Does What?
Compare retirement plan provider roles service models, responsibilities, questions, and review steps for an informed employer decision.
Retirement plan provider roles are easiest to manage when the committee maps each job rather than assuming one vendor performs every function.
Retirement Plan Advisor, TPA, Recordkeeper, Custodian, and Actuary: Who Does What? is a buying decision with consequences long after the sales call. A useful evaluation starts with the daily work: payroll changes, eligibility questions, participant requests, corrections, notices, testing, filings, and committee records. The goal is not to predict every exception. It is to make ordinary work clear and exceptional work visible early.
At a glance
- Core question: Can the provider explain its responsibility in plain language and show how work moves from payroll to review?
- Focus: Evaluate advice, administration, records, custody, and actuarial analysis, not a vague promise of “full service.”
- Reading path: Define the role, compare operating models, then test implementation and review practices.
Define the work before comparing providers
Start with a written inventory of the plan’s recurring events. Include payroll frequency, employee groups, eligibility and entry rules, employer contribution formulas, vesting, loan or distribution workflows, testing, annual notices, Form 5500 coordination, and committee reporting. The inventory does not decide who is legally responsible; it gives the committee a common way to discuss work and exceptions.
A 401(k) plan must be operated according to its governing provisions as well as applicable qualification rules. The IRS explains that tax-favored qualified plans need both compliant plan language and operation in accordance with the plan’s provisions.[1] That is why a provider comparison should ask for the operating process behind the promise, including inputs, review points, documentation, and escalation.
For example, a payroll file can be transmitted accurately but still require review when a compensation definition, rehire date, ownership change, or employer contribution calculation is unusual. A good service design identifies which party detects the issue, who interprets the plan document, who approves the response, and how the decision is recorded. The same question applies to routine work: a smooth handoff is valuable only if it remains understandable when staff change.
Compare the operating models
| Comparison lens | What to ask | Useful evidence |
|---|---|---|
| Scope | Which tasks are included, optional, or excluded? | A task list tied to the engagement |
| Handoffs | Who receives, validates, and resolves an exception? | A sample workflow and named contacts |
| Oversight | What remains for the committee to review? | A recurring report and issue log |
| Change | How are plan amendments or payroll changes introduced? | A documented change-control process |
Do not treat price as a standalone verdict. Compare the fee with scope, limits, service cadence, implementation effort, and the cost of internal time. A lower recurring fee can be less useful if the employer must build its own controls around unclear handoffs. Conversely, a broader service package should be tested for the specific work it actually includes.
The decision standard is who decides, who performs, who verifies, and who answers participant questions. Ask each candidate to walk through one normal payroll cycle and one plausible exception. Listen for ownership words: “we do it,” “you approve it,” “the recordkeeper receives it,” or “counsel interprets it.” Ambiguity is not always a defect, but unrecorded ambiguity is a risk for the committee to manage.
Implement with a documented transition
Before signing, translate the preferred provider’s proposal into an implementation checklist. Confirm the plan document version, service calendar, payroll contacts, file specifications, historical data needs, participant communications, current open items, and approval authority. Assign an employer owner for each deliverable and require the provider to identify its owner. A transition is easier to govern when a missed dependency has a visible escalation route rather than an informal email chain.
Build a short test period into the plan. Review a sample census and payroll output, verify the treatment of common employee events, and compare expected results with the plan’s written terms. The IRS notes that traditional 401(k) plans can involve annual nondiscrimination testing; whether and how a particular test applies depends on plan design and facts.[1] That makes early data review more useful than a generic assurance that testing will be handled.
- 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.
Review the relationship, not just the invoice
Set a committee cadence that matches the plan’s complexity. At each review, look for completed work, open exceptions, late inputs, corrections, participant-impacting issues, service changes, and decisions requiring employer action. Keep minutes that describe the information considered and the next owner. The aim is a usable record of prudent process, not a ceremonial meeting.
| Review signal | Question for the provider | Committee response |
|---|---|---|
| Repeated exception | What caused it and how will recurrence be prevented? | Approve a corrective owner and due date |
| Unclear boundary | Which party owns the next action under the engagement? | Document the handoff or amend scope |
| Data mismatch | What source controls were applied before processing? | Validate payroll and census controls |
| Service change | What changes for participants and administrators? | Request a transition and communication plan |
Questions that expose fit
- Show us a current task calendar and distinguish included work from optional work.
- Which report will identify missing payroll inputs, failed validations, or overdue decisions?
- Who may interpret the plan document, approve corrections, or communicate a participant-impacting change?
- How do you train a new employer contact and preserve context when your own team changes?
- What is the escalation path when a response affects a filing, testing result, or participant transaction?
These questions are intentionally practical. They give competing providers a fair chance to explain their model while giving the committee artifacts it can compare. A clear answer may reveal that a narrower provider scope is acceptable because the employer has capable internal owners. It may also show that broader support is worth the cost because the plan has complex payroll, frequent changes, or limited internal capacity.
Takeaway
Retirement plan provider roles are easiest to manage when the committee maps each job rather than assuming one vendor performs every function. Choose the arrangement that makes responsibilities legible, exceptions actionable, and review repeatable. No provider selection removes the need for employer governance. The stronger outcome is a documented operating model that the committee can understand, test, and revisit as the workforce and plan change.
Editorial disclaimer: This article is general educational information, not legal, tax, investment, actuarial, or compliance advice. Plan documents, contracts, and individual facts matter; consult qualified advisers for decisions about a particular plan.
References
- [1] Internal Revenue Service, “401(k) plan overview.” https://www.irs.gov/retirement-plans/plan-sponsor/401k-plan-overview