FLSA overtime rules don’t fail in court, they fail at payroll close
In This Article
A $409,457 back-wage settlement shows FLSA overtime rules fail at payroll close
When FLSA overtime rules are not enforced at the payroll level, a single wage case can start with one store and end with months of rework. On February 25, 2026, the U.S. Department of Labor (DOL) announced a settlement with MG Fast Food Inc. The company operated a Little Caesars in Redwood City, California, and will pay $409,457 in back wages to 32 workers. (DOL news release)
If your time totals, payroll register, and edit logs do not tie out by employee and by workweek, overtime and minimum wage errors can sit quietly until someone forces the math into the open.
Featured Takeaway
$409,457 across 32 workers averages nearly $12,800 per employee ($409,457 ÷ 32), tied to straight-time overtime, unpaid hours, and mismatched records. (DOL news release)
Put the DOL findings into three payroll-close buckets
The DOL’s Wage and Hour Division described three failure modes that show up at close, not in a handbook.
3 Buckets
Controller Insight
One of the first things I reconcile is “hours worked” in timekeeping to “hours paid” in the payroll register, by employee-week. A pay-period total can look fine while a workweek overtime break is wrong, and that flows straight into the general ledger.
This control work is easier when your time and attendance workflow and earning codes in payroll processing are built to produce the same totals. See how VertiSource HR’s automated T&A does this.
Run one control pack each pay period (owners, proof, red flags)
Five controls, five owners. Run each one every pay period and save the proof together.
Store the packet somewhere your team can actually find it next quarter – VertiSource HR can set this up for you. If you are using an HR system, keep the same naming convention every pay period. HR Cloud can help centralize that, but the real win is consistency.
Multi-state note: some states trigger overtime earlier than 40 hours
Federal overtime is time-and-a-half after 40 hours in a workweek for nonexempt employees. Some states add daily or consecutive-hour triggers, which changes what your overtime detail report needs to show.
Compliance Note
Colorado guidance effective February 1, 2026 recognizes overtime after 40 hours in a workweek, 12 hours in a workday, or 12 consecutive hours, whichever results in more pay. (Colorado Department of Labor and Employment INFO #1 PDF)
Operator Insight
Payroll teams pay what the file says. When the edit log is thin, you lose the story of what changed and why, and that is when a small fix turns into a reconstruction project.
Hover over a state to see how its overtime rules compare to the federal 40-hour standard.
Not sure which FLSA overtime rules apply to your workforce?
Multi-state payroll means multi-state compliance. Let VertiSource HR audit your overtime setup across every state you operate in.
Opens our scheduling link
How VertiSource HR helps you follow FLSA overtime rules
Overtime compliance breaks down when time records, earning codes, and payroll outputs live in separate systems that nobody reconciles. VertiSource HR closes those gaps with automated Time & Attendance, purpose-built payroll controls, and a team that understands FLSA math at the field level.
FLSA Qualified Overtime – built into every pay run
Our payroll engine flags FLSA Qualified Overtime automatically: any nonexempt hours beyond 40 in a workweek are calculated at 1.5× the regular rate, including required additions for nondiscretionary bonuses, shift differentials, and piece-rate earnings. You see the premium line before the batch closes, not after an auditor asks for it.
The One Big Beautiful Bill Act – why your overtime math just got harder
The One Big Beautiful Bill Act (OBBBA) changes federal tax brackets, deduction rules, and reporting thresholds that ripple straight into payroll. For multi-state employers, the real headache is this: several states already define their own overtime triggers – daily overtime, consecutive-hour overtime, double-time – that do not qualify as FLSA overtime. After the OBBBA, your payroll system has to track FLSA-qualified overtime (federal, 40-hour workweek, 1.5×) and non-FLSA-qualified overtime and double-time (state-specific rules like California’s daily OT or Colorado’s 12-hour trigger) as separate line items. If those two buckets are not split correctly, you either underpay workers under state law or misreport under the new federal rules. (Regulatory compliance support can help you stay ahead of these changes.) VertiSource HR’s payroll engine keeps FLSA-qualified and state-qualified overtime in separate earning codes so every premium dollar lands in the right bucket at close.
Automated Time & Attendance
VertiSource HR’s automated T&A platform captures clock-ins, meal breaks, and shift changes in real time, then maps every punch to the correct earning code before the payroll import. That eliminates the manual “hours worked vs. hours paid” reconciliation that tripped up the employer in the Redwood City case.
- Payroll-close reconciliation – employee-by-workweek tie-out between T&A exports and the payroll register, with FLSA Qualified OT broken out on every stub
- Exception reporting – automatic flags for straight-time overtime, missing punches, and hours-paid shortfalls before the batch closes
- Earning-code mapping review – we audit your time codes against payroll earning codes so hours never vanish in the import
- Document-retention checklist – every packet is version-stamped, re-printable, and backed by the record-keeping requirements in 29 CFR Part 516
Request a Payroll & Overtime Controls Review
FLSA Qualified OT setup • OBBBA compliance review • T&A integration check
Opens our scheduling link
Frequently Asked Questions
Diane Williams
Diane writes on payroll accounting, audit readiness, and the controls that keep the books clean.
Disclaimer – This content is for general informational purposes only and does not constitute legal, tax, or accounting advice. Consult a qualified attorney or licensed advisor before making employment, payroll, or compliance decisions. VertiSource HR disclaims liability for actions taken based on this material.
