Statute of Limitations for UCC / Sale of Goods in New Mexico

6 min read

Published April 8, 2026 • By DocketMath Team

Overview

In New Mexico, the default statute of limitations (SOL) for many UCC / sale-of-goods claims is 2 years under N.M. Stat. Ann. § 31-1-8.

If you’re tracking deadlines for a dispute involving contracts for the sale of goods, DocketMath’s statute-of-limitations calculator can help you estimate the end date based on key dates—most importantly, the date the claim accrued (which is often tied to delivery, breach, or refusal to perform). This page focuses on the general/default SOL rule because no claim-type-specific sub-rule was found in the jurisdiction data provided.

Note: This is general information about New Mexico’s default SOL rule in the UCC/sale-of-goods context. It isn’t legal advice. Accrual timing can vary based on the facts, and that can materially change your deadline.

Limitation period

2 years is the general/default limitation period referenced here: N.M. Stat. Ann. § 31-1-8.

How the 2-year rule is usually measured (practical workflow)

Although SOL rules use legal concepts (especially around when a cause of action accrues), you can usually follow a straightforward approach:

  • Step 1: Identify the triggering event.
    In a sale-of-goods dispute, the “start” of the clock is commonly tied to events such as:

    • delivery of the goods,
    • refusal to deliver,
    • non-conforming tender,
    • failure to pay, depending on the claim theory.
  • Step 2: Determine when the claim accrued.
    Accrual is typically when the buyer or seller has a complete and actionable claim—i.e., when the dispute becomes fit to sue on.

  • Step 3: Count forward 2 years.
    Add 2 years from the accrual date. (Some disputes may involve additional timing nuances, but the baseline period here is 2 years.)

Inputs that matter most for your deadline calculation

When you use DocketMath, the key input is:

  • Accrual date / breach-related date (the date you believe the claim “started” for SOL purposes)

Depending on the tool’s options, you’ll also want to ensure you’re calculating the correct “end” concept (for example, a last day to file a lawsuit). If you mix up dates, the output can be off by a lot.

Common accuracy pitfall: using an invoice date instead of the delivery date (or refusal/nonconformity date). That can cause the calculated deadline to be too early or too late by weeks or months.

Illustrative example (how to think about it)

If a claim is treated as accruing on 2024-05-15, then—using the 2-year default period—you’d expect an SOL expiration around:

  • 2026-05-15 (subject to any accrual/timing nuances based on the specific facts)

Key exceptions

The baseline rule presented here is 2 years under N.M. Stat. Ann. § 31-1-8. In practice, though, many “exception” issues arise not from a different SOL length (because none was identified in the provided jurisdiction data), but from when the clock starts or whether the clock is paused or extended.

1) The biggest “exception”: the accrual date

Even without claim-type-specific sub-rules identified in the jurisdiction data, accrual is often the decisive turning point. For example:

  • Installments or repeated deliveries:
    If performance happened in parts, the dispute may relate to when each installment was delivered or rejected, affecting which date accrues.

  • Non-conforming goods:
    Questions can arise about when the buyer’s right to sue became definite and actionable based on the alleged nonconformity.

Pitfall: using the wrong date—such as the date an invoice was issued—can create a misleading “last filing date,” even if the 2-year SOL period is correctly applied.

2) Tolling / suspension (fact-dependent)

Many legal systems recognize doctrines that can pause or extend an SOL in certain circumstances (often described as tolling or suspension). However:

  • tolling typically depends on the specific facts and the legal doctrine invoked,
  • and this jurisdiction brief only confirms the general/default 2-year period.

So treat tolling as a case-specific issue that you should validate using the controlling authority that fits your situation.

3) Contract language vs. statutory timing

Parties sometimes include contractual timing provisions (including notice or dispute steps). While you can model deadlines with DocketMath, keep in mind that contractual attempts to modify statutory timing rules may be constrained by law and how courts interpret such provisions.

Practical exception-spotting checklist (before you rely on a calendar date)

  • What exact event is the alleged breach?
  • When did the other side refuse performance (if refusal is part of the theory)?
  • Were there multiple shipments or installment deliveries?
  • Is there any reason accrual should be delayed based on the facts?
  • Are there contractual notice/pre-suit steps that affect accrual or readiness to sue?
  • Is there any potential tolling/suspension doctrine on your facts?

Statute citation

N.M. Stat. Ann. § 31-1-8 — 2-year general/default limitation period.

Based on the jurisdiction data provided for this tool page:

  • General SOL period: 2 years
  • General statute: N.M. Stat. Ann. § 31-1-8
  • Claim-type-specific sub-rule: None found in the provided jurisdiction data
    → Therefore, this page uses the 2-year general/default period.

If your specific claim theory or fact pattern seems unusual, it’s worth verifying whether a different timing framework could apply.

Use the calculator

Use DocketMath to calculate a statute-of-limitations expiration date in a way you can keep consistent and review later.

Open the calculator

Go to: /tools/statute-of-limitations

What to enter (typical workflow)

  1. Enter the accrual date (or the best-supported equivalent—such as a delivery/refusal/breach date).
  2. Confirm the 2-year general/default period applies (the tool can align the calculation to the jurisdiction/rule selection).
  3. Review the output and check what assumptions the tool is using.

How the output changes when inputs change

  • If the accrual date shifts forward by 30 days, the SOL expiration shifts forward by about 30 days.
  • If you correct a mistaken date (for example, invoice date vs. delivery/refusal date), your deadline can change by weeks or months.
  • If you suspect multiple breaches (e.g., multiple deliveries/installments), you may need multiple runs—one for each potential accrual event.

Sanity check before treating it as final

Before you rely on the calculator output as your final “last day”:

  • Confirm the date you used best matches the alleged breach trigger.
  • Look for multiple deliveries/installments.
  • Compare the computed expiration date with your real-world timeline (evidence collection, demand letters, and planned filings).

Sources and references

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