Read your own wage statement against §226(a), one item at a time.
A wage statement is the one document a plaintiff's firm can read without asking anyone a question. Pick the busiest stub you issued last quarter, read it in the order it prints, and ask nine questions of it. Two of the nine are set once, when payroll is configured, and rarely read again, and neither one is about the math.
Most owners read a pay stub the way the person who signs the checks reads it. Is the net right? Did the hours come through? A plaintiff's firm reads the same stub as a list. Labor Code §226(a) requires nine items on it, and each one is either on the page or it is not.
A wage statement is the itemized record §226 requires each payday — hours, rates, gross, deductions, net, the period dates, the employer's identity.
Pick the stub with the most on it
A quiet week tests almost nothing. Pick an hourly employee whose last quarter had the most going on: overtime, and double time if you pay it; a shift differential; a meal or rest premium; a bonus; a deduction beyond taxes; piece-rate pay if anyone earns it. A forklift operator on the night dock shift at a Stockton warehouse is a better test than the office manager.
Pick it from after the last change you made to payroll: a new payroll system, a new entity, a new location, a merger. Defects come in with changes, and they print on every stub after.
The header: who pays, who is paid, and for when
Three of the nine items usually sit at the top of the stub. Read them first.
Item 8, the employer. The name and address of the legal entity that is the employer. Is the name on the stub the entity that employs this person, spelled the way the Secretary of State has it? A trade name is a different name. So is the parent company's, and so is the name the business had before it converted from an LLC to a corporation. Is there an address at all?
Item 7, the employee. The employee's name, and only the last four digits of the Social Security number or an employee ID number that is not the Social Security number. A stub that prints the full number has a different and worse problem.
Item 6, the period. The inclusive dates of the period the employee is being paid for: a start date and an end date. A stub that prints only the pay date, or only the last day of the period, is missing half of the item.
The middle: hours and rates
Item 9, every rate. All the hourly rates in effect during the period, each with the number of hours worked at it. Read this item with the time record for the same period beside it. Overtime at its rate, with its hours. Double time, if there was any. The night differential. A premium hour paid under its own earning code and printed on its own line shows the reader what was paid and at what rate. Folded into a line called "other earnings," it shows neither.
Item 2, total hours. Total hours worked in the period, as one number. Subdivision (j) leaves this item off the stub for certain exempt employees.
Item 3, piece rate. Where the employee is paid by the piece, the number of units earned and the rate for each. Piece-rate work brings its own required lines for rest and recovery time and for nonproductive time, under §226.2, and the piece-rate post reads those.
The bottom: gross, deductions, net
Item 1, gross wages earned. The total earned in the period, before anything comes out.
Item 4, all deductions. Every deduction. Deductions made on the employee's written orders may be grouped and shown as one item; everything else is listed. On most stubs, tax withholding prints by type. A line called MISC, with no written order from the employee behind it, is the line to question.
Item 5, net wages earned. What the employee takes home.
Two items are set once and never read again
Deductions and the employer's name drift for the same reason. Both are set once, when payroll is configured, by whoever configured it, and nobody reads them again. Then the business adds an entity, changes its name, or brings deduction codes over from an old system, and the stub keeps printing what it was first told. From that day on, every stub carries the same defect.
That is why the busiest stub and the most recent change are the two places to look first.
A line the nine items do not list
Many California stubs carry a tenth line that §226(a) does not name. Labor Code §246 requires the employer to show each employee's available paid sick leave every payday, either on the wage statement or in a separate writing given with the wages. If the stub carries it, read it: does the balance move from one period to the next? If it does not, someone in the office should be able to hand you the separate writing.
What the stub cannot tell you
A stub with all nine items can still be wrong. If the time record shows 46 hours and the stub shows 44, every item is present and two hours are missing. If overtime was paid at one and a half times the base rate and a bonus was left out of the rate, the rate line is present and the rate is low. Reading against §226(a) checks that the items are there. Checking that they are right means reconciling the stub to the time record and the payroll register, and that is a separate job.
What a missing item costs, and what fixes one
The statute judges the stub on its face. Section 226(e)(2)(B) deems an employee injured where the employee cannot determine the required information "from the wage statement alone." A reconciling document kept somewhere else does not repair the stub.
The same test runs through PAGA (Labor Code §2699), California's private-enforcement law, under which an aggrieved employee may pursue civil penalties, the amounts a court can award, on behalf of themselves and other current or former employees. An aggrieved employee — the one who may bring a PAGA action — is one who personally suffered each of the violations alleged (§2699(c)(1)). For most wage-statement defects the only PAGA penalty is $25 for each aggrieved employee per pay period, where the employee could promptly and easily determine the accurate information from the wage statement alone; that rate does not apply where no wage statement was provided (§2699(f)(2)(A)(i)). That is a sentence about the statute. It is not an estimate of anything you owe, and nothing here multiplies it.
The audit reaches §226; the signature does not. A worker's sign-off is a record about breaks and hours. It is not the wage statement, and the test is the wage statement alone. What reaches a stub is a recurring audit: a sample of stubs read against the nine items on a schedule, each gap opened as an item, and each item closed with the payroll change that fixed it and the date the change took effect.
One stub is enough to start, provided it is the busiest one. Bring it, with the payroll system's list of earning and deduction codes, to a free 30-minute call, and we will read it with you against the nine items and mark each one we can find and each one we cannot. Whether a gap is a violation is your counsel's call, and fixing the stub is a job for your payroll system.
Free · 30 minutes. If it fits, the next step is the records diagnostic, a fixed fee quoted on the call, and anything paid after that is a separate agreement you sign first.