Statute of Limitations for Common Law Fraud / Deceit in Singapore

6 min read

Published March 22, 2026 • By DocketMath Team

Overview

In Singapore, claims for common law fraud / deceit don’t rely on a single, always-fixed “clock.” Instead, the limitation period is tied to when the cause of action accrues, and that accrual can be affected where the claimant’s awareness of the wrongdoing comes later.

For many fraud-related disputes, the question becomes less about when the alleged deception occurred and more about when the fraud was discovered (or could with reasonable diligence have been discovered). That framing matters for calculating deadlines and for deciding what documents and timelines you’ll want to assemble early—before limitation arguments surface.

DocketMath’s statute-of-limitations calculator helps you model those timelines so you can sanity-check whether your filing window is likely to be constrained.

Note: This post focuses on common law fraud / deceit limitation issues. It does not cover every fraud-adjacent regime (for example, certain statutory claims or specialized remedies), which may have different time limits.

Limitation period

Baseline rule (when the clock starts)

For common law claims in Singapore, the baseline limitation framework is governed by the Limitation Act (Cap. 163). For fraud/deceit, the key is that limitation is generally measured from the date the action accrues—but the Act provides a “discoverability” mechanism for fraud.

A practical way to think about it:

  • If you knew (or were plainly put on notice) about the fraud early, the limitation period tends to start earlier.
  • If the fraud was concealed and only later discovered, the limitation period may start later, but not indefinitely—because “could with reasonable diligence” language prevents open-ended delay.

The typical limitation window you’ll calculate

A commonly encountered outcome for fraud/deceit under the Limitation Act is a two-part structure:

  1. A standard limitation period for the claim type, and
  2. A special discovery-based extension (when fraud is involved) that can delay when time starts running.

In other words, you often end up calculating:

  • an “earliest accrual” date based on knowledge, and
  • a final deadline that is the relevant number of years from that adjusted start point.

What information changes your result?

When you input dates into the DocketMath calculator, your output can move depending on how you choose the “discovery” date inputs. The calculator is designed for you to model those choices consistently.

Use these concepts as your inputs checklist:

  • Date of the transaction / representation (the event you allege was fraudulent)
  • Date of discovery (when you learned enough to know you had a claim)
  • Date you could reasonably have discovered (if you suspect the court could find earlier notice)
  • Filing date (the date you plan to commence proceedings)

Typical effects you’ll see:

  • Later discovery dates usually produce later limitation deadlines.
  • Earlier “could reasonably have discovered” dates tighten the window and can make a filing look too late.
  • If the calculator detects a “standard” period expiry regardless of discovery, the result may still show the claim is time-barred.

Key exceptions

Fraud/deceit claims often involve procedural and factual exceptions that influence whether the limitation argument is resolved on technical timing grounds.

Below are key areas that commonly matter in practice (in terms of how courts treat the limitation question). This is not a substitute for legal advice, but it should help you plan what to document.

1) Fraud with concealment and notice dynamics

Courts typically look closely at whether the claimant:

  • truly lacked knowledge, and
  • acted with reasonable diligence once red flags existed.

So even if you didn’t actually know, the timeline can still start earlier if knowledge is attributed through what you “ought” to have found.

Documents to gather early:

  • emails/messages around the discovery
  • internal reports, audit notes, or compliance reviews
  • communications where you asked questions and received explanations

2) “Knowingly deceived” vs. “diligent inquiry” expectations

A frequent friction point is the difference between:

  • being misled, and
  • ignoring obvious inconsistencies that would have revealed the fraud with prompt steps.

This affects how you choose “discovery” versus “could reasonably have discovered.” If your facts show early attempts to investigate, that tends to support a later discovery characterization.

3) Mixed claims and the importance of claim framing

In many disputes, fraud/deceit appears alongside other causes of action. When you bring multiple heads of claim, limitation questions can be different per cause. For that reason, it’s useful to isolate:

  • what exactly is pleaded as fraud/deceit,
  • which representations are alleged,
  • what was concealed,
  • and when the claimant learned enough to sue.

DocketMath’s tool is best used when you can identify the relevant claim date anchors (event date and discovery dates).

Warning: Some claim categories in Singapore have different limitation schemes than common law fraud/deceit under the Limitation Act. If your claim is statutory (or relies on a different legal duty), your limitation calculation may not match fraud/deceit inputs.

Statute citation

The principal limitation provisions for common law fraud / deceit in Singapore are found in the Limitation Act (Cap. 163), specifically:

  • Section 29(1)(a) and/or related fraud provisions: allows the limitation period to run from the date of discovery (or the date the claimant could with reasonable diligence have discovered the fraud), rather than strictly from the original accrual date.

The Act’s framework is applied to many fraud-based civil claims, with the discovery-based mechanism acting as the key statutory “switch” for timing.

For the precise wording applicable to your fact pattern, confirm the current text of Limitation Act (Cap. 163), s 29 and any related sections governing the general limitation framework for the claim type.

Use the calculator

DocketMath’s statute-of-limitations calculator helps you estimate a likely limitation deadline by modeling discovery-based start dates and comparing them to a filing date.

Inputs to consider

Before you start, collect the following:

  • Event date (date of representation/transaction)
  • Discovery date (date you knew enough to sue)
  • Reasonable diligence date (optional but useful—date you think a court could find you ought to have discovered)
  • Proposed filing date
  • Jurisdiction: Singapore (SG)

How outputs change

When you adjust these inputs, the calculator may shift the deadline in predictable ways:

  • If you move the discovery date later, the computed “start of limitation” moves later, which typically moves the deadline later too.
  • If you include an earlier reasonable diligence date, the start may move earlier, which can make the claim appear more time-barred.
  • If the filing date is close to the calculated deadline, small date changes can flip the result. That’s why it’s worth documenting discovery milestones carefully.

Practical workflow (fast)

Check your timeline in this order:

To calculate directly, use: **/tools/statute-of-limitations

Related reading