California Pay Stub Compliance: All Nine LC §226(a) Fields, Sick Leave, and SDI

A California pay stub is a legal document with nine required fields, a tenth requirement borrowed from a different statute, and a penalty structure that applies per employee, per pay period. For a PEO, which issues every one of those stubs for every co-employed worker in the state, it is the compliance obligation with the highest frequency and the lowest tolerance for error. A handbook can be wrong for a year before anyone notices. A pay stub is wrong twenty-six times a year, for every employee.

This post walks through what the statute requires, checked against the text of Labor Code §226 and §246, the 2026 SDI rate, and where the exposure comes from. It is written for PEO operations people and is not legal advice.

The nine items in §226(a)

Labor Code §226(a) requires that every employer, at the time wages are paid, furnish an accurate itemized statement in writing showing the following nine items. The language below is paraphrased closely from the statute.

1. Gross wages earned. 2. Total hours worked by the employee, with an exception for exempt salaried employees under subdivision (j). 3. The number of piece-rate units earned and any applicable piece rate, if the employee is paid on a piece-rate basis. 4. All deductions, provided that deductions made on the employee's written orders may be aggregated and shown as one item. 5. Net wages earned. 6. The inclusive dates of the period for which the employee is paid. 7. The name of the employee and only the last four digits of their social security number, or an employee identification number other than a social security number. 8. The name and address of the legal entity that is the employer, with additional requirements for farm labor contractors. 9. All applicable hourly rates in effect during the pay period and the corresponding number of hours worked at each rate, with additional per-assignment requirements for certain temporary services employers.

The ones that produce litigation are the ones that are easy to get almost right.

Where stubs go wrong

Item two, total hours, fails when the stub shows hours by earning code but not a total, or shows a total that does not reconcile to the sum of the rates in item nine. It also fails when an employer treats a non-exempt salaried employee as exempt and omits hours entirely.

Item four, deductions, fails when a stub shows a combined "other deductions" line without the employee's written authorization to aggregate, or when a pre-tax benefit deduction is shown in a way that does not let the employee identify it.

Item six, pay period dates, fails more often than anyone expects. A stub that shows the pay date but not the start and end of the period, or one where the period shown does not match the hours worked, is a §226(a)(6) problem, and a common one on off-cycle checks, retro pay, and final paychecks.

Item seven, the identifier, fails when a stub shows more than the last four digits of the social security number. The statute is explicit, and a partially masked SSN that shows more than four digits is noncompliant regardless of intent. In HALO IQ the identifier is masked at the display layer, not left to the template.

Item eight, the employer's legal name and address, is the item specific to PEO. The stub must show the name and address of the legal entity that is the employer. In a co-employment arrangement, the question of which entity that is, and whether both appear, is one the PEO's counsel has answered in the CSA and the stub must reflect that answer consistently. A stub that shows a DBA with no legal entity, or a PEO's trade name with no address, is a problem that repeats on every stub in the state.

Item nine, rates and hours at each rate, is where the regular rate of pay comes in. If an employee earned overtime, a shift differential, or a nondiscretionary bonus that changed the regular rate, the stub has to show each rate in effect and the hours at that rate. A stub that shows a single blended rate for a week with overtime is wrong. A stub that shows the overtime hours but at the base rate rather than the regular rate, because the bonus was not folded in, is wrong in a way that also underpays the employee.

Meal and rest period premiums are paid at the regular rate as well and belong on the stub as their own line. This is where §226 meets PAGA: an employer that gets the regular rate wrong has a wage-and-hour violation and, on the same stub, a wage statement violation, and the second is often easier to prove.

The tenth requirement: paid sick leave balance under §246

Labor Code §246 is the paid sick leave statute, and subdivision (i) requires an employer to provide written notice of the amount of paid sick leave available, either on the itemized wage statement or in a separate writing provided on the designated pay date with the payment of wages. In practice every PEO puts it on the stub, because a separate writing every pay date is an invitation to miss one.

