State-by-State Pay Transparency Laws in 2026: A Compliance Guide for Multi-State Employers

In Washington state, roughly 250 employers have been sued in a wave of pay transparency class actions, with potential exposure approaching half a billion dollars — and many of the targets are not local companies. They are national employers who left a single posting up without a salary range, never realizing the listing was visible to candidates who could legally work the role from Seattle or Spokane.

That is the central problem with pay transparency in 2026. Seventeen states plus Washington, D.C. now require some form of salary disclosure in job postings, and at least four major cities in Ohio have their own ordinances on top. The rules look superficially similar — "post a good faith range" — but the thresholds, geographic scope, penalty structures, and reporting obligations vary enough that a single nationwide job ad can violate three statutes at once.

This guide walks through the current map, the traps remote-friendly employers keep falling into, and the structural moves that turn compliance from a recurring fire drill into a steady operating discipline.

Why 2026 Is the Inflection Year

Pay transparency started as a Colorado experiment in 2021. By the end of 2024 it had spread to roughly a dozen states. What changed in 2025 and 2026 is twofold.

First, the enforcement got real. Washington's Department of Labor and Industries received 224 complaints in a single fiscal year, and private plaintiffs' attorneys discovered that the statute allowed class certification with statutory damages of $5,000 per affected applicant. That math turned modest oversights into headline-grade liability.

Second, the laws stopped being coastal. Minnesota's law took effect January 1, 2025. New Jersey followed on June 1, 2025. Massachusetts's expanded posting requirement went live October 29, 2025. Vermont's took effect July 1, 2025. Cleveland and Columbus both enacted ordinances in 2025, with Columbus's enforcement window opening January 1, 2027. Delaware will join the list on September 26, 2027.

For a company with employees in even five or six states, the practical question is no longer "do we need to comply" but "which state's version do we use as our default?"

The Current Map: Who Is Covered

The full list of jurisdictions with active pay transparency laws as of mid-2026 includes:

• California — all employers with 15+ employees; pay scale on every posting; separate annual pay data report for employers with 100+ employees.
• Colorado — all employers; pay range plus benefits in postings; internal promotional opportunities must be announced.
• Connecticut — all employers; disclose range upon applicant or employee request, or when making an offer.
• Delaware — effective September 26, 2027; employers with 25+ employees; range plus benefits description.
• Hawaii — employers with 50+ employees; hourly rate or salary range required in posting.
• Illinois — employers with 15+ employees; pay scale and benefits in postings; pay data reporting on a separate track.
• Maine — effective 2026; range required upon request.
• Maryland — all employers; range upon request and in postings.
• Massachusetts — employers with 25+ employees; pay range in postings, promotions, and transfers; pay data reports for 100+ employees.
• Minnesota — employers with 30+ employees; range plus benefits.
• Nevada — all employers; range upon completion of an interview, or at a candidate's request.
• New Jersey — employers with 10+ employees; range plus general benefits description.
• New York — employers with 4+ employees; range and job description in postings.
• Rhode Island — all employers; range upon request and at hire.
• Vermont — employers with 5+ employees; range in postings.
• Washington — employers with 15+ employees; range plus benefits in every posting.
• Washington, D.C. — all employers with at least one D.C.-based employee; range in postings.
• Ohio cities — Cincinnati, Cleveland, Columbus, Toledo have separate ordinances with their own thresholds and timelines.

Notice the spread of thresholds: New York covers anyone with four employees, while Hawaii does not kick in until you reach fifty. A 20-person startup with remote hires in both states is fully subject to New York's rules and exempt from Hawaii's — but that does not save the New York posting from also having to satisfy Colorado if a Denver-based candidate could perform the work.

What "Good Faith Range" Actually Means

Every statute uses some version of the phrase "good faith range." None of them give you a formula. Courts and labor commissions have started filling in the gap, and three patterns have emerged.

The range must be specific to the role and location. A posting that says "$50,000 to $400,000" for a software engineer is the textbook example of bad faith. Most enforcement guidance treats spreads larger than $40,000 or roughly 30% of the midpoint as presumptively suspect for non-executive roles.

It must reflect what the employer would actually pay. If your internal salary band for the level is $90,000 to $115,000, posting "up to $200,000" to attract clicks is a violation even if a real person at that level eventually got $200,000 through equity or a sign-on.

