Statute of Limitations for Written Contract in Netherlands

7 min read

Published March 22, 2026 • By DocketMath Team

Overview

In the Netherlands, the timeframe for enforcing a claim based on a written contract is governed by the Dutch Civil Code (Burgerlijk Wetboek, BW). For many contract disputes, the analysis turns on two separate time concepts:

  • The limitation period (how long you have to bring a claim)
  • The moment the limitation starts running (often tied to when the creditor becomes aware of the claim, or when a claim is otherwise considered “due”)

DocketMath’s statute-of-limitations calculator helps you translate those legal rules into a usable timeline. You provide the contract’s key dates (for example, the due date or the date you became aware of the breach), and DocketMath estimates the relevant deadline so you can plan next steps.

Note: This article explains the Netherlands’ general limitation rules for contractual claims. It’s not legal advice, and your situation may involve special facts (like fraud, multiple breaches, or settlement communications) that affect the starting date or characterization of the claim.

Limitation period

1) General rule: 5 years for many contractual claims

Under Dutch law, many claims arising from contractual relationships fall under a five-year limitation period. The key question is when the period starts.

In practice, you typically look for one of these triggers:

  • When performance becomes due (e.g., payment was scheduled for a specific invoice date)
  • When the creditor becomes aware (or is expected to become aware) of:
    • the damage, and
    • the person liable (in a broader legal sense)

For written contracts, the “written” aspect mostly matters for proof and enforcement. The limitation period itself is generally tied to the legal category of the claim and the moment awareness/performance triggers occur—rather than the contract being written vs. oral.

2) “Due” vs. “awareness” timing can change the deadline

Different contract disputes can move the limitation deadline in different directions:

  • Straightforward non-payment: The due date for payment often provides a clean reference point.
  • Latent breach: If the breach becomes apparent later (for example, defective goods not discoverable immediately), the awareness trigger may become more relevant.
  • Continuing performance problems: If multiple breaches occur (e.g., recurring late delivery), you may have multiple claim dates, not just one.

3) Output mindset: dates, not just a “yes/no”

When you use DocketMath, think in terms of:

  • a calculated final date (the last day to file, depending on procedural framing), and
  • whether your key facts suggest the clock likely started on:
    • the due date, or
    • the awareness date.

DocketMath will use the dates you input to produce a deadline you can verify and adjust.

Key exceptions

Dutch limitation rules include meaningful exceptions and “interrupting” events. Even when the general period is five years, real cases often pivot on whether events occurred that:

  • changed the starting point, or
  • paused/interrupted the running clock.

1) Written demand and legal steps can interrupt timing

Certain actions—commonly including formal steps toward enforcement—can affect limitation timing. Practically, this is where many disputes turn:

  • A mere informal message may not be enough to interrupt.
  • A more formal action (for example, commencing proceedings or issuing a demand with legal effect) is more likely to matter for limitation purposes.

Pitfall: Relying on emails or brief letters alone can create uncertainty about whether the limitation clock was truly interrupted. If the timeline is tight, you generally want a clear paper trail and the right procedural form.

2) Negotiations and settlement communications: be careful with assumptions

Business parties often negotiate to resolve the dispute. Negotiations can be helpful, but they can also create uncertainty about limitation if you assume the clock “stops.”

Instead of assuming, track:

  • when negotiations started,
  • what was exchanged,
  • whether any party took steps that have legal consequences for limitation timing.

3) Fraud and special conduct can alter the analysis

Claims involving misleading conduct or fraud can sometimes lead to different treatment regarding starting dates or the ability to rely on limitation defenses. The legal category can also shift (contract claim vs. tort-like framing), and that can affect the limitation timeline.

DocketMath can’t replace a legal characterization analysis, but it can help you model date scenarios (for example, “what if the awareness date is later?”).

4) Multiple breaches and segmented limitation periods

For written contracts with ongoing obligations, you may have:

  • breaches tied to specific delivery dates,
  • separate damages events,
  • later discovery of nonconformity.

That can create multiple possible limitation start dates. A practical approach is to list:

  • each invoice/payment due date,
  • each delivery milestone,
  • each date you learned key facts, then evaluate each item’s potential limitation deadline.

Statute citation

The primary statutory basis for limitation in the Netherlands is found in the Dutch Civil Code (BW), specifically:

  • Burgerlijk Wetboek (BW) Book 3, Article 306: establishes a 5-year limitation period for certain actions (including many payment-related contractual claims).
  • BW Book 3, Article 307: addresses limitation periods for specific categories of claims and may include different timeframes depending on the claim type.
  • BW Book 3, Article 310: commonly referenced for 5-year limitation periods in relation to (among other matters) certain claims such as those for periodic payments or damages connected to the law of obligations, depending on the precise claim framing.

Because contractual claims can be categorized differently based on the nature of the demand (payment, damages, performance-related claims) and the factual pattern, the correct article can depend on the legal characterization of your claim.

Note: If your dispute concerns regular payments, interest, damages, or a mixture of remedies, the cited BW articles may vary by how the claim is formulated. DocketMath focuses on the timing mechanics; it can’t replace the choice of correct legal category.

Use the calculator

DocketMath’s statute-of-limitations calculator turns the rules into a timeline you can use: statute-of-limitations tool. Here’s how to get accurate results.

1) Gather the key dates

For written contract disputes, collect these facts:

  • Due date / performance date
    Example: the invoice due date (e.g., 15 April 2026)
  • Breach date (if known)
    Example: delivery was missed on 30 March 2026
  • Awareness date
    Example: the date you learned the counterparty failed to perform or that goods were defective
  • Any relevant interruption event date (if applicable)
    Example: when proceedings were initiated or a legally effective demand was issued

If you only know one of these, the calculator can still be useful—but your output may change materially if the legal analysis uses a different trigger.

2) Understand how outputs change with inputs

Your deadline shifts based on which date the rule treats as the limiter:

  • Earlier due/awareness date → earlier deadline
  • Later due/awareness date → later deadline
  • Interruption/pausing event (if applicable) → deadline moves forward

Use scenario testing. For example, compare:

  • Scenario A: limitation starts on the due date
  • Scenario B: limitation starts on the later awareness date

3) Use DocketMath as a checklist, not just a single number

A practical workflow:

Primary CTA: **statute-of-limitations tool

Related reading