Minnesota Pay Transparency Rules for Employers

Which Minnesota employers must include pay ranges in job postings?

Any employer with 30 or more employees at one or more sites in Minnesota must comply. The threshold is total employees in Minnesota, counted across all of the employer’s Minnesota sites combined. Smaller employers (under 30 Minnesota employees) are not subject to the disclosure requirement, though many post ranges anyway because applicants increasingly expect them. The covered-employer definition is broad: corporations, partnerships, nonprofits, governmental subdivisions, school districts, and unincorporated associations are all reached. The defining language: “Employer means a person or entity that employs 30 or more employees at one or more sites in Minnesota.” (Minn. Stat. § 181.173 subd. 1(b)).

The 30-employee count includes part-time, seasonal, and full-time employees. It does not include independent contractors. The contractor-versus-employee distinction is its own audit area in Minnesota; for the analytical framework, see our overview of the employee versus independent contractor test. Employers near the threshold should run the count carefully because crossing 30 mid-year pulls every subsequent posting into compliance. In my practice, the recurring trap is a Minnesota-headquartered company with a remote workforce that treats only its in-state desk-based employees as the count. The statute reaches every Minnesota employee, regardless of where the desk sits.

The threshold is fixed, not phased. There is no graduated rule for employers in the 25-to-29 range. An employer counts as covered or not, and the count runs as of the date the posting goes live.

What does the pay-disclosure rule actually require?

Three pieces, all in each posting: a starting salary range, a general description of benefits, and a general description of any other compensation. The controlling subdivision states: “An employer must disclose in each posting for each job opening with the employer the starting salary range, and a general description of all of the benefits and other compensation, including but not limited to any health or retirement benefits, to be offered to a hired job applicant.” (Minn. Stat. § 181.173 subd. 2(a)).

The “starting” qualifier is meaningful. The rule asks for the range a successful applicant would land in at hire, not the lifetime ceiling for the role. A range that pretends a senior performer’s salary is the floor is not a starting range. Conversely, a range that tops out at the maximum the employer would ever pay misrepresents the actual hiring envelope.

The benefits description is “general” rather than line-by-line. A good-faith summary of major categories (health, dental, vision, retirement contribution, paid time off, leave benefits) satisfies the statute. The categorical “other compensation” piece reaches bonuses, equity, profit sharing, sign-on payments, and any other variable component a hire could expect. Vague boilerplate (“competitive benefits package”) does not satisfy this rule. Minnesota’s paid family and medical leave program and earned sick and safe time both create benefits that should appear in this disclosure for every covered position. In my practice, the cleanest postings list 5 to 8 lines of benefits in plain English, with one or two lines on bonus or equity if either applies.

How specific does the salary range have to be?

It must be a good-faith estimate of the minimum and maximum a successful applicant would actually be offered. The statutory definition: “Salary range means the minimum and maximum annual salary or hourly range of compensation, based on the employer’s good faith estimate, for a job opportunity of the employer at the time of the posting of an advertisement for such opportunity.” (Minn. Stat. § 181.173 subd. 1(d)).

“Good faith” is the operative phrase. The early-adopter states (Colorado, California, Washington) saw widespread use of theatrical ranges (for example, “$50,000 to $250,000”) that technically named numbers without communicating anything. Minnesota’s statute closes that loophole in two ways. First, the good-faith standard is a content rule: the range must reflect what the employer would actually pay. Second, subdivision 2(b) explicitly bars open-ended ranges and requires a fixed rate where the employer has not settled on a range.

The practical width that holds up in audit and litigation is rarely more than 25-to-30 percent from floor to ceiling. A floor of $80,000 with a ceiling of $105,000 reads as a real range; a floor of $80,000 with a ceiling of $200,000 reads as no range at all. About half of the postings I have audited for clients used a width that would have failed a good-faith test under any state’s rule, and the fix was almost always to narrow the upper bound to what the employer would in fact pay a strong candidate.

What benefits and bonus categories must appear in the disclosure?

Yes. Both. Subdivision 2(a) requires “a general description of all of the benefits and other compensation, including but not limited to any health or retirement benefits.” The “including but not limited to” language is intentional. It signals that health and retirement are the floor, not the ceiling, of what the description must cover. The disclosure obligation runs to whatever the employer would in fact extend at hire: any health-care benefit, any retirement contribution, paid leave categories, and any other compensation an applicant should know about before deciding whether to apply.

A workable benefits description block lists, at minimum: health and dental coverage (with a brief note on employer contribution if material), retirement contribution (401(k) match percentage, vesting summary, or pension category), paid time off and holiday categories, applicable leave benefits (Minnesota’s earned sick and safe time and the new paid family and medical leave program both apply by statute), and any tuition assistance, equity, or wellness benefits the employer offers. Equity disclosure deserves its own attention: see our discussion of enforceability of equity promises in recruiting for why ambiguous equity language at the posting and offer stage causes the most disputes downstream.

