If your business has ever had a part-time cashier, a seasonal warehouse worker, or an hourly assistant who quietly logged more hours than anyone realized, you may already have an employee entitled to join your 401(k) plan — whether or not your plan documents say so.
That's the practical bite of the SECURE 2.0 long-term part-time (LTPT) employee rule. It sounds like a niche retirement-plan technicality, but the IRS's finalized guidance turns it into an operational problem: if you sponsor a 401(k) and employ anyone on a part-time, seasonal, or variable-hour basis, you now need a system that tracks individual employee hours year over year and flags eligibility automatically. Get it wrong, and the fix isn't a warning letter — it's a retroactive correction involving missed deferral opportunities, potential excise taxes, and an uncomfortable conversation with your plan's auditor.
Here's what changed, who it affects, and the exact tracking system a small business needs to stay compliant.
What the Long-Term Part-Time Rule Actually Requires
Before 2019, employers could lawfully exclude any employee working under 1,000 hours a year from 401(k) participation indefinitely. A barista working 18 hours a week, year after year, could be frozen out of the retirement plan forever — legally.
The original SECURE Act closed that gap by creating a new eligibility path: an employee who works at least 500 hours in three consecutive 12-month periods must be allowed to make elective deferrals into the 401(k), even if the plan's normal eligibility rule requires 1,000 hours. SECURE 2.0 then shortened that window from three years to two, meaningfully accelerating when part-time staff become eligible.
The mechanics, once you strip out the jargon:
- Hours threshold: at least 500 hours of service in each of two consecutive 12-month periods.
- Age requirement: the employee must be at least 21 by the end of the second qualifying period.
- What they're entitled to: the right to make their own elective salary-deferral contributions. That's it.
- What you don't owe them: employer matching or profit-sharing contributions are not required for LTPT employees, and you can generally exclude them from ADP/ACP nondiscrimination testing and top-heavy minimum contribution requirements.
- Once in, always in: after an employee qualifies as LTPT and enters the plan, the eligibility "locks in" — you cannot make them requalify after a break in service the way you might for other rehires.
The IRS's final regulations also settled a point that tripped up a lot of plan sponsors during the proposed-rule era: vesting. Every 12-month period (going back to January 1, 2021, when the hour-counting clock started under the original SECURE Act) in which an LTPT employee logs 500+ hours must count as a year of vesting service. And once an employee has been credited on that 500-hour vesting schedule as an LTPT participant, it sticks — even if they're later promoted to full-time and would otherwise fall under your plan's standard 1,000-hour vesting computation.
A Small Business Example
Say a 22-employee retail shop runs a 401(k) with a standard 1,000-hour annual eligibility requirement. Maria works the sales floor part-time, roughly 15 hours a week, and has done so continuously since early 2023. By the end of 2023 she logged 620 hours; by the end of 2024, another 640. She's never hit the plan's 1,000-hour threshold, so nobody flagged her for enrollment — and under the old rules, that would have been the end of it.
But Maria has now completed two consecutive 12-month periods with 500+ hours each, and she's over 21. Under the LTPT rule, she became eligible to start deferring into the 401(k) as of the 2025 plan year, whether or not anyone at the shop noticed. If the business didn't offer her that opportunity, it now owes a missed-deferral correction — even though Maria herself never asked to join the plan and may not have known she was eligible either. The failure isn't about intent; it's about not having a system that would have caught her hours crossing the threshold in real time.
Why This Catches Small Businesses Off Guard
Large employers with dedicated HR and benefits teams built LTPT tracking into their HRIS the moment the proposed regulations came out. Small and mid-size businesses — the ones most likely to run payroll through a generalist bookkeeper or a part-time HR contractor — are the ones most likely to miss it, for a few predictable reasons:
Part-time hours aren't watched the way full-time hours are. Most payroll systems flag full-time status changes (for ACA purposes, for example) but don't automatically track a rolling two-year hours history for every part-time worker against a 500-hour threshold.
Seasonal and gig-adjacent staffing hides the pattern. A retail store that brings back the same part-time staff every holiday season, or a landscaping company that rehires the same seasonal crew every spring, can easily accumulate two consecutive 500-hour years without anyone connecting the dots across calendar years.
Turnover masks eligibility. If a part-time employee leaves and is rehired within the same measurement structure, the "once eligible, always eligible" rule can apply retroactively in ways that are easy to miss if your system treats a rehire as a brand-new employee.
The compliance deadline snuck up quietly. Because the rule phased in gradually — three years under the original SECURE Act, then two years under SECURE 2.0, with the IRS granting transition relief and pushing back formal effective dates along the way — many small business owners assumed "the final rule isn't out yet" meant "I don't need to do anything yet." In practice, operational compliance has been expected since plan years beginning in 2024–2025, well before the formal plan-amendment deadline.
Building a Tracking System That Actually Catches This
The core requirement is simple to state and easy to get wrong in practice: for every part-time or variable-hour employee, you need a rolling two-year hours-of-service history that your plan administrator or payroll provider checks automatically, not manually once a year during open enrollment.
A workable process looks like this:
1. Identify who's in scope
Pull a list of every employee who has ever worked under your plan's standard eligibility threshold (typically 1,000 hours/year). This includes anyone classified as part-time, seasonal, on-call, or per diem — job title doesn't matter, actual hours worked does.
2. Reconstruct hours history back to the relevant computation period
For 401(k) plans, the measurement clock for LTPT purposes started with 12-month periods beginning on or after January 1, 2021. If you haven't already, you need historical hours data for every in-scope employee going back to whichever computation periods your plan uses. This is where messy or inconsistent payroll recordkeeping becomes expensive — you can't apply a rule that depends on 2021–2024 hours if nobody preserved that data in a queryable form.
3. Set an automated 500-hour flag
Whatever system runs your payroll — whether that's a dedicated HRIS, your plan recordkeeper's portal, or a spreadsheet a bookkeeper maintains by hand — needs a recurring check that flags any employee who crosses 500 hours in a 12-month computation period, and cross-references whether this is their first or second consecutive qualifying period.
4. Coordinate with your plan recordkeeper before the deadline hits
Most third-party administrators and recordkeepers now offer LTPT tracking as part of standard plan administration, but only if you've told them which employees are in scope. Don't assume this is happening automatically in the background — confirm it in writing, and ask for a report showing who's approaching eligibility this plan year.
5. Document the exclusion basis for anyone kept out of testing
Since LTPT employees can be excluded from ADP/ACP and top-heavy testing, your plan's compliance file should clearly document which employees were excluded and why, so a future audit or IRS inquiry doesn't turn into a scramble to reconstruct the logic after the fact.
What Happens If You Miss It
Failing to offer eligible LTPT employees the chance to defer isn't a paperwork violation you can quietly fix going forward — it's typically treated as an operational plan failure. Under the IRS's correction programs, that usually means calculating a "missed deferral opportunity" for the affected employee (often a percentage of what they would have contributed, funded by the employer), plus potential excise tax exposure and the administrative cost of a formal correction filing. For a business with a handful of long-tenured part-time staff, that's a real, unbudgeted liability — and one that only grows the longer it goes undetected.
Common Questions Employers Ask
Does this apply if my business doesn't offer a 401(k) at all? No — the LTPT rule only applies to employers that already sponsor a 401(k) or ERISA-covered 403(b) plan. If you don't sponsor a plan, there's nothing to track.
Do LTPT employees count toward my plan's total participant count for Form 5500 filing purposes? Generally yes, once they've entered the plan as participants, which can push a small plan past filing thresholds it previously avoided — one more reason to catch eligibility early rather than discover it at audit time.
Can I just lower my plan's standard eligibility requirement to 500 hours for everyone, instead of tracking LTPT separately? Some employers do exactly this to simplify administration, since it makes the two-tier tracking irrelevant. It's a legitimate option, but it also changes your matching and testing obligations for a wider group of employees, so model the cost before assuming it's the simpler path.
What about union employees or employees covered by a collective bargaining agreement? The LTPT rules generally don't apply to employees covered under a collective bargaining agreement where retirement benefits were the subject of good-faith bargaining — check your plan document and CBA language before assuming an exclusion applies.
The Bookkeeping Angle Most Employers Miss
This rule is fundamentally a data problem before it's a legal one. The IRS doesn't care how you track hours — it cares that you can produce an accurate, defensible hours-of-service history for every part-time employee, on demand, going back multiple years. That's much easier when your payroll and financial records are clean, consistent, and auditable from day one, rather than reconstructed under deadline pressure from a patchwork of old timesheets and pay stubs.
Whether you're tracking employee hours, matching contribution accruals, or the payroll liability accounts your 401(k) deferrals flow through, the underlying discipline is the same one that makes any compliance requirement manageable: records you can trust and query, not records you have to reconstruct.
Keep Your Records Ready Before the Auditor — or the IRS — Asks
Retirement plan compliance is just one more place where clean, well-organized books pay off long before anyone asks to see them. Beancount.io offers plain-text accounting that gives you complete transparency and version-controlled history over your financial data — no black boxes, no vendor lock-in, and no scrambling to reconstruct years of records under deadline pressure. Get started for free and see why developers and finance professionals are switching to plain-text accounting.