Pay Transparency Laws in 2026: What Multi-State Employers Need to Change in Job Postings

Pay transparency is no longer a California-and-Colorado story. As of early 2026, 17 states and multiple municipalities have active laws requiring employers to disclose salary ranges in job postings — and the list is growing. An estimated 65% of U.S. employers now operate somewhere under a pay transparency mandate, whether they know it or not.

For multi-state employers, the compliance picture is particularly complex. The requirements aren’t uniform: employee count thresholds differ, disclosure requirements differ, penalty structures differ. And the rules for remote positions — who must comply based on where an applicant lives versus where an employer is based — are the source of most of the confusion.

This guide walks through the state-by-state compliance landscape, explains the remote job posting trigger problem that catches multi-state employers off guard, covers the internal notification requirements most HR teams miss, and addresses what happens internally the moment you post a salary range externally.

Note: This guide reflects requirements as of March 2026. Pay transparency law is evolving rapidly. Consult employment counsel to confirm requirements for specific jurisdictions before publishing job postings.

The State-by-State Compliance Landscape in 2026

Every jurisdiction with an active pay transparency law requiring salary disclosure in job postings — or upon request — has different thresholds. Colorado, California, New York, Washington, Illinois, and Minnesota are the most commonly encountered. But states like Nevada, Connecticut, Rhode Island, and Maryland also have active requirements with distinct employer size cutoffs and trigger conditions.

The requirements aren’t just “post a salary range.” Several states also require: a description of benefits and other compensation, internal notification of open positions, and specific formatting for how ranges are presented. Delaware’s law, signed in September 2025, doesn’t take effect until September 2027 — so it’s not yet in the active compliance count.

For multi-state employers, the practical move is to identify your highest-compliance-burden states and build your job posting template around them. That typically means Colorado and Illinois, which currently carry the most comprehensive requirements. According to the U.S. Department of Labor and state agency guidance, failing to comply can trigger civil penalties ranging from $500 to $10,000 per violation in some jurisdictions.

The Remote Job Trigger Problem: You May Owe Disclosure in States Where You’ve Never Had an Office

Here’s the part most HR teams don’t see coming. Most state pay transparency laws don’t limit compliance to employers with physical locations in that state. They apply based on where the work will be performed — which, for remote positions, means anywhere an applicant could plausibly work from.

If a role is posted as remote — or even as hybrid or flexible — and an applicant located in a covered state could legitimately apply and perform the work from that state, most pay transparency laws require you to comply with that state’s disclosure requirements. Your company’s headquarters location doesn’t change that. A Florida-based employer posting a remote role that could be filled by someone in New York, Colorado, or California must comply with those states’ requirements.

Several states make this explicit:

• New York: The law applies to all opportunities “that may be performed remotely” that would report to a supervisor or office in New York. Enforcement guidance has extended this: if the role is fully remote with no specified location and an employer with NY presence posts it, NY compliance is expected.
• Colorado: Colorado’s Equal Pay for Equal Work Act is read broadly — any role that “could be performed” in Colorado by a Colorado resident is subject to Colorado’s requirements. The Colorado DOL has issued interpretive guidance addressing employers who tried to exclude Colorado applicants from postings.
• Illinois: The law explicitly covers positions “performed at least in part in Illinois” or positions performed outside Illinois if the employee “reports to a supervisor, office, or other worksite located in Illinois.”
• Washington State: Applies to employers with 15+ employees that recruit for positions in Washington, which has been interpreted to include remote positions available to Washington residents.

The Practical Decision Framework for Remote Postings

When evaluating whether a remote job posting requires pay disclosure, work through these questions in order:

Is the role explicitly restricted to a specific state where no pay transparency law applies? If yes, you may not need to disclose. If no, continue.

Is the role fully remote with no geographic restriction? Assume you’re subject to the most stringent requirements among: all states where you have employees or offices, plus all covered states where applicants are likely to apply — New York, California, Colorado, and Washington at minimum.

Does the role report to a supervisor or work location in a covered state? If yes, that state’s law applies regardless of where the remote employee will physically work.

The simplest compliance solution for most multi-state employers: use one job posting template that satisfies Colorado and Illinois requirements — the most comprehensive currently — and apply it to all postings. This eliminates the need to manage per-state posting versions.

A Compliant Job Posting Template for Multi-State Employers

The strictest posting requirements as of March 2026 are found in Colorado, Illinois, New York State, and Washington. All four require: (1) a minimum and maximum salary or hourly rate, (2) a general description of benefits and other compensation, and (3) internal notification of opportunities to current employees.

A compliant posting template should include a clearly labeled “Compensation” section with an explicit range (not “competitive” or “DOE”), a brief benefits summary listing health insurance, retirement, PTO, and other key offerings, and a note that the range reflects what the employer expects to pay someone entering the role — acknowledging that individual placement may vary based on experience and qualifications.

