Pay Stub (Wage Statement) Requirements by State

Federal law does not require employers to give employees a pay stub. That's the counterintuitive starting point: the Fair Labor Standards Act requires employers to keep payroll records but does not require them to deliver any of those records to employees. Every meaningful pay-stub right in the United States comes from a state statute — and the variation is wider than for any other area of wage-and-hour law. California's Labor Code §226 generates statutory penalties of $50 for the first violation, $100 per pay period for each subsequent violation, up to $4,000 per employee, plus mandatory attorney's fees, plus a separate $750 records-request penalty, plus a PAGA layer on top — all for missing a single item on a wage statement. Nine other states require no pay stub at all.

The most consequential ruling of the post-2020 era is Naranjo v. Spectrum Security Services (2022): the California Supreme Court held that missed meal-break premium pay is "wages," which means it must appear on the pay stub. A single non-compliant break practice now creates a four-statute cascade — §512 (meal period) + §226.7 (premium pay) + §226 (itemization) + §203 (waiting-time penalty up to 30 days at separation) — plus PAGA + mandatory attorney's fees. This guide covers what federal law actually requires (less than you think), California's §226 mechanics, state-by-state variation, the named cases that drive litigation, the multi-state Ward framework, and the 2024 reforms that meaningfully blunt PAGA exposure while leaving the §226 stack intact.

Quick reference

• Federal floor (29 CFR Part 516): employers must keep payroll records (three years) and time/wage-rate records (two years) — but the FLSA imposes no requirement to furnish a pay stub. The employee never has to see them.
• California (Labor Code §226): nine required items per stub + piece-rate add-ons via §226.2. $50 first violation + $100 per pay period subsequent, $4,000 cap per employee, mandatory attorney's fees, separate $750 records-request penalty, PAGA stack on top, Naranjo cascade for missed-break premium pay.
• Strong-stub states: New York ($250/workday), Massachusetts (mandatory treble damages), DC (3× damages + criminal penalties), Illinois ($500/violation + 5%/month interest), plus meaningful regimes in Washington, Colorado, Oregon, Maryland (expanded Oct 2024), Hawaii, Connecticut.
• No-stub states: Alabama, Arkansas, Florida, Georgia, Louisiana, Mississippi, Ohio, South Dakota, Tennessee have no statutory pay-stub requirement at all.
• Multi-state rule: §226 follows the employee's work location, not the employer's HQ (Ward v. United Airlines, 2020). A Texas-headquartered company with a California-based remote employee owes a §226-compliant stub.

The 5 Most Expensive Pay Stub Mistakes

Before the rule tables, the patterns that drive litigation. Each has produced eight- or nine-figure exposure.

