Direct answer
Wage-and-hour audit software for skilled nursing facilities should produce employee-by-employee payroll, daily and weekly hours, overtime support, and meal-period records on demand. Federal FLSA recordkeeping rules set the baseline, and California SNFs add meal-period, written-agreement, and 21-day payroll-record access duties.
Key takeaways
- Federal audit-ready output starts with employee-by-employee hours worked each workday and each workweek, plus payroll fields that explain how pay was calculated.
- California SNFs need more than punches: Wage Order 5 adds meal-period records, split-shift intervals, total daily hours, total payroll-period hours, and applicable rates of pay.
- If a facility uses the federal 14-day 8-and-80 method, the system should preserve the 14-day setup and the agreement or memorandum that supports it.
- Federal law does not require one specific clock, device, or form, but it does require complete and accurate records.
- In California, payroll records requested by a current or former employee must be made available as soon as practicable, but no later than 21 calendar days.
At 4:15 p.m. on payroll-close day, most operators do not need a prettier dashboard. They need the exact record trail behind a missed meal break, a blended-rate overtime question, or a former employee’s payroll-record request. ePeople AI, compliance software for skilled nursing facilities, fits this topic because the labor-law buying question is really a proof question.
What records do federal investigators expect a skilled nursing facility to produce?
Start with the FLSA baseline. Federal recordkeeping rules require employers to keep records that show, among other items, the time and day the workweek begins, hours worked each workday, hours worked each workweek, the basis on which wages are paid, and total wages paid each pay period. The Wage and Hour Division also has authority to inspect records and make transcriptions, so a system has to produce underlying records, not only summaries.
- Hours worked each workday by employee.
- Total hours worked each workweek by employee.
- The time and day of week when the employee’s workweek begins.
- The pay basis and regular hourly rate where required.
- Additions to or deductions from wages and total wages paid each pay period.
- The payment date and pay period covered.
Why is a nursing-home wage-and-hour audit different from a generic timecard export?
Because the dispute usually sits around the shift, not only inside it. DOL’s nursing-care guidance flags work before and after a scheduled shift, work during a scheduled meal period, compensable meetings and training, and overtime errors when hours from more than one department or more than one facility are not combined. In a skilled nursing setting, software should help you reconstruct the day, not merely print a punch list.
What should wage-hour audit software for SNFs be able to produce on demand?
Use the checklist below when comparing tools. The real test is not whether a vendor says the system is compliant. The test is whether the system can produce the exact record, agreement, or calculation a payroll manager, investigator, or employee will ask for next.
Buyer’s checklist: what wage-and-hour audit software for SNFs should produce
| Capability | Why it matters | What to ask the vendor |
|---|---|---|
| Daily and weekly hours by employee | Federal rules require hours worked each workday and each workweek. | Can I export hours by employee, workday, and workweek without rebuilding the file in Excel? |
| Payroll-period totals and pay detail | An audit packet needs wages paid, pay-period coverage, additions, deductions, and rate logic. | Can I trace gross pay back to earnings codes, rates, and payroll-period totals? |
| Meal-period records for California facilities | California Wage Order 5 requires meal-period recording, along with split-shift intervals and total daily hours. | Can the system show missed, short, or late meal periods by employee and pay period? |
| Signed agreements tied to the employee record | California on-duty meal agreements and some meal waivers require written proof, not just punch data. | Where are signed agreements stored, and can I retrieve them by employee? |
| 14-day 8-and-80 support, if used | A facility using the federal 14-day method should preserve the setup and supporting agreement or memorandum. | Does the system retain the 14-day period structure and the related agreement record? |
| One-employee record retrieval | California payroll records requested by a current or former employee must be produced within 21 calendar days. | Can staff produce one employee’s payroll record packet without exporting the whole payroll? |
| Exception-based timekeeping visibility | Federal law does not require one device or form, but the record still must be complete and accurate. | If we use fixed schedules plus exceptions, can I show both the scheduled hours and the exception history? |
| Edit trail and correction history | When time or pay is corrected, the building should be able to explain what changed and when. | Can I see edits to punches, approvals, premiums, and pay codes in a usable audit trail? |
Does federal law require one specific timekeeping device or software format?
No. DOL’s recordkeeping guidance says the FLSA requires no particular form for records. For employees on fixed schedules, the employer may keep a schedule of daily and weekly hours and then record only the exceptions when the employee works more or less than that schedule. That means the buying standard is proof quality and retrieval speed, not whether the vendor uses one mandated clock format.
How long do the federal records need to be kept?
Federal retention is split. Payroll records and certain agreements, including written agreements or memoranda used under section 7(j), generally must be preserved for at least 3 years. Supporting wage-calculation records such as time cards, work and time schedules, and records of additions to or deductions from wages generally should be kept for 2 years. Software should therefore separate storage rules for core payroll history and supporting inputs instead of treating every record the same.
What extra outputs do California skilled nursing facilities need?
California changes the checklist materially. Wage Order 5 covers the health care industry and specifically includes skilled nursing facilities. It requires time records showing when the employee begins and ends each work period, and it adds meal periods, split-shift intervals, total daily hours, total wages paid each payroll period, total payroll-period hours, and applicable rates of pay. Authorized rest periods still must be provided, but Wage Order 5 says they need not be recorded.
Which California meal-break documents should the system store with the time record?
Two written documents matter most. First, an on-duty meal period is permitted only when the nature of the work prevents relief from duty and the parties have a written agreement that can be revoked in writing by the employee at any time. Second, in health care, employees working shifts over 8 total hours in a workday may waive one of two meal periods only by written agreement. If the building cannot pull those documents, the punch record is incomplete.
The pay consequence is also direct. Wage Order 5 requires 1 hour of pay at the employee’s regular rate of compensation for each workday a compliant meal period is not provided. A system that only stores punches but does not connect the exception to the premium question leaves the payroll team doing the risk review by hand.
How fast should the software retrieve payroll records for one employee?
In California, a current or former employee can request payroll records, and the employer must comply as soon as practicable but no later than 21 calendar days. There is also a potential $750 penalty for noncompliance. That is why one-employee retrieval matters. A system that can only dump full-payroll files creates manual work right where the deadline is shortest.
What if the facility uses the federal 8-and-80 overtime method?
If a skilled nursing operator uses the federal 14-day method under section 7(j), the system should preserve the 14-day work period, daily hours, total hours in the 14-day period, straight-time wages, overtime excess compensation, and a copy of the agreement or a memorandum summarizing an oral understanding. The special calculation is not enough by itself. The record behind the calculation matters too.
What does a manual scramble look like in practice?
Example: a 120-bed building has 3 employees with disputed meal premiums, 2 CNAs whose hours were split across departments, and 1 former employee requesting payroll records. That is 6 separate proof packets. If each packet takes 30 minutes to rebuild, the payroll team loses 3 hours before anyone decides whether the pay was right. The numbers in this example are invented, but the workflow problem is the real one software should remove.
Where does ePeople fit if the time system already exists?
For most operators, the question is not whether software replaces the clock. The question is whether software closes the gap between time records, payroll rules, and proof. ePeople calculates premium pay owed, including missed meal breaks, shift differentials and blended rates.
What changes when software does this work well is straightforward. Payroll stops reconstructing the same missed-meal, differential, and blended-rate questions after the fact. The building gets a cleaner handoff from timekeeping to payroll, and a faster response when an employee, manager, or investigator asks for the record packet.
Buy for record production, not for vendor adjectives. In a wage-and-hour review, the winning system is the one that can show the hours, the rate, the premium, and the signed document behind them.
