Accuracy & the Derivative Defect

The figures have to be right

The requirements page established that the statement must contain the nine items; this page establishes that those items must be correct. Section 226(a) requires an accurate itemized statement, and accuracy is a distinct obligation from completeness: a statement can list every required item and still violate the statute because the numbers it lists are wrong. The gross wages are understated, the overtime pay reflects an incorrect rate, the premium line is short — the format is impeccable and the substance is false. This is the derivative defect, and it is analytically different from the facial defect because it cannot be seen by inspecting the statement against a checklist; it can be seen only by comparing the statement to what the correct wages should have been. The statement, in other words, is accurate or not depending on whether the wage computations behind it were right.

The derivative defect is the engine of most section 226 litigation, and understanding why clarifies the entire defense. A facial defect is a self-contained violation, but it is also a discrete formatting problem that a competent employer usually avoids. The derivative defect, by contrast, attaches to the statement automatically whenever an upstream wage error exists — and upstream wage errors, as the regular-rate and misclassification categories show, are common, systematic, and easy to make. A plaintiff who establishes that the regular rate was understated has, in the same stroke, established that every wage statement reporting wages computed on that rate was inaccurate. The wage-statement claim thus rides along with the underlying wage claim, adding a separate penalty to the same error. The sections below develop how the statement mirrors the error, where the errors come from, why the cure is upstream, and how the derivative defect interacts with the penalty gates.

It reflects the error, faithfully

The mechanism of the derivative defect is reflection: the statement reports the wages the employer actually computed and paid, so whatever error infected the computation appears on the statement as a misstatement. If the employer computed overtime on an understated regular rate, the statement shows that understated overtime and the correspondingly understated gross — not because the statement was prepared wrongly, but because it accurately reports a wrong computation. The same is true of an underpaid premium, an unreported bonus, or wages omitted entirely for a misclassified employee. The statement is a faithful record of the payroll, which is exactly why it is inaccurate when the payroll is wrong: it inherits the error rather than introducing one. This is worth stating precisely because it locates the defect's origin outside the wage-statement function itself — the statement-preparation process did its job; the wage-computation process did not.

That origin has a direct consequence for how the defect is established and contested. To prove a derivative wage-statement defect, the plaintiff proves the underlying wage error and then observes that the statement reflected it — the two are established together, and the wage-statement violation follows almost automatically from the wage violation. To defend the derivative defect, conversely, the employer's strongest move is usually not to defend the statement in isolation but to defend the underlying computation: if the regular rate was correct, the statement that reported it is accurate, and the derivative defect disappears. The derivative wage-statement claim, in short, stands or falls with the underlying wage claim, and the litigation over it is largely the litigation over the underlying error, with the statement following along.

The statement inherits the error rather than creating one. Prove the wage error and the statement defect follows; cure the wage error and the statement defect disappears.

Where the inaccuracy comes from

The derivative defect has a small set of recurring sources, each developed at length in another category, and cataloguing them is useful because it shows how the wage-statement claim aggregates the section's other errors. The dominant source is the regular rate: when the rate is understated — by omitting tip-pool distributions, distributed service charges, nondiscretionary bonuses, or differentials — the overtime pay, the premium pay, and the gross wages on the statement are all understated, and the applicable-rate disclosure is wrong as well. The second is the premium rate: after Ferra, the meal- and rest-period premium is paid at the regular rate, so a premium computed on the base rate understates the premium wage on the statement, and because premiums are wages under Naranjo, that understatement is unpaid wages misreported. The third is misclassification: an employee wrongly treated as exempt receives statements with no hours and no applicable-rate disclosure at all, so reclassification surfaces both facial and derivative defects across the entire back period.