1. The Naranjo cascade. Missing the meal- or rest-break premium pay on a California wage statement is a §226 violation in its own right — not just a §226.7 violation. Naranjo v. Spectrum Security Services, 13 Cal.5th 93 (2022), held that §226.7 premium pay is "wages" under Labor Code §200. Mechanical consequence: an employer with a non-compliant break practice now faces a four-statute stack — §512 (meal-period rule) + §226.7 (premium pay) + §226 (itemization) + §203 (waiting-time penalty at separation, up to 30 days' wages) — plus PAGA + attorney's fees. The 2024 Naranjo follow-up added an objectively reasonable good-faith defense to the §226 piece, but only to that piece.

   Cited cases

   • Naranjo v. Spectrum Security Services, Inc., 13 Cal.5th 93 (2022)
     California Supreme Court — Meal/rest break premium pay is "wages" — missed itemization triggers §226 + §203 cascade
   • Naranjo v. Spectrum Security Services, Inc., 15 Cal.5th 1056 (2024)
     California Supreme Court — Objectively reasonable good-faith defense to §226(e) statutory penalties

2. Derivative §226 claims off underlying overtime errors. Whenever the regular rate for overtime is miscalculated — non-discretionary bonuses excluded, shift differentials missing, piece-rate earnings not blended — the pay stub now violates §226(a)(2) (total hours) and §226(a)(9) (hourly rates × hours at each rate) for every affected pay period. The exposure compounds: a $50K underlying overtime bug becomes $50K + statutory penalties + PAGA + 30-day waiting-time + attorney's fees. Magadia v. Wal-Mart produced a roughly $102M district-court judgment on this pattern before the 9th Circuit reversed (the appeal turned on technical §226(a)(9) interpretation, not on the broader derivative-claim theory). The reversal narrowed the law; it did not eliminate the exposure shape. The same §226(a)(2) "total hours" derivative violation is created when an employer rounds rather than pays exact time — see our time clock rounding rules guide for the Camp v. Home Depot doctrine (pending at the California Supreme Court). Buddy-punched hours produce the asymmetric inverse: §226 violations can attach even on OVERPAID hours, because the §226 claim is about accuracy of the statement, not directionality of the error — see our buddy punching guide.

   Cited cases

   • Lubin v. The Wackenhut Corp., 5 Cal.App.5th 926 (2016)
     California Court of Appeal — Class of ~13,500 California security officers; settled 2019 for $100M–$130M
   • Ridgeway v. Walmart Inc., 946 F.3d 1066 (9th Cir. 2020)
     US Court of Appeals, 9th Circuit — $54.6M jury verdict for California-based truck drivers affirmed
   • Magadia v. Wal-Mart Associates, Inc., 999 F.3d 668 (9th Cir. 2021)
     US Court of Appeals, 9th Circuit — Reversed the district court's ~$102M §226 + PAGA judgment

3. Piece-rate pay stubs that don't separately compensate rest breaks. Bluford v. Safeway Stores, 216 Cal.App.4th 864 (2013), held that piece-rate compensation pays for productive time only — rest breaks and other nonproductive time must be separately compensated AND must appear as a separate line on the wage statement. The 2015 piece-rate statutory amendment (Labor Code §226.2) codified this and added a back-pay election period for prior violations. Trucking, agriculture, manufacturing piece-work, and commission-based retail all routinely fail this test.

4. Misclassifying which state's law applies to remote workers. Ward v. United Airlines, 9 Cal.5th 732 (2020), is the controlling answer: §226 applies to employees whose principal place of work is California, or — for mobile workers who don't spend a majority of time in any single state — whose base of operations is California. A Texas-headquartered employer with a California-based remote employee owes §226-compliant pay stubs for that employee. Multi-state payroll systems that apply HQ rules to all employees miss this systematically.

5. The §203 waiting-time cascade at separation. Any §226-related unpaid wages still owed when an employee separates trigger §203 waiting-time penalties — the employee's daily wage for every day the wages remain unpaid, capped at 30 days (see our final paycheck laws by state guide for the multi-state penalty math + the post-Naranjo good-faith defense). A terminated employee with $200 of unpaid §226.7 premium pay accumulated over the prior year is owed $200 + 30 days of waiting-time penalty + the §226 derivative statutory penalties + PAGA + attorney's fees. The waiting-time cascade is what turns small unpaid amounts into high four-figure individual claims — and class-wide it scales linearly with terminated headcount. Post-2024 Naranjo provides an objectively reasonable good-faith defense to §226 statutory penalties but NOT to the §203 cascade; the waiting-time exposure remains.

Federal Baseline: FLSA Recordkeeping, Not Pay Stubs

This is the counterintuitive load-bearing fact. The Fair Labor Standards Act and its regulations (29 CFR Part 516) require employers to keep records about each non-exempt employee — but they do NOT require the employer to furnish those records to the employee.

§516.2(a) lists what every covered employer must maintain for each non-exempt employee:

1. Name, address, occupation, sex, birth date if under 19
2. Day and time of day the workweek begins
3. Regular hourly rate of pay for any week overtime is due
4. Hours worked each workday and total each workweek
5. Total daily or weekly straight-time earnings
6. Total premium pay for overtime hours
7. Total additions to or deductions from wages
8. Total wages paid each pay period
9. Date of payment and pay period covered

Payroll records: keep for three years (§516.5). Underlying time cards, work schedules, and wage-rate tables: keep for two years (§516.6). No required form — paper, microfilm, or electronic all acceptable (§516.2(b)). Our free timesheet template renders the §516.2(a) fields as a printable starting point when no electronic system is in place.

There is no federal penalty for omitting an item from a pay stub, because there is no federal requirement to issue a pay stub in the first place. DOL investigators can request the §516 records and use missing or inadequate records to invoke the Anderson v. Mt. Clemens Pottery, 328 U.S. 680 (1946), burden-shifting rule — but that's enforcement against unpaid wages, not pay-stub enforcement. See our recordkeeping requirements guide for the §516 framework and the federal layered statutes that determine how long the underlying records must be preserved.

State law fills the gap. Every meaningful pay-stub right in the United States comes from a state statute, not from federal law.

California Labor Code §226 — The Centerpiece

California's wage statement statute is the single most-litigated pay-stub law in the country. Plaintiffs' bar treats §226 violations as a multiplier on top of underlying wage-and-hour claims: a missing item on the pay stub turns a $50K unpaid-overtime claim into a $50K + per-pay-period statutory penalty + waiting-time + attorney's fees + PAGA claim.

The nine required items — §226(a)

Every wage statement furnished with payment of wages must show:

1. Gross wages earned
2. Total hours worked (except for salaried exempt employees)
3. Piece-rate units earned and the applicable piece rate (for piece-rate workers)
4. All deductions (deductions made on written orders of the employee may be aggregated and shown as one item)
5. Net wages earned
6. Inclusive dates of the period for which the employee is paid
7. Name of the employee and only the last four digits of their SSN or an employee ID number
8. Name and address of the legal entity that is the employer — a PO box alone is not enough
9. All applicable hourly rates in effect during the pay period AND the corresponding number of hours worked at each rate

§226.2 adds piece-rate-specific items on top: total hours of compensable rest/recovery periods, the rate of compensation for those periods, gross wages paid for that time during the pay period, and a separate listing for "other nonproductive time."

Beyond §226 — §246(i) sick leave balance disclosure

California layers a second pay-stub disclosure requirement on top of §226: Labor Code §246(i) requires the employer to provide to each employee, each pay period, the amount of paid sick leave available — either on the wage statement itself OR in a separate written document furnished with the paycheck. The employer elects the disclosure vehicle, but the disclosure is mandatory under either election. See our paid sick leave laws by state guide for the underlying accrual and use-cap framework.

The mechanics: under California's Healthy Workplaces, Healthy Families Act (Labor Code §245 et seq.), employees accrue 1 hour per 30 hours worked with a balance cap of 80 hours. Each pay period, the employer must compute the running balance (accrued minus used) and disclose the current available amount. The disclosure is per-employee, per-pay-period — a static balance shown on every stub is not enough; the number must update.

The §246(i) disclosure is enforced separately from §226. Failure to disclose is not a §226(a) violation (the nine items don't include sick-leave balance), and the §226(e) penalty schedule doesn't apply. But §246's own penalty regime applies — the labor commissioner can recover wages plus penalties under §248.5, and a private right of action with attorney's fees is available. The post-Naranjo §226-cascade analysis does NOT touch §246(i): there is no §226 derivative violation when only the sick-leave balance is missing. But practitioners frequently see §226 and §246(i) violations co-occur — a payroll system that fails to capture missed-break premium pay (the §226 derivative trap) typically also fails to track and disclose sick leave correctly. Audit both at the same time.

The penalty schedule — §226(e)

An employee who suffers injury as a result of a knowing and intentional §226(a) failure may recover the greater of actual damages or:

• $50 for the initial pay period in which a violation occurs;
• $100 per employee per pay period for each subsequent violation;
• Up to an aggregate cap of $4,000 per employee;
• Plus mandatory costs and reasonable attorney's fees.

Separately, §226(c) gives current and former employees the right to inspect or receive copies of payroll records within 21 days of request; failure triggers a $750 penalty payable to the employee or the Labor Commissioner, plus injunctive relief.

The $4,000 cap is per employee, not per case. In a class action of 1,000 affected employees, the §226 ceiling alone is $4M — and PAGA penalties layer on top.

Knowing and intentional + the injury requirement

Two pleading-stage gates defendants use to attack §226 claims:

"Knowing and intentional" — §226(e)(3) excludes "an isolated and unintentional payroll error due to a clerical or inadvertent mistake." Courts have construed this broadly. It does NOT require malicious intent. An employer that knows what its payroll system is doing and uses it consistently across a workforce meets the standard, even believing in good faith that the practice is legal.

Injury — §226(e) requires the employee to show injury from the deficient statement. Price v. Starbucks Corp., 192 Cal.App.4th 1136 (2011), established that deprivation of §226(a) information, standing alone, is not an injury. But the 2013 amendment to §226(e)(2)(B) provides that an employee is deemed to suffer injury if the employer fails to provide accurate information as to specific items (hours, rates, gross/net wages, deductions) and the employee cannot promptly and easily determine the required item from the wage statement alone. The injury element is therefore much easier to plead today than under Price.

2024 development — the Naranjo good-faith defense. Naranjo v. Spectrum Security Services, 15 Cal.5th 1056 (May 6, 2024), held that an employer's "objectively reasonable, good faith belief that it has provided employees with adequate wage statements precludes an award of penalties under section 226, subdivision (e)(1)." Meaningful — but the burden is on the employer, and "objectively reasonable" is a high bar where the legal question was clearly settled. The defense applies only to §226 statutory penalties, not to the underlying §226.7 premium pay or to §203 waiting-time penalties.

Standalone vs. derivative §226 claims

The most important practical distinction in California wage-and-hour litigation:

• A standalone §226 claim is one where the wage statement is defective even though wages were paid correctly — e.g., it omits the employer's address, lists only a PO box, doesn't break out two rates of pay separately, doesn't show piece-rate units. The statement itself is the violation.
• A derivative §226 claim is one where the wage statement is defective because the underlying wages were wrong — unpaid overtime didn't show up because it wasn't paid, missed-break premium didn't show because it wasn't paid, off-the-clock hours weren't recorded so they couldn't be itemized.

Derivative claims are the multiplier. Every $1 of unpaid overtime becomes $1 + statutory penalty + PAGA + §203 waiting-time + attorney's fees. The penalty stack is why a $50K unpaid-wage exposure routinely turns into a $5M+ class settlement.

Things California employers consistently miss

• Missed-break premium pay not itemized. The post-Naranjo trap. Many employers pay the §226.7 premium but list it as a generic "adjustment" line — the stub must show it as separately identified wages.
• Retroactive bonus rate not reconciled with rates "in effect." Magadia stands for the proposition that a retroactive non-discretionary bonus isn't an hourly rate "in effect" during the prior period. But the underlying overtime recalculation must still appear correctly on subsequent stubs; get this wrong and the next stub becomes a §226(a)(9) violation.
• Multi-rate workers shown at a single blended rate. §226(a)(9) requires "all applicable hourly rates" AND "corresponding number of hours worked at each hourly rate" — not a blended average. Healthcare workers with shift differentials, manufacturing workers with skill premiums, and trucking workers with task-based rates all routinely lose on this.
• Piece-rate workers without separate rest-break compensation. Bluford + §226.2: piece-rate productive time, rest/recovery time, and "other nonproductive time" (training, meetings, waiting) all need to be itemized as separate lines, even when paid. Many piece-rate stubs show two lines when the statute requires three.
• Statutory deductions improperly aggregated with voluntary ones. §226(a)(4) lets voluntary deductions made on written employee authorization be aggregated (401(k), HSA, supplemental insurance under a single "voluntary deductions" line). Statutory deductions (tax, garnishments, child support) and involuntary deductions must be itemized separately. Many payroll systems do this backwards.
• Full SSN on the stub. §226(a)(7) limits the SSN display to the last four digits (or an employee ID instead). Full SSN is prohibited, not required. Legacy payroll systems that still print full SSN are creating a §226(a)(7) violation per pay period plus an arguable UDAAP / state-privacy exposure.
• Statements listing a PO box instead of a physical address. §226(a)(8) requires the "name and address of the legal entity" that is the employer. Courts have read this strictly; a PO box without a physical address fails.

What's NOT a §226 Violation

Several common practices look like §226 violations but aren't. Knowing the boundary is as important as knowing the rule — a remediation pass that "fixes" non-violations wastes time and signals an over-broad reading of the statute.

• Aggregated voluntary deductions. §226(a)(4) explicitly allows deductions made on written orders of the employee to be aggregated and shown as one item. The employer doesn't need to itemize every voluntary deduction (401(k), HSA, supplemental insurance) on its own line — a single aggregated "voluntary deductions" line covers them. Statutory deductions (taxes, garnishments) and involuntary deductions still need to be itemized.
• A PO box paired with a physical address. §226(a)(8) requires the legal entity's address. A PO box alone fails; a PO box AND a physical street address satisfies the statute.
• Electronic delivery in California. Provided the employee can access the statement on payday, print it at no charge, and is notified of the right to elect paper at any time. Per the DLSE Opinion Letter on Electronic Itemized Wage Statements (July 2006).
• An isolated clerical mistake. §226(e)(3) explicitly excludes "an isolated and unintentional payroll error due to a clerical or inadvertent mistake" from the knowing-and-intentional standard. A one-off typo in an employee name, a one-off duplicated line — not a §226 violation. The carve-out is narrow: once a practice is in place across a workforce, courts treat it as knowing regardless of intent.
• Last four digits of an SSN. §226(a)(7) requires the employee name PLUS the last four digits OR an employee ID. Full SSN is actually prohibited, not required. Many legacy payroll systems still print full SSN; the fix is to mask it, not to add it.
• Omitting the bank account number entirely. §226 does not require displaying the destination account for direct deposit. Privacy / UDAAP best practice is to display only the last four (or none at all) — and that's compliant.

The line in every case: did the employer fail to furnish required information that the employee needs to verify what they were paid? If yes, §226 violation. If the omission is privacy-protective, an administrative detail outside §226(a), or a one-off clerical mistake, not a violation.

State-by-State Pay Stub Requirements

Outside California, twelve to fifteen states have pay-stub rules with real teeth — specific per-violation penalty schedules, private rights of action, or both. The rest follow the federal floor (records-only) plus whatever thin state statute applies. The table covers the states where pay-stub-only litigation has real exposure.

Other states with itemized-statement requirements include New Jersey, Minnesota, Arizona, Michigan, Vermont, Virginia, and Nevada — each with its own statute and penalty structure.

States with NO pay stub requirement

Nine states have no statute requiring employers to furnish itemized pay stubs to employees:

Alabama, Arkansas, Florida, Georgia, Louisiana, Mississippi, Ohio, South Dakota, Tennessee.

In these states an employee has no statutory right to receive a pay stub. The employer must still maintain payroll records under 29 CFR §516 federally — and remains liable for unpaid wages under FLSA + any state minimum-wage law — but a wage-statement-only claim has no statutory hook. National multistate employers typically issue stubs in these states anyway because the federal payroll system produces them as a byproduct; the legal question is whether the employee has a cause of action when the stub is wrong or missing. In these nine states, the answer is no.

Electronic vs. Paper Pay Stubs

Three regimes:

• Electronic-default, employee can opt out (California, Texas, Washington, New York, Massachusetts and most others): the employer may default to electronic delivery as long as the employee can access and print the statement at no charge. California's regime (per the DLSE Opinion Letter on Electronic Itemized Wage Statements, July 2006) adds five specific conditions including an explicit right to elect paper at any time.
• Opt-in only (Hawaii): HRS §388-7 requires written employee consent for electronic delivery. The default is paper.
• No statutory regime (no-stub states + a few others): the employer-employee agreement governs.

The opt-in versus opt-out distinction is the load-bearing one. For a multi-state employer, the safest practice is opt-in plus paper on request — which satisfies every state's requirement.

Multi-State and Remote Workers

Pay-stub liability follows the employee's work location, not the employer's HQ. Ward v. United Airlines, Inc., 9 Cal.5th 732 (2020), is the controlling answer for California; analogous principles apply for other state statutes.

The Ward framework: §226 applies if California is the employee's principal place of work. For most employees, that's the majority-of-time-in-California test. For interstate transportation workers (and others who don't spend a majority of time in any single state), the test is the base of work operations rule — §226 applies if the employee performs at least some work in California and California is the physical location where the employee presents to begin work.

Practical applications:

• A California-headquartered employer with an employee working entirely from Texas → §226 does NOT apply to that employee. The Texas employee receives a §62.003-compliant stub.
• A Texas-headquartered employer with an employee working entirely from California → §226 DOES apply. The California employee receives a §226-compliant statement, even though the employer is headquartered in a no-pay-stub state.
• An employee splitting 60/40 between two states → §226 applies to the state where the majority is worked; the minority-state statute also applies for hours worked there.
• A truly mobile employee with no fixed work location → fall back to the base-of-operations test; usually where the employee reports for assignment.

For HR systems, the implication is that work location, not employer location or payroll location, drives pay-stub requirements. Multi-state payroll engines must apply §226 (and analogous state rules) per-employee based on actual work location.

The strict-everywhere approach. A multi-state employee can receive a pay stub that complies with multiple states' rules simultaneously — there's no inherent conflict in over-disclosure. The safest practice is California-compliant statements for everyone, even where state law requires less. This is the "standardize to California" recipe that recurs across overtime rules, meal and rest break laws, and off-the-clock work.

The PAGA Layer (California)

California's Private Attorneys General Act (Labor Code §2698 et seq.) lets an aggrieved employee sue on behalf of themselves AND other current or former employees to recover civil penalties for Labor Code violations — including §226 — that would otherwise be recoverable only by the state.

Default PAGA penalty per §2699: $100 per employee per pay period (initial violation) and $200 per employee per pay period (subsequent). The 2024 reforms layer caps on top.

2024 PAGA reform — AB 2288 + SB 92

Signed July 1, 2024; effective for actions filed on or after June 19, 2024. Key changes to the §226 piece:

• Harmless violations capped at $25 PAGA penalty per pay period (where the employee could promptly and easily determine the required information).
• Short-duration violations (30 days or less, or 4 consecutive weekly pay periods, and based on isolated, nonrecurring events) capped at $50 per aggrieved employee per pay period.
• Reasonable-steps defense: PAGA penalties capped at 15% of the penalties otherwise sought if the employer took all reasonable steps to comply before receiving a PAGA notice.
• Prospective-compliance defense: penalties capped at 30% if the employer takes all reasonable steps within 60 days of the PAGA notice.
• Malicious / recidivist multiplier: penalty raised to $200 per pay period for malicious, fraudulent, or oppressive conduct, or where the LWDA or a court has determined the same practice unlawful within the preceding 5 years.
• Personal experience requirement: plaintiff must personally have experienced each Labor Code violation they seek to recover representatively.
• Employee share increased to 35% (up from 25%); the rest goes to the LWDA.

The reforms substantially blunt the worst PAGA exposure patterns but do not eliminate PAGA. A non-compliant employer still faces §226(e) statutory penalties (capped at $4,000 per employee) plus the reduced PAGA layer plus attorney's fees.

Recent Changes (2024–2026)

• Naranjo good-faith defense (May 6, 2024). California Supreme Court added objectively reasonable good-faith as an affirmative defense to §226(e) statutory penalties. Meaningful for employers with documented compliance reviews; a high bar where the legal question is settled.
• PAGA reform — AB 2288 + SB 92 (June 19, 2024). Caps and tier-downs on PAGA penalties (see above). Not retroactive to actions filed before that date.
• Maryland §3-504 expansion (October 1, 2024). Substantially expanded pay-stub requirements. Prior law required only pay-rate-and-deduction notice; new requirements include employer name/address/phone, pay-period dates, hours, rate(s), gross/net, itemized deductions, additional pay (bonuses, commissions), and piece-rate units.
• Oregon SB 906 (effective January 1, 2026). Expanded the disclosure regime around the pay stub: employers must disclose at time of hire all payroll codes used, all benefit deductions and contributions, and all pay rates the employee may be eligible for. BOLI civil penalty up to $500 per violation. The pay-stub statute (ORS 652.610) itself is not substantially expanded.
• Colorado CDLE Wage Protection Rules expansion (effective February 1, 2026). New leave-balance recordkeeping requirements for vacation/PTO and HFWA sick leave: employers must track hours accrued, used, and available for the current benefit year. Employers may disclose the running balance via the pay stub, electronic self-service system, or separate written/electronic communication; on employee request, disclosure must be in writing or electronically (no more than once per month unless employer policy is more permissive). The article's Colorado row of the State-by-State table now reflects the new election.
• Massachusetts pending wage-theft bill. Multiple sessions have seen proposed legislation (the current 194th General Court successors are S.1300 / H.2094) that would create a private right of action with civil penalties in the $7,500–$25,000 range. As of this article's publication date, no such expansion is enacted Massachusetts law. The current Massachusetts regime remains M.G.L. c.149 §148 + the §150 mandatory treble-damages remedy.

Frequently Asked Questions

If You Discover Your Pay Stubs Are Out of Compliance

Self-audits frequently reveal accumulated §226 exposure: missing piece-rate breakdowns, blended rates instead of per-rate detail, missed-break premium pay buried under a generic line, employer address listed as a PO box, retroactive bonus adjustments without correct overtime recalculation. The unwinding playbook:

1. Audit by employee work location. Pull pay stubs for the §226 statute period (one year from each violation for §226(e) statutory penalties; up to four years under California's Unfair Competition Law for the underlying wage claims). Identify per-stub which §226(a) items are present, missing, or incorrect. For California employees, every pay period counts.

2. Reconcile the underlying wage data. Most §226 violations are derivative — wrong because the underlying overtime, premium, or hourly rate is wrong. Fix the underlying calculation before fixing the stub. A correct-looking stub built on miscalculated wages still violates §226(a)(9).

3. Pay corrective wages voluntarily. Self-correcting before a claim is filed is admissible as good-faith evidence and (post-2024 Naranjo) is what supports the objectively-reasonable-good-faith defense to §226 penalties. Voluntary payment can also eliminate the §203 waiting-time multiplier for former employees who receive back wages.

4. Set up a §226(c) records-request response process. §226(c) requires that current and former employees be allowed to inspect or receive copies of payroll records within 21 days of request. Failure triggers a $750 penalty plus injunctive relief — and plaintiffs' bar uses records requests as a litigation tactic to establish bad faith. The fix is operational: name a person responsible, set a 14-day internal deadline to buffer against the 21-day statutory cap, and document the response. This is the cheapest §226 violation to avoid and one of the most-litigated.

5. Fix the stub-generation pipeline. Time records → payroll engine → wage statement is the chain that produces §226 compliance. If the time records lack the data — multi-rate hours captured at each rate, missed-break premium itemized, off-the-clock activities recorded — no downstream stub system can produce a §226-compliant statement. Fix the data-capture layer first.

6. Consult counsel for class-action exposure. Rough rule: more than 10 California employees with a uniform §226 defect, or any systematic derivative-violation pattern (e.g., a regular-rate calculation that excludes a non-discretionary bonus across the workforce), crosses into class-action territory. PAGA notice letters (a single employee files with the LWDA, then can pursue representative claims) are a precursor signal — the 2024 reform's cure window is meaningful but short, and the response strategy needs to be in counsel's hands within days of the notice.

The Through-Line

The pay stub is a derivative artifact. It reports what payroll computed; it doesn't determine what the employee was owed. The §226 docket exists in the shape it does because plaintiffs' bar discovered that an inaccurate stub is easier to litigate than an unpaid wage — the stub is a discrete record, date-stamped per pay period, with a per-violation statutory penalty that compounds across the workforce. Every derivative §226 claim is structurally a wage claim wearing a different statute number.

The defense is therefore the same as it is for overtime, breaks, and off-the-clock work: fix the upstream data capture. Time records must show every minute worked at the rate it was worked at; premium pay must fire at the moment the trigger condition occurs; multi-state employees must be flagged by work location, not by HQ. With clean upstream data, §226 compliance is mechanical — the stub just prints what's already true. Without it, no downstream stub-generation logic can produce a §226-compliant statement, because the statement has nothing accurate to report.

For multi-state employers, the strict-everywhere recipe applies: California-compliant statements for everyone, even where state law requires less. The marginal cost is small; the elimination of per-state policy complexity and the defensive posture against §226 derivative claims are large.

Sources and Authorities

Federal

• 29 USC §211(c) — FLSA recordkeeping
• 29 CFR Part 516 — records to be kept by employers
• DOL Fact Sheet #21 — Recordkeeping Requirements Under the FLSA

State (selected)

• California Labor Code §226
• California Labor Code §246 (Healthy Workplaces, Healthy Families Act — accrual + §246(i) pay stub disclosure)
• California DLSE Opinion Letter — Electronic Itemized Wage Statements (July 2006)
• New York Wage Theft Prevention Act — DOL overview
• Massachusetts G.L. c.149 §148
• Illinois Wage Payment and Collection Act (820 ILCS 115)
• Washington WAC 296-126-040
• Oregon ORS 652.610
• Maryland Labor & Employment §3-504
• DC Code §32-1008
• Texas Labor Code §62.003

Case law

• Anderson v. Mt. Clemens Pottery Co., 328 U.S. 680 (1946) — burden-shifting when employer recordkeeping is inadequate (FLSA recordkeeping foundation).
• Price v. Starbucks Corp., 192 Cal.App.4th 1136 (2011) — §226 requires showing of injury beyond bare omission (substantially softened by the 2013 deemed-injury amendment).
• Bluford v. Safeway Stores, Inc., 216 Cal.App.4th 864 (2013) — piece-rate workers must be separately compensated for rest breaks; rest-break pay must appear on the wage statement.
• Lubin v. The Wackenhut Corp., 5 Cal.App.5th 926 (2016) — reversed class decertification of approximately 13,500 California security officers; settled in 2019 for between $100M and $130M.
• Ridgeway v. Walmart Inc., 946 F.3d 1066 (9th Cir. 2020) — $54.6M jury verdict for California-based truck drivers affirmed; activity-based pay structure produced §226 derivative violations.
• Ward v. United Airlines, Inc., 9 Cal.5th 732 (2020) — §226 applies to multi-state employees with California as principal place of work or base of operations. Oman v. Delta Air Lines, Inc., 9 Cal.5th 762 (2020), is the same-day companion ruling.
• Magadia v. Wal-Mart Associates, Inc., 999 F.3d 668 (9th Cir. 2021) — reversed the district court's roughly $102M §226 + PAGA judgment; held that a retroactive non-discretionary bonus adjustment is not an hourly rate "in effect" for §226(a)(9) purposes.
• Naranjo v. Spectrum Security Services, Inc., 13 Cal.5th 93 (2022) — meal/rest break premium pay is "wages"; missed itemization triggers the §226 + §203 cascade.
• Naranjo v. Spectrum Security Services, Inc., 15 Cal.5th 1056 (2024) — §226(e) statutory penalties subject to an objectively reasonable good-faith defense.