California Pay Transparency Law: A Compliance Guide for Employers

The Compliance Clock Is Ticking — And Each Posting Is Its Own Exposure

Picture this: a 40-person professional-services firm in San Jose has been growing steadily. The HR manager — who is also the HR department — just posted the same software engineer opening on LinkedIn, Indeed, and the company's own careers page. Three platforms, one role, one morning's work.

What she may not realize is that under California's pay transparency law, if any of those three postings is missing a compliant salary range, each one is a separate violation — three penalty events from a single hiring decision, before any candidate has even applied.

California has built one of the most detailed, most actively evolving pay-transparency frameworks in the country. Getting it right is not a one-time project; it is an ongoing operational commitment. This guide explains exactly what the law requires, who it covers, how it has changed, and what a defensible compliance posture looks like in 2026.

What California's Pay Transparency Law Actually Requires

The foundation is SB 1162, which took effect January 1, 2023. It extended California's pay-scale disclosure requirements in two significant directions.

For job postings: Any employer with 15 or more employees must include the pay scale — meaning the salary or hourly wage range — in all job postings for open positions. This applies whether the posting is made by the employer directly or through a third-party platform.

For current employees: Any employee may request the pay scale for their own position at any time. Employers must provide it — in writing — within a reasonable timeframe.

For pay data reporting: Employers with 100 or more employees must submit annual pay data reports to the California Civil Rights Department. Separately, employers with 100 or more employees hired through labor contractors must submit a distinct labor contractor pay data report. These reports are due the second Wednesday of May each year.

Each of these obligations is independent. A company can comply perfectly on job postings and still face enforcement risk if its pay data report is late, incomplete, or missing.

SB 642: What Changed in 2026

California does not let its pay transparency requirements sit still. SB 642, effective January 1, 2026, refined SB 1162 in two important ways.

First, the definition of "pay scale" tightened. Under SB 1162, the term was interpreted broadly; SB 642 defines it explicitly as a good-faith estimate of the salary or hourly wage range that the employer reasonably expects to pay for the position at the time of posting. This matters operationally: a range so wide it is meaningless (e.g., "$50,000–$250,000 for an entry-level coordinator") is unlikely to satisfy the good-faith standard, and it exposes the company to the argument that no meaningful range was disclosed.

Second, the statute of limitations extended for willful violations. Under the original statute, plaintiffs had three years to bring a civil action. SB 642 extends that window to six years for willful violations. That is a meaningful change in litigation exposure for employers who knowingly post without a compliant range.

Practical implication: A pay range posted today in bad faith — a placeholder range that has no relationship to what you actually intend to pay — could be the basis of a lawsuit filed as late as 2032.

Who Is Covered

Employer size threshold: 15 or more employees triggers the job-posting salary range requirement. Employee count is calculated across all of the employer's employees — not just those in California — so a 20-person company headquartered in Texas with two California employees must comply when posting roles that a California resident could fill.

Role type: The requirement applies to open positions — roles that are being posted to attract candidates. Promotions or transfers offered exclusively to current employees through a non-public process are handled differently, though the employee's right to request their own pay scale on request remains in place.

Third-party postings: If you send a job description to a staffing agency or recruiting platform, the obligation travels with the posting. The employer — not the platform — is responsible for ensuring the range appears. Many platforms have built compliance workflows, but verifying that the range is actually visible to candidates remains the employer's burden.

Remote roles: California has taken the position that if a role could be filled by a California-based employee — including a fully remote role — the posting must include a pay range. This is the most aggressive interpretation in the country, and it is the one to plan around.

If you are building out your employer footprint and need a broader map of where salary disclosure requirements now apply, see our state-by-state pay transparency law guide.

What the Penalties Look Like

California enforces through the Labor Commissioner and through private civil action. The numbers are material.

For job posting violations under Labor Code §432.3, civil penalties range from $100 to $10,000 per violation, with escalating fines for subsequent violations. Because each non-compliant posting is its own violation event, a company that posts the same non-compliant listing across five job boards before anyone flags it faces potential exposure of up to $50,000 from a single hire cycle — before any private litigation.

For pay data reporting failures under Government Code §12999, administrative penalties run $100 to $200 per employee for employers that fail to file or file late.

SB 642's six-year statute of limitations for willful violations compounds the financial risk: the clock on past non-compliance does not reset when a company discovers the problem and fixes the posting going forward.

For a deeper explanation of how California enforcement works in practice — and how it compares to other states' penalty structures — see pay transparency fines explained.

The "Good-Faith Estimate" Standard: What It Means in Practice

The requirement is not to post a salary range. The requirement is to post a good-faith estimate of what you actually expect to pay. That is a higher bar than it sounds.

