PAGA gets the headlines. §226 wage statement penalties get the recovery. A reframe of California wage-and-hour exposure as a stacked recovery, not a single penalty.
The first thing a California wage-and-hour plaintiff's firm looks at is the wage statement. Not the time records. Not the policy handbook. Not the employee count. The wage statement.
There's a reason. Labor Code §226 lists nine specific items that every itemized wage statement must include, including the employee's full name, the employer's name, the pay-period dates, gross wages, hours, hourly rate, deductions, net wages, and the basis on which all of this is computed. If any of the nine is missing, ambiguous, or wrong, the employer is exposed to $50 for the first violation and $100 for each subsequent violation, per employee, capped at $4,000 per employee, plus attorneys' fees and costs under §226(e). On a 200-person workforce with a 26-pay-period year, the cap math alone exposes the employer to $800,000 per year, before §226 attorneys' fees are layered on.
PAGA gets the press because PAGA scales: any aggrieved employee can bring civil penalties on behalf of all others, the multiplier is brutal, and the LWDA gets a 65% cut post-2024. But the dollars that get paid out in a typical California wage-and-hour matter sit in three places:
The PAGA layer is the multiplier. The §226 layer is the floor. The underlying wage recovery is the body of the claim. A demand letter that reads as a PAGA case is almost always a §226 case with a PAGA wrapper.
This post is about the §226 layer specifically — what it looks like, why it's the most predictable line item in a defense, and what makes it survive scrutiny.
Section 226(a) lists the nine itemized items every wage statement must include. Item-by-item, the practical failure points:
Each item is a discrete check. The plaintiff's bar processes wage statements like a checklist: pull the statement, verify each of the nine items, flag the defects. A defect is a violation. A violation per employee per pay period accumulates against the cap.
A §226 claim has three properties that make it the most attractive entry point for a plaintiff's firm:
It is documentary. The claim doesn't require depositions, witness recollection, or any factual development beyond reading the pay stub. The wage statement either includes the nine items correctly or it doesn't. The evidence is in hand at the moment of filing.
It doesn't require proof of injury. Under §226(e), a "knowing and intentional" violation creates a presumption of injury once the employee establishes the defect. The employee doesn't have to prove they suffered actual harm. The defect is the harm.
It is per-period and per-employee. Every pay period multiplies the count. Every employee multiplies the count. On a 26-pay-period schedule, three hundred employees, and a single recurring defect across the year, the per-employee count crosses the $4,000 cap inside a year. The plaintiff's firm doesn't need to find a different defect on each statement; the same defect repeated is enough.
These properties mean §226 is the layer that pays the bills in most wage-and-hour matters. PAGA is the multiplier and the fee-shifting hook. §226 is the dollars-to-employees floor.
Two things, in order of priority:
The wage statement itself has to be complete and correct. This is not MicroForensics work — it's payroll work. The HRIS or payroll provider has to produce a statement that includes the nine items. Most modern providers — Gusto, ADP, Paylocity, QuickBooks Payroll — do this correctly by default. Older systems and custom payroll setups fail more often than people expect.
The supporting record has to reconcile. This is where attestation matters. If the wage statement claims 40 hours at $25, the time record has to show 40 hours, and the attestation has to confirm the employee saw and agreed to the 40-hour figure as it appeared in payroll. A clean wage statement that doesn't reconcile against the time record and the per-period attestation is exposed on a different theory — the records are inaccurate, which feeds §226 and §1174 and the Donohue presumption.
The per-pay-period attestation that defeats Donohue is the same instrument that reconciles the §226 statement. When the employee signs the attestation, they confirm both that the breaks were taken as recorded and that the hours and pay align with their understanding. The single artifact does double duty.
MicroForensics produces the per-period attestation that reconciles the wage statement against the time record. It does not produce the wage statement itself — that remains the payroll provider's job. The orchestration is at the boundary: the employee sees the wage statement, reviews the time record alongside it, attests to both in the same flow, and signs.
A defense built on this architecture covers §226, §226.7, and PAGA penalties on the same record. The 15% PAGA cap conversation in §2699 turns on whether reasonable steps were documented; the §226 reconciliation is one of the steps the LWDA's proposed regulations explicitly contemplate. The two layers point at the same evidence. Built once, they defend together.
A PAGA notice is the moment of crisis, but it isn't the moment the dollars are being calculated. The dollars are being calculated against your wage statements, which were produced months or years ago, and which the plaintiff's firm pulled before they ever drafted the notice.
The work, if you haven't done it: pull your last twelve wage statements and check each one against the nine §226 items. Anything missing or ambiguous is a violation per period per employee. The math compounds from there.
If you'd like a walkthrough against your actual statements, the discovery call is the right starting point. We won't recommend §226 work in isolation — it's part of the broader reasonable-steps record — but we will tell you whether your current statements pass the checklist.