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, §226(e) provides $50 for the initial violation and $100 for each subsequent violation, per employee, to an aggregate of $4,000 per employee, plus costs and reasonable attorney's fees.
It is worth naming the shape of that arithmetic rather than gesturing at it. Two hundred employees at the $4,000 per-employee aggregate produces a six-figure statutory ceiling — a ceiling on a hypothetical headcount, not a forecast, not an average, and not what any particular matter recovers. Two things constrain it immediately in practice: the one-year limitations period on the §226(e) penalty, and the fact that the per-employee counter takes more than a single year of biweekly periods to reach the aggregate at all. The number is the arithmetic upper bound of a hypothetical, because that is all it is.
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.
The injury element is thin. The statute requires a knowing and intentional failure, but §226(e)(2)(B) deems an employee to suffer injury where the statement omits required information or where the employee cannot promptly and easily determine the required information "from the wage statement alone." That last phrase is the whole ballgame, and it is worth committing to memory: the sufficiency of the statement is assessed on the face of the statement. Reconciling documents held elsewhere do not repair a facially defective stub.
It is per-period and per-employee. Every pay period multiplies the count, and every employee multiplies it again. A single recurring defect across a workforce needs no individualized proof — the plaintiff's firm doesn't have to find a different defect on each statement, because the same defect repeated is enough. The count runs against the per-employee aggregate rather than against anyone's sense of proportion.
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. Whether yours does is a question about your configuration rather than about your provider: item 8 turns on which legal entity is printed on the stub, and item 4 on how deductions are itemized — both set per employer, neither shipped in a default. So the answer comes from a statement, not from a brand name. Pull a recent one and read it against the list; whether anything short of the list is short enough to matter is counsel's call, not ours and not the vendor's.
The supporting record has to reconcile. If the wage statement claims 40 hours at $25, the time record has to show 40 hours. A clean-looking statement that doesn't reconcile against the underlying time record is exposed on a different theory — the records are inaccurate, which feeds §226 and §1174 and the Donohue presumption.
Be careful about which instrument does which job here, because the two get run together constantly. An employee signature does not cure a facial §226(a) defect. It cannot: §226(e)(2)(B) asks what the employee can determine from the wage statement alone, and a document that is not the wage statement is by definition not part of that inquiry. If the entity name on the stub is the parent instead of the operating subsidiary, no amount of attestation fixes the stub.
What reaches §226 is the recurring payroll audit — the first of the four examples §2699(g)(2) enumerates, and the one that pulls a sample of statements against the nine items on a schedule, opens an item on each defect, and records what was done to correct it. The audit finds the defect and drives the fix in payroll; the attestation is a Donohue instrument doing a different job on the same pay period. One system, two instruments, and the reason to keep them distinct is that a prospect who is told the signature covers §226 will stop checking the stub.
MicroForensics runs the wage statement through the recurring audit, not through the signature. Each cycle, a sample of statements is checked item by item against the nine §226(a) requirements; anything missing or ambiguous opens an item; the item stays open until someone records the correction made in payroll and the date it took effect. We do not produce the wage statement itself — that remains the payroll provider's job, and it is the payroll provider who has to fix a defective one.
That audit-and-response pattern is what §2699(g)(2) enumerates first. (The LWDA's proposed February 2026 regulations are procedural; their only §226 content is a cure pathway for wage-statement violations, and no regulation or appellate decision yet construes "all reasonable steps.") The durable point does not depend on how any of that lands: the audit is the only instrument in the set that looks at the stub, and the stub is where the plaintiff's firm starts.
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 belongs inside the recurring audit or nowhere. And to be clear about the boundary: we can tell you which of the nine items we can and cannot find on your statements. Whether what we find is a violation is your counsel's call, not ours.