Tracking 401(k) Eligibility Hours for Employees Who Aren’t Paid Hourly

A driver paid by the load doesn’t generate hours. Neither does a salaried manager, in most payroll systems. Both still need hours for the retirement plan.

That’s the mismatch. Plan eligibility and vesting are measured in hours of service, but a lot of real compensation isn’t. When payroll has no hours to send, somebody makes a number up. Not maliciously, and often with the administrator’s blessing, but 401(k) eligibility hours end up being an estimate rather than a record.

Last updated: September 2026

A thousand hours, assigned once a year

A fuel and convenience retailer pays its drivers by the load. Units, not hours. Their plan defines a year of service as 1,000 hours in twelve consecutive months from the date of hire, then switches to the plan year afterward.

So what do they do? Their third-party administrator explained it without embarrassment, because it was a deliberate decision made with the client years ago. At annual accounting, every driver who didn’t terminate during the year gets 1,000 hours entered. The reasoning was that a driver employed and driving all year almost certainly worked at least that many. It gets them into the plan.

His own description of it was honest. It isn’t a true hourly calculation. It’s a guide that lets eligible people participate. That works fine as an annual estimate, and it stops working the moment the plan starts receiving data every payroll instead of once a year.

Salaried employees have the same gap

This isn’t only a driver problem. The same administrator was explicit that hours have to go on salaried people too, because the record keeper needs them for eligibility tracking regardless of how someone is paid.

Plenty of payroll setups carry hours for salaried staff automatically. Plenty don’t. The client above wasn’t sure which category her drivers fell into and had to go and look, which is itself the answer to whether it was being monitored.

Long-term part-time made estimates riskier

Rules introduced under the SECURE Act and expanded by SECURE 2.0 require employers to let certain long-term part-time employees into a 401(k) after consecutive years of limited service. The threshold is measured in hours.

That changes the stakes on estimation considerably. An annual round number is a reasonable proxy for whether a full-time driver cleared 1,000 hours. It’s useless for determining whether a part-time worker crossed a lower threshold in each of several consecutive years, which is exactly the population these rules were written for. Seasonal and part-time heavy employers feel this first.

The IRS overview of 401(k) plans sets out the participation and coverage requirements, and the Employee Benefits Security Administration publishes the fiduciary guidance that sits alongside them. Both assume the employer can evidence hours worked.

Where the hours could come from instead

The interesting thing about most of these businesses is that the underlying data usually exists. It just doesn’t reach payroll in a usable form.

• Route and load records. A logistics operator paying by mileage runs software that calculates totals per employee, then an assistant retypes the results into a spreadsheet and again into payroll. The trip data is there.
• Scheduled shifts. For workers whose pay isn’t hourly but whose attendance is scheduled, scheduled hours are a defensible measure and far better than a flat annual figure.
• Equivalency methods. Plan documents can permit crediting a set number of hours per day, week or period worked. That’s a documented method rather than an informal estimate.
• A default carried on the employee record. If a per-period hours value rides on the profile, it reaches the record keeper every cycle rather than once at year end.

Once a year works until it has to be every payroll

The retailer above hit this precisely. Moving to a live connection with their record keeper meant hours had to be present on every paycheck, not reconstructed each January. Their administrator said it plainly: because the information is going over every payroll, something has to get calculated.

That’s the moment most employers discover the estimate. Not during an audit. During an integration project, when a field that used to be filled in annually by a human suddenly has to be populated automatically.

Keeping time and attendance on the same platform as payroll and tax means hours exist on the employee record whether or not they drive the paycheck, so 401(k) eligibility hours can be reported from something real. Where third-party systems hold the operational data, direct integrations are what get it into payroll without a retyping step in the middle.

Frequently Asked Questions

This guide reflects publicly available product information and independent reviewer data (G2, Capterra, Trustpilot, Yelp, Better Business Bureau, Reddit, Software Advice, GetApp) as of 2026. Feature availability and pricing may vary by plan. Contact each provider for current details.

Disclaimer: Any product roadmap or future plans provided herein are for informational purposes only. They do not represent a commitment to deliver any material, code, feature, or functionality. Plans may change without notification. The development, release and timing of any features or functionality described remain at the sole discretion of Netchex, its affiliates, and partners. Netchex does not give legal, tax, or accounting advice. You are responsible for ensuring your use of Netchex product meets your individual business and compliance requirements.

Print this page