Wage Counsel Group

The Rounding Rule Trap: Why Most California Timekeeping Systems Are Non-Compliant Without Anyone Noticing

Date Published

If your company still rounds employee time punches to the nearest five, six, or ten minutes, you are running a payroll practice that California courts have been steadily dismantling for over a decade — and most employers have no idea it's happening until a demand letter arrives.

The Old Rule Everyone Still Relies On

For years, employers leaned on See's Candy Shops, Inc. v. Superior Court (2012), which upheld neutral rounding policies as lawful under California law — provided the policy was facially neutral and didn't, over time, shortchange employees for time actually worked. That case is why nearly every off-the-shelf timekeeping system still ships with rounding enabled by default. It felt settled. It isn't anymore.

Two Cases That Quietly Changed the Math

Troester v. Starbucks Corp. (2018). The California Supreme Court held that California's wage and hour statutes have not adopted the federal de minimis doctrine — the rule that lets employers ignore small chunks of uncompensated work time. Starbucks required employees to perform brief closing tasks after clocking out, totaling roughly four to ten minutes a day. The Court rejected the argument that this was too trivial to matter, holding that regularly required off-the-clock work, however brief, must be paid. This isn't the same doctrine as time-punch rounding, but it establishes the same posture the Court has taken across this whole line of cases: California does not treat small increments of unpaid time as immaterial, and employers who assume otherwise are exposed.

Donohue v. AMN Services, LLC (2021). This is the one that should have every employer auditing their system configuration. The Court held that rounding cannot be applied to meal period punches at all — full stop, regardless of neutrality. The employer's system rounded punches to the nearest ten minutes, which meant a 21-minute lunch could round up to a compliant-looking 30-minute lunch on paper. The Court also held that time records showing short, late, or missed meal periods create a rebuttable presumption of a violation — meaning the burden shifts to the employer to prove compliance, not the other way around.

Why This Matters More Than It Looks Like It Does

Most timekeeping systems don't distinguish between shift-time rounding and meal-period rounding. If your system rounds punches uniformly across the board — which is the default configuration in a large share of commercial timekeeping platforms — every rounded meal period is a data point working against you, and it's been quietly accumulating since the day the system was configured. This isn't a policy problem you can fix by updating a handbook. It's a system configuration problem, and it shows up in the punch data whether or not anyone at the company has looked at it.

That's the trap: the exposure isn't in what your policy says. It's in what your system actually does, punch by punch, and that gap is invisible until someone runs the data.

What an Audit Actually Surfaces

A forensic review of punch data doesn't just tell you whether rounding is turned on. It tells you:

  • Whether meal periods are being rounded into apparent compliance
  • How many shortened, late, or missed meal periods exist in the raw (unrounded) data versus what payroll reports show
  • Whether the Donohue rebuttable presumption is currently working against you, and by how much
  • What the exposure looks like extrapolated across the employee population and the statute of limitations period

That last point is usually the number that gets attention. PAGA penalties and unpaid premium wages compound per employee, per pay period, per violation type. A rounding configuration that looks like a minor technical setting can represent a six- or seven-figure exposure across a mid-size workforce once you run it out.

The Practical Move

Turn off meal period rounding. That part isn't optional after Donohue. Beyond that, the only way to know your actual exposure — as opposed to your assumed exposure — is to look at the raw punch data against actual statutory requirements, not against what your timekeeping system's summary report says.

That's the gap our punch report audit is built to close: it takes raw timekeeping exports and identifies where rounding, meal period timing, and premium pay obligations diverge from what's actually being paid — before that gap shows up in a class certification motion instead of a spreadsheet.


David Ehrlich | Licensed, State Bar of California | Wage Counsel Group
Forensic wage and hour analysis for employer-side defense counsel
info@wagecounselgroup.com | (213) 290-2660 | wagecounselgroup.com