A personal-injury practice that starts taking wage-and-hour referrals learns fast that the pay stub is where a modest single-plaintiff dispute becomes a six-figure exposure. Labor Code section 226 does not require an employer to underpay anyone. It requires the employer to write down, accurately and in one place, what it paid and how it got there. When the writing is wrong, the statute supplies its own penalties, and those penalties attach to every pay period across the limitations window and, through PAGA, across the entire workforce.
The claim is deceptively small on paper — fifty dollars, then a hundred, capped at four thousand per employee. The value is in the multiplication. A wage statement defect is almost never isolated; it rides on top of an underlying pay error and then generates its own separate recovery, and a representative filing turns each defective period into a per-employee, per-pay-period penalty. Understanding which defects trigger which layers is the difference between pleading a nuisance and pleading real money.
The Nine Categories and Where They Actually Break
Section 226(a) requires nine items on every wage statement: gross wages earned; total hours worked by non-exempt employees; the number of piece-rate units and the piece rate, where applicable; all deductions; net wages earned; the inclusive dates of the pay period; the employee's name and the last four digits of the Social Security number or an employee identification number; the name and address of the legal entity that is the employer; and all applicable hourly rates in effect during the period with the corresponding number of hours worked at each rate.
The categories that generate the most litigation are the hourly-rate breakdown and gross-versus-net reconciliation. Employers that pay shift differentials, non-discretionary bonuses, or multiple rates frequently list a blended figure or omit the corresponding hours at each rate, so the reader cannot reconstruct the math from the document itself. The name-and-address item under 226(a)(8) is another recurring failure — statements that identify a payroll processor or a d/b/a rather than the legal entity fail on the face of the statute. These are not clever theories; they are read-the-stub-against-the-list defects, and they are why a defendant's own payroll records are the first document request.
The Injury Element and "Promptly and Easily Determine"
Section 226(e) is the private damages provision, and it carries an injury requirement that defendants press hard. An employee recovers the greater of actual damages or the fifty/one-hundred-dollar schedule only on a "knowing and intentional" failure that causes injury. The statute then does most of the plaintiff's work: under 226(e)(2)(B), an employee is deemed to suffer injury when the employer fails to provide accurate and complete information and the employee cannot "promptly and easily determine" required items from the statement alone. Subsection (e)(2)(C) defines that phrase as what a reasonable person could readily ascertain without reference to other documents or information.
That definition is the whole ballgame on many stubs. If the reader has to pull a rate sheet, a separate bonus memo, or a prior period's statement to reconcile the numbers, the injury element is satisfied by the defect itself. Defendants who argue the employee "knew" what she earned miss the statutory test — the question is what the document conveys, not what the worker independently understood.
How 226 Rides Underlying Violations
The derivative structure is where a wage statement claim earns its keep. When an employer fails to pay overtime, a minimum-wage shortfall, or a premium, the resulting stub understates gross and net wages and misstates the rate-and-hour breakdown. That inaccuracy is an independent 226(a) violation for every affected period. The California Supreme Court sharpened this in Naranjo v. Spectrum Security Services, Inc. (2022) 13 Cal.5th 93, holding that meal- and rest-period premiums under section 226.7 are wages, not penalties, and therefore must be reported on wage statements and are subject to waiting-time penalties under section 203.
Naranjo means a missed-break claim is never just a section 226.7 claim. Unpaid premiums that never hit the stub become a derivative 226 claim and, on separation, a section 203 waiting-time claim. Plaintiff-side lawyers moving into this area from injury work — the same crossover that put classification and non-delegable duty questions in front of tort practitioners after the Uber MDL non-delegable duty ruling — should read every wage claim as a potential three-count stack before drafting.
The "Knowing and Intentional" Gate
The derivative theory has a limit, and the Supreme Court drew it on remand. In its 2024 Naranjo decision, the court held that an employer's objectively reasonable, good-faith belief that it was complying defeats the "knowing and intentional" element of a section 226(e) claim, just as a good-faith dispute defeats the "willful" requirement for section 203 penalties. A defendant who reasonably but wrongly believed the premiums were not owed can escape the derivative wage-statement penalty even where the underlying pay was in fact due.
For the plaintiff, that ruling shapes discovery more than pleading. The good-faith defense turns on what the employer knew and when — payroll audits, prior DLSE citations, internal counsel memos, and the treatment of the same issue across pay periods all bear on whether the failure was knowing. Where a company kept paying the same defective way after a demand letter or an agency finding, the good-faith argument collapses, and the derivative penalty is back on the table. Building that record early is what separates a settled individual claim from a live representative one.
PAGA Stacking and the 2024 Reform
The representative layer is where section 226 exposure becomes serious. The Private Attorneys General Act lets an aggrieved employee recover civil penalties on behalf of the state and other employees. Section 226.3 sets a dedicated wage-statement civil penalty of $250 per employee for an initial violation and $1,000 per employee for each subsequent one, and PAGA plaintiffs pursue those figures per pay period across the workforce. Standing to bring the representative claim survives arbitration of the individual claims under Adolph v. Uber Technologies, Inc. (2023) 14 Cal.5th 1104, following the federal split-the-claim holding in Viking River Cruises, Inc. v. Moriana (2022) — so a defendant cannot buy peace on the named plaintiff's individual case and extinguish the representative penalties.
The 2024 PAGA reform, effective for notices filed on or after June 19, 2024, reshaped the arithmetic without eliminating it. The amendments added a lower default wage-statement penalty of $25 per pay period where the employee could promptly and easily determine the required information or where the violation is derivative, capped penalties at 15 percent of the schedule for employers that took all reasonable steps to comply before the notice and 30 percent for those that cured within sixty days after, and broadened the cure mechanism for section 226(a) defects. The practical effect is that stacking still happens — underlying claim, derivative 226 penalty, section 203 penalty — but the multiplier now depends heavily on whether the employer can show pre-notice compliance efforts. A defendant with no payroll audit and no cure attempt faces the full schedule; a defendant that documented reasonable steps argues for the cap.
What the Math Means for Case Selection
The reform rewards employers who prepare and penalizes those who ignored known defects, which pushes the plaintiff's value assessment toward the defendant's compliance history rather than the raw penalty schedule. The same instinct that PI lawyers bring to apportionment — reading how a California jury allocates fault before valuing a claim — applies here: the sticker number is the ceiling, and the recoverable number turns on what the record shows about the employer's state of mind and its cure conduct.
Read the stub against the nine categories first, then trace each defect back to the underlying pay error and forward to the section 203 and PAGA layers. A wage statement claim is worth pursuing precisely when it is not standalone — when the same defect repeats across periods and employees, and when the employer's own records show it knew. That is the case that stacks.