Minnesota Pay Transparency Law: The 2026 Employer Guide

Minnesota Pay Transparency Law: The 2026 Employer Guide

If you employ 30 or more people in Minnesota, every job posting you publish now has to carry a starting salary range and a description of the benefits that come with the role. The rule sits in Minnesota Statutes Section 181.173, which took effect January 1, 2025. It is short, it is broad, and — unusually for a pay transparency law — it says almost nothing about penalties, which trips up employers who assume vague enforcement means low risk.

This guide walks you through exactly who the law covers, what belongs in a compliant posting, how Minnesota's rules differ from other states', what the enforcement picture actually looks like, and how to build ranges that hold up. If you run compensation or talent for a company with a Minnesota footprint, treat this as your working checklist.

TL;DR: Minnesota pay transparency at a glance

• Section 181.173 took effect January 1, 2025 and applies to employers with 30 or more employees at one or more sites in Minnesota.
• Every job posting must include a starting salary range — a minimum and maximum, based on your good-faith estimate at the time of posting.
• Open-ended ranges are prohibited. If you won't offer a range, you must list a fixed pay rate instead.
• Postings must also carry a general description of all benefits and other compensation, including health and retirement benefits.
• The rule reaches postings made directly or through a third party, electronic or printed.
• The statute names no specific penalty, but general Chapter 181 enforcement — through the Department of Labor and Industry or the Attorney General — can reach it.

Who the Minnesota pay transparency law covers

You are covered if you employ 30 or more employees at one or more sites in Minnesota. Read that threshold carefully, because it is narrower than it looks. Minnesota counts employees within the state. A company with 2,000 people nationwide but only 20 in Minnesota falls below the line, while a regional employer with 35 Minnesota staff is squarely covered. This differs from states that count your entire workforce regardless of location.

The definition of "employer" is deliberately wide. It reaches corporations, partnerships, associations, nonprofits, and governmental subdivisions — the state, counties, cities, towns, and school districts all sit under the same rule as private business. If you are a public-sector HR leader in Minnesota, this applies to you as much as it does to a private company down the street.

A few coverage points worth flagging:

• Site count doesn't matter, headcount does. "One or more sites" means you add up Minnesota employees across every location. Three offices of 12 each still clears the 30-employee threshold.
• Third-party recruiting is included. The posting rule follows the job, not the channel. If a staffing firm or recruiter advertises your opening, that posting still has to carry the range and benefits description.
• The format is irrelevant. Electronic listings and printed hard copy are both "postings" under the statute, as long as they solicit applicants for a specific position and list qualifications.

If you hire across several states, Minnesota rarely stands alone. Layer it on top of the broader patchwork we map in our 2026 multi-state pay transparency compliance guide so a single national posting can satisfy the strictest jurisdiction it touches.

What every job posting must include

Section 181.173 asks for two things in each posting, and both matter.

A starting salary range. You must disclose the minimum and maximum annual salary, or the minimum and maximum hourly rate, that reflects your good-faith estimate for the role at the time you post it. The word "starting" is a helpful narrowing: this is the entry point for the role, not the full career span of the pay grade. And the range cannot be open-ended — "$70,000 and up" or "competitive" does not satisfy the law. If you genuinely do not plan to offer a range for a position, the statute gives you one alternative: list a single fixed pay rate.

A general description of benefits and other compensation. Every posting also has to describe the benefits and other compensation on offer, expressly including any health or retirement benefits. This is broader than the pay range and is where many employers fall short — they add a salary band but forget the benefits language. A short, honest summary of health coverage, retirement contributions, bonuses, and other compensation elements meets the bar.

The phrase "good-faith estimate" carries weight. The range you publish is supposed to reflect what you actually expect to pay. A floor-to-ceiling band so wide it tells a candidate nothing — the kind that spans an entire pay grade and then some — runs against the purpose of the law. Post the range you would genuinely offer within, not the widest band your payroll system will allow.

Here is a quick way to see the difference:

If your ranges feel like guesses, that is a signal your underlying structure needs work — not that you should widen the band to stay safe. Ranges that flow from a real job-leveling structure hold up far better than numbers pulled to cover every contingency. We break down how to build numbers you can stand behind in our guide to defensible pay ranges.

How Minnesota compares to other state laws

Minnesota's law rhymes with the wave of state pay transparency rules but has its own quirks. Three stand out.

The 30-employee, in-state threshold is distinctive. Many states set a lower bar — New York and others reach employers with as few as four employees, counted nationwide. Minnesota's higher, state-specific count means some multi-state employers are covered in New York or California but not in Minnesota, and vice versa. Do not assume a policy built for one state satisfies another.

