Every Spring, California Asks 100+ Employee Companies for a Wage X-Ray. Most Wait Until March to Start Gathering Data.
If your company has 100 or more employees — even just one of them working from California — you owe the state a detailed breakdown of who gets paid what, sorted by race, ethnicity, and sex, across ten job categories. This isn't a survey you can skip. It's an annual filing with the California Civil Rights Department (CRD), it carries per-employee penalties for missing it, and the paperwork trail starts months before the actual deadline. If you've never built the report before, the biggest risk isn't the filing itself — it's discovering in April that your payroll and HR systems don't talk to each other cleanly enough to answer the questions the state is asking.
Here's what the pay data report actually requires, who has to file it, and how to get ahead of it instead of scrambling in the final weeks.
Who Has to File
Two overlapping employer populations are covered:
- Payroll employees: Any private employer with 100 or more payroll employees, with at least one employee based in California, must file a Payroll Employee Report.
- Labor contractor employees: Any private employer with 100 or more workers supplied through labor contractors (staffing agencies, PEOs, contract labor firms) must file a separate Labor Contractor Employee Report — even if none of those workers are on the company's own payroll.
These are counted separately. A company with 90 W-2 employees and 40 contract workers sourced through a staffing agency still has to file the contractor report, because the 100-worker threshold is met through the contractor headcount even though the payroll headcount alone wouldn't trigger it. Many first-time filers miss this and assume only their direct employees count.
Filing is done exclusively through the CRD's online portal. Submissions by email, mail, or phone are disregarded outright, and — as of a recent CRD clarification — third parties, including PEOs and outside payroll administrators, cannot file on the employer's behalf using their own credentials. The employer of record has to be the one submitting.
The Deadline Is a Moving Target — But the Snapshot Isn't
The filing deadline for 2025 reporting-year data is May 13, 2026. That date shifts slightly year to year (the statute sets it as the second Wednesday of May), so don't assume it's fixed on the calendar — check the CRD's portal each cycle rather than relying on last year's date.
What doesn't move is the underlying snapshot methodology: employers pick a single pay period sometime between October 1 and December 31 of the reporting year and use it as the basis for every headcount, demographic, and pay figure in the report. Whoever was employed during that specific pay period gets counted, regardless of whether they've since left the company or whether pay was actually disbursed during that window. Pick your snapshot period deliberately — a pay period right after a big seasonal hire or a round of layoffs will skew your report in ways that are hard to explain later if the numbers ever get scrutinized.
What Actually Goes Into the Report
For each of the ten current EEO-1 job categories (executive/senior officials, first/mid-level managers, professionals, technicians, and so on), employers report the number of employees broken out by race, ethnicity, and sex, and then further broken out by pay band. California uses 12 pay bands modeled on the U.S. Bureau of Labor Statistics' Occupational Employment Statistics survey — so an employee isn't just "counted," they're counted into a specific earnings bracket within their job category and demographic group.
On top of the headcount-by-band breakdown, employers must also calculate and report the mean and median hourly rate for every race/ethnicity/sex combination within each job category. This is the part that trips up companies relying on manual spreadsheets: it requires converting salaried annual pay into an hourly-rate equivalent using a standardized formula, consistently, across every employee in the file — not an estimate, an actual calculation the CRD can audit against your payroll records if it ever asks.
A few details that catch first-time filers off guard:
- Remote workers count where they're assigned, not where they sit. An employee assigned to an out-of-state office but working remotely from a home in California is still included in the California employer's headcount for threshold purposes — geography follows the assignment, not the WiFi router.
- Job category classification is about to change. Effective January 1, 2027, the ten EEO-1 categories are being replaced with 23 categories drawn from the Standard Occupational Classification (SOC) system, under a separate bill (SB 464). If you're building internal tooling or a template to automate this report, don't hardcode the old ten-category structure — it has an expiration date.
- Demographic data now needs its own storage lane. As of January 1, 2026, employers must store the race/ethnicity/sex data collected for this report separately from general employee personnel files — not commingled with the rest of an employee's HR record.
Penalties Are Per Employee, Not Per Filing
Missing the deadline isn't a flat fine. The CRD can seek civil penalties of $100 per employee for a first failure to file and $200 per employee for any subsequent failure — and "per employee" means the number scales with your headcount, not with the number of forms you skipped. For a company with 250 employees, a first missed filing alone carries a maximum exposure in the tens of thousands of dollars, before accounting for the Labor Contractor Employee Report if that also goes unfiled.
The CRD can pursue these penalties in a civil action, and — notably — there's no "clean hands" exception left in the statute for employers who simply didn't realize they crossed the 100-employee threshold mid-year. If your headcount grew past 100 sometime in the reporting year, the obligation attaches; ignorance of the threshold isn't a defense.
This Is Not the Same Thing as the Salary-Range Law
California employers already juggle a separate pay transparency requirement: job postings for positions that could be filled in California must disclose a salary or hourly-rate range, and employers with 15 or more employees have to provide pay scales to current employees on request. It's easy to lump that requirement in with the pay data report because both involve the word "pay" and both come from the same broader push for wage transparency, but they're different obligations with different triggers, different thresholds, and different enforcement bodies to track.
The salary-range law is about what you disclose publicly before someone is hired. The pay data report is about what you disclose privately to a state regulator, after the fact, in aggregate, broken out by demographics. A company can be fully compliant with one and still miss the other — they don't share a filing calendar, a headcount threshold, or a portal. If you've already built a process for the job-posting disclosure, don't assume it covers your pay data reporting obligation; treat them as two separate compliance checklists with two separate owners.
Why This Report Is Harder Than It Looks on Paper
On the surface, this looks like an HR compliance task with nothing to do with accounting. In practice, the report is only as good as the underlying pay data, and pay data lives in whatever system reconciles your payroll runs — which is often a patchwork of a payroll processor, a spreadsheet tracking bonuses and commissions, and a general ledger that was never designed to answer "what was this person's actual hourly-equivalent rate in the fourth quarter." Companies that keep clean, auditable financial records — where every payroll disbursement, bonus, and contractor payment is tagged and traceable back to a specific pay period — can pull the numbers for this report in an afternoon. Companies that reconstruct payroll history from bank statements and memory spend weeks on it, and often still second-guess the final numbers.
That gap tends to show up first in accounting practices, not HR software. If your books can't tell you, without manual reconstruction, exactly what every employee and contractor was paid during a specific week last October, the pay data report is going to be painful regardless of how well you understand the CRD's rules.
Getting Ahead of Next Year's Filing
A few habits make the annual filing dramatically less stressful:
- Pick your snapshot period early and flag it in your payroll calendar, rather than scrambling to choose one retroactively in April.
- Tag contractor and staffing-agency headcount separately from payroll headcount year-round, so the 100-worker threshold for the Labor Contractor Report doesn't sneak up on you.
- Reconcile compensation data at least quarterly, not just at tax time, so bonuses, commissions, and hourly-rate conversions are already sitting in a clean, exportable format when the filing window opens.
- Watch for the 2027 job-category change now. If you're building an internal report template, structure it so the job-category mapping is a configurable field, not a hardcoded list.
Frequently Asked Questions
Does a company outside California have to file if it has one remote California employee? Yes. The 100-employee threshold applies to the employer as a whole, and having even one payroll employee based in California is enough to trigger the filing obligation for the entire company's headcount, not just the California portion of it.
What if we use multiple staffing agencies for contract labor? The 100-worker threshold for the Labor Contractor Employee Report counts all workers supplied through labor contractors combined, across every agency you use — not per-agency. Track contractor headcount in aggregate, not agency by agency.
Can our payroll provider or PEO file on our behalf? No. The CRD has clarified that third parties, including PEOs and payroll administrators, cannot submit the report using their own portal credentials. The employer of record must be the filer, even if a vendor prepares the underlying data.
What happens if we file late instead of not at all? The statute doesn't distinguish cleanly between "late" and "never filed" for penalty purposes — the CRD can pursue civil penalties once the deadline has passed and the report is outstanding, so treat a late filing with the same urgency as a missing one rather than assuming there's an informal grace period.
Keep Your Financial Records Filing-Ready Year-Round
Whether it's a CRD pay data report, a wage-and-hour audit, or a routine year-end close, the common thread is the same: you can only report what your books can actually answer. Beancount.io offers plain-text accounting that keeps every transaction — including payroll runs, contractor payments, and bonus accruals — transparent, version-controlled, and queryable, so compliance filings pull from data you already trust instead of a scramble to reconstruct it. Get started for free and see why developers and finance-savvy operators are switching to plain-text accounting.