A defensible good-faith range has three characteristics:

1. It is anchored to real data. A range that floats in isolation from market data is hard to defend as "good faith." The U.S. Bureau of Labor Statistics Occupational Employment and Wage Statistics (OEWS) program publishes median and percentile wages for approximately 830 occupations across the nation, states, and metro areas — updated annually. Using a BLS OEWS figure as your range midpoint and building a spread around it is both methodologically sound and documentable.

Worked example: Suppose you are posting a mid-level HR Generalist role in the San Francisco Bay Area. You pull the relevant OEWS 10th, 25th, 75th, and 90th percentile wages for the SOC code. You decide your role sits at roughly the 50th–75th percentile for the metro, reflecting your total-comp positioning. You build a band with a range spread of roughly 50% (band minimum = midpoint ÷ 1.25; band maximum = midpoint × 1.25). The result is a defensible, documented range tied to a public government source — not a number you pulled from a conversation. (See our guide to what is a posting-safe salary range for the full band-math explanation.)

2. It is specific to the role and level, not to the job family. Posting a $60,000–$150,000 range for a position that your internal leveling framework places clearly at a single level is not a good-faith estimate for that posting — it is the range for your entire job family. California's enforcement posture is moving toward specificity.

3. It is consistent with what you pay incumbents. The most common red flag in California pay-scale litigation is a posted range that bears no relationship to actual pay. If your current HR Generalists earn $78,000–$95,000 and your posting shows $55,000–$130,000, that inconsistency is a discoverable fact in any civil action.

Building a structured compensation framework — defined job levels, documented salary bands, consistent methodology — is the operational foundation of a defensible good-faith estimate. Without a band structure, a good-faith range is difficult to construct and nearly impossible to defend. Our complete guide to job band structure walks through the framework from scratch.

Pay Data Reporting: The Other Obligation

SB 1162's pay data reporting requirement is often overshadowed by the job-posting rules, but it carries its own compliance burden.

Employers with 100 or more employees must submit to the California Civil Rights Department an annual pay data report breaking down employee headcount by job category, pay band, race/ethnicity, and sex. The report must cover workers both paid by the employer directly and — separately — workers hired through labor contractors if that population reaches 100 or more.

The filing deadline is the second Wednesday of May each year. Late filers and non-filers face per-employee administrative penalties. The Civil Rights Department publishes aggregated data from these reports, meaning your pay distribution — at least in aggregate — becomes a matter of public record.

For companies that have never built a formal compensation structure, preparing these reports often reveals internal pay equity gaps that were not visible in a spreadsheet environment. Addressing those gaps proactively, before the report is filed, is strategically important.

Building a Compliance Process That Holds

One-time fixes do not hold. California's pay transparency requirements create recurring compliance obligations tied to every new posting, every new hire, every annual pay data report. A durable process has four components:

Structured salary bands. If you do not have documented, approved salary ranges for every role you post, you cannot post a compliant California range. The band is the source of truth; the posting is downstream of it.

A posting review step. Before any job description leaves your ATS or goes to a job board, someone verifies that the pay range is present, that it matches the approved band for that level, and that it appears on all channels simultaneously. This step catches the multi-platform violation risk before it becomes multi-event exposure.

A documentation log. Under California law, employers should retain records of pay scales provided to employees on request. While the statute does not specify a retention period for job posting ranges, retaining records consistent with your pay data reporting obligations (generally three years for pay records) is a defensible baseline.

Annual band review. SB 642's good-faith standard implies that your range reflects what you actually expect to pay at the time of posting. If your bands were last updated two years ago and the market has moved, your ranges are stale — and potentially no longer "good faith."

Visit our pay transparency compliance hub for a full operational checklist covering California, Colorado, New York, and the other active jurisdictions.

Get Compliant Faster with the Pay Transparency Job Posting Kit

Building defensible salary ranges from scratch — anchored to BLS OEWS data, formatted for posting compliance, and organized by job level — takes meaningful time. The Pay Transparency Job Posting Kit gives you the templates, the worked methodology, and the documentation structure to build compliant California ranges without starting from a blank spreadsheet.

Download the Pay Transparency Job Posting Kit →

If you are ready to move beyond one-off templates and into a structured compensation system that keeps every future posting compliant — including band documentation, midpoint tracking, and range-spread logic — start a free trial of Job Band Builder.

This article describes the law as understood from publicly available statutory and regulatory sources as of the date of publication. It is not legal advice. California's pay transparency requirements are subject to enforcement interpretation and regulatory guidance. Verify your specific compliance obligations with employment counsel or the California Civil Rights Department before taking action. ```