Decide which system is the record of hours worked and paid, how non-hourly staff are counted, and how paid leave flows in.
Payroll is usually the record. Scheduling and time clocks feed it and are reconciled to it.
Choose actual hours, days-worked or weeks-worked for each classification, and test it against actual hours.
Make sure paid time off and holiday hours are included in the feed.
Sources: 26 CFR § 54.4980H-3. General information, not legal advice.
An employer’s benefits platform imports hours from payroll but leaves out paid time off, so employees with long vacations appear to average fewer hours.
Adding the paid-leave codes to the feed raises several employees above 30 hours a week and moves them into the full-time group. The fix is made before the window closes.
Name payroll the source.
Include worked and paid-leave codes.
Compare a sample against pay stubs.
Refresh the feed regularly.
Where it goes wrong. Importing only worked hours and omitting paid leave.
Many can, through payroll integrations. Check how the integration handles leave and rehires.
Consolidate the data in one place before the window closes.
Payroll, with benefits as the reviewer.
Many can through payroll integrations. Check how leave and rehires are handled.
Freeze a copy at close and document corrections.
Plan-specific questions belong with ERISA counsel, and we will bring them in.
Check halfway through that hours are landing in the right employee records and that new hires are in the right measurement group.
Total the hours, classify each employee, notify and enroll them inside the administrative period, and keep prior-period coverage running meanwhile.
Every rule, example and source behind this page, in one place.
We help you choose the design, document it and reconcile the hours before the numbers reach your reporting.
An independent employee benefits consulting firm. We look at the entire benefits program — cost, plan performance, risk and administration.
Switch to CFH. Unhappy with your broker? Your employees won’t notice. You will. →
We use cookies to keep the site working properly and to understand how it is used. You can decline anything that is not essential. See our Privacy Policy for the detail.