VertiSource HR | HRIS and HR Outsourcing

FLSA overtime rules don’t fail in court, they fail at payroll close

Overtime • California

FLSA overtime rules don’t fail in court, they fail at payroll close

March 5, 2026 | 5 min read | By Diane Williams • VertiSource HR

A $409,457 back-wage settlement shows FLSA overtime rules fail at payroll close

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)

Overtime Rules Navigator

Federal baseline, state triggers, and selected local overlays

Updated Mar 8, 2026

Multi-state payroll? We’ll review your setup.

Alabama Alaska Arizona Arkansas California Colorado Connecticut Delaware Florida Georgia Hawaii Idaho Illinois Indiana Iowa Kansas Kentucky Louisiana Maine Maryland Massachusetts Michigan Minnesota Mississippi Missouri Montana Nebraska Nevada New Hampshire New Jersey New Mexico New York North Carolina North Dakota Ohio Oklahoma Oregon Pennsylvania Rhode Island South Carolina South Dakota Tennessee Texas Utah Vermont Virginia Washington West Virginia Wisconsin Wyoming District of Columbia
State-specific OT variations Federal FLSA baseline only

Select a state

Click any state on the map to see federal, state, local, classification, and payroll-system overtime details.

Curated orientation tool. Not legal advice. Verify with primary sources before making payroll decisions.

Operating in multiple states? Let us audit your overtime setup so every jurisdiction pays correctly.

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

1
Straight-time overtime What to look for: 40+ hour weeks with no overtime premium line.
Red flags: overtime hours paid at base rate. (DOL news release)
2
Unpaid hours What to look for: time totals higher than paid hours for the same dates.
Red flags: repeated “rounding” that always reduces paid time. (DOL news release)
3
Records that do not tie What to look for: timesheet totals match payroll records used for overtime math.
Red flags: rerun reports change, or exports are missing. (DOL news release)

Controller Insight

One of the first things we look at 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.

Time-to-payroll tie-out
Payroll Processor
What to look for
Employee-week hours match between time and payroll.
Red flags
Variances “fixed” with no ticket or note.
Overtime premium test
Payroll Processor + reviewer
What to look for
Weeks over 40 show overtime hours and premium dollars.
Red flags
Overtime rate equals base rate.
Edit-log review
Operations manager
What to look for
Edits have reason codes and approvers before export.
Red flags
Bulk edits, or edits after payroll is processed.
Close packet
Controller or HR
What to look for
Saved time export, payroll register, OT detail, dated sign-off together.
Red flags
“We can rerun it later.”
Code mapping check
HR or payroll admin
What to look for
Every time code maps to an earning code.
Red flags
Unmapped codes or growing “misc” pay.

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 2026 COMPS materials recognize overtime after 40 hours in a workweek, 12 hours in a workday, or 12 consecutive hours, whichever results in more pay. (CDLE INFO #1 PDF)

Payroll controls • Time & attendance • Compliance support

How VertiSource HR helps you follow FLSA overtime rules

Overtime errors happen when time records, earning codes, and payroll outputs do not reconcile. VertiSource HR helps tighten those links with payroll-close controls, time-and-attendance support, and multi-state overtime setup guidance.

Built for multi-state payroll accuracy

FLSA-qualified overtime

Under the FLSA, covered nonexempt employees are generally entitled to overtime at 1.5× their regular rate for hours worked beyond 40 in a workweek. The regular rate is broader than base hourly pay. Nondiscretionary bonuses, shift differentials, and certain other forms of compensation may need to be included before the overtime multiplier is applied. When those inputs are missing or miscategorized, the overtime premium can come in lower than it should.

Our payroll engine surfaces the regular-rate calculation and the resulting overtime premium before the batch closes, giving your team a chance to catch discrepancies while they are still correctable.

What this helps address: visibility into weekly overtime premiums at the regular rate before payroll is finalized.

Why multi-state overtime setup gets harder

Federal overtime under the FLSA and state-law premium-pay rules do not always overlap. Some states require daily overtime, consecutive-day premiums, or double-time calculations that sit outside the federal 40-hour workweek framework. The One Big Beautiful Bill Act (OBBBA) increases the importance of separating FLSA-qualified overtime from other state-law overtime or premium pay for reporting and payroll-close control purposes.

Federal FLSA overtime Hours over 40 in a workweek, paid at 1.5× the regular rate under the Fair Labor Standards Act
State-law overtime or double-time premiums Daily, consecutive-day, or other state-specific triggers that may not qualify as FLSA overtime
Why separate earning codes help Distinct codes make it easier to report federal and state overtime correctly, reducing the risk of underpayment under one framework while misreporting under the other

VertiSource HR structures earning codes so that federal and state overtime categories stay separated through payroll close, making reconciliation and reporting cleaner on both sides.

Time & attendance and payroll-close controls

Our time-and-attendance platform captures punches, meal breaks, and shift changes in real time, then maps each record to the correct earning code before payroll import. That connection between T&A and payroll is where most overtime errors either get caught or slip through.

Payroll-close reconciliation Employee-by-workweek comparison of T&A exports against payroll outputs, reviewed before the batch is finalized
Exception reporting Pre-close flags for straight-time overtime, missing punches, and hours-paid shortfalls that could affect compliance
Earning-code mapping review Periodic review of time codes against payroll earning codes to confirm hours are not lost or miscategorized during import
Recordkeeping support Payroll records maintained in a version-stamped, reprintable format to support federal recordkeeping requirements under 29 CFR Part 516

Request a payroll and overtime controls review

FLSA-qualified OT setup • OBBBA review • T&A integration check

We help employers catch overtime setup, coding, and close-process issues before they turn into wage-and-hour problems.

See payroll and compliance support

Frequently Asked Questions

If a nonexempt employee works more than 40 hours in a workweek and those extra hours are paid at the same base rate, that is straight-time overtime. The February 25, 2026 DOL release described this pattern in the Redwood City case. (DOL news release)
You need records that show hours worked and wages paid, and they need to match. In the February 25, 2026 matter, the DOL cited inaccurate payroll records and said discrepancies between timesheets and payroll records affected overtime calculations. (DOL news release)
Yes. Colorado overtime can be triggered by 40 hours in a workweek, 12 hours in a workday, or 12 consecutive hours, whichever results in more pay, under current CDLE guidance. That means a weekly-only overtime check can miss premiums that a day-level report would catch. (CDLE INFO #1 PDF)
Diane Williams, FLSA overtime rules payroll expert at VertiSource HR

Diane Williams

Controller, VertiSource HR

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.

Schedule a Call with Our Team