Rehired Employees and 401(k) Eligibility: Which Prior Service Counts?
Learn the questions HR and payroll should ask when a former worker returns: prior service, breaks in service, entry dates, vesting, and plan-document controls.
The first record to collect is the person’s prior employment and plan participation history: original hire, termination, rehire, hours or elapsed-time record, prior entry date, account balance, and prior vesting percentage. The IRS explains that vesting is ownership of employer-provided benefits and that plan documents set important conditions.[1] That makes the written plan, not a supervisor’s recollection, the starting point.
For employers, this is a plan-design and operations decision—not a one-line HR setting. The useful question is whether the rule can be explained clearly, applied from reliable data, and reconciled to the governing plan document.
At a glance
- Core question: What does the written plan permit and require?
- Decision lens: Balance worker experience, cost, and repeatable administration.
- Reading path: Define the rule, compare outcomes, then implement controls.
Define the rule before choosing a workflow
A rehire should trigger a plan review, not an assumption that the employee starts over or picks up exactly where they left off. Eligibility, entry, vesting, and forfeiture rules can use different service concepts. The employer’s adoption agreement, basic plan document, amendments, and administrative procedures should be read together. The IRS describes the basic 401(k) structure and the Department of Labor emphasizes that sponsors have ongoing plan responsibilities.[1][2]
Start with the boundary of the decision. Identify which employees, contribution sources, dates, and service records are in scope. Then separate what the law requires from the optional design choice. This prevents a discussion about employee experience from accidentally changing a protected contribution rule or a recordkeeping process.
Compare the practical tradeoffs
A break in service may matter, but it is not a substitute for reading the plan’s definitions. Payroll should also avoid treating a rehire as a new hire if the administrator has information that changes eligibility or vesting treatment. The operational risk is often a late enrollment or an incorrect employer contribution, followed by a correction project.
| Lens | More immediate/simple approach | More conditional/batched approach |
|---|---|---|
| Employee experience | Fewer timing surprises and a clearer explanation. | May align with a defined workforce policy but needs precise communication. |
| Operations | Frequent processing and prompt data handoffs. | More checkpoints and a greater need for exception tracking. |
| Governance | Still requires document and payroll alignment. | Requires the same alignment plus disciplined service or status records. |
Use the table as a conversation aid, not as a legal conclusion. A choice that works for one employer can fail at another if hiring patterns, payroll timing, or plan terms differ.
Before approving a change, write down the intended employee outcome, the operating steps, and the exception path. Run a small set of real employee records through the proposed process. This makes hidden dependencies visible: a missing payroll code, a delayed data feed, an unclear service definition, or an enrollment notice that no longer matches the rule. The goal is not maximum complexity; it is a rule the sponsor can demonstrate, repeat, and audit.
Keep the decision memo short but concrete. It should state the affected population, the effective date, the responsible operations owner, the report used to monitor compliance, and the person who must approve an exception. This record helps future HR and payroll teams understand why the design was selected and reduces the temptation to fill gaps with informal practices.
Implement with named controls
Create a rehire intake checklist shared by HR, payroll, and the recordkeeper. Reconcile the returning worker to historic records before the first eligible payroll. Escalate ambiguous service credit questions to the TPA or ERISA counsel and retain the determination with the personnel and plan files.
- Assign an owner. Name who receives hire, termination, service, and status-change data.
- Use a documented trigger. Define the payroll or administration event that starts the action.
- Reconcile exceptions. Compare HR, payroll, and recordkeeper outputs before money moves or notices are issued.
- Retain the evidence. Keep the calculation, approvals, and communications with plan records.
- Know terms: identify governing terms, eligibility, and participant facts.
- Compare choices: compare available choices, costs, and consequences.
- Guide action: guide the next action without replacing required advice.
- Confirm: confirm records, notices, and unresolved questions.
Decision flow
Define the governing terms → compare employee and payroll data → implement the approved process → review exceptions and records.
Review questions for a sponsor meeting
| Question | Evidence to review | Why it matters |
|---|---|---|
| Does the document say what the team believes it says? | Adoption agreement, amendments, notices | Operations must follow written terms. |
| Can systems identify affected workers or dollars? | Payroll codes, service records, source reports | Rules fail when data cannot support them. |
| Who approves exceptions and corrections? | Calendar, workflow, escalation record | Clear ownership reduces missed actions. |
Review after a hiring surge, payroll-system change, plan amendment, merger, or unusual termination pattern. Those events often reveal a gap between a design decision and its day-to-day execution. Schedule the review before transactions are finalized when possible. The reviewer should compare a short sample of employee-level records with the plan document, recordkeeper output, payroll report, and notices. If a discrepancy appears, pause assumptions, identify the responsible owner, and obtain correction guidance. A documented review is also useful evidence that the sponsor has treated plan administration as a continuing responsibility rather than a one-time setup task. The review record should identify the period tested, the systems used, any findings, the corrective action, and the date the action was confirmed. Repeating this simple cycle creates a practical feedback loop: a documented decision leads to a controlled process, the process produces evidence, and the evidence informs the next review or amendment. It also gives the sponsor a clear starting point when personnel, vendors, or systems change.
Takeaway
The first record to collect is the person’s prior employment and plan participation history: original hire, termination, rehire, hours or elapsed-time record, prior entry date, account balance, and prior vesting percentage. The IRS explains that vesting is ownership of employer-provided benefits and that plan documents set important conditions.[1] That makes the written plan, not a supervisor’s recollection, the starting point. Treat the plan document as the control point, test the decision with actual workforce data, and obtain plan-specific advice before changing eligibility, contributions, vesting, or administration.
Editorial disclaimer: This educational article is not tax, legal, actuarial, investment, or ERISA advice. Retirement-plan rules and document terms are fact-specific; consult qualified ERISA counsel, a tax adviser, and the plan’s administrator before acting.
References
- [1] IRS, 401(k) plan overview. https://www.irs.gov/retirement-plans/plan-participant-employee/retirement-topics-vesting
- [2] IRS, retirement topics: vesting. https://www.dol.gov/sites/dolgov/files/ebsa/about-ebsa/our-activities/resource-center/publications/401k-plans-for-small-businesses.pdf
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: Employer Match Cost Calculator.
Continue learning
Rehired Employees: Recheck Service and Eligibility Before Payroll Restart
When an employee is rehired, do not treat the return as automatically requiring either immediate participation or a completely new eligibility wait. Compare the employee’s prior service, break period, former participation status, current eligible classification, and the plan’s stated rehire rules before determining the payroll enrollment and employer-contribution treatment.
Records and controls to review
Retain original hire and termination dates, rehire date, hours-of-service or elapsed-time records, prior eligibility and entry-date determinations, break-in-service calculations, former account and distribution information, and the plan provisions used. A standardized rehire checklist can document which service was credited, temporarily held out, or disregarded under the applicable document terms.
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.
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: The result can differ by plan document, service-crediting method, and the employee’s history. A one-year break may be measured through a defined computation period rather than simply by calendar dates, and special statutory reemployment protections may require separate analysis. Administrators should apply the adopted provisions consistently and obtain advice when the personnel history is unusual.
Reference
- Official source: https://www.irs.gov/pub/irs-tege/dclrm1017.pdf