- Pay transparency compliance is not a single deadline event. It is an ongoing architectural problem that starts with your internal pay band structure, and building that structure takes months.
- At least 10 US states now have active salary range disclosure laws, and the EU Pay Transparency Directive requires member states to transpose it into national law by June 2026, with reporting obligations starting in 2027.
- Most HR teams plan to comply jurisdiction by jurisdiction as each law takes effect. That approach guarantees you will be behind, because posting accurate ranges requires documented bands you almost certainly do not have yet.
- This 17-point checklist covers jurisdiction mapping, band architecture, posting language, internal disclosure, audit trails, and remediation planning across both the US multi-state environment and the EU Directive framework.
- The download below gates the full printable checklist. Completing it will show you exactly which workstreams are blocking your compliance and in what order to fix them.
Pay transparency compliance requires building a documented pay band architecture before any posting deadline arrives. That means auditing your current salary data for defensible ranges, mapping every jurisdiction where you hire, setting band widths that reflect actual pay decisions, and creating an audit trail that survives a regulator inquiry. For multi-state US employers and any company hiring in the EU, the groundwork takes six to twelve months minimum.
Why Waiting for Each Deadline Is the Wrong Compliance Strategy
The assumption that you can handle each state or country as its law activates sounds reasonable until you examine what compliance actually requires. Posting a salary range is not the hard part. Posting a range that is accurate, defensible, and consistent with what you actually pay is the hard part, and that requires documented pay bands backed by compensation data.
Companies that build bands reactively, one jurisdiction at a time, end up with incoherent structures. A range posted in Colorado may contradict what your New York team sees, which may conflict with the band a recruiter in London is working from. When those ranges surface in litigation or a regulatory audit, inconsistency is its own liability.
The EU Pay Transparency Directive adds reporting obligations on top of posting obligations. Employers with at least 100 workers must report gender pay gap data under the Directive’s framework, and member states were required to transpose the Directive into national law by June 7, 2026. Building the data infrastructure to produce that report takes time that most HR teams are not factoring into their timelines. Our compensation management software comparison covers the platforms best positioned to support both band documentation and reporting workflows.
What Are the Current Pay Transparency Requirements by State?
The US regulatory environment is genuinely complex because there is no federal pay transparency law. Requirements vary by state, city, and sometimes by employer size threshold. The table below summarizes the key active requirements as of mid-2026, based on publicly available state legislative records. Confirm current obligations with employment counsel, as enforcement details and amendments may have occurred after publication.
| Jurisdiction | What Must Be Disclosed | Who It Applies To | Posting Trigger |
|---|---|---|---|
| California (SB 1162) | Salary range on all job postings; pay scale on employee request; annual pay data report to DFEH | 15+ employees; 100+ employees for pay data report | All postings including remote roles that could be performed in CA |
| Colorado (EPEWA) | Salary range and benefits on all job postings | All employers with at least one CO employee | All postings, including remote roles |
| New York State (S9427A) | Salary range on job postings and promotions/transfers | 4+ employees | All postings for roles that can or will be performed in NY |
| Washington State (SB 5761) | Salary range, benefits, and other compensation on postings; disclose on request | 15+ employees | All postings, including remote roles that could be performed in WA |
| Illinois (HR SB 3105) | Pay scale and benefits on job postings | 15+ employees | All postings including third-party postings |
| Massachusetts (H 4109) | Pay range on job postings; disclose on request | 25+ employees | All postings; law active as of publication |
| New Jersey (A4151) | Salary range and benefits on postings; internal notice of promotion opportunities | 10+ employees | All postings; law active as of publication |
| Minnesota (HF 3120) | Starting salary range or fixed pay on postings | 30+ employees | All postings; law active as of publication |
| Vermont (H.704) | Compensation range on job postings on request | All employers | Upon candidate request |
| Connecticut (PA 21-30) | Salary range on request; disclose upon offer | All employers | Upon request or offer stage |
Note that several jurisdictions extend their requirements to remote roles where the position could reasonably be performed in that state. That means a company headquartered in Texas may still be subject to California, New York, and Washington requirements on any role posted as remote. Legal counsel familiar with employment law in each relevant jurisdiction should confirm your specific obligations. This checklist is not legal advice.
What Does the EU Pay Transparency Directive Require Before the 2026 Deadline?
The EU Pay Transparency Directive (2023/970) came into force in June 2023. Member states were required to transpose it into national law by June 7, 2026, the deadline set in Article 35 of the Directive’s legislative text. For employers with operations in the EU, that transposition means national-level pay transparency obligations are now active or imminently active across member states.
The core obligations include: disclosing pay or pay ranges in job postings or before interviews, prohibiting employers from asking candidates about their pay history, giving employees the right to request information about average pay levels by gender for their category of work, and mandatory gender pay gap reporting for employers above certain workforce thresholds. Employers with 250 or more workers must report starting in 2027. Employers with 150 to 249 workers report starting in 2031. Employers with 100 to 149 workers report starting in 2031.
The Directive’s pay reporting requirements are more demanding than any current US state law because they require comparative data broken down by worker category. That means your job architecture, your pay grades, and your reporting infrastructure all need to be aligned before 2027, not after.
The 17-Point Pay Transparency Compliance Checklist
Phase 1: Jurisdiction and Scope Mapping (Points 1 to 4)
1. Build a jurisdiction matrix. Map every location where you have employees or where remote roles could legally be performed. For each jurisdiction, document the applicable law, the employee size threshold, the posting trigger, and the effective date. Update this quarterly as new laws pass.
2. Identify which postings are in scope. Remote roles are frequently in scope for multiple jurisdictions simultaneously. Decide whether to post a single range that satisfies the broadest requirement or maintain jurisdiction-specific postings. Most multi-state employers choose a single range to reduce operational complexity, but that requires the range to be defensible in every covered state.
3. Confirm contractor and third-party posting obligations. Several state laws require disclosure on postings made through third-party job boards or staffing agencies, placing the compliance obligation on the employer, not the platform. Audit your ATS and external posting workflows. Our roundup of multi-state employment compliance software covers tools that automate this mapping.
4. Document EU workforce thresholds by entity. If you have multiple legal entities in EU member states, confirm the employee count per entity and per country. The Directive’s reporting thresholds apply at the employer level within each member state. A 50-person entity in Germany and a 60-person entity in France are each below the 100-person threshold independently, even if you have 110 employees across Europe.
Phase 2: Pay Band Architecture (Points 5 to 9)
5. Audit existing pay grades for defensibility. Pull your current pay grades or salary bands. For each band, ask: does the posted range reflect the actual distribution of compensation in that role? If the band is too wide to be meaningful, or if actual pay frequently falls outside it, the band is not defensible. Ranges like “$50,000 to $200,000” for a single job title invite regulatory scrutiny and candidate skepticism.
6. Conduct a market pricing refresh. Salary ranges posted in job ads become outdated quickly. Use a compensation benchmarking tool to confirm your bands are within a reasonable range of market data. Point 5 and Point 6 feed each other: if your current pay distribution does not align with market data, you have a pay equity problem alongside a transparency problem.
7. Define band width policy. A defensible band width for most individual contributor roles is roughly 50 to 80 percent spread from minimum to maximum. Bands wider than that suggest the role is not well-defined or that pay decisions within the band are arbitrary. Document your policy for what band width is acceptable and why.
8. Map all roles to a documented job architecture. Pay bands only work if roles are consistently classified. If your HRIS has 400 job titles and no formal leveling structure, fixing that is a prerequisite to posting defensible ranges. Job architecture work typically takes three to six months in a company of 300 to 500 employees.
9. Establish band review cadence. Bands drift out of market alignment without a regular review schedule. Commit to reviewing all bands at least annually, and build a process for off-cycle adjustments when a market for a specific skill moves quickly. Document the review cadence and the approval chain.
Phase 3: Posting Language and Internal Disclosure (Points 10 to 13)
10. Standardize posting language templates. Create ATS-ready templates that include salary range and required benefit disclosures by jurisdiction. The template should pull the approved band for the role and auto-populate it, reducing the risk of a recruiter manually entering a range that conflicts with the documented band.
11. Define internal pay band disclosure rules. Most laws with internal posting requirements mean current employees have the right to see the range for roles they apply to internally. Decide what you will proactively communicate about pay bands to current employees versus what you will disclose on request. The EU Directive gives workers the right to request pay comparison data, which is a significantly broader internal disclosure obligation than most US states currently require.
12. Train recruiting teams on compliant candidate conversations. Pay transparency laws in several US states and the EU Directive prohibit asking candidates for salary history. Recruiters need scripted language for common situations: when candidates ask whether the posted range is negotiable, when a candidate’s current salary is volunteered, and when an offer is above the posted range. Document the approved language and deliver training before any posting goes live in a new jurisdiction.
13. Review promotion and transfer disclosure obligations. New York’s law explicitly covers promotions and transfers, not just external postings. Several other state laws are interpreted to cover internal moves as well. Build a process for disclosing the pay range when an employee is notified of a promotion opportunity, and document that process.
Phase 4: Audit Trail and Reporting (Points 14 to 17)
14. Establish a compensation decision audit trail. For every offer made within a posted range, document the rationale for where within the range the offer landed. This is the single most important protection against pay equity litigation, and it is frequently absent. The audit trail should live in your HRIS or compensation management system, not in a recruiter’s email.
15. Build the EU pay gap reporting data structure now. EU reporting requires gender pay gap data by worker category. That means your HRIS needs clean, consistent gender data, a job architecture that maps workers into comparable categories, and the ability to generate average pay by gender per category. If your HRIS cannot produce that report today, that is a gap to close before 2027. Tools like Syndio, Trusaic, and PayAnalytics are built specifically to automate this analysis.
16. Create a remediation plan for identified pay gaps. A compliance audit that surfaces a pay gap without a documented remediation plan is worse than not auditing at all, because it creates discoverable evidence of a known problem. Pair your pay equity analysis with a budget-approved remediation roadmap. The roadmap should include which gaps you are addressing, in what order, over what timeline, and what the estimated cost is.
17. Assign a named owner for recurring compliance reviews at a defined cadence. Pay transparency compliance is not a one-time project. Laws will continue to expand, band structures will drift, job architectures will grow inconsistently, and the EU reporting cycle will create annual disclosure obligations. Document the review schedule and treat it as a recurring budget line, not a one-time implementation cost.
Which Tools Support Pay Transparency Compliance?
Pay transparency compliance touches at least four categories of software: compensation management, pay equity analytics, HRIS, and ATS. No single vendor covers all four well, which is why the tooling decision matters as much as the process design.
For compensation band management and documentation, platforms like Payscale, Radford, Compaas, Carta Total Comp, and Pave specialize in band-building backed by market data. For pay equity analysis and EU reporting, Syndio, Trusaic, and PayAnalytics are the category leaders.
Your HRIS is the foundational data layer. If your HRIS cannot produce clean job architecture data with consistent classification and gender data by entity, no overlay tool will compensate for that. Our compensation benchmarking tools roundup covers the specific platforms that integrate market data with internal band structures.
ATS integration matters because posting language compliance happens at the point where a job requisition is published. Without an ATS that can enforce posting language rules by jurisdiction and pull from a live band library, compliance becomes dependent on individual recruiter behavior, which is not a compliance strategy.
How Long Does Pay Transparency Compliance Implementation Actually Take?
The honest answer is longer than most HR teams budget. The timeline depends primarily on how mature your existing job architecture is. The ranges below reflect practitioner experience reported across compensation consulting engagements and are consistent with guidance published by compensation advisory firms; they are directional estimates, not guaranteed outcomes for any specific organization.
| Starting Point | Estimated Implementation Timeline | Primary Bottleneck |
|---|---|---|
| No formal job architecture, no documented bands | 9 to 14 months | Job leveling and architecture design |
| Informal job levels, some salary bands exist but undocumented | 6 to 9 months | Band documentation and market pricing refresh |
| Documented job architecture, bands exist but not market-validated | 3 to 6 months | Market pricing, legal review, ATS integration |
| Mature job architecture, validated bands, existing pay equity analysis | 1 to 3 months | Jurisdiction mapping, posting templates, training |
Companies at the first stage that are planning to comply with laws already active are already behind. The job architecture work alone requires HR time, manager buy-in, legal review, and usually a compensation consultant or software vendor to provide market data anchors.
For HR teams evaluating where they stand on the overall compliance and technology readiness spectrum, the AI HR compliance and bias audit tools comparison covers platforms that can run a baseline pay equity analysis as a starting point.
Download the Full 17-Point Pay Transparency Compliance Checklist
The printable checklist formats all 17 points into a workable audit template with owner fields, completion dates, and status tracking. It also includes a jurisdiction matrix template pre-formatted for the US states and EU member states with active or transposed transparency requirements.
Download the Pay Transparency Compliance Checklist
Enter your work email to get the full printable checklist and enter our pay transparency software evaluation guide series.
Frequently Asked Questions
Which US states currently require salary ranges in job postings?
As of mid-2026, states with active salary range posting requirements for job advertisements include California, Colorado, New York, Washington, Illinois, Massachusetts, New Jersey, and Minnesota. Connecticut requires disclosure upon request or at offer. Vermont requires disclosure upon candidate request. Several cities, including New York City, have their own ordinances. Requirements vary by employer size threshold and whether remote roles are in scope. Confirm specific obligations with employment counsel in each applicable jurisdiction.
What do employers need to do before the EU Pay Transparency Directive deadline?
Member states were required to transpose the Directive into national law by June 7, 2026, per the Directive’s legislative text. For employers in those countries, that means active obligations now, not in 2027. Immediate requirements typically include posting pay ranges in job advertisements, prohibiting pay history inquiries, and giving employees the right to request pay comparison data. The gender pay gap reporting obligation, which applies to employers with 100 or more workers, starts in 2027 for large employers. Building the data infrastructure to produce that report should start now.
Do remote job postings need to include salary ranges for every state?
It depends on how the role is posted and how the relevant state law defines scope. Colorado, California, Washington, and New York all extend their requirements to remote roles that could be performed in those states. A company headquartered outside those states that posts a nationwide remote role is generally required to disclose a salary range that complies with all of those states’ requirements simultaneously. Many employers choose to include the salary range on all remote postings to avoid jurisdiction-by-jurisdiction management.
How wide should a salary band be for a posted range to be legally defensible?
There is no universal legal standard for band width, but ranges that are extremely wide, such as “$60,000 to $180,000” for a single individual contributor role, attract regulatory scrutiny and damage candidate trust. Most compensation practitioners consider a spread of 50 to 80 percent from minimum to maximum appropriate for a well-defined role at a single level. Bands wider than that typically indicate a leveling problem or undocumented pay decision criteria, both of which create pay equity exposure independent of the posting requirement.
Does pay transparency compliance require a compensation management software platform?
Not technically, but practically yes for companies with more than 100 employees. Managing pay bands in spreadsheets creates version control risks, audit trail gaps, and ATS integration failures that make posting language compliance dependent on manual processes. A compensation management platform connected to market data and integrated with your HRIS and ATS automates band documentation, range validation, and posting population. For companies operating across multiple jurisdictions, the operational overhead of spreadsheet-based management is not sustainable at scale.
What is the difference between pay transparency and pay equity?
Pay transparency refers to disclosing pay ranges in job postings, to current employees, or to candidates, as required by law. Pay equity refers to the practice of ensuring employees in comparable roles are paid comparably regardless of gender, race, or other protected characteristics. The two are related but distinct. Transparency laws create the obligation to post ranges. Pay equity analysis determines whether your actual pay distribution is defensible within and across those ranges. Compliance with transparency laws does not guarantee pay equity, and pay equity gaps create liability that transparency laws make more visible.
How should HR teams handle internal pay band disclosure to current employees?
At minimum, comply with whatever your applicable state and EU laws require, which typically includes disclosing a pay range when an employee applies for an internal promotion or transfer in covered jurisdictions. Beyond legal minimums, proactively communicating band structures to employees reduces the informal pay information sharing that leads to morale and retention problems. The EU Directive gives workers a right to request average pay data by gender for their job category, which is a stronger internal disclosure obligation than most US state laws currently impose.
What is a jurisdiction matrix and why does it matter for pay transparency compliance?
A jurisdiction matrix is a documented map of every location where your company has employees or posts jobs, cross-referenced against applicable pay transparency laws, employer size thresholds, and effective dates. It is the foundational document for a multi-state or multinational compliance program because it forces you to identify every obligation in one place before you start designing processes. Without it, compliance teams discover requirements reactively, usually after a job posting has already gone live in a covered jurisdiction without the required disclosure.
Building Compliance That Does Not Break Every Time a New Law Passes
The companies that handle pay transparency compliance well have one thing in common: they built their job architecture and pay band structure as an internal management tool years before any law required them to publish it. Compliance was a byproduct of good compensation practice, not a scramble triggered by a deadline.
The companies that struggle have the opposite problem. They manage pay informally, set offers based on candidate expectations rather than documented bands, and have HRIS data that does not map cleanly to a defensible job structure. For those teams, each new state law is a fire drill. The EU reporting cycle will be a larger fire drill. The checklist above gives you the workstreams. The sequencing matters: jurisdiction mapping first, job architecture second, band documentation third, then posting templates, audit trails, and reporting infrastructure. Skipping to the posting templates without fixing the architecture produces ranges that are legally posted but operationally indefensible.
If your current compensation review cycle readiness concerns you, our compensation cycle readiness audit covers the internal process gaps that surface long before a posting deadline arrives.
Legal Disclaimer: The information in this article is provided for general informational purposes only and does not constitute legal advice. Pay transparency laws vary by jurisdiction and change frequently. Consult qualified employment counsel in each applicable jurisdiction before making compliance decisions.
