Statute of Limitations for Wage and Hour / Overtime (state law) in Minnesota

6 min read

Published April 8, 2026 • By DocketMath Team

Overview

Run this scenario in DocketMath using the Statute Of Limitations calculator.

Minnesota’s statute of limitations (SOL) for wage and hour / overtime claims under Minnesota law is 3 years, using Minnesota Statutes § 628.26 as the general/default period.

If you’re tracking deadlines for back pay, unpaid overtime, wage statement issues, or related wage-and-hour remedies, the starting point is usually the date the claim “accrues” (often tied to the paycheck period and the employer’s failure to pay). For Minnesota wage-and-hour matters, the practical takeaway is straightforward: if a specific statute for the claim type does not provide a different limitations window, the general 3-year rule governs.

Note: You requested a claim-type-specific sub-rule, but none was found for Minnesota in this brief. That means this article uses the general/default SOL and does not claim a shorter or longer period for a particular wage-and-hour theory.

Limitation period

Minnesota provides a general limitations period of 3 years for many types of civil actions. In this brief, the working rule is the general/default period (i.e., no claim-type-specific sub-rule was identified).

Default rule (what you should assume first)

  • SOL length: 3 years
  • General statute: Minnesota Statutes § 628.26
  • Applies when: there is no claim-type-specific SOL that changes the deadline

How the deadline typically matters in practice (lookback approach)

For wage and hour / overtime disputes, SOL timing is often a “lookback” question: which work/pay periods are still reachable when measured against the filing date.

A practical way to think about it under the general/default rule:

  • Work performed and wages not paid more than 3 years before the filing date may be time-barred.
  • Work/pay periods within the 3-year window are the ones most likely to remain actionable under the default rule.

Because wage-and-hour situations commonly involve many pay periods, the effective “range” frequently ends up being:

  • Filing date
  • minus 3 years
  • then counting back through pay periods to see which unpaid amounts fall inside the window

DocketMath tip: model it as a rolling 3-year lookback window

Use DocketMath to compute the 3-year lookback by inputting:

  • your planned filing date (the “as-of” date), and
  • representative accrual/pay period dates (often pay period end dates)

Then watch how included vs. excluded pay periods change as you move the filing date by weeks or months.

Key exceptions

The 3-year general rule is the baseline, but wage-and-hour disputes can involve timing doctrines and procedural factors that affect how the SOL plays out. These are not automatic rules—consider them categories to evaluate with your facts.

1) Accrual (when the clock starts)

Even with a fixed limitations period, the start date (accrual) can shift. In wage-and-hour disputes, accrual may be argued to occur:

  • each time unpaid wages are due, or
  • based on another triggering event related to when the employer failed to pay.

Practical impact: if accrual is earlier than expected, a larger portion of damages may fall outside the 3-year lookback.

2) No claim-type-specific SOL identified in this brief

You asked whether a claim-type-specific SOL exists. In this brief, no claim-type-specific sub-rule was found, so you should treat Minn. Stat. § 628.26’s general/default 3-year rule as the working deadline for planning.

If later research identifies a different SOL tied to a specific Minnesota wage-and-hour statute, the computation could change.

3) Tolling arguments (pauses/extension theories)

Some legal doctrines can pause or extend time periods. Common examples in many jurisdictions include arguments related to:

  • circumstances that prevent timely filing, or
  • specific tolling mechanisms.

Because wage-and-hour disputes are fact-intensive, tolling is best handled via case-specific analysis. Still, you can use DocketMath for scenario planning—e.g., compare “no tolling” vs. an assumed tolling period to see how sensitive the lookback window is.

Warning: Don’t rely on informal assurances from an employer or repeated payroll adjustments to automatically “extend” deadlines. As a planning step, model the default 3-year timeline first, then separately document any reasons you believe accrual or tolling should be different.

Statute citation

This page uses § 628.26 as the general/default limitations period because no claim-type-specific sub-rule was found in this brief. The goal is to support deadline planning using the default rule rather than to provide legal advice.

Use the calculator

DocketMath can help you compute the 3-year lookback window to estimate which pay periods likely fall within the limitations period under the general/default rule.

Start here: /tools/statute-of-limitations

Suggested workflow

  • Step 1: Choose your “as-of” date
    • Use the date you’re planning to file (or the date you’re working backward from).
  • Step 2: Set the SOL length to 3 years
    • This page’s default is 3 years under Minn. Stat. § 628.26.
  • Step 3: Enter pay period dates
    • Input pay period end dates (or other accrual dates you’re using for analysis) as the “event” dates to test.
  • Step 4: Review outputs
    • DocketMath will show which dates fall inside vs. outside the SOL lookback window.
    • Use the included periods to scope which unpaid amounts may be time-sensitive.

Inputs and how outputs change (what to adjust)

  • If you move the filing date later:
    • the lookback window shifts later, potentially including newer pay periods while excluding older ones.
  • If your assumed accrual/pay period end dates are earlier than expected:
    • more of the early work may become outside the window.
  • If you scenario-test tolling or delayed accrual assumptions:
    • rerun the calculator using revised “effective accrual” or adjusted event dates to see how the included window changes.

Output interpretation (practical, not legal advice)

Treat DocketMath as a deadline-planning lens:

  • It helps estimate whether unpaid amounts likely fall within the 3-year general/default SOL window.
  • It does not replace a fact-specific evaluation of accrual, tolling, or whether another statute applies.

Related reading