The balance shown has to be right. Under §246, employees accrue at a rate of not less than one hour for every 30 hours worked, or the employer may front-load the full amount at the start of each year, where the full amount is defined as five days or 40 hours. Local ordinances in several California cities require more, and an employee who works in one of those cities is entitled to the local amount. An employer providing unlimited paid sick leave or unlimited PTO may satisfy the notice by writing "unlimited" on the stub.

The practical failures are a balance that lags the accrual because the accrual job runs after the stub is generated, a balance that ignores the local ordinance for the employee's work location, and a balance omitted entirely for covered part-timers. A PEO with clients in multiple cities needs the balance computed per employee per work location, not per client.

SDI for 2026: 1.30 percent, no wage cap

California State Disability Insurance is an employee-paid withholding, and for 2026 the rate is 1.30 percent, up from 1.20 percent in 2025, as reported by CalChamber from the EDD's annual announcement. There has been no taxable wage limit since January 1, 2024, so the withholding applies to all subject wages at every income level.

SDI is a deduction under item four and has to be shown as its own identifiable line. The failure here is rarely the rate; it is a stub that still shows a year-to-date cap, or a template that labels the line so the employee cannot identify it as SDI.

The penalty structure

Labor Code §226(e) provides that an employee who suffers injury as a result of a knowing and intentional failure to comply with subdivision (a) may recover the greater of actual damages or $50 for the initial pay period in which a violation occurs and $100 per employee for each violation in a subsequent pay period, not to exceed an aggregate penalty of $4,000, plus costs and reasonable attorney's fees.

Two parts of that structure matter for a PEO.

The first is "injury." The statute deems an employee to have suffered injury if the employer fails to provide a wage statement at all, or if the statement is missing or inaccurate on any of the nine items and the employee cannot promptly and easily determine the required information from the statement alone. "Promptly and easily" means a reasonable person could determine it without reference to other documents. A stub that requires the employee to pull up a separate portal to figure out their pay period is a stub that fails this test.

The second is "knowing and intentional." The statute says this does not include an isolated, unintentional payroll error due to a clerical or inadvertent mistake, and the factfinder may consider whether the employer adopted and followed compliant policies and procedures before the alleged violation. For a PEO this is the defense: a documented, consistently applied, and periodically tested wage statement process is the difference between an isolated error and a knowing failure. A template defect that repeats on every stub for a year is not an isolated error.

The $4,000 aggregate cap applies per employee under §226(e). It does not cap PAGA civil penalties for the same underlying violations, which are assessed separately and, under the post-reform structure of AB 2288 and SB 92, are reduced for employers that took reasonable steps to comply. Wage statement violations are among the most commonly pleaded PAGA claims precisely because every stub is a discrete, documented violation and the class is every employee who received one.

Why PEO payroll must get this right every cycle

The arithmetic of exposure is what makes this a PEO problem rather than a client problem. A single SMB with 40 employees and a template defect has 40 employees times 26 pay periods of violations per year. A PEO with a few hundred California clients on the same stub template has that multiplied by every client, and the defect is the PEO's. The co-employment relationship means the PEO generated the stub.

That is why the stub cannot be a template someone edits. It has to be rendered from a payroll engine that holds every required field as structured data, computes the sick leave balance per work location, computes the regular rate before the overtime line, masks the identifier at the display layer, and refuses to issue a stub missing a required item.

The audit should be continuous. Every pay run, a sample of stubs should be checked against the nine items and the sick leave notice, with results logged, and a failed check should stop the run before the stubs go out. That is the policy-and-procedure record §226(e) tells the factfinder to consider, and the only kind that holds up.

Where this lives in HALO IQ

PAGA IQ models the exposure from wage statement defects alongside the underlying wage-and-hour violations, per employee, with the math shown, so a PEO can see what a template defect would cost before a demand letter arrives. The California-specific rules, the nine items, the §246 notice, and the 1.30 percent SDI rate with no wage cap, are maintained as data rather than buried in a template. The point is not that software makes the stub compliant. The point is that the stub comes from a record where every required field exists, is validated, and can be audited, which is the only way to be right twenty-six times a year for every employee in the state.