$409,457 for 32 workers: 5 payroll-to-GL close checks that catch overtime errors early
In This Article
When back wages show up as a labor variance
You run payroll, the direct deposit hits, and a few weeks later your labor line is off and nobody can explain why. When minimum wage or overtime math is wrong, it stops being “just payroll” and turns into a repeat variance that finance has to book, explain, and unwind. Five payroll-to-GL (general ledger) close checks can catch these errors before the journal entry (JE) posts.
Verified Facts
On Feb. 25, 2026, the U.S. Department of Labor (DOL) recovered $409,457 in back wages for 32 workers from a Little Caesars in Redwood City, CA (MG Fast Food Inc.), citing Fair Labor Standards Act (FLSA) minimum-wage, overtime (OT), and recordkeeping violations—including paying straight time for OT hours—from May 2022 to May 2025.
Source: DOL WHD release, Feb. 25, 2026.
The DOL does not recover $409K because someone forgot to run payroll. It happens because the controls that prove hours became the right dollars were never there. Here is the close packet that should sit in front of finance before the payroll JE posts.
5 payroll-to-GL close checks before you run payroll
Close Packet Checks
System Tip
PASS: JE preview ties posted batch, cost centers tie payroll summary, close packet attached.
FAIL: summarized JE with no support, or cost center movement without an approved mapping change.
If one of these payroll-to-GL close checks fails, the root cause almost always lands in one of three breakpoints below.
Where wage and overtime failures break
3 Breakpoints
Multi-State Note
Federal-only overtime settings miss state layers. The gaps usually show up in overtime triggers, pay-statement rules, final-pay timing, and meal/rest enforcement. That’s why our close packet includes a pay-rule audit and effective-dated mapping controls by location.
Controller Insight
When earning codes map to the wrong cost centers, you lose the departmental pattern that would flag a wage gap before it compounds. Fix the mapping and the variance report does the auditing for you.
How VertiSource HR can help
Finance sees dollars by cost center, managers see scheduled hours, and payroll translates time into earning codes and then into the general ledger. When that translation is not documented, the variance conversation turns into guesswork.
We close the gap with a purpose-built HR and payroll platform that keeps timekeeping, payroll rules, and GL mapping in one auditable system.
Here is what we implement so the paper trail is there before close:
- Payroll close packet template with required artifacts (Payroll Register Detail, overtime audit, Timecard Change Log, Payroll JE Preview) and named sign-offs
- Earning code governance with definitions plus a locked GL mapping table with effective dates and an approval workflow
- Timekeeping-to-payroll export controls including cut-off time, export versioning, and an export reconciliation step (hours and dollars) before payroll is finalized
- Exception reporting routed to payroll and finance (overtime hours with no overtime premium, mid-period rate changes, manual checks and voids)
Operations Insight
Timecard edits made after the payroll export are invisible to the pay run. Payroll locks a snapshot at export; any manager corrections after that point create a gap between what timekeeping shows and what employees are paid. An export-reconciliation step before finalization catches the drift.
Get the Payroll-to-GL Close Packet
Close packet, sign-off workflow, GL mapping controls—built for your team.
Schedule a callFrequently 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.