What unites these sources is that the wage-statement defect is parasitic on an error the employer made elsewhere, which is both why the claim is so commonly pleaded and why it is rarely the center of gravity. A plaintiff alleging a regular-rate violation will almost always add a derivative wage-statement claim, because the statement necessarily reflected the rate error and the derivative claim adds a separate penalty at little additional pleading cost. The same is true of premium and classification claims. The wage-statement count thus functions as a penalty multiplier on the section's other violations — it does not usually introduce a new substantive wrong so much as attach an additional consequence to an existing one. That structure is the key to the defense: because the derivative defect is parasitic, defeating or curing the host error defeats or cures the derivative defect, and the wage-statement claim cannot outlive the underlying claim it depends on.

Fix the wage, and the statement follows

The most important practical consequence of the derivative defect's parasitic nature is that it is cured upstream, at the wage computation, not at the statement. An employer confronting a derivative wage-statement problem should not treat the statement as a separate compliance project to be solved on its own terms; it should correct the underlying wage error — fold the omitted remuneration into the regular rate, pay the premium at the correct rate, reclassify the misclassified employee — and the statement, which simply reports the now-correct wages, becomes accurate as a result. Treating the statement as the problem rather than the symptom leads to wasted effort and incomplete fixes: reformatting a statement that still reports wages computed on an understated rate does nothing, because the figures remain wrong. The reconciliation that matters is between the wage computation and the statement, ensuring that the statement reflects the corrected wages.

This upstream-cure principle is what ties the wage-statement category back into the others as their terminus rather than a freestanding silo. The audit that corrects the regular rate, prices the premium correctly, and resolves the classification question is the same audit that cures the derivative wage-statement defect, because the statement is downstream of all of them. An employer that runs the regular-rate audit the foundational category describes, and reconciles the statement to its results, has addressed the derivative wage-statement claim in the same exercise — there is no separate wage-statement remediation to perform beyond confirming that the corrected figures flow through to the statement and that the facial items are present. The wage-statement category, in this sense, is where the section's other corrections are verified to have landed: the statement is accurate when, and only when, the wages behind it are right.

The inaccuracy and its source

Each example is tested for whether it makes the statement inaccurate and, if so, which upstream error is the source. Select a scenario:

Fig. 1. Derivative defects and their sources. Ferra (2021); Naranjo I (2022); § 226(e)(3). A derivative defect is cured by curing the upstream error; an isolated clerical error is inaccurate but likely outside the knowing-and-intentional element (04). Outcomes are fact-specific.

Inaccuracy is not yet a penalty

Establishing that a statement was inaccurate is necessary but not sufficient for the statutory-damages penalty, because that penalty has two further gates the inaccuracy must clear — and the derivative defect interacts with each in a way that favors the employer on the damages track. The first gate is injury: section 226(e) damages require injury, and while an inaccurate statement can supply deemed injury where the employee cannot determine the correct figures from the statement alone, the injury analysis the next page develops can defeat the damages claim where the deficiency caused no cognizable harm. The second gate is intent: section 226(e) damages require a knowing and intentional failure, and a derivative defect that flows from a genuinely contestable wage question — a reasonable position on whether a payment is includable in the rate, for instance — is exactly the situation in which the Naranjo good-faith defense applies, because the employer reasonably believed its computation, and therefore its statement, was correct.

This interaction is the derivative defect's silver lining for the defense and the reason the category's exposure is so often smaller than the gross. A regular-rate error that the employer made in good faith, on a reasonable reading of a contestable question, produces inaccurate statements — but the inaccuracy was neither knowing nor intentional, so the section 226(e) damages penalty does not attach, just as the good-faith defense defeats the section 203 penalty on the underlying wages. The wages are still owed, and the statement was still inaccurate, but the wage-statement penalty on the damages track falls away with the good-faith showing. The crucial caveat, developed two pages on, is that this reasoning addresses the section 226(e) damages track; the section 226.3 civil-penalty track recovered through PAGA does not require a knowing and intentional failure, so the good-faith defense does not bar it in the same way. The derivative defect, then, is strongly defensible on the damages track and must be managed differently on the civil-penalty track — which is the distinction the tracks page draws.

Defend the host error, cure upstream, and match the defense to the track