Statute of Limitations for Common Law Fraud / Deceit in Netherlands

Overview

In the Netherlands, “common law fraud / deceit” doesn’t map 1:1 to a single, named English-law cause of action. Instead, civil claims based on fraudulent or deceitful conduct are typically handled under Dutch civil law frameworks—most commonly tort (onrechtmatige daad) and, depending on the facts, other liability theories where deception is alleged.

A recurring practical issue in fraud/dispute cases is the statute of limitations: how long a claimant has to bring a claim before the right to sue becomes time-barred. The Dutch limitations regime for civil damages claims is largely governed by the Civil Code (Burgerlijk Wetboek), with a structure that includes:

• a general limitation period (usually 5 years),
• a “knowledge” trigger (the clock often starts when the claimant discovers the relevant facts), and
• an outside limit (a long-stop date even if the claimant did not discover earlier).

If you’re tracking timing, DocketMath’s statute-of-limitations calculator can help you model the relevant dates using the Civil Code’s structure.

Before diving into the timeline mechanics, it helps to distinguish “what” is being claimed and “when” the claimant became aware—because those facts often determine when the clock starts.

Limitation period

The core structure (what the 5-year period and the long-stop do)

For many civil damages claims in the Netherlands (including claims framed around fraudulent/deceitful conduct), the general rule is:

1. A 5-year limitation period that begins on the day the injured party:

   • knows or should reasonably have known the facts that justify the claim (commonly described in practice as knowledge of: the damage, the conduct, and the relevant person).

2. A long-stop outside limit: even if knowledge is delayed, there is generally a maximum time beyond which a claim cannot be brought.

Concretely, Dutch law uses a combination of:

• 5 years from knowledge, and
• 20 years from the event (or from the relevant act/date, depending on the claim category and how the duty is framed).

How this plays out in fraud/deceit fact patterns

Fraud and deceit allegations often involve “delayed discovery,” such as:

• concealed documents,
• misleading statements that only later come to light, or
• asset transfers discovered after the fact.

That delayed discovery matters because:

• if you can credibly argue the claimant did not know (and could not reasonably have known) earlier, the 5-year period may start later; and
• the claimant’s ability to act “reasonably” is assessed based on what information was available, not just what was actually known.

Practical checklist: timeline inputs you should gather

To estimate the limitation window accurately, collect:

• Discovery date: the date the claimant learned the “fraud/deceit” facts (or the date a court would likely find they should have learned).
• Event/act date: the date of the allegedly deceitful conduct (e.g., signature of misleading agreement, misrepresentation, transfer, publication).
• Claim type: confirm whether you’re modeling a civil damages claim that falls under the general tort/civil damages limitations framework.
• Person/party linkage: when the claimant can connect the alleged conduct to the defendant.

Even without giving legal advice, these inputs determine how outputs from a limitation calculator shift—move the discovery date forward, and the “5-year” component usually moves too, while the long-stop still anchors an outer deadline.

Key exceptions

Dutch limitation rules have important variations depending on the claim category and the specific statutory framework. In fraud/deceit scenarios, the main “exceptions” you typically watch fall into two buckets:

1) Legal classification differences (tort vs. other civil bases)

If the claim is not analyzed under the same general limitations regime, the clock mechanics may change. For example, claims based on specific contract law mechanisms or other statutory frameworks might be governed by different limitation periods or triggers than the general civil damages rule.

What to do practically: confirm the legal basis you’re modeling in the dispute timeline, because the statute-of-limitations logic follows the legal category.

2) Suspension/interruptions (procedural steps)

Even where the general 5-year/long-stop structure applies, the limitations clock can be affected by events such as:

• certain formal demands,
• service of process, and
• other legal actions recognized by Dutch law as affecting limitation.

Because interruption/suspension can be technically dependent on what happened procedurally (and when), it’s often safest to treat this as a “fact-sensitive overlay” rather than something you assume automatically.

Fraud-related reasoning: “knowledge” is the battleground

A fraud/deceit dispute frequently turns on the knowledge trigger:

• When did the claimant know (or should have known)?
• What would a diligent claimant have discovered sooner?

That question becomes a practical evidence issue—emails, audits, due diligence reports, litigation notices, and internal investigations can all influence the “reasonable knowledge” date.

Statute citation

The key provisions for civil damages limitation in the Netherlands are in the Dutch Civil Code (Burgerlijk Wetboek), notably:

• Article 3:310 of the Dutch Civil Code (Burgerlijk Wetboek): establishes the general civil damages limitation structure of a 5-year period from knowledge and a 20-year long-stop.

When modeling timelines for fraud/deceit allegations, you typically start with Article 3:310 as the default limitation framework for the civil damages theory, unless a different statutory category clearly applies.

Use the calculator

DocketMath’s statute-of-limitations tool helps you model how the Dutch limitations timeline changes when you adjust key dates and assumptions.

Recommended inputs for NL (fraud/deceit framing)

In the DocketMath calculator, use these inputs:

• Event/act date (date of the allegedly deceitful conduct)
• Knowledge/discovery date (date claimant knew or reasonably should have known key facts)
• Case type (select the scenario that matches your claim category—typically a civil damages framework under the Dutch Civil Code if you’re modeling general tort/deceit-style damages)
• Any interruption/suspension details (if the calculator supports it; otherwise treat interruption as outside-model and note the procedural step date separately)

How the outputs work (what you’ll see)

You should expect outputs that separate:

• a computed end date for the 5-year period (based on your discovery/knowledge date), and
• a computed long-stop end date (anchored to the outside maximum, typically the 20-year component under Article 3:310).

If you change the knowledge/discovery date by 60 days:

• the 5-year end date shifts accordingly,
• while the long-stop usually stays the same (because it is driven primarily by the event/act date).

If you change the event/act date by 60 days:

• both the long-stop and (depending on modeling approach) potentially other anchoring dates shift.

Run it directly

Start here: DocketMath Statute of Limitations Calculator

After you run it, double-check:

• whether the discovery date you entered is defensible on the facts, and
• whether the calculator’s case-type choice matches the legal basis your dispute is using.

For quick navigation and consistency with DocketMath workflows, you may also find it helpful to review our tooling area: /tools.

Related reading

• Choosing the right statute of limitations tool for Vermont — Tool comparison
• Statute of limitations in Singapore: how to estimate the deadline — How-to guide
• Choosing the right statute of limitations tool for Connecticut — Tool comparison