A lot of employers want to let new hires start deferring into the 401(k) right away—it’s good for recruiting, it’s good for employees, and it’s straightforward to communicate. But if the plan is a safe harbor 401(k), and the safe harbor employer contribution doesn’t kick in until the employee reaches the statutory age and service ceiling (age 21 and one year of service), you’ve created a split population where some participants can defer but don’t receive the safe harbor contribution while others can defer and do.
That split has real consequences for testing, for plan administration, and for how your TPA handles year-end compliance—and it introduces a concept that often is misapplied: “otherwise excludable employees.”
The Code says a plan can require up to age 21 and one year of service (1,000 hours in a 12-month period) before letting someone participate—that’s the statutory ceiling. A safe harbor plan can set deferral eligibility lower than that (if they choose to): immediate entry, or after 3 months, or at age 18. But the safe harbor contribution—whether it’s the 3% nonelective, the basic safe harbor match, or an enhanced safe harbor match—only goes to employees who have met the statutory age and service requirements.
The plan doesn’t lose its safe harbor status just because some participants can defer before they’re eligible for the safe harbor contribution, but what this design does create is a disaggregated testing structure: the group that has met the applicable minimum age-and-service conditions can use the safe harbor method, while the earlier-entry group may need separate nondiscrimination testing. For ordinary early-entry employees, that earlier-entry group generally remains subject to ADP testing on their elective deferrals—and potentially ACP testing if the plan has matching or employee after-tax contributions outside the safe harbor that apply to that group. Employees who are eligible solely by reason of the LTPT rules may be treated differently under the statutory LTPT carveout, which is worth its own discussion below.
“Otherwise excludable” is a testing concept—it refers to employees who are participating in the plan but who could have been excluded under the Code’s maximum age-and-service rules. If the plan lets a 19-year-old start deferring on day one, that person is in the plan before they would have satisfied the statutory ceiling of age 21 and one year of service, and they are “otherwise excludable” because the plan is being more generous than it has to be. The IRS gives a way to handle that generosity without wrecking your test results.
Specifically, if the plan document provides for it, the plan can use permissive disaggregation—split the plan into two components, one for the otherwise excludable employees and one for everyone else, and test each group separately. Each component has to pass its own coverage test under Section 410(b), and for the ADP test the plan can either run one test using a special rule or two separate ADP tests. This is a permissive testing method (the plan has to elect it and the plan document needs to support it), and it’s useful because otherwise excludable employees tend to be younger, newer NHCEs who defer at lower rates—they drag down the NHCE average in the ADP test, make it harder for HCEs to pass, and disaggregation solves that problem.
IRS Chief Counsel Advice 201615013 describes three permissible methods for determining when an employee stops being otherwise excludable. The first—and most common—uses the maximum Code waiting period, meaning the employee remains otherwise excludable until the earlier of the first day of the next plan year after they attain age 21 and complete one year of service, or six months after satisfying those requirements (whichever comes first). The second uses the plan’s own entry date after the employee meets the age 21 and one year of service threshold (for example, “first of the month (or quarter) after 1 year of service”), and the third uses actual attainment of age 21 and one year of service with no entry-date buffer —and the plan needs to pick one and apply it consistently.
The common error is treating everyone who can defer but doesn’t yet receive the safe harbor contribution as “otherwise excludable,” which is not what the term means.
Consider a 25-year-old hired 10 months ago who has been deferring since day one but hasn’t completed one year of service yet, so they don’t receive the safe harbor match. This person is otherwise excludable for testing purposes because they haven’t reached the statutory ceiling—so far so good.
Now consider a 30-year-old hired 14 months ago with over 1,000 hours who has also been deferring since day one and has clearly satisfied the age 21 and one year of service requirements (plus the applicable entry date), but the plan requires one full year of service before the safe harbor match kicks in AND the plan only lets people enter on July 1 and January 1 each calendar year. Let’s imagine that this 30 year old was hired on February 1st. This person has satisfied the one year and 1,000 hours requirement but is receiving the safe harbor contribution yet.
Is this person “otherwise excludable”? Generally no—they’ve passed the statutory ceiling, so they’re a regular participant who happens to not yet be eligible for a specific contribution source, and that’s a plan design feature (separate eligibility rules for deferrals versus employer contributions) rather than a testing classification. IRS guidance distinguishes CODA eligibility from employer-contribution eligibility, and the otherwise excludable framework is about the former, not the latter—so if you put this person in the “otherwise excludable” disaggregated group when they don’t belong there, the testing is wrong.
The LTPT (long-term, part-time) rules under SECURE 2.0 add another layer: for plan years beginning on or after January 1, 2025, employees who work at least 500 hours in two consecutive 12-month periods (and meet the age 21 requirement) must be allowed to make elective deferrals even if they haven’t met the plan’s standard one-year-of-service threshold, which puts them into the plan earlier than the plan’s normal eligibility would allow.
LTPT employees get a different testing treatment than ordinary early-entry employees, though. Under Section 401(k)(15), while an employee is eligible to defer solely by reason of the LTPT rules, the employer may elect to exclude that employee from the application of Sections 401(a)(4), 401(k)(3), 401(k)(12), 401(k)(13), 401(m)(2), and 410(b)—in other words, from ADP testing, ACP testing, general nondiscrimination testing, and coverage testing. The plan can also exclude LTPT employees from employer contributions—including safe harbor contributions—without jeopardizing the plan’s safe harbor status, and if the employer makes the election to exclude LTPT employees from testing it must apply across all of those tests (it’s all-or-nothing).
The contrast with the “otherwise excludable” disaggregation framework matters here: ordinary early-entry employees who haven’t reached the statutory ceiling can be separately tested through permissive disaggregation—they’re still tested, just in their own group—while LTPT employees can be excluded from testing entirely if the employer makes that election.
The LTPT exclusion is not permanent, though—once an LTPT employee later satisfies the plan’s regular eligibility conditions (typically one year of service with at least 1,000 hours), the special LTPT rules cease to apply as of the first plan year beginning after the plan year in which they met those conditions. At that point they become a “former LTPT employee,” must be included in all nondiscrimination and coverage testing, and must receive any applicable employer contributions including safe harbor contributions if otherwise eligible. The carveout is a bridge, not a permanent classification.
If the plan document provides for permissive disaggregation—and it should, if you’re running this kind of split-eligibility design—the TPA needs to correctly sort participants into the right testing groups: otherwise excludable employees can be separately tested if the plan uses the special testing methodology, employees who have passed the statutory ceiling go in the main group, and LTPT employees may be excluded from testing entirely if the employer has elected that treatment. The sorting criterion for the “otherwise excludable” question is the statutory age-and-service ceiling, not the safe harbor contribution eligibility date.
Getting this wrong means your ADP test results are off, your coverage test may be off, and if the plan is relying on the safe harbor method to skip testing for the main group, the boundaries of that skip are wrong too—none of these are catastrophic on their own, but they’re the kind of operational error that compounds over time and gets expensive to correct.
Letting new hires defer immediately in a safe harbor 401(k) is a perfectly good plan design—but it creates a disaggregated testing structure, which means some participants may need to be tested separately. “Otherwise excludable” means the employee is in the plan before reaching the statutory ceiling of age 21 and one year of service, and it does not mean “can defer but doesn’t get the safe harbor match yet”—those are two different concepts that need to be applied separately. LTPT employees add a third category, with the option of full exclusion from testing under the Section 401(k)(15) carveout, but that exclusion ends once they meet the plan’s regular eligibility conditions.
If you’re running a split-eligibility safe harbor plan and aren’t sure whether your testing groups are set up correctly, Fellow Travelers can help sort it out.