Last updated: April 2026

Paid Sick Leave California: The Multi-State Payroll Rulebook for 2026

California paid sick leave is now 5 days per worker, not 3. Senate Bill 616 lifted the statutory floor on January 1, 2024, and most multi-state payroll systems still run the old 3-day accrual setting.

Any multi-state employer running multi-state payroll across California and neighboring states hits a bigger jolt: California stacks more local ordinances on top than any other jurisdiction in the country. Out-of-state HR leaders learning how reciprocity works between a state floor and a city ordinance usually discover that their software does the math wrong. Remote worker tax rules layer on a third complication, because a single laptop logging from Oakland triggers Oakland sick leave on top of the California base.

One more wrinkle trips up teams running payroll in more than one state. A reciprocity agreement with Arizona or Oregon covers income tax only. State tax reciprocity never touches the leave floor, and state withholding settings sit on a different axis entirely. A nonresident tax election on Form W-4 doesn't waive California paid sick leave for anyone who logs hours inside the state. The convenience of the employer rule that New York enforces is unrelated as well, so do not import that mental model to a California remote worker tax setup. Convenience of the employer doctrines from other jurisdictions are equally irrelevant to the California leave calculation.

Why the California sick-pay floor changed in 2024 and what missing it costs

Senate Bill 616 amended California Labor Code section 246 to raise the floor from 3 days to 5 days per benefit year. Roughly 17 million covered workers fall under the Healthy Workplaces Healthy Families Act, so running the old setting is not a theoretical exposure.

Backpay awards run from $1,000 to $25,000 per worker under Labor Code section 248.5. Administrative penalties tack on up to $4,000 per violation, and willful violations can double that figure during a Labor Commissioner audit.

Wage statement claims stack on top.

Section 226 requires the available leave balance to print on every pay stub or appear in a separate quarterly notice. A missing balance line costs $250 per pay period per worker, and PAGA multipliers turn a small administrative slip into a six-figure exposure fast. A 50-employee shop missing the balance line for one year owes potentially $325,000 before any underpayment claim is even filed.

Federal FMLA doesn't preempt this. FMLA only protects 12 weeks of unpaid leave for employers with 50 or more workers nationwide, while California law applies to nearly every employer with one California worker. The two regimes run concurrent for qualifying medical events but cover different ground.

California is not a 5-day state. It is a 5-day floor.

Front-loading 5 days at the start of the benefit year keeps the math clean but eliminates carryover. Accrual is cheaper at exit yet harder to administer correctly across 26 pay periods. Pick the wrong method for your workforce and you either give away too much leave or trigger DLSE complaints over carryover errors.

How accrual and front-loading actually work in California

Two methods satisfy California Labor Code section 246. Pick one per employee group, document the choice in writing, and run it consistently across the benefit year. The tradeoff between the two methods is real: neither is free, and the right pick depends on turnover and headcount volatility.

Method one is accrual. A worker earns 1 hour of leave for every 30 hours worked. Cap accrual at 80 hours total. Cap annual use at 40 hours or 5 days, whichever is greater for the worker. Carryover continues from year to year up to that 80-hour ceiling.

Method two is front-loading.

Hand out 40 hours or 5 days at the start of each benefit year, with no accrual and no carryover. The bargain is faster admin in exchange for losing the carryover backstop. A worker who quits in February walks with the full 5 days, even though only one month of work supported the grant. That is the downside you accept in return for zero ledger complexity.

A worker doing 32 hours per week accrues roughly 55 hours over a full year under method one. The 80-hour cap rarely binds for part-time staff. Full-time workers at 40 hours per week reach the 80-hour cap in roughly 60 weeks of cumulative tenure. The annual use cap of 40 hours still controls how much can be drawn in any single year, even after that 80-hour ceiling is reached.

Kin care is a separate California rule worth flagging. Labor Code section 233 lets a worker spend up to half of accrued time on a family member, not the worker alone. Family includes parents, children, spouses, registered domestic partners, grandparents, grandchildren, and siblings under the statute.

Eligibility kicks in once a worker logs 30 days in California within 12 months. Use rights start after 90 days of employment with your business, even though the accrual clock began on day one.

When this does not apply: union workers covered by a collective bargaining agreement that meets statutory equivalency are exempt from section 246. The CBA must spell out paid leave equal to or greater than the state minimum to qualify for that carve-out. In-home support service providers and certain construction trades follow separate accrual rules under section 245.5.

