ATS Pay Transparency Compliance 2026: How to Handle 16 State Salary Disclosure Laws

Acknowledging the frustration first: pay transparency compliance in 2026 is genuinely difficult to manage. The rules are a patchwork of 16 state laws, each with different thresholds, definitions, and effective dates. Remote work has blurred which state laws apply to which postings. The penalties for non-compliance are real — and in states like California and New York, the private right of action means individual candidates can bring claims, not just state agencies.

Most ATS platforms were designed before pay transparency was a material compliance concern for US employers. The salary range field exists on most job posting forms, but the compliance infrastructure around it — state-specific rules, audit trails, multi-state publishing logic — is less consistently implemented. This guide covers the legislative landscape, what your ATS must do, and how to audit your current setup.

It sounds like what you need is a system that handles state-specific compliance automatically rather than requiring your HR team to maintain a separate compliance checklist for every job posting. That's the right instinct — and it's what a properly implemented ATS should do. The question this guide answers is whether your current ATS is doing it.

The 16-state pay transparency landscape in 2026

The states with active pay transparency laws fall into two categories: those requiring salary ranges in job postings, and those requiring disclosure only when requested (typically during the interview process or upon request from an employee).

States requiring salary ranges in job postings

These are the laws with the most operational impact on your ATS workflow, because they require disclosure at the point of posting — before any candidate interaction.

States requiring disclosure on request

Connecticut, Maryland, Nevada, and Rhode Island require employers to disclose salary ranges on request — either when an applicant asks during the interview process, or when an employee asks about ranges for comparable roles. These states don't require proactive disclosure in job postings, but your HR team needs a consistent process for responding to requests, and your ATS should have salary range data recorded so those responses are accurate and documented.

Pay transparency and internal equity: the harder problem

The legislative requirements are the visible compliance layer. The harder operational problem is internal equity. When you disclose salary ranges in job postings, existing employees can compare their current compensation against the range you're advertising for new hires doing the same role. If your internal compensation is out of alignment — which is common, particularly in organisations that haven't done regular compensation benchmarking — pay transparency disclosures trigger internal equity complaints.

This isn't a reason to avoid compliance. It's a reason to address internal equity proactively before disclosures make the gaps visible. The companies that have managed pay transparency well have typically done the internal equity analysis first: identified the gaps, planned the remediation timeline, and prepared clear communication for employees before external transparency requirements made the gaps publicly visible.

Your ATS role in internal equity is primarily documentation: maintaining salary band data for each role, recording the range applied to each posting, and creating the audit trail that demonstrates consistent application of compensation bands across candidates.

What your ATS must do for pay transparency compliance

Given the legislative requirements across the 16 states, here is the functional minimum your ATS needs to support:

DOL and NLRA considerations alongside state laws

State pay transparency laws are the most operationally immediate compliance concern, but two federal frameworks also interact with how you handle compensation information in hiring.

The National Labor Relations Act (NLRA) protects employees' rights to discuss wages and working conditions. It's illegal to prohibit employees from discussing their compensation with colleagues or applicants. This means any internal HR policy that discourages compensation discussion is legally problematic — and it has implications for how you communicate about salary ranges internally. Pay transparency policies that are externally mandated but internally discouraged create a compliance contradiction that the NLRB has taken notice of.

The Department of Labor's Equal Pay Act requires equal pay for equal work regardless of gender. Pay transparency laws interact with this by making compensation disparities more visible — and more litigatable. An organisation that posts salary ranges and then consistently offers female candidates the bottom of the range while offering male candidates the top of the range has created a documented equal pay violation. Your ATS compensation data becomes evidence in that scenario. Managing compensation data in your ATS with consistency is not just good practice — it's legal risk management.

How Treegarden handles pay transparency

Treegarden's job posting workflow includes structured salary range fields for minimum and maximum compensation, a benefits summary field, and location-based publishing configuration. The salary range data is included in all job postings published through Treegarden's distribution channels, passed through as structured data rather than free-form text.

The compensation data is recorded in the job record and retained in audit logs, creating the documentation trail needed for compliance verification. Internal compensation band management allows HR teams to define approved ranges by role, with the job creation flow referencing these bands. All plan tiers include pay transparency workflow support — there is no compliance add-on pricing.

Common ATS implementation failures for pay transparency

Pay transparency requirements have been in effect in some US states since 2020, which means most ATS platforms have had time to add salary range fields. But having a field is not the same as having a compliance-ready implementation. The failures that actually create compliance risk are more specific.

