SB464 requires private employers meeting a size threshold to submit an annual, establishment-level pay data report to the state department that captures demographic and pay information across job categories. The rule covers workers on the employer’s payroll and, separately, workers supplied through labor contractors; employers must disclose contractor names and the law treats contractor-supplied data as reportable.
The statute gives enforcement and investigatory agencies a structured dataset to detect pay disparities, while also imposing operational and data-security responsibilities on affected employers and contractors. The bill balances confidentiality protections with an express authority to publish aggregate statistics and to pursue noncompliant firms through court orders and civil penalties.
At a Glance
What It Does
Requires private employers with 100 or more employees to submit annual pay-data reports to the department that break out counts and pay information by race, ethnicity, and sex across detailed job categories and pay bands. It also mandates separate reports and contractor-name disclosure for workers supplied through labor contractors.
Who It Affects
Private employers of 100+ employees (reporting at the establishment level), labor contractors who supply workers to those employers, human-resources and payroll teams, and state enforcement agencies that will use the data for investigations and aggregate analysis.
Why It Matters
The bill creates a standardized, multi-year dataset for pay-equity enforcement and public policy analysis while attaching civil penalties for noncompliance. Compliance will require HR systems changes, new vendor and contractor data flows, and careful handling of sensitive demographic data.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
SB464 creates a recurring, structured reporting obligation for large private employers. Each year an employer must produce an establishment-level file that enumerates employees by race, ethnicity, and sex across a long list of occupational categories, and maps each employee’s annual earnings into the Bureau of Labor Statistics Occupational Employment Statistics (OES) pay bands.
The law requires employers to calculate mean and median hourly wages within each job-category and demographic cell, and to report total hours worked for employees in each pay band.
The statute prescribes how employers must define and count employees for reporting purposes. For headcounts by job category and demographics the employer builds a single “snapshot” count from one pay period chosen between October 1 and December 31 of the reporting year.
For pay-band and wage calculations the employer uses W-2 reported earnings for the entire calendar year for every individual included in that snapshot, even if the worker did not work the full year. Employers with multiple establishments must file separate reports for each establishment and include the employer’s NAICS code.SB464 treats workers supplied through labor contractors as reportable employees for the client employer and requires the client to submit a separate report covering those contractor-supplied workers; the client employer must also disclose the ownership names of all labor contractors used.
Labor contractors must supply the pay data necessary for client employers to comply, and the statute gives courts the power to apportion penalties to contractors that fail to provide required data. The bill also requires that any demographic information collected be stored separately from personnel records.On enforcement and data governance, the department may seek court orders to compel filing and recover associated costs; courts are authorized to impose civil penalties (with different maximum amounts for first and subsequent failures) payable to the Civil Rights Enforcement and Litigation Fund.
The statute treats individually identifiable report data as confidential and exempt from the California Public Records Act, but it permits the department to publish aggregate reports designed to prevent associating data with a specific person or business. The department must retain reports for at least ten years and may request employer contact data from the Employment Development Department to identify covered businesses.
Finally, the section contains an operative date and a saving clause preserving earlier filing requirements as amended by prior legislation.
The Five Things You Need to Know
Filing timetable: employers must submit annual reports on or before the second Wednesday of May covering the preceding calendar year.
Coverage threshold and contractors: the filing threshold is 100 or more employees; employers also must file a separate report for employees hired through labor contractors and disclose the contractors’ ownership names.
Data required: counts by race, ethnicity, and sex across 23 occupational categories, counts by BLS OES pay bands, mean and median hourly rates for each demographic/job cell, total hours worked per pay band, and the employer’s NAICS code.
Counting and earnings method: headcounts are a single pay-period “snapshot” chosen between October 1 and December 31 of the reporting year; pay figures come from each employee’s IRS Form W-2 for the full calendar year.
Enforcement and secrecy: the department can seek court orders and recover costs; courts may impose civil penalties up to $100 per employee for first failures and up to $200 per employee for subsequent failures (payable to the Civil Rights Enforcement and Litigation Fund); individually identifiable data is confidential but the department may publish aggregate reports; the department must retain reports for at least 10 years.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Who must file and contractor reporting obligation
This subsection sets the core filing duty: private employers meeting the 100-employee threshold must submit annual pay data reports covering the previous calendar year. It creates a parallel duty to submit a separate report for workers supplied through labor contractors and requires employers to list the ownership names of all contractors used. Practically, the provision forces employer–contractor data flows: client employers will need contractual or operational access to contractor payroll and demographic data to comply.
Required data elements and metrics
This section enumerates the report fields: employee counts by race/ethnicity/sex across detailed occupational categories, counts within BLS OES pay bands, median and mean hourly rates for each demographic–job cell, and total hours worked per employee per pay band. Including both distribution into pay bands and central-tendency metrics means the dataset supports multiple analytical uses—from detecting concentration in low pay bands to measuring typical wage gaps.
Snapshot and W-2 methodology
The bill prescribes a two-step counting and earnings method: headcounts come from a single payroll period between October 1 and December 31, while pay calculations use W-2 earnings for the full calendar year for those snapshot employees. That approach is intended to align headcount and annual earnings, but it creates seasonality and part-year employment considerations employers must operationalize in payroll and HR systems.
Establishment reporting, remarks, and format
Employers with multiple establishments must file separate reports for each site and include the establishment’s NAICS code. The statute also provides an optional clarifying-remarks field and requires submissions to be in a machine-searchable, sortable format. Those requirements push employers toward standardized, exportable data outputs rather than narrative or PDF-based filings.
Enforcement pathway and civil penalties
If an employer fails to file, the department may seek a court order to compel compliance and recover its costs. Courts may impose civil penalties not to exceed $100 per employee for a first failure and $200 per employee for subsequent failures, payable to the Civil Rights Enforcement and Litigation Fund. Where noncompliance results from a labor contractor’s failure to provide data, the court may apportion penalties to that contractor.
Confidentiality, permitted use, and aggregate publication
Individually identifiable report data is confidential and exempt from public-records disclosure; officers cannot publicly release such data before enforcement actions except as necessary in proceedings. The department is explicitly allowed to develop and publish aggregate reports so long as they are reasonably calculated to prevent associating data with a particular person or business. This creates a legal boundary between investigation-level confidentiality and public transparency at an aggregate level.
Retention, definitions, and interagency cooperation
The department must retain submitted pay-data reports for at least 10 years. The statute defines key terms—'employee' tied to payroll and Social Security withholding, 'labor contractor' as any supplier of workers for the client’s usual business, and 'establishment' as the unit producing goods or services. The Employment Development Department must provide the department, within 60 days of request, names and addresses of businesses with 100+ employees to identify covered employers.
Savings clause and operative date
The bill preserves earlier reporting requirements created under prior legislation for 2021–2022 filings so those enforcement rights remain intact. It also sets the section’s operative date: the reporting regime becomes operative on January 1, 2027, giving employers and contractors time to adjust systems and processes.
This bill is one of many.
Codify tracks hundreds of bills on Employment across all five countries.
Explore Employment in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Workers subject to pay disparities — employees (especially women and people of color) gain a state-collected dataset that can surface systematic wage gaps and underpin enforcement or collective actions.
- Civil-rights and labor enforcement agencies — the Division of Labor Standards Enforcement and the department receive standardized, multi-year data to prioritize investigations and measure systemic pay-equity issues.
- Researchers and policy advocates — aggregate, long-term data by occupation, pay band, and demographics enables independent analysis and benchmarking of pay-equity progress.
- Employers that proactively manage pay equity — firms with rigorous pay-audit programs can use the reporting exercise to identify issues early and reduce litigation risk by documenting remediation steps.
Who Bears the Cost
- Large private employers (100+ employees) — increased compliance costs for HR, payroll, and IT to extract, reconcile, anonymize, and submit detailed demographic and W-2-based pay data for each establishment.
- Labor contractors — must supply pay and demographic data to client employers and face potential apportionment of civil penalties if they refuse or provide incomplete data.
- The state department and DLSE — will need funding and technical capacity to process large, machine-readable datasets, maintain confidentiality controls, run aggregate analyses, and enforce noncompliance.
- Employers with small or seasonal workforces — may face difficulties with the snapshot/W-2 methodology that can overstate pay disparities or misrepresent turnover, requiring legal and analytic support to comply.
Key Issues
The Core Tension
The central tension is between transparency for detecting and remedying pay discrimination and the privacy, business-confidentiality, and administrative burdens that large-scale mandatory reporting imposes: collecting the granular demographic and payroll data needed to find pay gaps risks exposing sensitive information and imposing significant costs that could alter employer behavior in ways that complicate the law’s enforcement goals.
SB464 presses a familiar set of trade-offs: it gives enforcement agencies rich, standardized data for spotting systemic pay disparities, but doing so requires collecting and storing sensitive demographic and payroll data, raising re-identification and privacy risks. The law mitigates that with express confidentiality protections and an aggregate-publication carve-out, but operational safeguards (access controls, data minimization, and secure transfer protocols) are left to implementing agencies and employers to design.
The statute’s technical rules create implementation wrinkles. The snapshot (a single pay period between October 1 and December 31) paired with reliance on W-2 annual earnings can distort measures for seasonal, part-time, or newly hired workers and may produce apparent gaps driven by turnover rather than ongoing pay practices.
Apportioning penalties to labor contractors raises contractual and evidentiary questions: who bears liability when records differ, and how will courts assess whether a contractor’s failure caused an employer’s noncompliance? The bill also presumes employers can obtain demographic categories consistent with reporting needs; in practice employers must reconcile voluntary employee self-identification, state/federal category definitions, and local privacy rules.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.