Before any posting goes live, HR or legal should review it. That’s not just a compliance best practice — it’s what several state enforcement agencies now recommend as the baseline standard of care.

Internal Notification: The Requirement Most Employers Miss

Several states require employers to notify current employees of open positions at the same time — or before — those positions are posted externally. The mechanism and timing differ:

• Colorado: All current employees must be notified the same day the external posting goes live. Colorado is particularly strict here — internal and external postings must happen simultaneously.
• Illinois: Current employees must be notified of promotion or transfer opportunities no later than 14 calendar days after any external posting.
• New Jersey: Employers must make “reasonable efforts” to notify existing employees of promotional opportunities before making a promotion decision.
• Minnesota: All job postings — internal and external — must include pay range and benefits description.

For multi-state employers, the cleanest compliance posture is to post all positions internally — with pay range — at the same time as the external posting, or before. This satisfies Colorado’s same-day requirement and exceeds the 14-day windows in other states. It also prevents the awkward situation where employees learn about openings from external job boards before internal communication goes out.

When Employees See What You’re Paying for Their Job

Posting a salary range externally is a compliance act. It immediately becomes an HR event. The moment a current employee — or their spouse, friend, or former colleague — sees the external posting for their role and compares it to their own compensation, the conversation starts.

Employees comparing the posted range to their own pay typically have one of four reactions. They’re at the top of the range — generally positive, low disruption. They’re in the middle — usually neutral, may wonder about advancement potential. They’re below the posted minimum — this is the high-disruption scenario. Or a colleague appears to be paid significantly more for the same role, which surfaces pay equity concerns and, if disparities exist along protected-class lines, potential legal exposure.

The third scenario — employees below the posted minimum — is the most urgent. If your compliance posture requires you to post a range starting at $X, and you have current employees earning less than $X in that role, you have a pay equity problem that predates the job posting. The posting just made it visible.

How to Prepare Managers for the Conversations That Are Coming

When you start posting salary ranges externally, managers will get questions they’ve never fielded before. Prepare them with clear language:

What the range means: “The range represents what we expect to pay someone entering this role. Your compensation reflects your experience, tenure, performance history, and the value you’ve built here — which may place you differently than a new hire entering at the bottom.”

What they should do if an employee believes they’re underpaid: “Bring that to HR. We have a process for reviewing compensation and we take those conversations seriously.” Managers shouldn’t promise increases, explain other employees’ pay, or speculate.

What they absolutely should not do: Discourage employees from discussing pay with each other. The National Labor Relations Act protects employees’ right to discuss wages with coworkers. Discouraging those conversations is an unfair labor practice — full stop.

Conduct a Pay Equity Audit Before Your First Posting Goes Live

Before your first compliant external job posting includes a salary range, run a pay equity review for all affected roles. The review should identify employees currently paid below the new posting’s minimum, pay disparities within a job title that correlate with gender, race, age, or other protected characteristics, and whether your ranges reflect actual market data or are engineered around current incumbents.

A pay equity audit conducted before external posting is protected by attorney-client privilege if conducted under the direction of employment counsel. Per SHRM’s guidance on pay equity, this privilege gives you time to make adjustments proactively rather than reactively — and to document the compensation methodology you’ll use when employees ask why they’re paid what they’re paid.

Outliers above the posted range also need attention. Document legitimate, non-discriminatory justification for each one. In a pay transparency environment, unexplained above-range pay becomes a liability.

Pay Transparency Compliance Is a Compensation Strategy Problem, Not Just a Posting Problem

The tactical compliance question — what language goes in the posting — is the easy part. The hard part is making sure the range you post is defensible, that your current employees’ compensation holds up under scrutiny, and that your managers are equipped to have honest conversations when pay becomes visible.

Employers who treat pay transparency as a job posting checkbox will struggle with the internal ripple effects. Employers who treat it as the forcing function to build a coherent, documented, defensible compensation structure will be better positioned for both compliance and retention. That’s not an abstract observation — it’s what the data from early-adopter states like Colorado consistently shows.

Netchex helps employers build that foundation. With Netchex’s HR platform, compensation data is organized by role, market benchmarks integrate into pay structure decisions, and reporting tools let you audit internal equity before external transparency creates external pressure. Learn more about how Netchex supports payroll and compliance for multi-state employers.

Frequently Asked Questions

This guide reflects publicly available product information and independent reviewer data (G2, Capterra, Trustpilot, Yelp, Better Business Bureau, Reddit, Software Advice, GetApp) as of 2026. Feature availability and pricing may vary by plan. Contact each provider for current details.

Disclaimer: Any product roadmap or future plans provided herein are for informational purposes only. They do not represent a commitment to deliver any material, code, feature, or functionality. Plans may change without notification. The development, release and timing of any features or functionality described remain at the sole discretion of Netchex, its affiliates, and partners. Netchex does not give legal, tax, or accounting advice. You are responsible for ensuring your use of Netchex product meets your individual business and compliance requirements.

Print this page