The owner of a San Diego seafood restaurant got the certified letter on a Tuesday. A former dishwasher who’d left three months earlier had filed a PAGA claim – California’s Private Attorneys General Act, alleging the wage statements he received during his employment were “missing required information” under Labor Code §226. The owner read it twice and called his lawyer. The lawsuit had nothing to do with unpaid wages. The kitchen had paid the dishwasher every dollar he was owed, including overtime and meal premiums. The issue was the format of the pay stub.
The defects were technical. The pay stub showed the inclusive pay period dates, but written as “5/01-5/14” instead of “May 1, 2024 to May 14, 2024.” It showed the SSN in full instead of the last four digits. The employer’s legal name appeared as “Pacific Coast Seafood LLC” on the stub but as “Pacific Coast Seafood Restaurant, LLC” on the company’s articles of incorporation. None of these had cost the dishwasher a cent of actual wages. All of them constituted §226 violations. The settlement, after mediation, was $47,000, plus the worker’s attorney’s fees on top.
This is the California reality every operator needs to internalize before opening a paycheck program in this state. Labor Code §226 lists nine items every itemized wage statement must contain. Get one wrong, and PAGA gives the worker standing to sue on behalf of all “aggrieved employees”, which, in legal practice, means every employee in your company over the past four years. The base statutory penalty is up to $250 per pay period for the initial violation and $1,000 per pay period for each subsequent violation. For a thirty-person team paid biweekly, an honest formatting mistake that recurs over a year carries seven-figure potential exposure. Plaintiff’s lawyers know this. So do their litigation funders.
Map your last four years of pay stubs against GPS clock-ins on one real pay period before the next PAGA letter lands.
No credit card, up and running in 2 minutes.
Open your trialThe nine §226 items and where time tracking carries the weight
The nine items §226(a) requires on every wage statement are: gross wages earned, total hours worked (for non-exempt employees), the number of piece-rate units earned, all deductions itemized, net wages earned, the inclusive dates of the pay period, the employee’s name and last four of SSN, the employer’s name and address, and all applicable hourly rates with the corresponding hours worked at each rate. Four of these nine depend directly on time tracking data: total hours worked, applicable hourly rates and corresponding hours, net wages earned (which derives from hours × rate), and the inclusive pay period dates.
If your time records are paper-based and reconstructed manually for payroll, any discrepancy between the underlying time records and the resulting wage statement becomes a §226 claim waiting to happen. A worker who notices that the stub says “80 hours regular” but his memory and his text messages say “82 hours regular” doesn’t need to prove the difference financially, he needs only to prove the wage statement was inaccurate. A GPS clock-in produces a record that can be cross-checked: the worker physically had to be at the location to register. When the wage statement says “8 hours at $25 regular, 2 hours at $37.50 overtime,” the underlying GPS log shows precisely where and when those hours were accumulated. PAGA plaintiffs can no longer argue the hours were estimated or rounded; the evidence is timestamped and geocoded down to the second.
Daily overtime: the California twist that catches everyone
Federal FLSA calculates overtime only on a weekly basis: over 40 hours in the workweek. California calculates overtime daily as well. Over 8 hours in any single workday is 1.5x. Over 12 hours in a single workday is 2x, straight double-time. Working seven consecutive days triggers 1.5x for the first 8 hours of the seventh day and 2x for anything beyond. There are exceptions for alternative workweek schedules properly authorized through employee election, but they’re narrow and rarely applicable in field service or restaurant operations.
This is mathematically unforgiving when time records are imprecise. A field crew that rounded a 7-hour-45-minute shift up to 8 hours hasn’t done anyone a favor, they’ve triggered the daily overtime threshold on paper. If the next day the same worker put in 8.25 hours and got paid straight time for it (because the foreman didn’t realize they’d already crossed daily 8 the previous shift was an unusual one), the company now owes back wages plus penalties on the second day. Multiply by the number of times rounding error compounds across a year, and you’ve manufactured your own PAGA case.
The legal protection is precision: GPS clock-ins are timestamped to the second. The system computes daily and weekly thresholds independently and applies the correct premium automatically, no rounding rules, no foreman judgment calls, no inherited spreadsheet bugs. Your wage statement reflects what the system calculated; the time records show how the system got there. PAGA discovery doesn’t break the chain because the chain is mathematical, not human.
