Statute of Limitations for Written Contract in South Dakota

Overview

South Dakota’s statute of limitations (SOL) for a written contract claim is 3 years under SDCL 22-14-1. That 3-year period is the general/default rule, meaning it applies to written contract timing questions when no more specific sub-rule applies to the claim type based on the jurisdiction data provided.

SOL timelines matter because they control when a lawsuit must be filed. If you file after the deadline, a defendant may move to dismiss based on the SOL. This page gives you a practical baseline framework for written contract disputes in South Dakota, including what commonly changes the result—especially the accrual (trigger) date and any tolling.

Limitation period

South Dakota uses a 3-year SOL under SDCL 22-14-1 for the general category that includes many contract claims. Because no claim-type-specific written-contract sub-rule was identified in the jurisdiction data provided, you should treat SDCL 22-14-1 as the default rule for this topic.

What “3 years” means in practice

In many written contract scenarios, the 3-year period is counted from when the claim accrues—often tied to either:

• the breach date (e.g., nonpayment or refusal to perform), or
• the performance due date (e.g., when payment was due, or when delivery was required)

In a DocketMath SOL workflow, the key inputs that usually change the result are:

• Accrual date / trigger date: when the claim is considered to have started for SOL purposes
• Filing date: the date the lawsuit is filed (depending on the calculator’s method and court treatment of timing)
• Tolling or extending events (if any): any legally recognized pause/extension supported by facts

How the output changes when your dates change

Small date changes can significantly shift whether a filing is timely. Before relying on an SOL calculation, confirm the fundamentals:

• Identify the earliest breach / performance due date you can support with documents (e.g., invoice due date, delivery deadline, payment deadline).
• Choose and document your accrual basis (commonly breach date vs. performance due date vs. another contract-required trigger).
• Use the correct filing date (filing date often matters; service timing rules can vary).
• Check for any event that could toll (pause) the SOL—especially if it affects the “latest file-by” date.

Run it using DocketMath

Use the tool at /tools/statute-of-limitations to translate your dates into an actionable deadline.

A practical approach is to run multiple scenarios if you have more than one plausible trigger date:

• Scenario A (earlier accrual): accrual at the payment/delivery due date
• Scenario B (later accrual): accrual at a breach-confirmation or demand-type event date (if supported by the contract and facts)

If Scenario A falls outside the 3-year window but Scenario B falls inside, your next step is typically to focus on building the record for the later accrual theory using the contract language and the breach timeline.

Key exceptions

Even with a strong default rule, SOL results can change based on accrual, tolling, and how the claim is framed. Since this page is based on the provided jurisdiction data (default rule only), treat the following as the main categories to check rather than assumptions that exceptions apply automatically.

1) Accrual date disputes (often the biggest factor)

For written contract claims, parties frequently disagree about when the clock starts. Common arguments include:

• Performance due date (e.g., payment was due on X, delivery required by Y)
• Breach date (e.g., refusal to perform, missed payment treated as breach)
• Contract-specific triggers (e.g., conditions precedent that must occur or be excused before a right to sue arises)

2) Tolling effects from certain legal events

Tolling can pause or extend an SOL deadline, but it’s fact-specific and depends on the event and the statute authorizing tolling. Because the SOL “latest file-by” date is date-sensitive, list potential timing-related events you can support, such as:

• dispute-resolution steps that may affect timing under applicable rules,
• statutory pauses tied to certain legal events,
• written agreements that validly alter timing (if permitted by law and contract terms).

3) Whether the claim is truly “written contract” for SOL purposes

Even if the underlying dispute involves commercial conduct, a defendant may argue the claim doesn’t fit the written contract category for SOL purposes. Courts typically look to what is actually alleged and what the plaintiff is suing on.

If you’re relying on SDCL 22-14-1 as the default rule, the pleadings and contract language should align with the theory that the cause of action is based on a written contract.

4) Partial performance, payments, or acknowledgments

Post-breach conduct—like partial payment, written acknowledgments of debt, or modifications to a payment schedule—can become central to SOL analysis. Depending on how the documents tie back to the contractual obligations, the parties may dispute whether those actions affect:

• when the claim became actionable,
• whether earlier breaches were effectively addressed,
• whether later dates provide a better accrual basis.

Statute citation

South Dakota general SOL period (default): 3 years
Statute: SDCL 22-14-1

This 3-year period is the general/default rule for the written contract timing question covered here. Based on the jurisdiction data provided, no claim-type-specific written-contract sub-rule was identified, so you should start your analysis with SDCL 22-14-1.

Use the calculator

Use DocketMath at /tools/statute-of-limitations to generate an actionable SOL deadline from your timeline.

To get a reliable output:

1. Set jurisdiction: South Dakota (US-SD).
2. Use the SOL basis: the 3-year default rule under SDCL 22-14-1.
3. Enter the accrual/trigger date:

   • If multiple trigger dates are plausible, run multiple scenarios and compare the “latest file-by” results.
4. Enter your filing date (if requested by the tool) or otherwise rely on the tool’s deadline output.
5. Add tolling-related adjustments only when you can support them with facts (and understand they are legally dependent).

Two quick scenario examples:

• Scenario A: accrual at the payment/delivery due date
• Scenario B: accrual at a later demand/breach-confirmation date (if supported by contract terms and breach facts)

Sources and references

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

• S.D. Codified Laws § 15-2-1

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