Statute of Limitations for Written Contract 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 a written contract is generally 3 years under Minnesota Statutes § 628.26. In practical terms, that means a lawsuit based on a written agreement will typically need to be filed within 3 years from when the cause of action accrues (i.e., when the claim becomes actionable).

This is the default/general rule for the topic covered by this brief. No claim-type-specific sub-rule was identified in the information provided for this brief, so you should treat § 628.26’s 3-year period as the baseline starting point unless a recognized exception or different accrual rule applies (covered below).

Note: This guide is for informational purposes and focuses on Minnesota’s general SOL rules for written contracts. It’s not legal advice. Contract disputes can turn on accrual details and exceptions that may change the analysis.

Limitation period

3 years is the baseline SOL period for claims governed by Minn. Stat. § 628.26.

What counts as a “written contract” for SOL purposes (practical framing)

In real disputes, whether § 628.26 applies often depends on whether the claim is fundamentally tied to a written agreement—for example:

  • a signed contract,
  • written terms the parties agreed to,
  • a written promise that forms the basis of the dispute.

The SOL analysis then usually focuses on three practical questions:

  • Accrual: When did the claim become actionable?
  • Exceptions/doctrines: Do anything pause, delay, or extend the time to sue?
  • Proper fit: Is the claim the kind that falls under § 628.26, or is another SOL rule involved?

When does the clock start?

Even if the length is “3 years,” many cases turn on the start date. While this page focuses on the statute length, the deadline depends on accrual—often tied to when the contract was breached or when the plaintiff could first sue under the relevant legal theory.

To pinpoint accrual in a written-contract case, consider:

  • the contract date (often not the accrual date),
  • the due date for performance (for missed deadlines),
  • the breach event date (e.g., nonpayment when payment was due),
  • any repudiation or demand timing that may affect when a claim is actionable under the theory pleaded.

Because contracts vary, the safest approach is to identify potential breach points and then test which one fits the accrual standard for your claim.

Key exceptions

Even with a general 3-year SOL under Minn. Stat. § 628.26, timing can change due to doctrines that affect accrual or pause the limitations period.

1) Tolling (pausing the SOL)

Tolling generally refers to situations that pause (or sometimes suspend) the SOL clock for a defined period.

Common things people look for (fact-specific) include:

  • whether the claim was not legally actionable during a certain period,
  • whether a recognized legal condition prevented filing,
  • whether a statutory or procedural mechanism effectively paused the clock.

Practical checklist:

  • Is there a period where the claim was legally “not yet” in a suing posture?
  • Did the parties’ conduct create a legally recognized pause?
  • Are there any statutory conditions that affect timing for your specific situation?

2) Accrual disputes (the “start date” issue)

Many cases don’t fail because the SOL period is short—they turn on when accrual occurred.

For example, if the written contract includes:

  • installment payments,
  • continuing duties,
  • milestone deliverables,
  • ongoing performance obligations,

then there may be competing breach dates.

A practical way to map accrual:

  • list each performance obligation,
  • identify the exact deadline for each obligation,
  • mark the earliest date each obligation was arguably breached,
  • evaluate whether later events are truly new breaches or just continuing performance issues.

3) Written-contract label vs. actual legal claim

Even if your documents are “written,” the legal theory you plead can sometimes bring in different timing rules.

If your dispute includes multiple theories (for instance, a written-contract count plus other causes of action), you may face multiple SOL rules. In that situation, the 3-year baseline is a starting point, not a guarantee that every count is controlled by § 628.26.

Reminder: This brief is designed to identify the general/default period for written-contract claims. If your facts involve multiple legal theories, confirm which SOL governs each theory.

Statute citation

Minnesota Statutes § 628.26 provides the general 3-year statute of limitations period relevant here.

From the jurisdiction data provided for this brief:

  • General SOL Period: 3 years
  • General Statute: Minn. Stat. § 628.26
  • Claim-type-specific sub-rule: None identified → apply the general/default period unless an exception applies.

Use the calculator

Use DocketMath’s statute-of-limitations calculator to convert the 3-year rule into a concrete deadline date.

  1. Open the calculator: /tools/statute-of-limitations
  2. Choose Minnesota as the jurisdiction.
  3. Enter the accrual date you believe applies to the written-contract claim (often tied to the breach date or when the claim first became actionable).
  4. Review the output deadline.

How inputs change the output

  • Earlier accrual date → earlier filing deadline
  • Later accrual date → later filing deadline
  • Accrual date drives the result, because the calculator applies the 3-year period associated with Minn. Stat. § 628.26 (based on your inputs)

Practical tip: If the contract has multiple installments or milestone dates, run the calculator for each plausible accrual date and compare which deadline is earliest.

Note: The calculator walkthrough here assumes the general/default 3-year rule. If tolling or another exception doctrine applies based on your facts, you’ll need to incorporate that into how you interpret the final deadline.

Sources and references

Start with the primary authority for Minnesota and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

Related reading