)
US Pay Transparency Patchwork: What Changed in Q3 2026
Two new state pay transparency laws took effect within four weeks of each other at the start of Q3: Virginia on July 1, and Maine on July 29. Neither is a small addendum to an existing rule. Virginia's law applies to employers of any size, and Maine's replaces an earlier, narrower disclosure requirement with a broader one carrying new recordkeeping obligations.
For a company running payroll and hiring across multiple US states, this is the pattern to plan around, not the exception. Pay transparency in the US isn't one law with fifty local variations. It's a fast-growing list of separate statutes, each with its own trigger for coverage, its own definition of what must be disclosed, and its own effective date, adding one state at a time. Q3 2026 is a clear example of how quickly that patchwork moves and what it demands of a multi-state employer.
Neither law came with a grace period for getting oriented. Virginia's disclosure and salary-history rules have applied to every posting made since July 1, with weeks of exposure already accumulated by the time this publishes. Maine's obligations, including a three-year recordkeeping duty that runs after termination, went live on July 29 with no ramp-up period. A posting still up today without the required pay range isn't a future item on a compliance roadmap. It's either compliant right now, or it's a live violation.
What changed on July 1: Virginia
Virginia's law, signed by Governor Spanberger, took effect July 1, 2026. Two things make it worth attention beyond its date.
No size threshold. Most state pay transparency laws only apply once an employer reaches a headcount threshold, often 10, 15, or 25 employees. Virginia applies to any employer doing business in the state that employs one or more people. There's no headcount floor to clear before the disclosure and salary-history obligations apply.
Two obligations, not one. The law requires employers to disclose the wage, salary, or wage or salary range for a position in both public and internal job postings, covering new hires, promotions, and transfers, and to set the wage, salary, or wage or salary range in good faith. It also prohibits employers from asking about or relying on a candidate's salary history, and bars retaliation against candidates or employees who decline to share it or who ask for a wage range.
A cure period, but only against private lawsuits. If an employer corrects a job posting missing the required pay information within 15 business days of written notice, it isn't liable for that violation in a private lawsuit. The cure period doesn't stop the Attorney General from pursuing civil penalties regardless, up to $1,000 for a first violation and $5,000 for later ones, and it doesn't extend to other violations, such as asking a prohibited salary history question.
What changed on July 29: Maine
Maine's LD 54, signed April 24, 2026, took effect July 29, 2026. It applies to employers with 10 or more employees.
Covered employers must include a pay range in job postings, or note when a role is commission-only, and provide an employee, on request, with the pay range offered for the position that employee holds. It also introduces a recordkeeping obligation that's easy to miss: employers must retain pay history records for the duration of an employee's employment and for 3 years after termination.
That retention requirement is a payroll-data problem as much as a legal one. It means pay history has to be preserved, structured, and retrievable per employee, per state, for years after the employment relationship ends, not just current at the point a job posting goes live. From July 29, covered employers must retain each employee’s pay history throughout employment and for 3 years after termination. That requires records to remain structured and retrievable long after the employment relationship ends.
Remote hiring extends both laws further than a state-by-state list
Virginia's law applies to any employer with employees in Virginia and covers every posting the employer makes, internal or external, even for a position located outside the state. A single Virginia-based employee is enough to bring a company's postings everywhere into scope, regardless of where the open role itself sits.
Maine's threshold is less settled. The law applies to employers with 10 or more employees, but the statute doesn't specify whether that count includes only Maine-based staff or a company's full workforce, an ambiguity employment counsel has flagged directly as a likely source of compliance confusion. Until the Maine Department of Labor or a court resolves it, a company can't assume its Maine headcount alone determines coverage.
Either way, a state's payroll footprint isn't the test. Obligations can turn on a single hire in one state or an unresolved headcount question in another, which is one more reason "which states are we in" undersells the problem.
The baseline this landed on
Virginia and Maine didn't arrive in a vacuum. By mid-2026, a well-established group of states already required salary range disclosure in job postings, including California, Colorado, Hawaii, Illinois, Maryland, Massachusetts, Minnesota, New Jersey, New York, Vermont, and Washington, each with its own employer-size threshold, geographic test, and posting definition. Connecticut, Nevada, and Rhode Island take a different starting point built around disclosure on request, though each of those laws also triggers disclosure at other defined points, such as before an offer or at hire, not only when an employee asks for it. Posting-required and on-request aren't two clean categories; they're two starting points that each state then complicates in its own way. Sources differ on the exact total count once every city and county ordinance is factored in, which is itself part of the point: there is no single authoritative number, only a state-by-state check that has to be run fresh for each place where a company posts a role or employs someone.
Delaware has also enacted a law set to take effect September 26, 2027. The law exempts employers with 25 or fewer employees, which means it applies to employers with 26 or more.
Why "which states am I in" is the wrong question
The instinct is to treat this as a checklist of states you operate in. It understates the problem in three ways.
Coverage triggers differ by employer size, not just by state. Virginia has no floor. Maine applies to 10 employees. Others sit at 15, 25, or higher. A company can be in scope in one state and out of scope in a neighboring state, even with identical headcount, because the thresholds differ.
Coverage triggers differ by activity, not just by presence. States use different connecting factors to decide who's covered: where the work may be performed, where the employee reports, whether the employer is based in the state, or whether the posting is tied to a state location. Visibility to candidates in a state isn't itself a universal test, but several of these factors, alone or combined, can pull a remote posting into a state's regime without the employer having a local office there.
The obligations themselves aren't uniform. Posting-based disclosure, pay-on-request, salary history bans, promotion and transfer coverage, and recordkeeping requirements like Maine's don't all apply the same way in every state with a pay transparency law. Meeting the letter of one state's requirement doesn't tell you whether you're meeting another's.
The result is that "are we compliant with pay transparency" isn't a single yes-or-no. It's a question that has to be asked per state, per posting, and periodically re-asked as more laws take effect and existing ones are amended.
What this asks of the underlying data
Meeting these obligations at scale depends on data that most companies don't hold in a single, current place.
A live map of where coverage applies. Which states, at what headcount, and for which postings, are kept current as new laws take effect.
Pay ranges are set in good faith and tied to the role, not a placeholder wide enough to avoid the question. Most of these laws don't set a categorical cap on the range’s width, but several, including Virginia's and Delaware's, treat the breadth of the range as evidence of whether it was set in good faith.
Salary history is separated from current pay decisions, so a ban on asking for or relying on it can be honored rather than assumed.
Retention that survives the employment relationship. Maine's three-year post-termination window requires that pay history remain accessible well after the usual reasons for keeping it close at hand have passed.
In a fragmented payroll and HR setup, spread across regional vendors and disconnected recruiting tools, that combination doesn't exist in one place. It's assembled manually, state by state, every time a role is posted or a law changes. The same fragmentation that drives up reconciliation time and adds hidden vendor cost elsewhere shows up here as a quieter, ongoing exposure: a posting that's technically out of date the moment a new state law lands, with no single system tracking that it happened.
What "current" looks like against this patchwork
| What the patchwork requires | What it asks of your data |
|---|---|
| Know where disclosure applies | Coverage rules tracked per state and kept current as laws take effect |
| Post a good-faith range, not a placeholder | Pay ranges tied to the actual role and reviewed, not defaulted wide |
| Honor salary history bans | Salary history separated from current pay decisions in the system |
| Meet retention requirements like Maine's | Pay history retained and retrievable per employee, past termination |
| Apply the right rule to the right posting | Postings checked against the specific state and size threshold that applies, not a single company-wide policy |
None of the above substitutes for legal review of how a specific law applies to a specific company. What it does is make the underlying facts, where you're covered, what you've disclosed, and what you're required to retain, something the system already tracks, rather than something reconstructed after a new law takes effect or a posting is challenged. That's the same principle behind how Globalli generally approaches payroll compliance: monitor what changes at the country or state level, and keep the data in a state where answering the question is fast, not a project.
Virginia and Maine are two additions to a growing list of state and country-level obligations that depend on connected workforce and pay data. See how a unified global payroll operating model can reduce the manual work created by fragmented systems and changing requirements.
Frequently asked questions
What changed in US pay transparency law in Q3 2026?
Virginia's pay transparency and salary history law took effect on July 1, 2026, and applies to employers of any size. Maine's LD 54 took effect July 29, 2026, applying to employers with 10 or more employees and adding a pay history retention requirement.
Does Virginia's law have a minimum employee count?
No. It applies to any employer doing business in Virginia that employs one or more people, which is broader than most state pay transparency laws.
What does Maine's new law require beyond posting a pay range?
Employers with 10 or more employees must include a pay range in job postings or flag a commission-only role, provide an employee, on request, with the pay range offered for the position that employee holds, and retain pay history records for the duration of employment plus three years after termination.
How many states now have pay transparency laws?
Sources vary on the exact total once city and county ordinances are included, but well over a dozen states require salary range disclosure in job postings, with several more requiring a range on request, and that number is growing. The specific requirement always depends on the state and the employer size in question.
Why is this hard to manage across multiple states?
Coverage thresholds, disclosure formats, salary history rules, and retention requirements all differ by state, and several are triggered by where the work may be performed or where the employer is based, rather than only where it has an office. Meeting one state's rule doesn't confirm compliance with another's, and the underlying pay and posting data needed to verify this is often not held in one place.
Disclaimer: This article provides general information only and does not constitute legal, tax, or financial advice. National implementation requirements and effective dates may change. Last reviewed: July 2026. Consult qualified legal advisers in each relevant jurisdiction when assessing how the pay transparency laws apply to your organization.