The 90-Day Waiting Trap That DLSE Audits Catch

Here is the catch most California businesses miss. Accrual and use are different clocks, and they do not start on the same day.

Section 246(c) lets a worker accrue statutory leave from the first hour worked. The right to actually use that leave doesn't vest until the 90th day of employment with your business. Most onboarding documents show only one of these clocks, usually the use date, which leaves accrued balances invisible to a new hire.

Auditors at the Labor Commissioner ask for the full accrual ledger from the hire date. A missing or zero balance for the first 90 days reads as a denial of accrual rights, even when actual policy is correct.

The fine for that paperwork pattern is harsh.

One real claim out of San Diego cost a 22-employee restaurant group $48,000 in backpay plus $11,000 in section 226 wage statement penalties. Workers eventually received their hours, although the violation was tied to the missing balance during the first 90 days, not the leave itself.

Cure: track accrual from hire date in the payroll system. Display the balance on every wage statement starting with the first paycheck. Show the use-eligibility date as a separate field, not as a substitute for the balance.

The 90-day clock is for use, not for the ledger.

When this does not apply: front-loaded plans bypass the accrual ledger problem because 5 days appear instantly in the system. The downside is that quitting workers walk with the full grant on day one, which gets expensive in high-turnover industries like restaurants and warehousing.

Local ordinances stack on the California state floor

Nine California cities run their own sick leave ordinances, and every one of them exceeds the state minimum on at least one variable. The state floor is a floor, not a ceiling.

San Francisco grants 1 hour per 30 worked with a 72-hour accrual cap. Use caps in San Francisco run 72 hours for businesses of 10 or more, 40 hours for smaller shops. Los Angeles requires 6 days or 48 hours per year, more generous than the California minimum. Oakland mirrors the state on accrual yet raises the use cap to 9 days for businesses with 10 or more workers.

Berkeley, Emeryville, Santa Monica, and West Hollywood each layer in their own thresholds. Berkeley caps accrual at 72 hours for larger employers and 48 for smaller. Emeryville mirrors San Francisco closely but adds family member coverage that goes beyond state law.

San Diego runs an annual 40-hour use cap with an 80-hour accrual cap. Long Beach added hospitality and grocery worker rules during 2020 that survived past the original sunset date and still apply to those industry classifications today.

The reciprocity question never gets answered cleanly. When a worker logs hours across two ordinances, whichever floor is higher controls that hour. Balance accruals can split between the two systems, although the rule applies only when work locations are recorded separately in the payroll file.

Remote worker tax location tracking matters double here. A laptop logging from Oakland for 30 minutes a day raises a state tax reciprocity question on income tax AND pulls the Oakland sick-pay ordinance into the accrual ledger. State withholding on the wage statement has to match the city floor applied to leave for the same hours. Nonresident tax status, incidentally, does not change either side of that equation.

Cost of getting this wrong is double.

Both the state Labor Commissioner and the city enforcement agency can pursue the same violation. San Francisco's Office of Labor Standards Enforcement collects independently of the DLSE, and a citation from one body doesn't bar a parallel claim from the other. Two enforcement bodies, one underpayment, two checks written.

Common Mistakes That Trigger a Labor Commissioner Claim

Five errors generate the bulk of California sick-pay wage claims at the DLSE. Each one is a payroll setup issue, not a benefits design problem. The tradeoff with airtight audit-proofing is paperwork volume, since a zero-error accrual ledger eats 15 to 30 minutes of admin per pay period for small teams.

First mistake: running the old 3-day accrual cap into 2024, 2025, or 2026 payrolls. Section 246 changed; your software did not auto-update. Pull a current pay stub and confirm the accrual rate.

Second mistake: tying use rights to part-time status. Part-timers, temporary staff, and seasonal workers all qualify once they log 30 days in California. Excluding them is grounds for a citation, although a written CBA can carve out a narrow exemption for union members.

Third mistake: requiring a doctor's note for a 1-day absence. Section 246(h) prohibits this. The statute lets workers self-certify, and demanding documentation for short absences is itself a violation that surfaces in DLSE intake interviews.

Fourth mistake: docking attendance points for sick-pay use. Section 246.5(c) bars retaliation. A no-fault attendance policy that counts protected leave hours against an employee is a per-se violation, even when the worker is never disciplined.

Fifth mistake: paying out unused balances at termination as a substitute for prior denial. Although California does not require a payout at termination of regular sick pay, retaliating with a payout instead of allowing in-service use does not cure the violation. Reinstatement of the balance is required if a worker returns within 12 months of separation.

