Back to blog

Former Employees in a Defined Benefit Plan: Records to Review

Reconcile departures, rehires, and unresolved participant records before using a smaller current payroll roster in a defined benefit plan review.

Woman reviewing retirement plan documents at a desk

Staff turnover changes the facts behind a defined benefit plan review, but a departure does not automatically close the person's plan record. Reconcile the current payroll roster with historical employment and participant records, then ask the administrator to confirm each former employee's status. A smaller active workforce alone cannot establish that benefit questions or administration work have disappeared.

For an established owner practice, the useful deliverable is a departure reconciliation with a dated change log. Our staff census guide explains how service and pay records support the initial review. Here, the focus is keeping former employees visible after they leave payroll.

Separate employment status from plan status

A payroll system may label someone inactive because employment ended. That label describes the employment record. Ask the administrator what participation history, benefit determination, payment evidence, communications, or reporting questions remain under the actual plan.

Avoid assuming that a short employment period means no benefit, that a payment request means payment was completed, or that an old statement remains current. Have the administrator interpret the governing documents and history, including any rehire. Record the conclusion and its supporting document rather than selecting a convenient label yourself.

The IRS retirement plan records guide identifies census data, compensation information, participant statements, and notices among records to retain. Keep the source history available while the professionals resolve the status.

Build a roster that explains every departure

Start with the last submitted census and the administrator's participant listing. Compare both with payroll employment changes for the review period. Add earlier unresolved former employees even if they received no current-year wages. Use a stable person identifier to connect records across payroll providers.

For each departure, collect original employment date, separation date, employing entity, relevant pay and service support, last known contact details, and the location of plan correspondence. Identify missing periods and conflicting dates. Use a secure transfer method for personal information; employee codes are enough for the owner's summary.

Keep three fields separate: employment event, administrator-confirmed plan status, and next action. A row might say “separated September 18; status awaiting review; obtain earlier service record.” That is more useful than “inactive,” because it names the uncertainty and the person responsible for resolving it.

Hypothetical: the current payroll screen misses four people

Original invented reconciliation: A professional practice begins the year with eight employees, excluding the owner. Three leave during the year, and two new employees join. The closing active roster is seven: 8 minus 3 plus 2. The three departures remain in the year's employment history, giving ten unique employees who worked during the year.

The administrator's prior file also lists one former employee who left before this year and whose benefit status still needs confirmation. The review packet therefore contains eleven distinct people: seven currently active, three departed this year, and one earlier unresolved record. These categories organize records only; eleven is not a count of participants, covered employees, or people owed benefits.

Record groupPeopleReview action
Currently employed7Confirm current records and identify new hires
Departed during the year3Reconcile separation dates and request status review
Earlier unresolved former employee1Locate the outstanding determination and correspondence
Total distinct people in packet11Ask administrator to reconcile to plan records

The difference between eleven review records and seven active employees is four people. Removing those four from the packet would remove the very questions the administrator needs to resolve. Conversely, retaining a record does not assert that the person has an unpaid benefit. Let the documented review establish that answer.

Use a change log that survives the next handoff

Continue the hypothetical with employee E04. Version one records an August 31 separation from an office spreadsheet. Payroll confirms September 18 from the final employment record. Version two preserves the original entry, records the corrected date, identifies the payroll evidence, and asks the administrator whether the correction affects its work.

Employee E09 requested benefit information, but the practice cannot find a response. Log the request date, the missing document, the administrator contact, and the next follow-up date. Do not mark the row “paid” because the person left or sent a request. Close the issue only when the responsible professional identifies the appropriate completion evidence.

Our plan administration continuity guide addresses access and provider handoffs. The same discipline helps when a practice manager leaves: a successor should be able to understand each unresolved departure without reconstructing an inbox.

Address stale contact information before it becomes a search project

For plans subject to ERISA, DOL's missing participant best practices discuss keeping contact information current, correcting census errors, and documenting actions. Treat this as guidance to discuss with the fiduciary and administrator, rather than a universal checklist that settles every plan's duties.

Flag returned mail, unanswered communications, and inconsistent addresses. Ask who maintains contact information after employment ends and who follows up. If someone cannot be located, obtain the administrator's instructions for the particular circumstances and retain a record of the steps taken.

PBGC's Missing Participants Program concerns eligible plans that terminate. It is not an automatic destination for every departing employee in an ongoing plan. If termination is being considered, have the professionals determine program applicability and the required process.

Make the next plan review reproducible

Send the reconciled roster, supporting records, open issues, and change log together. Ask the administrator to acknowledge the version used and identify conclusions still pending. Ask whether the corrected population changes any illustration, valuation input, communication, or administrative task before relying on the next plan review.

TaxBowl's tax team can reconcile payroll and accounting records and coordinate the open questions with your plan professionals. Bring the last submitted census and current departure list so the meeting starts with explainable changes and assigned follow-up.