The “other compensation” piece is where employers most often underdisclose. A role that pays a base of $80,000 plus a discretionary bonus historically running 10-to-15 percent should say so. A role with equity participation should name it, even if the structure is “RSU grant per executive compensation policy.” Generic boilerplate (“comprehensive benefits”) does not work. The disclosure is not asking for grant agreements; it is asking for honest categories the applicant can evaluate. For a parallel discussion of how Minnesota handles wage-disclosure protections among existing employees, see our article on legal risk of salary disclosures under pay transparency laws.

How does the rule apply to commission, hourly, and tipped positions?

The statute uses “annual salary or hourly range of compensation” in the definition, which means hourly rates count and must follow the same good-faith estimate rule that applies to salaried roles. A retail role posted at “$18.00 to $22.50 per hour” is compliant if those numbers reflect the actual hiring envelope for the position. A role posted at “$15 to $40 per hour” almost certainly is not, because the breadth alone signals the absence of a real range.

Commission-based roles and tipped positions are not exempt from the rule. The cleanest disclosure for a commission-based role is the expected total annual compensation a typical performer earns, with a plain-English note on the commission structure (rate, draw, ramp). A “base only” disclosure for a commission-heavy role misleads applicants and invites enforcement attention. For tipped roles, disclose the base hourly rate and the historical tip range, both labeled. The rule does not require employers to predict future tip amounts. It does require honesty about what an applicant should expect.

In my practice, the recurring failure mode in sales-heavy organizations is a posting that lists only the base salary on a role where 60 percent of total comp is variable. That misstates the real offer in a way the employer would not stand behind in a meeting. The fix is mechanical: publish a target on-target-earnings figure alongside the base.

How does the rule reach internal promotions, remote work, and out-of-state hires?

The statute applies to “each posting for each job opening with the employer.” A posting is “any solicitation intended to recruit job applicants for a specific available position, including recruitment done directly by an employer or indirectly through a third party.” (Minn. Stat. § 181.173 subd. 1(c)). The definition is medium-neutral and applicant-source-neutral: an internal-only listing on a company intranet, a public posting on the employer’s careers page, and a recruiter’s distribution of a role specification are all postings if they describe a specific position and include qualifications.

Internal promotion solicitations that are open to internal applicants and contain qualifications are postings under this definition and are covered. Internal-only postings on company intranets carrying qualifications language fall inside the rule. A purely informal “anyone interested in the warehouse manager role, talk to Nancy” hallway announcement is not a posting; a written internal listing distributed to employees is.

Remote roles posted by a Minnesota-covered employer are covered if the role can be performed by a Minnesota resident. Out-of-state employers without a Minnesota site or any Minnesota employees are not covered. Out-of-state employers with at least 30 Minnesota employees are covered for any posting that could be filled by a Minnesota worker. The conservative rule for any covered employer is to publish a Minnesota-compliant range on every public posting, regardless of whether a particular hire is likely to land in or outside Minnesota. The cost of a single uniform format is small compared to the cost of explaining a state-by-state divergence in an audit.

What counts as a job posting under the rule?

Any solicitation intended to recruit applicants for a specific available position that includes qualifications. The definition reaches printed and electronic postings, postings made directly by the employer or indirectly through third parties (recruiters, staffing agencies, job boards), and any posting that lists what applicants must have. The statutory text: “Posting means any solicitation intended to recruit job applicants for a specific available position, including recruitment done directly by an employer or indirectly through a third party, and includes any postings made electronically or via printed hard copy, that includes qualifications for desired applicants.” (Minn. Stat. § 181.173 subd. 1(c)).

Three implications follow. First, a job-board listing on Indeed or LinkedIn is a posting. Second, a retained-search firm’s listing distributed by the recruiter to its network is also a posting if it includes qualifications. Third, a posting that omits qualifications language (a brief social-media teaser saying “we are hiring”) is not necessarily a posting under the statute, though qualifying it as a non-posting is risky if applicants would reasonably treat it as recruitment.

A few items I have analyzed for clients fall in the gray zone. Stock language at the bottom of a careers page (“we are always interested in hearing from talented people”) is not a posting because it is not about a specific available position. A LinkedIn post by a recruiter naming a specific role and listing required experience is a posting and triggers the rule. A networking-event flyer naming open positions and qualifications is a posting. The test runs to specificity plus qualifications, not the medium.

Who enforces the rule, and what triggers an investigation?

