Post a remote job opening today, and you might be breaking the law in a state you've never set foot in — without knowing it.
That's the trap catching small businesses in 2026. What used to be a handful of West Coast disclosure rules has become a patchwork of 20-plus state and local pay transparency laws, each with its own salary-range requirements, employee-count thresholds, and penalty structure. And because most of these laws apply based on where a job could be performed — not where your company is headquartered — a single "Remote — US" listing can trigger compliance obligations in a dozen jurisdictions at once.
If you're a small business owner hiring outside your home state, here's what changed, what it means for your job postings, and how to stay compliant without hiring a compliance department to do it.
What Pay Transparency Laws Actually Require
At their core, these laws force employers to stop treating compensation as a closely guarded secret during hiring. Depending on the jurisdiction, that means one or more of the following:
- Salary range disclosure in job postings — listing the minimum and maximum pay you genuinely intend to offer, not a placeholder range designed to preserve negotiating leverage
- Upon-request disclosure — providing pay ranges to a candidate or current employee who asks, even if it's not required in the posting itself
- Salary history bans — prohibiting employers from asking applicants what they made in a previous role
- Benefits and total compensation disclosure — in some states, listing bonus structures, equity, or benefits alongside base pay
- Internal posting requirements — notifying current employees of open roles and promotional opportunities before or alongside external postings
The common thread: regulators want candidates negotiating from real numbers, not guesswork. For employers, it means the days of "salary commensurate with experience" as a placeholder are ending fast in covered states.
Which States Have Pay Transparency Laws in 2026
As of 2026, roughly 20 states and Washington D.C. — plus several individual cities — have active pay transparency mandates. The core list includes:
California, Colorado, Connecticut, Delaware, Hawaii, Illinois, Maryland, Massachusetts, Minnesota, Nevada, New Jersey, New York, Rhode Island, Vermont, Washington, and Washington D.C., along with city-level ordinances in Cincinnati, Cleveland, Columbus, and Toledo, Ohio.
More states are expected to join by 2027, including additional counties and municipalities layering on their own local requirements. If you hire remotely, treat this list as a moving target and check it at least quarterly.
Employee-Count Thresholds Vary Widely
Not every law applies to every employer, and thresholds differ by state:
| Threshold | States |
|---|---|
| All employers (1+ employees) | Connecticut, Nevada, Rhode Island, Vermont, Washington D.C., Colorado |
| 4+ employees | New York |
| 15+ employees | Illinois |
| 50+ employees | Hawaii |
A five-person startup might be fully exempt from Illinois' law but squarely covered under Colorado's or New York's. This is precisely why small businesses get tripped up — "we're too small for this" is only true state by state, not universally.
The Remote Job Posting Trap
This is the part that catches the most small employers off guard: pay transparency laws generally apply based on where the work could be performed, not where your company is registered.
If you post a role as "Remote" or "Hybrid — flexible location," and someone in Colorado, New York, or California could legitimately apply and do the job from there, most legal guidance treats that posting as subject to those states' disclosure rules — even if you never intended to hire someone from that state. Courts and enforcement agencies have generally sided with the applicant's location, not the employer's headquarters, when determining which law applies.
There are two practical ways to handle this:
- Apply the strictest standard to every posting. Include a salary range, and where relevant, a summary of benefits, in every job ad regardless of location. This is the approach most multi-state employers land on because it's simpler than tracking 20 different rule sets per req.
- Explicitly geo-restrict the posting. If you genuinely don't want applicants from a covered state, state that limitation clearly in the listing ("Remote — must reside in Texas, Florida, or Georgia"). Vague remote listings without a stated restriction are the riskiest posture.
For most small businesses, option one is both safer and better recruiting practice — transparent ranges tend to attract more qualified applicants and reduce time wasted on candidates whose expectations don't match your budget.
Penalties: What Non-Compliance Actually Costs
Penalty structures vary enormously, and a few examples illustrate why this isn't a "we'll deal with it if we get caught" problem:
- Illinois: $250 for a first violation, up to $10,000 for repeat offenses — though employers get a 14-day cure period on the first violation and 7 days on subsequent ones.
- New York: Each non-compliant job posting can be treated as a separate violation, with fines of $1,000 to $3,000 per posting. Ten bad listings can mean five figures in exposure.
- Massachusetts: Enforcement escalates from a warning on a first offense up to $25,000 for a fourth or later violation, with the Attorney General's office now running active enforcement audits.
- New Jersey: Fines start smaller — up to $300 for a first offense, $600 for subsequent ones — but the state Department of Labor and Workforce Development began active audits in 2026 as well.
The pattern across states: first offenses are often forgiving (warnings or small fines with cure periods), but repeat or willful violations escalate quickly, and several states now treat each individual job posting as its own violation rather than counting a bad practice as one infraction.
A Practical Compliance Checklist for Small Employers
- Audit every active job posting for a real, good-faith salary range — not a $40,000–$150,000 spread that tells candidates nothing.
- Identify your remote-eligible postings and either add a range or add an explicit geographic restriction.
- Check your employee count against each state's threshold before assuming you're exempt — thresholds range from "any employer" to 50+.
- Train hiring managers and recruiters not to ask about salary history in states with a ban, even informally in a phone screen.
- Document your range-setting methodology (market data, internal bands, etc.) so you can show good faith if a range is ever questioned.
- Revisit this quarterly. With multiple states set to add requirements through 2027, a posting template that was compliant in January can be out of date by summer.
Why This Connects to Your Books, Not Just Your Job Postings
Pay transparency compliance isn't purely an HR exercise — it touches your financial records too. Once you commit to a public salary range, that range needs to be consistent with your actual payroll budgeting and job-costing categories, or you risk offers that don't match what your books can support. Businesses that track compensation bands, payroll costs, and departmental budgets in a clear, auditable ledger are far better positioned to set ranges confidently — and to defend them if a state agency ever asks how a posted range was determined.
Keep Your Financial Records as Transparent as Your Job Postings
If salary transparency is becoming table stakes for hiring, the same clarity is worth applying to the rest of your business's finances. Beancount.io offers plain-text accounting that gives you complete transparency and control over your financial data — every transaction is version-controlled, auditable, and free of vendor lock-in. Get started for free and see why developers and finance-minded business owners are switching to plain-text accounting.