Statute of Limitations for UCC / Sale of Goods in Denmark
7 min read
Published March 22, 2026 • Updated April 8, 2026 • By DocketMath Team
Overview
Run this scenario in DocketMath using the Statute Of Limitations calculator.
In Denmark, the deadline to bring a claim connected to the sale of goods typically depends on whether the dispute is treated as a contractual claim (most common) and, if so, which limitation regime applies. A practical baseline often used for contractual goods disputes is 3 years—but the exact timeline can move based on how the claim is characterized and when it becomes due and/or when the claimant gains sufficient knowledge.
In practice, you’ll get a more reliable result by starting with the legal “bucket” your facts fit, such as:
- Payment/invoice dispute (unpaid price)
- Defective/nonconformity dispute (goods don’t conform)
- Remedy dispute (repair, replacement, price reduction, damages)
- Refund/offset (money back or deductions)
- Special wrongdoing theories (e.g., fraud/misrepresentation)
DocketMath’s Statute of Limitations tool helps you model these timelines for Denmark without manually searching for the right rule each time. It’s built to support deadline estimation, not a definitive legal conclusion.
Note: Limitation periods are fact- and classification-dependent. Use the tool to estimate your deadline and then sanity-check it against your timeline and the nature of your claim.
Limitation period
3-year baseline is common for contractual claims
For many sale-of-goods disputes that are treated as contractual performance issues, Denmark often applies a 3-year limitation period. The key question is less “how many years?” and more when the clock starts.
Use a practical workflow for goods disputes
1) Identify the claim type
Translate your dispute into the closest limitation “bucket”:
- Payment/invoice claim (buyer owes price; seller seeks payment)
- Nonconformity/defective goods claim (buyer alleges goods are defective/nonconforming)
- Remedy dispute (repair, replacement, price reduction, damages)
- Refund/offset claim (buyer seeks money back or to deduct amounts)
- Fraud/misrepresentation or other special wrongdoing claim
Why it matters: the limitation start date logic may shift depending on whether the claim is treated as a standard contract claim about performance or as something else.
2) Determine the start date (the common source of surprises)
For goods-related contractual claims, limitation analysis often turns on one or both of these ideas:
- When the claim became due (for example, the payment due date), and/or
- When the claimant knew or should have known the relevant facts and that they could assert the claim (commonly in defect/nonconformity contexts)
Two buyers can face different deadlines even with the same delivery date—because one discovered the problem earlier (or obtained decisive evidence earlier) than the other.
3) Don’t assume a single “delivery date + X” formula
Even when the dispute is about “goods,” Denmark’s limitation outcome can be influenced by how the law treats the practical defect/remedy pathway—especially when rights become exercisable or when the facts rise to a level sufficient to sue.
So instead of relying on “delivery date + 3 years,” model the due/knowledge trigger that matches your claim characterization.
4) Run a date sanity check
Before you rely on an output, confirm your proposed start date aligns with the factual record.
A quick “what date would you test?” guide:
| Scenario | Most likely start date to test in DocketMath |
|---|---|
| Seller sues for unpaid invoice | Invoice due date (and any contract-defined due date) |
| Buyer sues for nonconformity discovered quickly | Date buyer knew/should have known of the nonconformity |
| Buyer sues after prolonged issues | Date knowledge became sufficient to assert the claim (not just first suspicion) |
| Dispute centers on representations | Date buyer knew (or should have known) the representation issue |
Key exceptions
A 3-year baseline is common, but the effective deadline can change due to several practical “exception drivers” in Denmark—usually tied to (a) characterization and (b) when the claimant can be treated as having a sufficient basis to sue.
1) Claim recharacterization (contract vs. other theories)
If the case is reframed away from ordinary contractual performance (e.g., toward wrongful conduct), a different limitation framework may apply. Practically, limitation analysis should track the elements of the asserted cause of action, not only the commercial label “goods dispute.”
Checklist:
- Are you pleading breach of contract/nonconformity?
- Is your theory closer to a tort-like allegation for separate wrongful conduct?
- Are you alleging fraud (which can affect start-date analysis and/or treatment)?
2) Knowledge-based triggers for defect/nonconformity claims
In many goods disputes, the limitation start can depend on when the claimant knew or should have known the key facts needed to assert the claim. A late “we only learned later” story may not succeed if the claimant had enough information earlier (for example, repeated failures, clear test results, or documented communications).
3) Timing changes through procedural posture
If a claimant files and later amends the theory, adds parties, or changes the nature of the claim, limitation can become contested. While DocketMath can’t replicate every procedural nuance, you can reduce uncertainty by modeling:
- the earliest plausible date you could assert the claim, and
- the actual filing date.
4) Contract terms (within legal limits)
Commercial contracts sometimes add clauses about notice or dispute processes. These terms can affect when rights become exercisable or what counts as timely action. For best results, rely on milestone dates you actually have (notice dates, due dates, discovery dates) rather than assuming the contract will not matter.
Statute citation
DocketMath’s Denmark limitation modeling is anchored on Denmark’s Danish Limitation Act (Forældelsesloven), which provides a general 3-year limitation period structure that is commonly applied to many contractual claims (including claims for payment and contract-based disputes).
Because sale-of-goods disputes can also interact with goods-specific legal rules (especially around defects and remedies), a complete “citation mapping” for every scenario depends on factors such as:
- whether the claim is strictly contractual,
- what remedy is sought,
- and which due/knowledge trigger applies to the facts.
For the most accurate result for your fact pattern, run the calculator first, then compare the resulting start/end dates to your delivery, notice, discovery, and filing timeline.
Use the calculator
Use DocketMath’s Statute of Limitations calculator to estimate your likely Denmark deadline and test how different triggers affect the outcome.
Step 1: Open the tool
Start here: /tools/statute-of-limitations
Step 2: Enter the relevant Denmark dates
Common inputs include:
- Transaction timeline
- delivery date (when goods conformity matters)
- invoice date / due date (when payment matters)
- Defect/issue timeline (when nonconformity is central)
- discovery date (facts became known)
- notice date (when notice of the issue was sent)
- Claim filing date
- the date you plan to file (or the date filed)
Step 3: Choose the closest claim characterization
Select the option that best matches your dispute so the tool can apply the most relevant Denmark pathway. Typical selections include:
- payment/invoice breach (contractual payment claim)
- defective goods/nonconformity claim
- mixed issues (if the tool prompts additional clarification)
Practical tip: if your facts could support more than one theory, run separate scenarios instead of forcing everything into one bucket.
Step 4: Review the output and run “what-if” scenarios
A robust workflow is to run at least two scenarios:
- using the earliest plausible trigger date, and
- using the latest plausible trigger date.
Then compare:
- calculated limitation start date (the key moving part)
- calculated limitation end date (your estimated deadline)
- how changing inputs shifts the result (especially discovery/notice vs. payment due dates)
Step 5: Export and document your estimation
Record the tool output as a structured deadline estimate (start/end dates plus the trigger logic). This is useful for internal review when multiple dates (delivery, invoice due, notice, discovery) compete.
Related reading
- Choosing the right statute of limitations tool for Vermont — Tool comparison
- Choosing the right statute of limitations tool for Connecticut — Tool comparison