The Minnesota Department of Labor and Industry handles wage-and-hour enforcement under the broader chapter, and the most common enforcement entry point for § 181.173 is an applicant complaint or a competitor or current-employee tip. The statute itself does not create a stand-alone civil penalty, but the Department’s broader enforcement authority and the practical risks (applicants self-screening, public complaints, and use of the disclosure record in Minnesota Human Rights Act, Minn. Stat. § 363A.08 compensation-discrimination claims) supply meaningful pressure.

What I see in audit-prone industries (retail, healthcare, professional services, technology) is that complaints arrive from one of three sources: an applicant who applied for a role, did not get it, and noticed the posting had no range; a current employee who learned that a recently posted role lists a range above the employee’s pay; or a competitor calling out a clearly noncompliant posting on a public board. Department staff have generally taken a corrective-first approach with first-time noncompliant employers, but a pattern of noncompliance or a pretextual range invites tougher treatment.

The federal angle is relevant too. The Equal Employment Opportunity Commission has signaled that range disclosures (or their absence) can become evidence in pay-discrimination cases. A pattern of below-range payment to women or minority hires for the same posted role is now visible in a way it was not before public disclosure was the rule.

How does Minnesota’s rule compare to other states’ pay-transparency laws?

Minnesota joins Colorado (effective 2021), Washington (2023), California (2023), and New York (2023) as states requiring pay-range disclosure in job postings. Each state’s definition of “covered employer,” “covered posting,” and “salary range” differs. Minnesota’s 30-employee threshold is higher than California’s 15-employee floor and matches the contemporary employee-count anchors used in several other state regimes. The good-faith requirement and the explicit ban on open-ended ranges align Minnesota with Washington and Colorado, both of which closed similar loopholes after early-adopter experience.

The most important comparative point: a multi-state employer cannot rely on a single posting to satisfy all jurisdictions. The conservative approach for an employer hiring across multiple jurisdictions is to publish a posting that satisfies the most-demanding state in the hiring footprint and verify state-by-state. In my practice, multi-state retailers and SaaS employers handle this by adopting a single nationwide posting standard that satisfies whichever jurisdiction in their footprint asks for the most. The compliance cost of one posting standard is materially lower than the cost of a posting matrix. For employers comparing Minnesota practice with neighboring states, see our overview of differences in Minnesota versus Wisconsin employment law compliance.

This area is moving fast. Several states have proposed or recently passed similar laws (Massachusetts and New Jersey both have bills moving). For employers building a 2026 hiring plan, the safer assumption is that more disclosure will be required by more states each year, not less.

What are the practical risks of getting the disclosure wrong?

Three practical risks, in order of likelihood. First, applicant attrition: about half the candidates I have surveyed for clients self-screen out of postings without a range, and the strongest candidates are the most likely to do so. A noncompliant posting is a hiring-funnel problem before it is a legal problem. Second, complaint exposure: a Department of Labor and Industry complaint from a non-hired applicant or a tipped current employee can put the employer’s hiring practices and the underlying pay structure under audit. Third, internal-equity exposure: once a public range goes live, current employees in the same role can see whether they are inside or below it, and a below-range current employee has the foundation for a question that quickly becomes a discrimination claim or a wage-disclosure-protected conversation.

The cleanest version of compliance is a written internal procedure: every posting goes through a single reviewer who checks the range against the actual hiring envelope, runs the range against the current pay band for the role, confirms the benefits description matches the offer letter the company would issue, and dates the version. That procedure reduces the most common failure modes (theatrical ranges, mismatched benefits descriptions, stale postings) to nearly zero.

A useful adjacency: Minnesota’s wage-disclosure protection statute protects employees who discuss their own wages with each other, including on social media. Once a public range is up for a role, the employees in that role have a near-certain right to talk among themselves about whether they fall above or below it. The pay-transparency rule and the wage-disclosure-protection rule reinforce each other, and an employer that ignored either historically has more housekeeping to do now. For the sequence of duties that bear on the same hiring file (notices, recordkeeping, paystubs), see our employer’s guide to Minnesota wage payment law and the broader Minnesota Wage Theft Act employer obligations overview.

Minnesota’s pay-transparency rule is short on words and long on consequences. The substantive ask is small: publish an honest range and an honest benefits description in each posting. The downstream effect is large because the data the rule surfaces, once public, makes the employer’s prior pay practices visible in ways the prior posting culture obscured. Employers that do the housekeeping (calibrated ranges, clean benefits descriptions, internal review before posting) generally find compliance straightforward and the hiring funnel improves. Employers that do not face a slow accumulation of applicant complaints, internal-equity questions, and audit risk that compounds over hiring cycles. For broader context on Minnesota’s employment-law layer cake, see our Minnesota employment law practice area. If you would like a second set of eyes on a posting template or your internal pay-band review process, email [email protected] with a sample posting and a brief description of the role mix.