Statute of Limitations for Credit Card / Open Account Debt in North Dakota

7 min read

Published March 22, 2026 • By DocketMath Team

Overview

In North Dakota, the statute of limitations (“SOL”) sets a deadline for a creditor to file a lawsuit to collect certain debts, including many credit card and other “open account” obligations. If the creditor sues after the SOL expires, the claim may be barred—meaning the case can be dismissed or judgment prevented—though the outcome depends on how the issue is raised procedurally.

This page focuses on North Dakota’s SOL rules for typical consumer debt scenarios where there isn’t a signed contract specifying a different limitations period. Because debt collection cases often turn on the type of claim (contract vs. account vs. other theory) and the date from which the clock starts, your documentation matters: statements, account opening/charge dates, and records of any payments or disputes.

Note: This is a reference overview, not legal advice. SOL defenses can depend on details like the claim’s legal theory and the litigation posture in your case.

If you want a quick, practical way to model timelines, DocketMath’s statute-of-limitations calculator can help you translate those dates into an estimated filing window: go to /tools/statute-of-limitations.

Limitation period

Default rule for many credit card / open account claims

North Dakota generally applies a limitations period of 6 years to actions “upon a contract” or an obligation arising from contract principles. For many credit card and open account situations, creditors commonly plead the case as a contract-based claim (for example, breach of contract or a claim “upon a contract,” depending on how the collection complaint is drafted and supported).

Practical meaning: if the creditor’s lawsuit is filed more than 6 years after the applicable “starting date,” the claim is typically time-barred under the contract SOL framework—assuming no exception or tolling applies.

How the clock usually starts (and why it can differ)

In many consumer debt cases, the “starting date” is tied to the last date the debtor made a payment or the date of default—often described as the date of last activity relevant to the account under the creditor’s theory. Creditors and courts may treat:

  • Last payment date (common in payment-based timelines), or
  • Date of default / acceleration / last charge (in some pleading theories)

Your creditor’s records (and the complaint, if one is filed) usually identify the key date they rely on. If you’re trying to assess risk or timing before any lawsuit is filed, you’ll want to identify what “last activity” date you have documentation for (statement cycles and payment histories are often the most concrete proof).

What changes the result

The calculator output depends heavily on your inputs. Here are the main inputs and how each one can change the result:

  • Date of last payment or last account activity

    • Moving this date forward can extend the estimated SOL window.
    • Missing the correct date can cause a misleading “safe/unsafe” conclusion.
  • **State jurisdiction (North Dakota)

    • Using the wrong jurisdiction code can produce the wrong SOL length.
  • Whether a tolling/exception applies

    • Some events can pause, delay, or alter the limitations period.
    • The SOL calculator typically models the baseline rule; if an exception applies, the real-world deadline may differ.

Key exceptions

North Dakota SOL rules include specific doctrines and statutory provisions that can affect deadlines. The exact application often depends on facts and the creditor’s pleading theory. Below are the most common exception categories that can matter in debt collection timelines.

1) Tolling or pause due to specific legal circumstances

Certain legal circumstances can toll (pause) or affect the limitations period. Examples include statutory tolling provisions tied to particular incapacity or legal disabilities. Because the presence of a tolling event is fact-specific, you’ll want to compare your situation to the statute’s text and the timeline.

Pitfall: Don’t assume “tolling” applies just because time passed. In many cases, tolling requires a qualifying event that can be proven, and it doesn’t automatically happen from ordinary circumstances like moving addresses.

2) Partial payments and acknowledgments

For some debt claims, later payments or certain acknowledgments can impact whether a claim is considered timely. North Dakota’s treatment can depend on the legal theory and how the creditor characterizes the obligation.

When using the DocketMath calculator, your most important input is typically the last payment / last activity date. If the creditor can show a later qualifying payment or an event that resets or affects the accrual date under the applicable theory, the filing window can shift.

3) Written contracts vs. open account pleadings

If a debt arises from a different kind of contract (for example, a written agreement with distinct terms), a different SOL may apply. Credit cards often involve account agreements and credit terms, but whether the creditor can rely on a particular contract characterization can vary by case.

How this affects your timeline: the same “date of last activity” can lead to a different SOL if the claim is categorized differently.

4) Bankruptcy stay (procedural timing effects)

Bankruptcy can complicate timelines because automatic stays and case proceedings affect when a creditor can sue or collect. While bankruptcy is not a simple SOL “reset,” it can functionally alter when the creditor can bring an action.

If you’re tracking deadlines around bankruptcy, the safest approach is to align the timeline with bankruptcy filings and stay periods rather than only relying on the SOL clock.

Statute citation

North Dakota’s contract-based statute of limitations is codified in the North Dakota Century Code. A common citation used for contract actions (including many claims pled as “upon a contract”) is:

  • N.D. Cent. Code § 28-01-16 — actions upon a contract (commonly cited as a six-year limitations period for contract claims)

Because debt collection complaints can be drafted under different theories (and sometimes different provisions), you should match the citation to the specific cause of action alleged in the lawsuit (if filed). If no lawsuit exists yet, you’ll still benefit from aligning your timeline to the “contract/open account” theory described above.

Use the calculator

DocketMath’s statute-of-limitations calculator helps you estimate the latest likely filing date based on North Dakota’s baseline limitations period.

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

When using the calculator, focus on these inputs:

Step 1: Pick the jurisdiction

  • Jurisdiction: **US-ND (North Dakota)

Step 2: Enter the key date

  • Date of last payment or last account activity
    Use the date that best matches the creditor’s likely “accrual” argument (often your last payment or last activity showing default/culmination of the account).

Step 3: Review the output window

The calculator will return a timeline such as:

  • Estimated SOL expiration date (the last date within the baseline limitations period)
  • Estimated “days remaining” (if you run it at or near the present date)

How output changes with different inputs (quick examples)

  • If the last payment date is moved from Jan 15, 2018 to Jun 1, 2019, the estimated SOL expiration typically shifts about 18 months later (because the 6-year term is measured from the updated starting date).
  • If you use an incorrect older date (e.g., the date you opened the account rather than your last payment), the calculator may produce an earlier expiration date—creating a misleading sense that the claim is time-barred.

Warning: The calculator models the baseline SOL framework. If you suspect an exception (tolling, bankruptcy stay effects, or a different contract theory), the actual deadline could differ from the calculator’s estimate.

Sources and references

Start with the primary authority for North Dakota 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