InCruiter: Tech Driven Hiring Solution
California Pay Transparency Law (SB 1162): The Complete 2026 Employer Compliance Guide | featured image
Talent Acquisition

California Pay Transparency Law (SB 1162): The Complete 2026 Employer Compliance Guide

SB 1162 is actually two separate obligations bundled into one law — a job posting salary range requirement and a considerably more consequential pay data reporting requirement most employers underweight. This guide covers exactly what each requires, what 'good faith' salary range actually means in enforcement practice, the real penalty structure for getting it wrong, and how to build a compliance process that holds up for both requirements at once.

September 3, 2026 10 min read 2,400 words

What you'll learn

  • What SB 1162 Actually Requires — Two Separate Obligations, Not One
  • The Job Posting Requirement: What 'Good Faith' Actually Means in Practice
  • Pay Data Reporting: The Requirement Most Employers Underweight
  • Penalties and Enforcement: What Actually Happens When Employers Get This Wrong
  • Building a Compliance Process That Actually Holds Up

California's SB 1162 gets referenced constantly as a single pay transparency law, and that framing causes real compliance gaps, because it actually bundles two distinct obligations with different triggers and different enforcement mechanisms: a job posting salary range requirement that catches far more out-of-state employers than most realize, and a pay data reporting requirement to the California Civil Rights Department that carries meaningfully larger financial exposure and functions, in practice, as a built-in pay equity audit most employers aren't prepared for. This guide breaks down exactly what each obligation actually requires, what the 'good faith salary range' standard means once you look at how it's actually been enforced, the specific penalty structure for both the posting and reporting requirements, and how to build a single compliance process that holds up for both rather than treating job postings as the whole of what SB 1162 demands.

Share

What SB 1162 Actually Requires — Two Separate Obligations, Not One

Quick answer

California's SB 1162, effective January 1, 2023, is frequently discussed as a single pay transparency requirement, but it actually creates two distinct and separately enforced obligations that employers need to track independently: a job posting salary range disclosure requirement, and a pay data reporting requirement to the California Civil Rights Department (CRD, formerly DFEH). Treating these as one compliance task is a common and consequential mistake, since they have different triggering thresholds, different mechanics, and different enforcement consequences.

The posting requirement applies to any employer with 15 or more employees, with at least one employee located in California — including remote employees who happen to reside in California, regardless of where the company itself is headquartered. This is the detail that catches out-of-state employers most often: a company headquartered in Texas or Florida with no California office, but with even a single fully remote California-based employee, is covered the moment that employer meets the 15-employee threshold company-wide, not just in California specifically.

The pay data reporting requirement applies separately to private employers with 100 or more employees (with at least one California employee) for direct-hire employees, and to employers with 100 or more employees hired through labor contractors for a separate labor contractor pay data report. This is a materially larger compliance undertaking than the posting requirement, involving detailed workforce demographic and pay-band reporting submitted annually to the CRD, and it deserves its own dedicated compliance process rather than being treated as an afterthought to the more visible job-posting rule.

The Job Posting Requirement: What 'Good Faith' Actually Means in Practice

Quick answer

Employers covered by the posting requirement must include the salary or hourly wage range they reasonably expect to pay for the position in any job posting, including postings distributed through a third-party recruiter or staffing agency acting on the employer's behalf — the obligation doesn't disappear just because a recruiting agency, rather than the employer directly, is the one publishing the listing. The statute requires the range to reflect a genuine 'good faith' expectation of what the employer would actually pay, not an artificially wide range designed to technically comply while disclosing nothing meaningful.

This 'good faith' standard has real teeth in practice. The CRD and worker advocacy groups have specifically scrutinized postings with implausibly wide ranges — a range spanning $60,000 to $250,000 for the same individual contributor role, for instance — as a functional attempt to circumvent the law's actual purpose while nominally satisfying its literal text. Employers whose compensation philosophy relies on very broad, multi-level salary bands need to publish the specific range applicable to the actual level and scope of the posted role, not the entire band spanning multiple levels, which requires genuine coordination between recruiting, HR, and finance before a requisition opens rather than defaulting to whatever band happens to already exist in the HRIS.

The posting requirement also extends to current employees: upon request, an employer must provide an employee the pay scale for their own current position, a distinct obligation from the job posting rule that applies regardless of employer size and has existed under California law since 2018, predating SB 1162 itself. Employers sometimes correctly implement the job-posting requirement while overlooking this separate, size-independent obligation to current employees who ask directly.

SB 1162 is actually two distinct obligations bundled into one law — a job posting salary range requirement affecting essentially any employer with a single California-based remote employee, and a separate, considerably more consequential pay data reporting requirement to the Civil Rights Department that most employers underweight relative to its actual enforcement risk.

Pay Data Reporting: The Requirement Most Employers Underweight

Quick answer

The pay data reporting requirement is considerably more involved than the posting requirement, and its relative invisibility compared to job postings — which candidates and employees see directly — means many employers underinvest in the compliance process relative to its actual regulatory significance. Covered employers must submit an annual report to the CRD, due by the second Wednesday of May each year, breaking down employee counts by job category, race, ethnicity, sex, and pay band, using the same 10 job categories and 12 pay bands established under existing federal EEO-1 reporting.