It must adjust for geography when the role is multi-location. A remote position open to candidates in New York City, Cleveland, and Austin should either post the highest applicable city's range, post separate ranges per location, or exclude jurisdictions that would force you to disclose ranges you do not want to publish.

The safest narrative test: if a current employee in the same role saw the posting, would they conclude you described the job honestly? If the answer is "no," you have a good faith problem regardless of the dollar amounts.

The Remote Work Trap

The single most common compliance failure in 2026 is the remote posting that fails to consider where the work could be performed. Both California and Washington explicitly cover jobs that can be done from those states, regardless of where the employer is located. New York and Colorado have similar reach.

That means a Texas-headquartered company posting "Remote — United States" for a software engineer must comply with the disclosure rules of every state on the list above. Not the states where the company has offices. The states where the eventual hire could log in from.

There are three legitimate ways to handle this.

Adopt the strictest standard everywhere. If you include a good faith range plus benefits on every posting and treat every posting as if California, Washington, and New York are watching, you are compliant in every U.S. jurisdiction. This is the simplest approach administratively and the one most labor and employment counsel recommend for companies above 100 employees.

Post location-specific ranges. Larger employers with sophisticated compensation systems list separate ranges for each major metro: "$130,000 to $155,000 (NYC); $120,000 to $143,000 (Austin); $115,000 to $138,000 (other U.S. locations)." This is more accurate but requires a real geographic differential structure to back it up.

Geo-fence the role. "This position is open to candidates residing in Texas, Florida, Georgia, North Carolina, Tennessee, Arizona, and Utah" is a perfectly legal way to limit your exposure — as long as you actually enforce it and do not hire someone in California anyway. Posting an exclusion you do not honor is itself a violation in several states.

The trap is doing none of the above: posting "Remote" with no salary, no benefits, and no geographic scope. That is the posting that ends up in a class action complaint.

Penalties and Real-World Enforcement

Statutory penalties give the headline numbers, but the practical exposure usually comes from elsewhere.

California authorizes $100 to $10,000 per violation through the Labor Commissioner, plus contributions to discrimination claims under the Equal Pay Act. A "violation" is typically one posting or one applicant, so a company with a hundred open requisitions left non-compliant for a quarter is staring at six- or seven-figure potential liability before any private litigation.

Washington is the cautionary tale. Statutory damages of $5,000 per affected applicant, plus attorney's fees, combined with a class action mechanism, produced the wave of lawsuits that prompted the 2025 amendment. Even with that amendment narrowing exposure, several settlements have already cleared eight figures.

Colorado can issue fines of $500 to $10,000 per violation but has no private right of action — enforcement is administrative only. This sounds protective until you remember that the state Department of Labor can audit your last three years of postings, calculate one violation per posting, and bill accordingly.

New York caps civil penalties at $3,000 per violation but allows the Department of Labor to escalate for repeat offenders, and the state has been increasingly willing to do so for national employers.

Massachusetts added an enforcement clause in 2024 that lets the Attorney General sue on behalf of aggrieved employees with penalties up to $25,000 per violation for repeat offenders.

Beyond statutory damages, the reputational tax is real. Postings that violate disclosure rules are screenshotted, posted to LinkedIn, and used as evidence in EEOC charges and individual pay discrimination claims. A compliance failure on a recruiting page tends to surface during litigation discovery, not before.

Pay Data Reporting: The Second Track

Pay transparency in postings is only half the story. California, Illinois, and Massachusetts also require employers above a size threshold to submit detailed pay and demographic data to a state agency on a yearly cycle.

California's pay data report applies to employers with 100+ employees and is due in May each year. The report breaks down median and mean hourly pay by race, ethnicity, and sex within each of ten job categories, with separate reporting for workers hired through labor contractors.

Illinois's equal pay registration certificate requires employers with 100+ Illinois employees to recertify every two years, with detailed pay data submission and a sworn statement that pay practices are non-discriminatory.

Massachusetts's pay data filing kicked off February 1, 2025, requiring employers with 100+ Massachusetts employees to submit EEO data on an annual cycle starting in 2025.

