Minnesota Pay Transparency Law: Salary Range Posting Requirements

What Minnesota's Pay Transparency Law Actually Requires

Picture a Minnesota employer — a 45-person professional-services firm — who spent March of last year quietly updating every job posting template after realizing the salary ranges were missing. Not because a regulator knocked. Because a hiring manager mentioned, almost in passing, that a candidate had asked whether the company was following the new state law.

That firm was right to act. Minnesota's pay transparency requirement is now in effect, and the obligations go slightly further than most states. This guide explains exactly what the law requires, who it covers, and what a compliant posting looks like — so your team is not learning the rules from a candidate.

Who the Minnesota Pay Transparency Law Covers

Minnesota's salary-range posting requirement applies to employers with 30 or more employees operating in the state. That threshold places the obligation squarely on the mid-market employers — companies large enough to post roles regularly but often without a dedicated compensation function.

If your organization meets that headcount, the requirement applies to any job posting for a position that will be performed, at least in part, in Minnesota — including remote roles with a Minnesota-based workforce. The law is not limited to postings on your own careers page; any externally visible job advertisement is covered.

As of 2026, pay-transparency laws have been enacted across 25 jurisdictions in the United States — a count that includes states and localities — and the pace of adoption has accelerated each legislative session (Brightmine, 2025). Minnesota is among the more recent additions to that list.

Requirements vary in the details, and state laws evolve. Confirm the current rule — including the precise employee-count threshold and any regulatory guidance on remote workers — directly with the Minnesota Department of Labor and Industry or employment counsel before finalizing your compliance approach.

What Must Appear in Every Covered Job Posting

Minnesota's requirement is notable for two reasons: it demands both a salary range and a description of benefits. Most state pay-transparency laws stop at the wage range; Minnesota asks employers to go one step further.

Salary or wage range. Covered postings must include the minimum and maximum annual salary or hourly wage the employer genuinely expects to pay for the role. This should be a good-faith range — not a formality with a floor of $1 and a ceiling of $500,000. The range should reflect what your compensation band for that role actually looks like.

Benefits description. Alongside the pay range, the posting must describe any general benefits offered with the position. That does not mean a line-by-line summary of your plan documents. It means a good-faith description: health coverage, retirement contributions, paid leave, bonuses or incentive eligibility, and any other material benefits. The specificity required is proportionate to what a reasonable candidate would need to understand the full compensation picture.

What the law does not require is a precise salary figure or a commitment to pay anyone within the range. The posted range should represent your band for the role. If internal review shows that range to be inconsistent — wider or narrower than your actual practice — that is a signal your compensation structure needs attention, not just your posting template.

If your organization does not yet have defined pay bands, building a formal job band structure before drafting posting ranges is the more defensible path. A range derived from a structured band is auditable; a range estimated on the fly is a liability.

The Enforcement Picture and Why It Matters

Minnesota's pay transparency law is enforced through the state's Department of Labor and Industry. The specific penalty amounts and enforcement mechanisms are set by statute — confirm the current penalty schedule and any available regulatory guidance with the Department or with employment counsel, as these details are subject to amendment.

What is structurally true of nearly all state pay-transparency enforcement models is also true here: each non-compliant posting is treated as a separate violation. If your organization posts the same role across five job boards without a required salary range, that is five potential violations, not one. California, for example, explicitly treats each posting lacking a required pay range as a separate violation, carrying civil penalties of $100 to $10,000 per violation under Labor Code §432.3(f) (SixFifty, 2026; HR.Law, 2025). Minnesota's mechanism is distinct, but the structural logic — posting × platform = exposure — is a useful frame for understanding the stakes regardless of jurisdiction.

Do not treat this as legal advice. Confirm Minnesota's current penalty structure, complaint and investigation process, and any applicable safe-harbor provisions with the Minnesota Department of Labor and Industry or employment counsel.

Why "Good Faith" Is the Operative Standard

