Audit before the notice arrives
Wage Statement Compliance Matrix
Nine Elements of § 226(a)
Why wage statements matter in PAGA.
Wage statement violations under § 226 are independently PAGA-actionable. After Naranjo, they also serve as derivative violations — every unpaid premium or miscalculated wage automatically generates a wage statement deficiency. In many PAGA cases, the wage statement exposure exceeds the exposure on the underlying violations.
The nine-element requirement.
Section 226(a) requires every wage statement to carry nine specific elements, and a deficiency in any one of them violates § 226(a). What follows from that violation depends on which statute is asked. Section 226(e) awards the employee the greater of actual damages or $50 for the initial pay period and $100 for each subsequent one, capped at $4,000 per employee — but only on proof of injury under § 226(e)(2) and a knowing and intentional failure under § 226(e)(1). PAGA asks neither question: for notices filed on or after June 19, 2024 the civil penalty runs on the § 2699(f)(2)(A) schedule — $100 per employee per pay period by default, reduced to $25 or $50 in the circumstances § 2699(f)(2)(A)(i) and (ii) define. A pre-reform notice runs the former $100/$200 schedule instead.
Each element is listed with compliance requirements, common deficiencies, and risk rating.
Curable
Element 1: Gross Wages Earned
Total gross wages before deductions. Must include all compensation: base pay, overtime, premiums, commissions, bonuses, piece-rate earnings. Deficiency: omitting meal/rest premiums (Naranjo derivative) or commission adjustments.
Curable
Element 2: Total Hours Worked
All hours worked in the pay period, "except as provided in subdivision (j)." Subdivision (j) is a closed list, not a general exempt-employee carve-out: it excuses the hours line only where compensation is solely based on salary and the employee is exempt from overtime, or where the employee falls within one of eight enumerated exemptions. A commissioned salesperson exempt from overtime under Wage Order 4-2001 or 7-2001, § 3(D), is on neither list and is not paid "solely" by salary, so total hours must still be shown. Non-productive time for piece-rate employees must be separately stated (§ 226.2, added by AB 1513). Deficiency: treating every exempt classification as excused, rounding errors, or omitting non-productive time.
Potentially Curable
Element 3: Piece-Rate Units & Rate
Required only for piece-rate employees. Number of units produced and the applicable piece rate. Deficiency: failing to separately state piece-rate earnings from non-productive time compensation.
Potentially Curable
Element 4: All Deductions
Every deduction must be itemized — taxes, insurance, garnishments — with one express exception written into the statute: deductions made on written orders of the employee may be aggregated and shown as one item, and § 226(e)(2)(B)(ii) confirms the injury provision does not disturb that allowance. Deficiency: burying statutory withholding, garnishments, or anything the employee did not authorize in writing inside an aggregate line, which the allowance does not reach.
Curable
Element 5: Net Wages Earned
Gross wages minus all deductions. This is typically calculated correctly by payroll systems. Deficiency: rare, usually only when gross wages or deductions are incorrect.
Curable
Element 6: Inclusive Pay Period Dates
The start and end dates of the pay period. Deficiency: omitting dates or using pay dates instead of pay period dates.
Curable
Element 7: Employee Name & ID
The employee's legal name and "only the last four digits" of the social security number, or an employee identification number "other than a social security number." The word doing the work is "only" — the litigated failure is showing too much, not too little. Deficiency: displaying the full social security number, using an "employee ID" that is the social security number, using an employee number without the name, or using a nickname or payroll alias in place of the legal name.
Curable
Element 8: Employer Name & Address
Legal entity name and address. DBA names alone are insufficient — the legal entity must be identified. Where the employer is a farm labor contractor as defined in § 1682(b), the statement must also carry the name and address of the legal entity that secured the contractor's services; § 226(g) provides that listing it creates no liability on that entity's part. Deficiency: using a DBA without the legal entity, an outdated address, or omitting the securing entity on a farm labor contractor's statement.
Potentially Curable
Element 9: All Applicable Hourly Rates & Hours
Every hourly rate at which the employee worked and the hours at each rate. This is the most commonly deficient element. Employees paid at multiple rates (regular, OT, double-time, shift differential) must have each rate and corresponding hours displayed. Temporary services employers as defined in § 201.3 carry an additional requirement dating to July 1, 2013: the rate of pay and the total hours worked for each temporary services assignment, broken out per assignment. Deficiency: showing a single blended rate, omitting the OT/DT rate breakdown, or reporting a staffing employee's hours in aggregate rather than per assignment.
Ferra v. Loews Hollywood Hotel (2021) requires that meal and rest period premiums be paid at the regular rate of compensation. This creates a wage statement display requirement.
What Ferra Requires on the Wage Statement
Premium rate display
If a meal or rest period premium is paid, the wage statement should display the premium at the regular rate — not the base hourly rate. Under Element 9, the premium rate is an 'applicable hourly rate' that must be listed with corresponding hours (1 hour per premium).
Multiple premium rates
If the regular rate varies across pay periods (due to variable commissions or bonuses), the premium rate will also vary. Each premium should reflect the regular rate for the pay period in which the violation occurred.
Practical challenge
Most payroll systems do not natively calculate meal/rest premiums at the regular rate. The premium is typically hard-coded at the base rate. Displaying the correct Ferra rate requires either payroll system reconfiguration or manual adjustment.
Every Ferra error is also a § 226 error.
If the premium is paid at the base rate instead of the regular rate, two violations occur simultaneously: (1) the premium underpayment under § 226.7, and (2) the wage statement inaccuracy under § 226(a)(1) (incorrect gross wages) and § 226(a)(9) (incorrect applicable rate). This is the Naranjo derivative cascade in action.
These patterns account for the majority of § 226 violations in PAGA cases.
Pattern 1: Missing Rate Breakdown (Element 9)
Description
The wage statement shows a single hourly rate (e.g., '$20.00/hr') without breaking down regular, overtime, and double-time rates and corresponding hours. For employees who work OT, this is a per-pay-period violation.
Prevalence
This is the most common § 226 deficiency. Many payroll systems display only the base rate. Element 9 requires all applicable rates — including OT (1.5×), DT (2×), shift differentials, and premium rates.
Remediation
Configure the payroll system to display each rate tier separately: Regular rate × [hours], OT rate × [hours], DT rate × [hours]. Test with a sample pay period to verify correct display.
Pattern 2: Naranjo Derivative — Unpaid Premiums
Description
Meal/rest premiums are not paid or are paid at the base rate instead of the regular rate. The wage statement either omits the premium or reports the wrong amount. This generates two violations: the § 226.7 premium failure and the § 226 statement inaccuracy.
Prevalence
Extremely common. Most employers who pay premiums pay them at the base rate (pre-Ferra practice). Every such payment since July 15, 2021 (the date Ferra was decided) is both an underpayment and a wage statement deficiency — and because Ferra applies retroactively, earlier underpayments within the limitations period are also actionable.
Remediation
Recalculate premiums at the regular rate. Issue corrected wage statements for all affected pay periods. Reconfigure the payroll system for prospective compliance.
Pattern 3: DBA Without Legal Entity (Element 8)
Description
The wage statement identifies the employer by its DBA (doing business as) name without including the legal entity name. Section 226(a)(8) requires the 'name and address of the legal entity that is the employer.'
Remediation
Add the legal entity name to the wage statement. This is typically a simple payroll system configuration change.
A deficient element establishes a violation of § 226(a). It does not establish a § 226(e) claim. Two further elements stand between the deficiency and the damages, and neither of them guards the PAGA track — an asymmetry that determines which defense is worth running first.
Gate 1 — Injury (§ 226(e)(2))
The deeming provision
Section 226(e)(1) reaches only "an employee suffering injury." Section 226(e)(2) then deems injury in two situations. Under (e)(2)(A), where the employer fails to provide a wage statement at all, injury is automatic and nothing further need be shown. Under (e)(2)(B), where a statement was provided but is inaccurate or incomplete, injury is deemed only if the employee cannot promptly and easily determine, from the wage statement alone, the wages paid or the other information in items (2) through (4), (6) and (9); which deductions were taken; the employer's name and address; or their own name and identifying number.
What the phrase means
Section 226(e)(2)(C) supplies the definition: "promptly and easily determine" means "a reasonable person would be able to readily ascertain the information without reference to other documents or information." That last clause is the operative limit. A statement the employee can only reconcile by pulling a schedule, a commission report, or a prior stub does not satisfy it — and a statement that is wrong on its face but internally self-explaining does.
What it does for the defense
A statement that is inaccurate but self-explaining closes the deemed-injury route. The employee is then left to prove actual injury, which a defect on the face of the statement does not by itself supply. On a small number of technical defects in an otherwise complete statement, this is usually a shorter route than litigating scienter, and it is available on the documents rather than on testimony about the employer's state of mind.
Gate 2 — Knowing and Intentional (§ 226(e)(1), (e)(3))
What the term excludes
Section 226(e)(3) provides that a "knowing and intentional failure" does not include an isolated and unintentional payroll error due to a clerical or inadvertent mistake. The exclusion is narrow by its terms — it wants the error to be both isolated and unintentional, and to trace to a clerical or inadvertent cause rather than to a design decision about how the statement is built.
The compliance-program factor
The same paragraph directs that "[i]n reviewing for compliance with this section, the factfinder may consider as a relevant factor whether the employer, prior to an alleged violation, has adopted and is in compliance with a set of policies, procedures, and practices that fully comply with this section." Two features matter. It is expressly a factor rather than a defense, so it informs the scienter question without resolving it. And it is keyed to the period before the alleged violation, which means the record has to predate the notice to do any work.
The record does double duty
That is the same record the § 2699(g) and § 2699(h) penalty caps are built on — written policies actually distributed, supervisor training with attendance recorded, payroll audits with findings and corrections, dated system configurations. Section 226(e)(3) names it as a relevant factor on scienter; § 2699(g)(1) and § 2699(h)(1) make it the predicate for the 15% and 30% caps. An employer assembling it for one purpose should be told it is evidence in the other, and an employer that has never assembled it is exposed on both fronts at once.
The reform borrowed § 226's injury test and made it a discount.
The PAGA civil penalty attaches to the § 226(a) violation itself — no injury, no scienter. So the same phrase does opposite work in the two statutes. Under § 226(e)(2)(B), the employee's ability to promptly and easily determine the information closes the deemed-injury route and defeats the damages claim outright. Under § 2699(f)(2)(A)(i), the identical showing reduces the PAGA penalty from $100 to $25 rather than eliminating it. The two tests are not perfectly congruent: § 226(e)(2)(B) lists four categories of information, while § 2699(f)(2)(A)(i) reaches "the accurate information specified by subdivision (a)" as a whole, so the showing that earns the $25 rate is the broader one. An employer that clears the PAGA test has necessarily cleared the § 226(e) one.
Understanding how § 226 violations interact with the Naranjo cascade and PAGA penalties.
The § 226(e) cap does not apply to PAGA penalties.
Section 226(e) caps statutory penalties at $4,000 per employee. But PAGA civil penalties under § 2699(f) are separate and uncapped (absent the reform penalty caps). This means the PAGA penalty exposure on § 226 violations can exceed the statutory penalty exposure.
The 2024 reform added two reductions defense counsel must run first.
For notices filed on or after June 19, 2024, § 2699(f)(2)(A)(i) sets the PAGA penalty at $25 per aggrieved employee per pay period — on either of two tests, depending on which element failed. For a violation of § 226(a)(1) through (7) or (9), the test is whether the employee could promptly and easily determine the accurate information from the wage statement alone. For a violation of § 226(a)(8), it is whether the employee would not be confused or misled about the correct identity of their employer, or, where the employer is a farm labor contractor, the identity of the legal entity that secured its services. The DBA-without-legal-entity defect described in Pattern 3 is often precisely the case in which no one was confused about who the employer was, and it is the branch defense counsel most often leaves on the table. Either branch is unavailable if the employer failed to provide an itemized payroll statement during any of the pay periods at issue — one missed pay period among those at issue disqualifies the reduction, not merely that period. Section 2699(f)(2)(A)(ii) sets $50 per employee per pay period for an isolated, nonrecurring event that did not extend beyond the lesser of 30 consecutive days or four consecutive pay periods. On the illustration above, the (A)(i) rate cuts the PAGA track from $130,000 to $32,500 before any penalty cap is applied. Neither reduction touches the § 226(e) statutory-damages track.
Correcting wage statement deficiencies involves both retrospective correction and prospective system changes.
Identify deficient elements.
Review a sample of current wage statements against all nine elements. Identify which elements are deficient and whether the deficiency is systemic (all employees) or sporadic (certain pay types or configurations).
Configure payroll system.
Work with the payroll vendor to configure correct display of all nine elements. Focus on Element 9 (rate breakdown), Element 1 (gross wages including premiums), and Element 8 (legal entity name). Obtain vendor confirmation of changes.
Issue corrected statements.
For all pay periods during the PAGA lookback where deficiencies existed, issue corrected wage statements. Distribute to all affected employees with a cover letter explaining the corrections.
Document the correction.
Retain copies of corrected statements, vendor configuration confirmations, and distribution records. This evidence supports the 30% penalty cap (remediation within 60 days) and the cure proposal (if applicable).
Test and verify.
Run a test payroll cycle with the new configuration. Compare the test statement against all nine elements. Verify correct display of multiple rates, premiums, and deductions before going live.
For illustrative and educational purposes only. Use the Wage Statement Compliance Checker tool for interactive element-by-element assessment.