Failure 1: Salary range as a free-text field. Several ATS platforms capture the salary range as a single free-text field in the job description. This means the range is part of the job description text blob, not a structured data field. The consequence: the range cannot be reliably extracted for audit purposes, it may or may not pass through to job boards as structured salary data, and it cannot be referenced in compensation band management systems. A proper implementation requires separate minimum and maximum salary fields that store numeric values and currency separately from the job description text.

Failure 2: Salary range on the internal form but not on the public posting. Some ATS platforms have an internal salary range field for HR use that isn't included in the public job posting or distributed to job boards. Compliance requires that the salary range appear in the public posting visible to applicants — not just in the internal ATS record.

Failure 3: Multi-board publishing that drops the range. When a job is distributed to LinkedIn, Indeed, or other job boards through the ATS, some platforms don't pass the salary range to the distribution. The ATS shows the range on your career page, but the job board posting omits it. Candidates applying from job boards see no range; you're non-compliant in states that require the range in any publicly accessible posting.

Failure 4: Remote job location defaulting to headquarters only. If your ATS defaults all remote jobs to your headquarters location for the purpose of determining which compliance rules apply, you may be underidentifying the states whose laws apply to a remote posting. A job explicitly labeled as "remote — open to candidates in any US state" should be evaluated against all 16 state laws with active requirements, not just the law of your headquarters state.

Failure 5: No benefits disclosure field. Colorado, Washington, Illinois, and Minnesota require benefits disclosure alongside the salary range. If your ATS only has salary range fields and no benefits field, you have a gap for roles posted in those states.

Auditing your current ATS for pay transparency readiness

Before you evaluate new platforms, run this audit on your current ATS setup to identify specific gaps.

Test 1: Create a job posting for a California-based role. Does the system prompt you to enter a salary range? Is the field structured (separate min/max fields with currency) or free-form text? Is the range included in job board distributions, or only on your career page?

Test 2: Create a fully remote job posting with no geographic restriction. Does the system flag that multiple state salary disclosure laws may apply? Does it prompt you to include a range? Or does it silently post without a range, leaving you non-compliant in Colorado, California, Washington, and any other applicable state?

Test 3: Pull an audit report. Can you generate a report showing all jobs posted in the last 12 months, their posting locations, and the salary range included (or absence of one) for each? If you received a regulatory inquiry tomorrow, do you have the documentation to demonstrate compliance?

If any of these tests expose gaps, the question is whether they're configuration gaps in your current ATS (fixable) or capability gaps (requiring a different platform).

Frequently asked questions

Which states require salary ranges in job postings?

As of 2026, states requiring salary ranges in job postings include Colorado, California, New York (state and NYC), Washington, Illinois, Massachusetts, New Jersey, Hawaii, Vermont, Minnesota, and Kentucky, with varying employee thresholds. States requiring disclosure on request include Connecticut, Maryland, Nevada, and Rhode Island. The list continues to expand — verify current requirements with employment counsel for each state where you hire.

Does pay transparency law apply to remote jobs?

Yes, with state-specific variations. Colorado's law has been interpreted broadly to cover remote jobs that could be performed from Colorado. California, New York, and Washington apply their laws to jobs performable in those states. For unrestricted remote postings, the safest approach is to include a compliant salary range covering all applicable states. Your ATS should support state-specific geographic targeting of postings.

What's the fine for violating pay transparency laws?

Penalties range from $250 to $10,000 per violation depending on the state, with higher penalties for repeat violations. In states with private right of action (California, New York), individual candidates can sue — and class actions covering systematic non-compliance are a significantly larger financial exposure than per-posting fines suggest.

How should an ATS handle pay transparency for multi-state job postings?

The ideal ATS workflow identifies applicable states based on job location and remote eligibility, prompts for salary range input, flags missing ranges for disclosure-required states, passes structured salary data through to all distribution channels, and maintains an audit trail of what was published, when, and where. Most platforms have salary fields but fewer have the state-specific rule logic and audit capabilities this requires.

What happens if our salary ranges are too narrow or too broad in job postings?

There's no legal requirement that salary ranges be narrow or specific beyond the general requirement that they reflect a "good faith belief" of the compensation range for the role. That said, ranges posted at extremes — such as $30,000–$300,000 for a single role — have attracted regulatory attention in Colorado and New York as potentially evasive of the law's intent. A range that is unrealistically wide tells candidates nothing useful and may draw scrutiny. Best practice is to publish ranges that reflect actual compensation band data for the role, typically within a 20–30% spread from minimum to maximum.