Some of these reports are publicly available; some are kept confidential. All of them create a documentation trail that becomes the first place a plaintiff's lawyer or the EEOC looks during a wage discrimination investigation. If your reported median pay shows a 12% gap between men and women in the same job category, expect questions — even if the gap has a defensible explanation.

The Internal Equity Problem

Once salary ranges are public, every current employee can compare what they earn to what the company is willing to pay a new hire. This is what HR teams have learned to dread.

Three scenarios produce the most internal pressure.

The new-hire premium. Recruiting markets often push starting offers above what equivalent tenured employees make. When a posted range for a Senior Engineer is $145,000 to $170,000 and a five-year tenured Senior Engineer earns $138,000, the conversation in the next one-on-one is predictable.

The promotion ceiling. Posted ranges expose how little upward mobility exists within a single title. If "Manager II" tops out at $180,000, the Manager II earning $172,000 now knows the maximum upside without a promotion is $8,000.

Benchmarking the bands themselves. Once enough postings are visible, candidates and employees use sites like Levels.fyi to triangulate where a company sits in the market. Employers with below-market bands lose recruits before the first interview.

The structural answer is what compensation consultants call a "compa-ratio" review: actively narrow the gap between in-band employees and external offers, ideally on a regular cycle rather than reactively. This is a budget line, not a one-time exercise.

Documentation: The Quiet Requirement

Most pay transparency statutes require not just that you post a range, but that you can defend how the range was determined. Several states explicitly require recordkeeping for two to three years; many more imply it through general wage and hour rules.

A defensible documentation package usually includes:

• The salary band or grade for the role, with the range and the date it was set.
• The market data source used (Radford, Mercer, Payscale, internal benchmark, etc.) and the date of the survey.
• The geographic differential methodology if applicable.
• The actual posted range for each requisition, with a timestamp.
• Any deviations from the standard range, with the business justification.

If you cannot produce this when a labor commission audit lands, the practical effect is to put you on the defensive in a regulatory investigation. Conversely, a clean documentation trail typically resolves complaints before they escalate.

This is one of the places where bookkeeping discipline and HR discipline intersect. Payroll records, benefit cost allocations, and bonus accruals all need to reconcile to the compensation philosophy reflected in your bands. When auditors find the payroll system and the posted ranges telling different stories, the discrepancy itself becomes the issue.

Practical Compliance Checklist for 2026

If you are building a transparency program from scratch — or auditing an existing one — work through the following in order.

Map your jurisdictional footprint. Pull a roster of every state where you have one or more employees, every state where you actively recruit remote workers, and every state-specific ordinance (Ohio cities, D.C., New York City) layered on top of the state law.

Identify your strictest jurisdiction. For most multi-state employers, this is California, Washington, or New York depending on industry. Use that state's requirements as your default posting template.

Build the salary architecture. You need a band structure that maps levels to ranges, ideally with geographic adjustments. If you do not have one, this is the prerequisite to everything else — without it, every range you post is a guess.

Standardize the posting template. Every requisition should auto-populate the range, benefits summary, location scope, and any geographic exclusions. Recruiters should not be deciding range disclosure on a per-posting basis.

Audit historical postings. Pull every posting from the past two years across LinkedIn, Indeed, your career site, and ATS. Identify gaps, fix the active ones, and assess statute-of-limitations exposure on the old ones.

Document the methodology. Compensation philosophy, band-setting process, geographic differentials, and revision history should all live in a single internal reference that legal can produce on request.

Schedule the recertification cycle. California's annual pay data report is May. Illinois recertification is biennial. Build calendar reminders 60 days in advance of each filing.

Train recruiters and hiring managers. Most compliance failures come from a manager pressuring a recruiter to leave the range off "just for this one." Make the policy non-negotiable in writing and back it up with consequences.

Keep Your Compensation Records Audit-Ready

Pay transparency laws have turned compensation data into a regulatory document — one that auditors, plaintiffs' attorneys, and state labor commissions can demand on short notice. The companies that handle this well treat payroll, benefits, and compensation expense as a single reconciled book of record rather than three siloed systems.

Beancount.io offers plain-text accounting that gives you complete transparency and version control over financial data, including the payroll and compensation line items that increasingly need to defend themselves in regulatory reviews. Get started for free and bring the same auditable discipline you apply to revenue and expenses to the compensation records that now sit in regulators' line of sight.