Statute of Limitations for Oral Contract in Denmark

7 min read

Published March 22, 2026 • By DocketMath Team

Overview

In Denmark, whether a contract is written or oral rarely changes how a claim is evaluated—what matters most for the statute of limitations is the type of claim and when it became due. Still, oral contracts do show up in disputes where the timeline hinges on facts like delivery, performance, payment milestones, and notices.

For claims based on an oral contract, Denmark’s main limitations framework generally points to the Danish Limitation Act (Forældelsesloven) rules for civil claims. In practice, parties fight about three things:

  • When the claim accrued (often tied to when payment was due or performance was completed)
  • Whether the debtor’s conduct qualifies as an interrupting event
  • Which claims category applies (for example, ordinary contractual claims versus certain special regimes)

DocketMath’s statute-of-limitations calculator is designed to help you translate those facts into a deadline you can work with—without replacing legal review.

Note: This is a practical overview of Denmark’s limitations rules for oral-contract scenarios. It’s not legal advice. Limitations outcomes can depend heavily on the exact contract terms, dates, and communications.

Limitation period

The baseline rule (ordinary civil claims)

Denmark’s Limitation Act uses a general limitation concept that most people encounter in contract disputes: a shorter limitation period starting from a point tied to knowledge and/or accrual, combined with an outer boundary in certain circumstances.

For many contractual claims, you should expect a period anchored in the time the creditor could demand performance and (in many cases) when the creditor became aware of the circumstances giving rise to the claim. The calculator is built to model this with date inputs so you can see how moving key dates changes the result.

How oral-contract facts typically affect the timeline

Because oral contracts don’t have a signed instrument, disputes often hinge on event dates. These commonly drive limitations calculations:

  • Invoice / due date: If the contract contemplated payment on a date, that due date often becomes the anchor for when the claim is enforceable.
  • Performance completion: If payment depended on delivery or acceptance, the completion/acceptance date may matter.
  • Partial performance: If there were multiple installments, each installment can create its own accrual timing.
  • Notice of demand: Communications may matter for interrupting limitations or for establishing when the creditor became aware.

Practical checklist: inputs that change the output

When you use DocketMath, the limitation deadline you get will change based on the dates and events you enter. Here’s a checklist of the most common inputs to consider:

The calculator won’t “guess” missing dates. Instead, it helps you test scenarios—e.g., “If accrual is treated as delivery date vs. invoice due date, does the deadline move?”

Key exceptions

Interrupting events (the deadline can reset)

Under Danish limitation principles, certain creditor actions or debtor acknowledgments can interrupt the limitations clock. The practical effect is that a creditor may extend the time to bring the claim compared with simply waiting out the ordinary period.

Common categories of interrupting or time-affecting events include:

  • Debtor acknowledgment of the debt or obligation
  • Court action or other legally recognized steps that “bring the claim forward”
  • Other steps specifically recognized under Danish law to stop the clock

Because the exact legal effect can depend on the type of step and documentation, you’ll want to enter the actual date of the event rather than an estimate.

Warning: “Sending a reminder” or “emailing again” may not have the same legal effect as a formal step recognized by the Limitation Act. In limitations disputes, classification and timing matter as much as the message content.

Special claim types and longer regimes

Not every contractual dispute is treated identically. Some matters can fall under special rules (for example, where legislation creates distinct limitation structures, or where the claim is framed differently than a standard payment demand).

For oral contracts, the most common mismatch happens when a claim is partially reframed—e.g., from “breach of contract” to a claim that effectively sounds in tort-like or statutory responsibility. That reframing can affect which limitation rule applies.

Use DocketMath to model the contractual-payment approach first, then run a second scenario if the facts suggest a different legal characterization.

Evidence and timing disputes

Oral contracts are often proven by circumstantial evidence: messages, testimony, deliveries, and payment history. In limitations terms, that evidence can determine:

This is less about changing the legal rule and more about identifying the correct “start date” for that rule.

Statute citation

The core statute governing limitations in these settings is Denmark’s Limitation Act (Forældelsesloven), primarily Sections 2 and 3, which address:

  • the general limitation period for civil claims
  • the starting point (including elements tied to knowledge/accrual)
  • how the period operates in common civil scenarios

For interruption rules and related mechanisms, the Limitation Act also contains provisions on how time can be stopped or affected by certain actions (commonly referenced alongside the general rule in Sections 2–3 and subsequent relevant sections).

Because the detailed mechanics can depend on the exact procedural step taken (and the relationship between general and interrupting rules), you should treat the citation as the legal backbone and use the calculator to anchor the timeline to your dates.

Use the calculator

DocketMath’s statute-of-limitations calculator helps you turn your oral-contract timeline into a projected deadline. The key is understanding which inputs control the result.

Step-by-step: what to enter

  1. Add the accrual anchor
    • Choose the most defensible date for when the claim became enforceable (often due date or delivery/acceptance).
  2. **Add the knowledge/discovery date (if applicable in your scenario)
    • If your facts involve delayed awareness, enter the date you can support as “known enough to sue.”
  3. **Add interrupting events (if any)
    • Enter dates for legally meaningful creditor actions or debtor acknowledgments.
  4. **Enter the filing / action date (optional)
    • If you’re trying to evaluate whether action was timely, compare the filing date to the calculated deadline.

How outputs change

Use the tool in “what-if” mode by adjusting dates:

  • If you move the due date forward by 30 days, the limitations deadline typically shifts forward by the same order of magnitude (unless an interrupting event or knowledge date dominates).
  • If you move the discovery date later, the deadline can extend or contract depending on the start rule applied.
  • Adding an interrupting event can restart or affect the limitations period, producing a noticeably different deadline than a “no-interruption” scenario.

Practical example (date mechanics, not legal advice)

Suppose you have:

  • due date: 2024-01-15
  • discovery date: 2024-02-20
  • no interrupting events
  • you want to know the last safe date to act

Enter those dates in DocketMath and observe:

  • the calculator’s computed “deadline” date
  • the difference in outcome if you substitute delivery date for due date
  • the impact of a recorded acknowledgment on 2024-03-10 (if it occurred and you can document it)

That comparative approach is often the most useful way to understand risk in oral-contract disputes, where the factual anchors are contested.

Primary CTA: Use DocketMath’s statute-of-limitations calculator

Related reading