What Triggers Derivative Pay-Stub Penalties

When a pay-stub problem is really a wage problem

Derivative pay-stub penalties fire when the statement is wrong because the underlying pay was wrong — not just because a template line looked ugly. If you underpaid overtime, skipped a meal-break premium, or never recorded hours, every affected California stub can become its own claim, and unpaid balances at exit can add up to 30 days of waiting-time pay.

If wages were paid correctly and only the statement is incomplete (missing address, two rates smashed into one line), that is a standalone stub problem — still real, but without the same multi-statute stack. If you are outside California, your state may still require itemized stubs, but this cascade is a California pattern. The surprise: a 2024 good-faith defense can cut some statutory stub penalties, but it does not erase the unpaid premium, the waiting-time clock, or every civil-penalty layer.

What to fix this week

• Pull last month's California stubs and confirm meal-break premiums show as their own line.
• List anyone who left with open premium or overtime shortfalls and pay the balance.
• Check multi-rate workers show each rate and the hours at that rate.
• Map remote workers to the state where they actually work, not headquarters.
• Save old stub samples and the redesigned version after you fix a line.

How a small miss becomes a big case

• Paying a missed-break hour as a vague "adjustment" no one can identify on the stub.
• Leaving a promised bonus out of overtime math, then reprinting the wrong rate every period.
• Applying Texas stub rules to a California remote employee.
• Waiting until someone quits to notice $200 of unpaid premiums still sitting open.

Pay the wages, then print the wages

The cascade stops when the pay is correct and the stub can prove it. Close premiums and overtime shortfalls while people still work there, itemize them clearly, and treat exit balances as urgent — not paperwork for next quarter.