Statute of Limitations for Written Contract in Montana

Overview

In Montana, the statute of limitations (SOL) for most claims based on a written contract is 3 years, under Montana Code Annotated (MCA) § 27-2-102(3).

Montana’s SOL rules are set out in statute. DocketMath’s statute-of-limitations calculator is built to apply that statutory timeline to a specific fact pattern—most importantly, the date the claim accrued (often tied to the contract breach or the event that made performance due and actionable). This page focuses on the written-contract default rule rather than special scenarios.

Limitation period

Montana’s default SOL is 3 years for covered actions under MCA § 27-2-102(3). Based on the jurisdiction data provided, there is no claim-type-specific sub-rule identified beyond this general/default period for written contracts—so this page treats 3 years as the baseline.

Here’s how the 3-year window typically works in practice:

• Start date (accrual): The SOL generally begins when the claim accrues—commonly when the breach occurs and you can sue (for example, when a party fails to perform by the contract due date).
• End date (expiration): Count forward 3 years from that accrual date. Claims filed after the expiration date are typically time-barred.

Quick timeline example (illustrative)

If a written contract required payment by January 15, 2023, and the other party failed to pay, a claim might accrue on or near that due date. The 3-year SOL window would end around January 15, 2026.

Because “accrual” depends on the facts, the practical step is to identify the event that made the breach actionable under the agreement. DocketMath supports this by letting you run calculations from the accrual trigger you select.

What you should gather before calculating

To use a SOL calculator effectively, you’ll usually need:

• Accrual date (or the “breach became actionable” date)
• Jurisdiction: US-MT
• (If applicable) any tolling/extension dates you want to model (see “Key exceptions”)

Common misunderstanding: using the wrong date

It’s common to start with dates that feel important, but aren’t always the accrual date for SOL purposes, such as:

• the date you discovered the breach,
• the date you sent a demand letter, or
• the date parties negotiated.

Those dates can matter for other legal questions, but they aren’t always the SOL start date. DocketMath’s goal is to help you compute deadlines based on the accrual trigger you choose.

Key exceptions

Montana’s 3-year default rule is a strong starting point, but a few variables can change the effective timeline—either by pausing the SOL (tolling) or by shifting the starting point (accrual).

Because the jurisdiction data provided identifies the written-contract rule as a general/default period and does not list claim-specific sub-rules, the “exceptions” below focus on the main categories that commonly affect SOL outcomes.

1) Tolling or pause of the clock

Some situations can pause the SOL. In that case, the limitations period stops running for a period of time and then resumes later.

When you use DocketMath, you can model tolling if your fact pattern supports it by entering (as applicable):

• tolling start date
• tolling end date
• confirmation that tolling applies under the controlling doctrine and your facts

2) Accrual disputes (start date disagreement)

Even with a written contract, parties may disagree about when the breach became actionable. Examples that can affect accrual include:

• obligations due in installments,
• conditions precedent that control when payment becomes owed,
• arguments related to “continuing breach” where missed payments may be treated as separate accrual events.

For a calculator workflow, this means the accrual date input can matter as much as the SOL length.

3) Procedural timing and filing mechanics

A SOL calculation is about the deadline to file, but practical filing mechanics can matter, such as:

• how a case is “commenced” under applicable court rules, and
• whether the relevant dates align when the filing occurs close to the expiration.

DocketMath helps you compute the deadline; you still need to ensure your actual filing process lines up with that deadline.

4) Contract terms that may affect “when you can sue”

Some contracts include timing-related terms such as:

• notice requirements,
• dispute escalation steps, or
• deadlines to demand payment.

These terms don’t automatically change the statutory SOL, but they can affect when the breach is measurable or when a claim becomes actionable, which in turn can change the accrual date used for the SOL calculation.

Statute citation

Montana’s general SOL rule relevant to this default written-contract timeline is:

• MCA § 27-2-102(3): 3 years

This is the general/default period reflected in the jurisdiction data provided. No additional claim-type-specific sub-rule for written contracts was identified beyond this general rule.

For documentation (for example, case management or internal tracking), it’s usually helpful to record both:

• the statute citation (MCA § 27-2-102(3)), and
• the accrual date you used to compute the deadline.

Use the calculator

Use DocketMath’s statute-of-limitations calculator to compute the deadline using Montana’s default 3-year period under MCA § 27-2-102(3):

• Start here: ** /tools/statute-of-limitations

If you want to compare scenarios, re-run the calculation with different accrual dates and any tolling dates you are modeling.

How the inputs change the output

Use this checklist to keep your workflow accurate:

Inputs to confirm

What changes the deadline most

• Later accrual date → later deadline
• Earlier accrual date → earlier deadline
• Modeled tolling (pause period) → later deadline (because less “clock time” runs)

A practical approach when facts are uncertain is to run at least two calculations:

• Scenario A: earliest plausible accrual date
• Scenario B: later plausible accrual date (and any tolling)

Then compare the resulting deadlines to understand the risk window.

Sources and references

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

• Mont. Code Ann. § 27-2-201

Related reading

• Choosing the right statute of limitations tool for Vermont — How to choose the right calculator
• Statute of limitations in Singapore: how to estimate the deadline — Full how-to guide with jurisdiction-specific rules
• Choosing the right statute of limitations tool for Connecticut — How to choose the right calculator