Statute of Limitations for Common Law Fraud / Deceit in Turkey

Overview

In Turkey, claims based on fraud / deceit typically rely on private-law rules that treat intentional misrepresentation as a civil wrong. That matters because the statute of limitations (time limits to sue) will depend on (1) which legal basis your claim fits and (2) when the injured party can reasonably be said to have discovered the wrongdoing.

For many “common law fraud” style disputes (misstatements, concealment, inducement to contract, or deceptive conduct), Turkish courts often analyze the case under tort (haksız fiil) concepts—especially where the dispute does not cleanly fall into a contract-specific regime. The key timing question is usually twofold:

• a subjective clock tied to discovery (when the claimant learns of the fraud and who is responsible), and
• an objective outside limit that runs from the wrongful act.

Because wording across jurisdictions differs, you’ll get the best results by using the DocketMath statute-of-limitations calculator for Turkey and pairing it with your case facts (date of the act, date of discovery, and any known tolling/interrupting events).

Limitation period

The Turkish framework: two clocks

For deceit/fraud-like claims under Turkish law, the most commonly cited civil limitation structure is:

1. A short discovery-based period (generally tied to “learning” the fraud/deceit), and
2. A longer outside period (generally tied to the act itself).

In practical terms, this means you should identify:

• Discovery date: when the claimant actually learned (or should have learned with reasonable diligence) of the misrepresentation/deceit and the responsible party.
• Occurrence date: the date the misleading act happened (e.g., signing date with deceptive statements, the moment of concealment, or the act that caused the loss).
• Whether any interruption/tolling event occurred: for example, formal steps that courts may treat as preventing the limitation clock from running (depending on the exact procedural posture).

How this affects real case timelines (simple examples)

Below are illustrative patterns showing how the two-clock structure changes outcomes:

Typical workflow to prepare

To use a statute-of-limitations calculator effectively (including DocketMath), gather:

• the date the deceit occurred (or the last date of the deceptive conduct),
• the date the claimant discovered the deceit and the liable party,
• whether there were procedural filings or other events you believe interrupted the clock, and
• whether the claim is framed as tort/deceit rather than purely contractual.

Key exceptions

Turkey’s limitation analysis doesn’t always operate as a straight “file by X date” rule. Several exceptions or special timing doctrines can matter, especially for deceit-style claims.

1) Discovery rules can shift when the clock begins

Even with a stated limitation period, the start date often hinges on discovery—meaning the claimant typically must show that they learned of the deceit and the identity of the responsible person only later. If discovery is contested, litigation can become fact-intensive around:

• what the claimant knew at earlier points,
• whether reasonable diligence would have revealed the fraud sooner, and
• when the claimant had sufficient information to bring a claim.

2) Claims may be characterized differently (tort vs. contract-related)

Fraud/deceit narratives sometimes overlap with contractual duties (e.g., misrepresentation that induces a contract). In Turkey, misclassification can change which limitation period applies. Practical implication:

• If your claim is anchored mainly in contract performance or breach, you may face a different limitation regime than if it’s treated as a tortious deceit claim.
• If your pleading focuses on intentional wrongful conduct causing extra-contractual harm, tort-style limitation analysis becomes more relevant.

3) Interruption of limitation may be argued through procedural steps

Turkish practice can treat certain filings or enforcement steps as legally significant for limitation (commonly discussed as “interruption” concepts). Because procedural details matter, you should track:

• filing dates,
• whether the filing relates directly to the same dispute and parties, and
• whether the court accepted the step as effective for limitation purposes.

4) One-year vs. longer periods are often the practical battleground

In many deceit/fraud situations, the litigation fight often focuses on whether the claim is brought within the short discovery window and whether an outside limit has already passed. That’s why identifying discovery and act dates precisely is often more valuable than debating finer doctrinal labels.

Statute citation

For civil claims resembling fraud/deceit under tort principles, Turkish limitation rules are commonly anchored in the Turkish Code of Obligations (Türk Borçlar Kanunu, “TBK”).

The central civil limitation rule for tort-based damages is set out in TBK Article 72, which provides a two-part structure:

• 1-year subjective period from the date the injured party learns of the damage and the liable person, and
• 10-year objective period from the date of the harmful act.

In addition, Turkish general civil limitation rules can include broader concepts about commencement and computation, but TBK Article 72 is the most frequently cited anchor for tort-like deceit claims involving damages.

(If your fact pattern is tightly contract-centered, the limitation analysis can shift. DocketMath helps you model the timing under the TBK framework most commonly used for deceit/deception in tort.)

Use the calculator

You can model Turkey’s statute of limitations for fraud/deceit-style claims using DocketMath’s Statute of Limitations calculator here:

• Primary CTA: /tools/statute-of-limitations

Inputs to enter

Use the following inputs (labels may appear slightly differently in the tool UI):

• Jurisdiction: Turkey (TR)
• Claim type: select the option aligned with fraud/deceit / tort-based damages (not purely contract breach)
• Harmful act date (occurrence): the date the deceptive conduct occurred (or last day of the deceptive conduct, if ongoing)
• Discovery date: when the claimant learned (or can be supported as having learned) of the deceit and the responsible party
• Any limitation-interrupting events (optional): if the tool supports it, add dates for filings/events you want considered

Outputs you should expect

DocketMath typically returns:

• Subjective deadline (the end of the discovery-based period), and
• Objective deadline (the outside limit from the harmful act), and
• a recommended latest filing date window based on which limitation expires first.

How outputs change with key inputs (quick guide)

Checkboxes and inputs often affect results in predictable ways:

• Later discovery date → later subjective deadline

  • If discovery moves from 6 months to 18 months after the act, the subjective deadline correspondingly pushes outward—until the objective limit still caps the overall deadline.
• Earlier act date → earlier objective deadline

  • Even if discovery is late, the objective cap can expire first.
• Adding an interruption date → may extend a deadline

  • If the tool models interruption, it can shift which date stops the clock. Use this only with accurate procedural dates.

Practical checklist before you rely on the result

Once those items are set, the tool output becomes a strong starting point for timing evaluation.

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