When someone leaves mid-year and the plan applies a profit-sharing last-day requirement, the sponsor has to decide whether that person gets an allocation at all. It looks like a simple yes or no, but the answer lives in the plan document, depends on facts only the employer holds, and can ripple into nondiscrimination testing. This post is about allocation conditions, not entry eligibility. If your question is when someone first joins the plan, start with our guide on 401(k) eligibility and entry dates. Here we assume the person is already a participant and the question is whether they share in this year’s employer contribution.
1. What a Last-Day Requirement Is and Why It Is Fiduciary, Not Clerical
An allocation condition is a rule in the plan document that says a participant must satisfy something, such as being employed on the last day of the plan year or completing a minimum amount of service, to receive a share of the employer contribution. Participants who miss the condition are simply not allocated a share. It is a legitimate plan design feature, but it is only valid if the document says so and the plan is operated exactly that way.
That is why this is a fiduciary matter. Someone has to read the document, apply it to each person, and be able to show their work. Getting it wrong in either direction creates a failure: excluding someone who was owed an allocation, or paying someone the document says should not receive one. For the broader framework, see our overview of profit-sharing plans.
2. How Last-Day Exclusions Go Wrong
- The plan document has no last-day condition, but the employer has been applying one by habit or by recordkeeper default.
- The condition applies to one contribution source but was applied to all of them.
- The document carves out certain terminations, and nobody checked whether this employee qualified.
- The employer’s census shows the wrong termination date or the wrong status, so the person was excluded on bad data.
- The exclusion was never tested, and it quietly pushed the plan out of compliance.
Several of these are the same document-versus-practice problem we cover in plan document, operations and notices mismatches.
3. What Sponsors Verify in the Plan Document
1. Whether a condition exists at all
Read the profit-sharing allocation section itself, not the summary. If the document is silent, there is no condition and everyone who otherwise qualifies shares in the contribution.
2. Which contribution sources it covers
Documents often treat discretionary profit sharing, employer match and safe harbor contributions differently. A last-day rule that is permitted for one may not be permitted for another. If you run a safe harbor design, review safe harbor sponsor commitments before assuming the same rule applies.
3. Any exceptions written into the document
Many documents waive the condition for retirement, disability or death during the year. Others require a minimum amount of service during the year as an alternative to the last-day test. Confirm whether the employee falls into an exception before excluding them.
4. How the condition interacts with plan termination or partial termination
If the plan is ending or a layoff is large, special vesting rules can override the document’s normal conditions. See plan termination and partial termination and our post on 401(k) partial termination after layoffs.
4. What Sponsors Verify in the Employer Data
1. The actual termination date
Payroll, HR and the recordkeeper often disagree. The date that controls is the one that matches the document’s definition of employment, and it needs to be provable.
2. Employment status and any breaks in service
A rehired employee, someone on approved leave, or a person whose status was reclassified may still be treated as employed on the last day. Our guides on rehires and breaks in service and worker reclassification cover how those facts change the answer.
3. Military leave and protected absences
Certain protected leave must be treated as continued employment for allocation purposes. If the employee was on military leave, review USERRA make-up contributions before finalizing the exclusion.
4. Hours or service credited during the year
If the document uses a service alternative, someone has to pull the hours records and confirm the count. Do not rely on an estimate.
5. Compensation that counts for the allocation
Even for employees who are allocated a share, the compensation definition drives the result. A wrong definition creates its own failure, as we explain in 401(k) compensation definition errors.
5. The Testing Check Before You Finalize
Excluding people who left during the year can change who actually receives a contribution. Because last-day rules tend to exclude shorter-tenured and lower-paid employees, they can cause trouble in coverage and nondiscrimination testing, and they can affect top-heavy status. Run the numbers with the exclusions applied before the allocation is final, not after. Our posts on nondiscrimination testing, top-heavy plans and coverage testing walk through what to model.
6. Eight-Step Self-Check Before You Exclude Anyone
- Pull the current plan document and every amendment, and locate the allocation conditions.
- Confirm the condition applies to the specific contribution source being allocated.
- Check for exceptions such as retirement, disability, death or a service alternative.
- Verify the termination date against HR and payroll records, and note any disagreement.
- Check for leave, rehire, reclassification or other status facts that change employment on the last day.
- Run testing with the exclusion applied and without it, and compare.
- Document the decision, the document language relied on and the data used.
- Retain the file and record the decision in the committee minutes. See plan committee meeting minutes.
7. Where Sponsors Get Hurt, and What You Can and Cannot Delegate
- Relying on the recordkeeper’s default settings instead of the signed document.
- Excluding a participant who was owed an allocation and discovering it years later at audit.
- Giving an allocation to someone the document excluded, creating an operational error that needs correction.
- Having no written record of why anyone was excluded.
If you find that an exclusion was wrong, the fix is a correction, not a quiet adjustment. Start with our guide to administrative error correction, and see 401(k) forfeiture accounts if funds were parked or reallocated along the way.
On who owns what: whether the plan has a last-day requirement at all, or whether to amend it, is a settlor decision that belongs to the employer. Applying the condition correctly each year, with accurate data and written support, is a fiduciary implementation task. The employer must supply the facts only it holds, such as termination dates, leave status and hours. Everything else can sit with a 3(16) plan administrator. Learn how that works on our 3(16) plan administration page.
The Named-Fiduciary Close
Allocation decisions are exactly the sort of recurring judgment call that creates liability when it lives in one person’s inbox. Admin316 takes on the work as 3(16) plan administrator, and we also accept formal appointment as your plan’s ERISA 402(a) named fiduciary, a role most providers decline. That puts a documented process and a responsible party behind every allocation decision. Read more on our 402(a) fiduciary services page, then book a call with Admin316 to review your last-day rule and your allocation process.
