Mortgage deficiency SOL in Oregon

Mortgage deficiency SOL in Oregon

5 min read

Published April 14, 2026 • Updated April 23, 2026 • By DocketMath Team

Article claim inventory in progress

Trust release 4

This page has legal or numeric text that still needs claim-level inventory before we can treat it as verified.

Rule or statute summary

Run this scenario in DocketMath using the Statute Of Limitations calculator.

In Oregon, “mortgage deficiency” usually refers to the lender seeking a remaining balance after a foreclosure sale—typically by suing for any unpaid amount left after applying sale proceeds, foreclosure-related costs, and other allowable amounts under the mortgage/loan documents.

For statute of limitations (“SOL”) purposes, the key practical question is:

What claim is the lender actually suing on?

Even though the dispute involves a mortgage, Oregon’s SOL analysis often turns less on the label “deficiency” and more on the legal theory and claim type—for example, whether the lender’s deficiency claim is treated like an action founded on a written contract (e.g., note/mortgage documentation) or founded on a contract not in writing, and whether any other ORS Chapter 12 provision better matches the pleaded cause of action.

DocketMath’s statute-of-limitations calculator helps you estimate the latest filing date using Oregon’s time limits in a consistent, date-driven way. Your inputs change the output in two main ways:

  • Accrual / trigger date (when the clock starts): this is the date the plaintiff has a present right to sue. In deficiency scenarios, that often aligns with foreclosure timing (such as when the sale result becomes fixed and the deficiency can be determined).
  • Claim category (what the clock length is): Oregon generally assigns different limitation periods based on statutory categories (often found in ORS Chapter 12), including different periods for contract-in-writing vs. contract-not-in-writing actions.

Note: This page is for research and planning—not legal advice. “Accrual” facts can shift the start date (e.g., foreclosure milestones, sale completion/confirmation, and how the deficiency amount becomes determinable).

Citations

Oregon SOL categories that commonly come up when lenders pursue deficiency amounts are often tied to contract theories and the “written vs. not written” distinction.

Common statutory anchors you’ll typically see for contract-style deficiency claims include:

  • ORS 12.080 — actions founded upon a written contract or writing, generally 6 years.
  • ORS 12.090 — actions founded upon a contract not in writing, generally 3 years.

Depending on how a deficiency complaint is drafted, other SOL provisions in ORS Chapter 12 can sometimes be relevant if the asserted cause of action fits a different statutory category than “written contract” or “contract not in writing.” That is why it’s important to match the actual pleaded theory to the correct ORS section.

Accrual date matters

Oregon SOLs typically run from the point the action accrues—i.e., when the plaintiff can sue and the claim becomes enforceable. In deficiency contexts, courts may look to when the foreclosure outcome creates a determinable deficiency and/or when the lender has the practical right to bring the deficiency claim based on the foreclosure results and any applicable foreclosure steps.

Because deficiency timelines can depend on the foreclosure process and how the complaint is structured, treat accrual timing as fact-sensitive.

Use the calculator

Use DocketMath’s statute-of-limitations calculator to compute a “latest filing date” for an Oregon deficiency claim based on your selected claim category and trigger date.

Primary CTA: /tools/statute-of-limitations

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

Step 1: Choose the claim category (drives the SOL length)

Pick the closest category to the lender’s pleaded theory:

  • Written contract (often invoked when the lender relies on note/mortgage documentation treated as a writing): generally 6 years under ORS 12.080.
  • Non-written contract / other contract: generally 3 years under ORS 12.090.

If the lender’s complaint is pled in a way that fits a different ORS category than “written contract” or “contract not in writing,” the relevant SOL may differ. DocketMath can help you compare scenarios, but you should align the category to the actual cause(s) of action and supporting allegations in the complaint.

Step 2: Enter the accrual / trigger date

In deficiency matters, you may need to consider multiple plausible trigger dates depending on how the legal “right to sue” is characterized:

  • Foreclosure sale date (when the sale occurs and the deficiency becomes computable), or
  • A later foreclosure milestone such as the date when a deficiency is treated as fixed/determinable (for example, tied to confirmation/judgment timing where applicable under the particular procedural posture).

DocketMath’s calculator workflow is scenario-friendly—run different date assumptions if you’re unsure which accrual theory a court would apply.

Step 3: Review the output

After you enter:

  • the claim category and
  • the accrual/trigger date (plus any optional comparison dates),

DocketMath will output things like:

  • the SOL duration (e.g., 3 or 6 years, depending on category), and
  • the latest filing date (accrual date + SOL period),
  • plus a time-bar check depending on what dates you compare.

What changes the result (quick input/output map)

Input you changeLikely SOL effectWhy it matters
Claim category (written vs. non-written)Changes duration (6 vs 3 years)Often reflects ORS 12.080 vs ORS 12.090
Trigger/accrual dateMoves the latest filing date forward/backwardSOL clocks typically start at accrual, not necessarily signing/recording

Caution: Amendments, separate counts, or re-pleading after dismissal can complicate SOL calculations. Consider the specific count and the specific filing date that matters for that count.

Sources and references

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