The benefits requirement is more explicit than most. Plenty of state laws require a pay range. Fewer spell out, as Minnesota does, that you must also describe health and retirement benefits in the posting itself. If your national posting template only carries a salary band, it is not Minnesota-ready.

Minnesota does not add a salary-history ban to this statute. Some states pair their posting rules with an explicit prohibition on asking about prior pay. Section 181.173 is narrower — it governs what goes into the posting, not what you may ask a candidate. That said, building offers from a role's worth rather than a candidate's pay history is still the sounder practice, and it keeps you aligned with the stricter states you may also operate in.

The throughline across every one of these laws is the same: your posted numbers are only as defensible as the structure behind them. That is why a consistent point-factor job evaluation method — scoring jobs against weighted compensable factors — travels so well across state lines. One rigorous internal structure answers the range question in Minneapolis, Manhattan, and everywhere else at once.

Enforcement: quieter than most, not toothless

Here is where Minnesota surprises people. Section 181.173 names no specific penalty and lays out no dedicated enforcement mechanism. On its face, the statute simply says what you must post and stops there.

That silence is not the same as safety. The rule lives inside Chapter 181 of the Minnesota Statutes, which carries general enforcement machinery. An individual can bring a claim to the Minnesota Department of Labor and Industry, and the state Attorney General has authority to enforce violations. Several statutes in this chapter allow a private right of action, and an employer found to have violated a Chapter 181 provision can be liable for compensatory damages and other appropriate relief, including injunctive relief.

In plain terms: the absence of a fixed fine schedule means the downside is less predictable, not smaller. A pattern of non-compliant postings can surface in a complaint, an investigation, or a broader employment dispute — and it hands a regulator or a plaintiff's attorney an easy, documented failure. The reputational cost of being the employer that posts ranges everyone can see are hollow is its own penalty. Treat the vagueness as a reason for caution, not a loophole.

A practical compliance checklist

Work through these before your next Minnesota posting goes live:

• Confirm you employ 30 or more people within Minnesota, counting across every in-state site.
• Put a bounded minimum and maximum starting range on every posting — or a single fixed pay rate if you truly won't offer a range.
• Kill any open-ended language: no "and up," no "competitive," no one-sided figures.
• Add the benefits description — health, retirement, bonuses, and other compensation — to every posting, not just the salary band.
• Send the range and benefits language to any third-party recruiter or staffing firm posting on your behalf, and confirm they use it.
• Tighten ranges so they reflect a good-faith estimate of what you would actually pay, not the full width of a pay grade.
• Anchor published ranges to a real job-leveling structure so they hold up under both a transparency complaint and a pay-equity review.

Frequently asked questions

When did the Minnesota pay transparency law take effect? January 1, 2025. The requirement was enacted in 2024 and codified at Minnesota Statutes Section 181.173. You can read the statute directly on the Minnesota Office of the Revisor of Statutes site.

Which employers are covered? Employers with 30 or more employees at one or more sites in Minnesota. The count is limited to employees within the state, and it includes private business, nonprofits, and governmental subdivisions such as cities, counties, and school districts.

What has to be in a Minnesota job posting? A starting salary range — a minimum and maximum annual salary or hourly rate based on your good-faith estimate — and a general description of all benefits and other compensation, including any health or retirement benefits. Open-ended ranges are prohibited.

Can we post a single pay rate instead of a range? Yes. If you do not plan to offer a range for a position, the statute lets you list a fixed pay rate instead. What you cannot do is leave the figure open-ended.

Does the law apply to postings by third-party recruiters? Yes. The definition of "posting" covers recruitment done directly by the employer or indirectly through a third party, in electronic or printed form. If a staffing firm advertises your role, the range and benefits description still apply.

What are the penalties for non-compliance? The statute itself specifies no penalty. Enforcement runs through general Chapter 181 mechanisms — a claim to the Department of Labor and Industry or action by the Attorney General — which can reach compensatory damages and injunctive relief. As the legal analysis from Seyfarth Shaw notes, the lack of a fixed penalty schedule makes the exposure less predictable, not necessarily smaller.

The bottom line

Minnesota's pay transparency law is compact, but its reach is real: a starting range and a benefits description on every posting, for every covered employer, with enforcement that is quiet rather than absent. The employers who stay out of trouble are the ones whose posted ranges are not guesses — they flow from a clear view of what each job is worth and where it sits in the structure.

That is the work PointFactors is built for: scoring jobs against weighted compensable factors so your levels, bands, and published ranges hold up under a transparency complaint and a pay-equity challenge alike. Book a demo and see how fast you can turn a messy set of jobs into ranges you can defend — in Minnesota and every other market on your map.

Justin Hampton is the founder and CEO of PointFactors.