Who Does What? Mapping the Plan Sponsor, TPA, Recordkeeper, Trustee, and Payroll Provider
Clear role mapping does not remove the sponsor’s responsibility; it makes handoffs visible so the right party can act and the sponsor can verify Learn the contr
Clear role mapping does not remove the sponsor’s responsibility; it makes handoffs visible so the right party can act and the sponsor can verify the result.
Who Does What? Mapping the Plan Sponsor, TPA, Recordkeeper, Trustee, and Payroll Provider is easiest to manage when the team treats each event as a small control cycle: identify the rule, capture the source data, send or approve the transaction, and retain proof that the outcome was reviewed. This approach is more useful than relying on a vendor portal or a single annual checklist because employee events and payroll changes happen throughout the year.
At a glance
- Core question: Does the actual payroll and provider activity match the written plan and approved elections?
- Focus: Build a repeatable trail for sponsor decisions, trustee authority, TPA calculations, recordkeeper transactions, and payroll data.
- Reading path: define the control, compare the records, then use a documented exception process.
Define the control
A control is a repeatable action that makes an error easier to prevent or find. For plan operations, it should name an owner, an input, an expected output, a timing expectation, and evidence of review. The owner may delegate work to a TPA, recordkeeper, trustee, or payroll provider, but delegation does not make the sponsor’s oversight disappear. The DOL explains that a plan must have at least one named fiduciary with control over plan operation and that written plan terms are the foundation for operations.[1]
Start by reading the plan document and the current service agreements together. Translate the provisions that affect routine work into plain-language operating instructions. Avoid a generic “best practice” that conflicts with the document. When terms, payroll configuration, and provider instructions point in different directions, treat the difference as an exception to investigate rather than a setting to work around.
Compare the records
| Record | Question to ask | Evidence to retain |
|---|---|---|
| Plan terms | What result does the document require? | Applicable provision and amendment history |
| Payroll or census | Which people, pay, or events should be included? | Approved source report and change log |
| Provider output | Did the processed result match the approved input? | Confirmation, exception report, and reviewer sign-off |
Comparison should be specific enough to reveal differences. For example, a total-dollar match can conceal a participant-level omission; a participant-level match can still miss the timing of a deposit or an incorrect compensation category. Set tolerances deliberately, but require a written explanation for every variance that is not automatically resolved.
Use a short exception log with the date found, affected period, owner, preliminary impact, action taken, and date closed. The log is not an admission of a violation. It is a practical way to prevent the same question from being rediscovered later without context.
Make the review usable under normal workload. A reviewer should be able to see the source, compare it to the output, and record a conclusion without rebuilding the transaction from scratch. Standard naming, a fixed storage location, and a one-page checklist reduce the chance that important evidence stays in an individual inbox.
Implement the routine
Turn the control into a calendar-backed routine. Before the first live cycle, run a parallel test using a recent payroll or census file. Confirm that field names mean the same thing across systems, that totals reconcile, and that corrections follow an approved path. Then use the same sequence each cycle: freeze the source report, review the transmission or transaction, compare confirmations, investigate differences, and save the evidence.
Keep implementation proportional. A small plan may use a secure folder and a reviewer checklist; a larger employer may need workflow tickets, automated exception reports, and segregated approvals. In either case, someone should be able to reconstruct what happened without relying on a former employee’s memory. Where a discrepancy may involve a plan-term failure, obtain plan-specific guidance before selecting a correction method.
Review before closing the period
- 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.
| Step | Practical action | Review question |
|---|---|---|
| Define | Identify the controlling provision and source report. | Is the rule current and understood? |
| Compare | Match records at participant and total levels. | Are amounts, people, and dates aligned? |
| Implement | Process approved corrections or escalate exceptions. | Is there a clear owner and deadline? |
| Review | Save evidence and look for recurring root causes. | Would an independent reviewer understand the file? |
Period-close review should distinguish an isolated data issue from a process design issue. If the same type of difference appears more than once, revisit the mapping, training, approval step, or calendar trigger rather than merely repairing the individual record. An annual review is also a good point to compare the operating procedure with amendments, vendor changes, and new payroll codes. The DOL explains that a plan must have at least one named fiduciary with control over plan operation and that written plan terms are the foundation for operations.[1]
When an exception appears
Do not let speed erase the evidence. First preserve the report used for the decision and identify the affected participants, pay dates, and plan provisions. Next, separate confirmed facts from open questions: a missing file, a late handoff, and an incorrect rule configuration may look similar in a summary but require different responses. Ask the responsible provider for a dated explanation and compare it against the original source data. If a correction may be needed, document the calculation inputs, approvals, communications, and completion evidence in one case file. Finally, make a preventive change—such as a new validation rule, staff instruction, or calendar reminder—and test it on the next cycle. This sequence gives the sponsor a defensible record while leaving technical correction decisions to qualified, plan-specific advisers.
Takeaway
401(k) plan administration roles is most reliable when it produces evidence, not just activity. Build one simple chain from plan term to source data to processed result to reviewer sign-off. That chain helps the team respond faster, delegate with clarity, and identify questions early enough for informed plan-specific review.
Editorial disclaimer: This article is general educational information, not legal, tax, fiduciary, actuarial, investment, or compliance advice. Plan documents, facts, and applicable law control. Consult qualified counsel, tax advisers, and plan service providers before acting.
References
- [1] https://www.dol.gov/agencies/ebsa/employers-and-advisers/small-business-owners/understanding-your-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
Map 401(k) Duties Across Sponsor, TPA, Recordkeeper, Trustee, and Payroll
Create a written operating map before assuming that a vendor owns a task. The sponsor and named fiduciary should establish governance and monitor providers; payroll supplies employment and contribution data; administration, recordkeeping, trustee, and custody functions should be defined by the plan documents and service agreements.
Records and controls to review
Maintain a responsibility matrix identifying each task, accountable and responsible party, plan-document authority, data source, review control, deadline owner, and retained evidence. Reconcile payroll, TPA administration, and recordkeeper or trustee records on a recurring schedule, with named reviewers and documented resolution of variances.
Before changing operations
Use the written plan and the current service agreement as the starting point. Compare them with the payroll configuration, provider report, and participant-facing materials that will actually be used. If the records conflict, pause the change, identify the controlling record, assign an exception owner, and document the resolution before the next processing cycle.
Test a normal example and a realistic edge case before release. Record what was verified, who verified it, the action taken, and the date for the next reconciliation. This gives the sponsor and its providers a repeatable record rather than a conclusion reconstructed after an exception occurs.
For each change, identify the event that triggers the work, the data source used, the person who approves the result, and the evidence retained after completion. A short exception log should also state when an item is escalated and when a corrected result has been independently reconciled. This control-oriented approach helps expose gaps between a decision and the daily administration that carries it out.
When a provider or internal team supplies information, retain the source version, confirm the effective date, and record unresolved assumptions before action. A concise review note should connect the operational conclusion to the governing document, the supporting report, and the responsible reviewer so future corrections can start from evidence rather than recollection.
For this review, also identify the system that produces each report, the point when its data becomes final, and the reviewer who confirms that a required handoff occurred. Keep that evidence with the decision record so the next annual, payroll, or provider-cycle review can test the same control rather than recreate it.
Implementation checkpoint
- Confirm: identify the governing provision and effective date.
- Reconcile: compare payroll, provider, and participant records.
- Assign: document who owns exceptions and follow-up.
- Retain: preserve approvals, reports, communications, and completion evidence.
Important boundary: Industry labels do not conclusively establish fiduciary status or legal responsibility, and bundled vendors may perform multiple functions. Do not assign plan-specific liability from a general role chart; rely on the plan document and contracts, and seek qualified ERISA counsel for responsibility questions.
Reference
- Official source: https://www.dol.gov/sites/default/files/ebsa/about-ebsa/our-activities/resource-center/publications/meeting-your-fiduciary-responsibilities.pdf