Mortgage deficiency SOL in North Dakota

Rule or statute summary

In North Dakota, a “mortgage deficiency” situation usually arises after a lender forecloses (or otherwise enforces) a mortgage and then seeks to recover the remaining unpaid loan balance—often called a deficiency balance.

For statute-of-limitations (SOL) purposes, the key is not the word “deficiency,” but the legal claim the lender actually files to collect the remaining balance. Different claim types can trigger different SOL timelines.

In North Dakota deficiency cases, the most common framing is:

• Breach of contract / action on the note (because the loan is typically evidenced by a promissory note and related written loan documents)

Other framings sometimes appear:

• Tort or statutory theories (e.g., fraud, certain statutory claims) can have different SOL periods, sometimes much shorter or otherwise distinct.
• If the lender’s pleading raises issues like the wrong party or non-signatories, the lawsuit may fail for reasons unrelated to SOL—so don’t treat SOL as the only defense angle.

Practical takeaway: when you’re assessing SOL risk, review the complaint to identify whether the claim is pleaded as a written contract (often breach of note agreement) versus something else. That choice generally determines which SOL provision you should use.

Gentle note (not legal advice): SOL analysis can depend on how the complaint pleads accrual and the precise loan documents involved. Use this as a checklist for questions to confirm with counsel or through your own document review.

Citations

For actions “upon a contract in writing” in North Dakota, the key provision is:

• N.D. Cent. Code § 28-01-15(1) — 6 years for an action upon a contract in writing

This is the typical anchor for deficiency collection suits when the lender’s claim is based on the written loan instruments (commonly the promissory note).

You may also see other SOL provisions depending on the pleaded theory. For example:

• N.D. Cent. Code § 28-01-20 — may apply to certain actions based on tort-related theories (exact applicability depends on the claim’s elements and how it’s pleaded)

Most common deficiency SOL anchor (contract on the note):

• N.D. Cent. Code § 28-01-15(1) → 6 years for actions on a contract in writing

If you are not sure which SOL applies, check the complaint’s cause(s) of action and whether the lender expressly alleges breach of written agreement / breach of note versus tort/statutory claims.

Use the calculator

Use DocketMath’s statute-of-limitations tool to compute the last day to file (or the deadline) under the applicable North Dakota SOL.

Primary CTA: DocketMath Statute of Limitations Calculator

Run the Statute Of Limitations calculation in DocketMath, then save the output so it can be audited later: Open the calculator.

1) Choose the cause of action (this changes the output)

Select the claim type that best matches the lender’s pleading:

• ✅ Written contract / breach of written note → typically aligns with N.D. Cent. Code § 28-01-15(1) (6 years)
• ⛔ Not written contract (e.g., certain tort-type allegations) → may require a different SOL provision (often not the 6-year written-contract period)

How to confirm: scan the complaint for language like:

• “breach of contract”
• “promissory note”
• “written agreement”
• “default under the note,” “amount due,” or similar contract enforcement language

2) Enter the “start date” for the SOL clock

The calculator’s output depends heavily on the trigger date you enter. In deficiency collection cases, common clock-start candidates include:

• Loan maturity date (when the full balance becomes due), or
• Acceleration date (when the lender accelerated the debt under the note), or
• Default-related date if the contract’s enforceability is tied to a specific event

Practical tip: use the date that best matches how the complaint explains when the debt became due or when the lender’s right to sue accrued. If the lender alleges a specific default, maturity, or acceleration date, entering that exact date generally produces the most meaningful result.

3) Enter the “filing date” (optional, for status checks)

If your workflow includes checking timeliness, you can compare:

• the calculated SOL deadline vs.
• the lawsuit’s filing date

This helps you evaluate whether the claim appears timely or potentially time-barred.

4) Read the output and adjust inputs

Here’s what commonly shifts the deadline:

• Changing claim type (written contract vs. other theories) → can move the deadline meaningfully
• Switching the start date (maturity vs. acceleration vs. default) → directly changes when the clock begins running
• Changing filing date → changes whether the filing appears before or after the cutoff

Pitfall to avoid: entering a start date that doesn’t match the complaint’s pleaded accrual theory can produce a deadline that doesn’t align with how a court may analyze timing.

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.

• N.D. Cent. Code § 28-01-18

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