Two of those mistakes also cross into wage theft territory. The Labor Commissioner can refer wage theft cases to the local district attorney under Penal Code section 487m. Felony filings have hit small business owners since the law changed in 2022. The limit of that referral is prosecutorial discretion: district attorneys do not pursue every referral, which is the one upside of a shaky deterrent system.

How multi-state payroll systems mishandle California sick leave

Most national vendors treat California sick leave as a generic accrual line, and the state payroll tax engine sits in the same data model. The configuration breaks in three predictable ways for any multi-state employer running a shared payroll environment.

Gusto, ADP RUN, Paychex Flex, and OnPay all let you set an accrual rate, a cap, and a use ceiling. None of them automatically apply local ordinances. An employee assigned to a Los Angeles work address still accrues at the California rate unless somebody manually overrides policy for that worker.

QuickBooks Payroll has the deepest gap. The platform lets you choose accrual or front-loading, but use eligibility date and accrual start date share one field. Setting one shifts the other, which guarantees a wage statement error for any worker hired mid-benefit-year.

Rippling handles location-based policies if a payroll admin builds the policy by hand. Out of the box, default California settings apply the state floor only. Cost is consultant time to configure each city ordinance, often 4 to 8 billable hours per location.

The same system stores Form 941 reporting, FUTA deposits, state payroll tax withholding, and state revenue filings alongside the accrual ledger. A misconfiguration in one bucket silently breaks the others. A reciprocity agreement override on a remote worker's tax profile, for example, can reset the leave accrual location flag in several platforms during the next sync.

Pulling the accrual report quarterly is the only consistent fix. Run a report by work location, compare each balance to the city ordinance for that location, and correct any deltas before the wage statement is issued. Skipping the quarterly check is the single biggest source of California leave underpayment claims at the DLSE.

One more drawback to watch.

Switching providers mid-year wipes accrual ledgers in many systems unless the migration team explicitly maps the prior balance into the new tool. A botched switch in October leaves new hires with zero visible balance for the rest of the year. The result is a wage statement audit finding the next time the Labor Commissioner pulls records.

Your next moves as a multi-state employer before the upcoming pay period

Open one current California paycheck. Confirm the accrual rate reads 1 hour per 30 worked. Confirm the available balance prints on the wage statement, not in a separate document. The tradeoff here is speed versus thoroughness: a 10-minute spot check catches 70 percent of setup errors, while a full ledger reconciliation per worker eats an afternoon.

Pull every California work address into a list. Cross-reference each address against the 9 city ordinances and flag any worker assigned to San Francisco, Los Angeles, Oakland, San Diego, Berkeley, Emeryville, Santa Monica, Long Beach, or West Hollywood. Apply the higher floor to those workers in your policy table.

Audit the wage statement template before the next run.

The available balance must appear on the stub, or your business risks $250 per pay period per worker under Labor Code section 226. Update onboarding paperwork to show two clocks: accrual start (day one) and use eligibility (day 90). Train any manager who answers new-hire questions, because verbal misstatements during week one show up in workers' phones and surface in DLSE complaints months later.

Verify state tax reciprocity, state payroll tax coding, and state withholding settings for any remote worker on the same sweep. A nonresident tax code on Form W-4 does not exempt California sick pay, and a reciprocity agreement with a neighboring state does not either. The convenience of the employer test from other states has no bearing either. Confirm Form 941 allocation and FUTA codes line up with the worker's true hours-logged state, because the audit ledger cross-checks both when a Labor Commissioner claim is filed.

The drawback of doing all this manually is admin time. Pulling reports, reconciling work locations, and rewriting onboarding paperwork eats hours that small payroll teams do not have. The cost of skipping the cleanup is bigger than the cost of doing it, though.

The official source of truth lives at DIR sick-pay guidance. Federal context for concurrent leave events lives at DOL state labor laws, useful when an FMLA event runs in parallel with a California sick-pay draw.

If you run payroll across multiple states, switch to a provider that maps location-based ordinances correctly. Review the Paid Leave Oregon sibling rulebook for parallel mechanics on a different state program, and check 2026 thresholds in the 2026 payroll tax rates reference. Confirm cross-border withholding logic in the state reciprocity guide and the state tax withholding playbook. For the broader picture, start at the multi-state payroll hub or the payroll tax hub.

This is not legal or financial advice. Consult a qualified professional for your specific situation.