SB 1162 specifically added a new, distinct reporting obligation for labor contractor employees — workers supplied to the employer through staffing agencies or similar labor contractor arrangements — requiring a separate report covering that population, submitted by the client employer, not solely by the staffing agency itself. This is a meaningful expansion that catches employers who rely heavily on contingent or contracted labor and who may not have previously needed to think about pay data reporting obligations for a workforce segment they don't directly employ.

The pay data report must also include the employer's mean and median hourly rate broken down by each combination of job category and demographic group — a level of granular disclosure that functions, in practice, as a built-in pay equity audit mechanism, since a pattern of pay disparity across a specific job category and demographic combination becomes directly visible in the submitted report itself, not just in an employer's own internal analysis. Employers who haven't run an internal pay equity audit before their first pay data report submission are, in effect, potentially disclosing a previously unidentified compliance problem directly to the state regulator rather than catching and correcting it proactively first.

Penalties and Enforcement: What Actually Happens When Employers Get This Wrong

Quick answer

The posting requirement carries a specific civil penalty structure: the Labor Commissioner can impose penalties ranging from $100 to $10,000 per violation for a job posting that fails to include a required pay scale, with no penalty for a first violation if the employer demonstrates all postings for open positions have been updated to comply — a narrow but real first-violation safe harbor that rewards prompt correction. Beyond the state's own enforcement, any person can bring a private right of action to obtain injunctive relief for violations of the posting requirement, meaning enforcement isn't limited solely to state regulatory action.

Failure to comply with the pay data reporting requirement carries its own separate penalty structure, and the CRD can seek a court order requiring compliance along with civil penalties of up to $100 per employee for a first failure to file, increasing to up to $200 per employee for subsequent failures — a penalty that scales directly and significantly with company size, making the reporting obligation a meaningfully larger financial exposure for a mid-size or large employer than the per-posting penalty structure for job listings.

Beyond the statutory penalty amounts, the practical enforcement risk includes reputational exposure from public CRD reporting and increased litigation risk connected to the underlying pay equity data itself — a pay data report that reveals a disparity pattern can become supporting evidence in a subsequent Equal Pay Act claim, which is a genuinely different and often more consequential exposure than the reporting penalty itself. Treating pay data reporting purely as an administrative filing task, disconnected from genuine pay equity analysis, misses this larger risk entirely.

Building a Compliance Process That Actually Holds Up

Quick answer

Establish a defined, documented process for setting the specific salary range attached to each individual requisition before it's posted — not a default to the broadest applicable band, but a genuine, role-specific range reflecting what the hiring team actually expects to pay for that specific opening, with the reasoning documented in case the range is ever challenged as not representing a genuine good-faith expectation. This process needs real coordination between recruiting, the hiring manager, and whoever owns compensation strategy, ideally built into the standard requisition approval workflow rather than left to individual recruiter judgment on a case-by-case basis.

Extend the same range-disclosure discipline to internal postings and promotion announcements, not just external job listings — this is one of the most commonly missed compliance gaps, since companies build a solid external job-posting compliance process while completely overlooking that the same underlying good-faith range disclosure principle, and California's separate current-employee pay scale request right, apply to internal moves and existing employees as well.

Run an internal pay equity analysis well before your first (or next) pay data report submission deadline, specifically so any disparity pattern is identified and can begin to be addressed proactively, rather than surfacing for the first time inside a report submitted directly to the state regulator. This connects directly to the broader pay equity audit discipline — see our dedicated guide on running a pay equity audit for the full methodology, including the privilege structure that protects a genuinely thorough internal audit from becoming discoverable evidence if a disparity is found and needs remediation.

If your company operates in California alongside other states, build your compliance process around the most demanding applicable requirement rather than maintaining entirely separate, disconnected processes for each jurisdiction — our broader guide on pay transparency laws across the US covers how California's requirements compare to Colorado, Washington, New York, and Illinois, and how to build a single job posting workflow that accommodates whichever specific jurisdiction's requirements are actually the strictest for a given role.

The posting requirement's 'good faith salary range' standard has already produced real enforcement action against employers who posted ranges wide enough to be functionally meaningless, which means the specific range-setting practice matters as much as the decision to disclose a range at all.

Frequently asked questions

Common questions about talent acquisition and how InCruiter helps teams solve them.

IC

InCruiter Editorial Team

AI Hiring Research · Interview Intelligence · Enterprise Talent Strategy

The InCruiter editorial team covers AI-driven hiring, interview intelligence, and modern talent acquisition strategy. Our guides draw on platform data from 2,000+ hiring teams, conversations with talent leaders, and published research in industrial-organizational psychology.

Expert reviewed Data-backed EEAT-optimized
InCruiter

Ready to put this into practice?

See how InCruiter transforms your hiring process. 30 minutes with an expert: live walkthrough of your actual use case, no slides.

No credit card required · Live demo · Dedicated onboarding support