Most well-drafted pay-transparency statutes — and Minnesota's follows this pattern — anchor the posting obligation to a good-faith range: what the employer reasonably expects to pay upon hire, given the role, the market, and its internal structure.

That standard has a practical consequence. A range that is technically present but clearly detached from reality — $30,000 to $300,000 for a mid-level accountant, for instance — likely fails the good-faith test. Enforcement bodies and plaintiff's counsel in pay-transparency cases look not only at whether a range was posted, but whether it was meaningful.

California's SB 642, effective January 1, 2026, made this explicit: it redefines "pay scale" as a good-faith estimate of the range the employer reasonably expects to pay upon hire (RemoteLaws, 2026). Minnesota's statutory language pursues the same principle. The practical implication is that posting compliance and compensation band discipline are not separate projects — they are the same project.

Our pay transparency compliance hub covers the good-faith standard across jurisdictions if you want to see how states are applying it in practice.

How Minnesota Fits the National Pay-Transparency Trend

Minnesota is one of a growing cohort of states that have moved from voluntary guidance to statutory obligation. Pay-transparency laws have now been enacted across a substantial share of the country — estimates range from 17 states with active laws (Lift HCM, 2026) to 25 jurisdictions including localities (Brightmine, 2025), depending on methodology. Maine's law takes effect July 29, 2026; Virginia's on July 1, 2026; Delaware's on September 26, 2027 (ADP, 2026; RemoteLaws, 2026). The trend is unambiguous.

For multi-state employers, Minnesota's benefits-description requirement adds a layer of complexity that purely wage-focused laws do not. A single posting template that satisfies, say, Colorado (which requires wage ranges and benefits descriptions of its own under the Equal Pay for Equal Work Act) and California (wage range only) may or may not satisfy Minnesota's formulation. Treating each state as a separate compliance item is prudent until you have mapped your posting template against each applicable jurisdiction.

Our state-by-state pay transparency overview is a useful starting reference for that mapping exercise. You may also want to review how neighboring states are approaching disclosure — see our guides on Massachusetts pay transparency and Rhode Island pay transparency if your workforce extends into the Northeast.

Building a Compliant Posting Process: The Practical Path

Compliance with the Minnesota pay transparency law is not, at its core, a legal project. It is a compensation-structure project with a legal deadline.

The sequence that works:

1. Confirm your covered roles. Identify every posting you publish for positions that could be performed in Minnesota by someone on your payroll.

2. Establish or validate pay bands. Each covered role needs a defensible min–max range. If your bands live in a spreadsheet, note that research finds 94% of spreadsheets used in business decision-making contain errors (Phys.org / Frontiers of Computer Science, 2024). A structured band tool creates an auditable record; a spreadsheet does not.

3. Draft a benefits summary template. Create a standard paragraph — or a role-type-specific variant — that describes your material benefits. Legal should review it once; then it is an operational asset.

4. Update your posting template. Embed the salary range and benefits summary fields as required, not optional, fields in your ATS or posting workflow.

5. Confirm with counsel. Before you publish the first compliant posting, have employment counsel confirm your interpretation of the statute and any regulatory guidance the Minnesota Department of Labor and Industry has issued.

Job Band Builder's pay-transparency generator covers Minnesota among its supported US states, producing posting-ready salary range language from your structured bands. But the precondition — the bands themselves — has to exist first.

Start with a Compliant Template

If you need a ready-to-use starting point, the Pay Transparency Job Posting Kit includes posting templates formatted for Minnesota's requirements — salary range fields, benefits description language, and guidance on the good-faith standard — alongside templates for other covered states.

The kit is a practical starting point, not a substitute for legal review. Use it to structure your posting process; confirm the final output with counsel or the Minnesota Department of Labor and Industry.

For a fuller picture of how to build the compensation bands that make compliant posting possible, the complete guide to job band structures covers the methodology from scratch.

Minnesota's law is clear in its intent: candidates deserve enough information to make informed decisions, and employers who build that information into their compensation process — rather than bolting it on at the posting stage — are better positioned to compete for talent and to withstand scrutiny. ```