What Does a 401(k) TPA Do? Services, Limits, and Questions to Ask
Learn the typical role of a 401(k) third-party administrator, where its work stops, and how to ask better provider questions.
Read an administration proposal as a scope discussion
A first-time sponsor can make a vague service proposal easier to discuss by asking for examples of the work described. Keep a list of included items, unclear items and items that need another provider’s explanation. The list is a purchasing aid, not a substitute for reviewing the eventual agreement.
- Ask who would explain a routine question and where that answer would be documented.
- Distinguish an included service from a feature mentioned only as an available option.
- Record questions about employer input without assuming that a provider has accepted a task.
Use the Plan Sponsor Responsibility Mapper to structure the scope conversation.
The provider resource hub contains broader reading; this page’s next step is selecting help for a first plan.
Describe the administration questions for the proposed new plan. Contact Us About a New Plan for a high-level conversation, not an online individualized recommendation or quote.
Plan-specific considerations
Hiring an administrator does not by itself establish that every employer duty has been transferred.[4] The IRS qualification framework addresses the plan’s actual operation as well as its terms.[5]
Sources for these considerations
- [4] Retirement plan fiduciary responsibilities | IRS. https://www.irs.gov/retirement-plans/retirement-plan-fiduciary-responsibilities
- [5] 401(k) plan qualification requirements | Internal Revenue Service. https://www.irs.gov/retirement-plans/plan-sponsor/401k-plan-qualification-requirements
A 401(k) third-party administrator, or TPA, can support plan administration, but its actual role depends on the service agreement and plan design. Employers should ask what the TPA calculates, prepares, reviews, files, escalates, and expects the employer to approve.[3]
Many administrative workflows turn on data: hire and termination dates, compensation, hours, elections, ownership information, and contribution deposits. The written plan tells the administrator how to treat that data; IRS guidance emphasizes that a qualified plan must be operated according to its provisions.[2]
At a glance
- Core question: What does the written plan require, and who verifies it?
- Employer focus: Connect design choices to payroll, providers, participant communication, and records.
- Reading path: Define the concept, compare responsibilities, then implement and review a controlled process.
Define the employer problem
A TPA may help with testing, allocation calculations, forms, and operational questions. It may coordinate with a recordkeeper, payroll provider, advisor, trustee, custodian, or auditor. Those helpful services do not automatically make the TPA the named fiduciary or relieve the employer of every sponsor responsibility.
The DOL's fiduciary framework turns on discretion and control, not a marketing label.[3] Ask whether the provider accepts discretionary authority, whether it makes recommendations or only performs calculations, what assumptions it uses, and how corrections are handled. Ask who checks the final data before filings or participant transactions occur.
Compare: decision versus operation
| Lens | Ask | Evidence |
|---|---|---|
| Design | What feature or rule is intended? | Adopted document and approval record |
| Operation | How is the rule applied? | Payroll and provider workflow |
| Oversight | Who checks the outcome? | Review notes and exception log |
A useful rule of thumb is to make every promise traceable: from document language to an owner, a data source, a timing rule, a participant-facing explanation, and a review step. That traceability makes an employer's process easier to train, monitor, and improve.
How the pieces connect
Consider a routine change in an employee's status. The HR system may hold the change, payroll may apply it on a scheduled cycle, a provider may receive a data feed later, and a participant may expect a result on a particular entry date. A sound process identifies each handoff before it occurs. It also states what happens if a data field is missing, late, or contradictory.
That discipline prevents a common mistake: treating a provider report as proof that the employer's underlying data was correct. Reports are valuable controls, but they reflect the data and instructions received. The employer should understand the assumptions behind a report, review exceptions, and decide whether a correction or document interpretation is needed. Keep the decision record with the related report.
Plain-language communication is part of operational quality. Employees need understandable descriptions of available choices and timing; administrators need procedures detailed enough to apply the terms consistently. When a new feature, acquisition, payroll code, or provider transition changes the process, refresh both audiences rather than relying on a past implementation memo.
Implement with an operating checklist
A good selection process compares like with like: same census, same requested services, same implementation assumptions, and transparent fees. DOL advises using comparable information, considering whether fees are reasonable for services, documenting the selection, and monitoring providers after hire.[3]
- Name an accountable owner. Give one person or committee clear authority to coordinate the work and escalate uncertainty.
- Translate the document. Build a plain-language procedure for payroll, HR, and providers; do not replace the document with the procedure.
- Test the handoff. Use a sample employee or payroll cycle to confirm timing, data fields, approvals, and participant communication.
- Retain evidence. Save approvals, reports, reconciliations, notices, and explanations of exceptions in a predictable location.
Decision flow
- Identify rule: identify the governing limit, date, and affected group.
- Model impact: model cost, eligibility, and interaction with other rules.
- Apply control: apply the rule through payroll or plan controls.
- Recheck: recheck inputs, corrections, and retained support.
Define → compare → implement → review. Pause for expert input whenever the document, data, or rule is unclear.
Review on a repeatable cadence
Use a periodic review to compare what was supposed to happen with what actually happened. Look for changes in workforce data, payroll systems, provider services, plan documents, and unresolved exceptions. A review is most useful when it ends with an owner, due date, and evidence of completion—not merely a meeting note.
Make the cadence realistic. A brief payroll control may be performed each pay cycle, while a broader governance review may be quarterly or annual. The frequency should match the operational risk and the plan's actual workflow. What matters is that the review has a defined trigger, an assigned reviewer, and a consistent record of results.
When a discrepancy appears, first preserve the facts: affected population, dates, data source, document provision, and actions already taken. Then route the issue to the person or professional with the right authority. Avoid informal fixes that make the data look correct but leave the underlying document or process unanswered. Close the loop by recording the decision and any needed procedure change.
| Review item | Practical question | Follow-up evidence |
|---|---|---|
| Data | Do HR and payroll inputs match the applicable rule? | Reconciliation and exception list |
| Provider work | Were services delivered on time and as agreed? | Report, invoice, and service review |
| Participant impact | Were elections, notices, and entries handled consistently? | Sample testing and communication record |
Before the next cycle
Set aside time to rehearse one real scenario with the people who supply data, approve decisions, and communicate with participants. A short rehearsal often reveals a missing owner, undocumented deadline, or unclear handoff. Update the procedure after the rehearsal so future work uses what the team learned rather than rediscovering the same problem.
Write the result in a form another team member can follow without relying on memory or an informal conversation.
Takeaway
The strongest employer process is not the longest checklist. It is a documented loop that connects plan terms, real data, accountable decisions, and recurring review. Use this guide to prepare better questions for your plan document provider, ERISA counsel, tax adviser, payroll team, and service providers.
Editorial disclaimer: This article is general educational information, not tax, legal, actuarial, investment, or compliance advice. Retirement-plan requirements are document- and fact-specific and can change. Obtain advice from qualified professionals before adopting, administering, amending, or relying on a plan decision.
References
- Supporting source: IRS, 401(k) plan overview. https://www.irs.gov/retirement-plans/plan-sponsor/401k-plan-overview
- [2] IRS, 401(k) plan qualification requirements. https://www.irs.gov/retirement-plans/plan-sponsor/401k-plan-qualification-requirements
- [3] U.S. Department of Labor EBSA, 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: Plan Sponsor Responsibility Mapper.
Continue learning
Separate administrative assistance from retained sponsor oversight
A TPA may support documents, testing, allocations, reporting, and operational questions, but its actual scope is defined by the service agreement and functions performed—not by the TPA label alone.
What to document before acting
Make a task map identifying payroll inputs, eligibility decisions, contribution approvals, testing data, participant notices, filings, correction escalation, and which party owns each handoff.
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: Hiring a provider does not automatically transfer every sponsor or fiduciary responsibility; verify discretionary authority and monitoring duties in writing.
Reference
- Official source: https://www.dol.gov/agencies/ebsa/employers-and-advisers/small-business-owners/working-with-service-providers