Abstract background illustration for: Statute of limitations in Singapore: how to estimate the deadline

Statute of limitations in Singapore: how to estimate the deadline

9 min read

Published April 17, 2025 • Updated February 2, 2026 • By DocketMath Team

Statute of limitations in Singapore: how to estimate the deadline

Singapore’s limitation rules are mostly statutory and look straightforward on paper—until you add in things like part‑payments, fraud, overseas defendants, or pre‑action negotiations.

This guide walks through how to estimate limitation deadlines for Singapore matters using DocketMath’s statute‑of‑limitations calculator, what inputs you need, and where the tricky edge cases usually hide.

Use it together with legal judgment and local procedure; it’s not a substitute for either.

Quick takeaways

  • Most civil claims in Singapore are governed by the Limitation Act 1959 (Cap. 163).
  • The “standard” limitation period is often:
    • 6 years for simple contract and tort claims
    • 12 years for certain deeds and judgments
    • 3 years for personal injury in some scenarios
  • The clock usually starts when the cause of action accrues (e.g., breach date, loss date), but:
    • It can be postponed for fraud, error, or concealment
    • It can be extended or restarted by acknowledgments or part‑payments
  • DocketMath’s statute‑of‑limitations calculator for Singapore:
    • Takes a small set of dates and claim‑type inputs
    • Applies jurisdiction‑specific default rules
    • Outputs an estimated “last safe day” and a breakdown of how it was computed
  • Always validate the output against:
    • The latest version of the Limitation Act
    • Relevant case law and any special statutory regimes (e.g., employment, IP, family, insolvency)

Inputs you need

To get a reliable estimate from DocketMath for Singapore limitation periods, you’ll want to collect the following before you start.

Use this intake checklist as your baseline for Statute Of Limitations work in Singapore.

  • cause of action category
  • accrual date
  • discovery date (if applicable)
  • tolling periods or pauses
  • jurisdiction-specific period

If any of these inputs are uncertain, document the assumption before you run the tool.

1. Claim characterisation

You’ll typically need to select or describe what the claim is. This drives which limitation regime DocketMath applies.

Common categories (illustrative, not exhaustive):

  • Contract
    • Simple contract (e.g., unpaid invoices, service agreements)
    • Deed / specialty (if applicable under Singapore law in context)
  • Tort
    • Property damage / economic loss
    • Personal injury / death
  • Judgment enforcement
    • Singapore court judgment
    • Foreign judgment (may involve separate regimes)
  • Statutory claims
    • E.g., specific statutes that set their own time limits

Why it matters:

A mis‑classified claim can attach the wrong limitation period. For instance, a professional negligence claim may engage both contract and tort analyses with different accrual logic.

2. Accrual‑related dates

DocketMath needs to know when the cause of action is treated as accruing under the applicable rule. You’ll usually enter one or more of:

  • Breach date (for contract)
    • When the defendant failed to perform, repudiated, or otherwise breached
  • Damage date (for tort)
    • When damage first occurred, not necessarily when it was discovered
  • Completion / delivery date
    • For work or goods; sometimes used to infer breach timing
  • Judgment date
    • For enforcement of judgments

In practice, you may not be certain which date a court would treat as the accrual point. DocketMath lets you run scenarios with different candidate dates so you can see how the deadline shifts.

3. Discovery / knowledge dates (where relevant)

For claims where discovery or “date of knowledge” might postpone limitation (e.g., certain personal injury or latent damage scenarios), you may also input:

  • Date the claimant first knew (or could reasonably have known) about:
    • The injury or loss
    • Its attribution to the defendant’s act or omission
    • The identity of the defendant

Not every Singapore claim uses a discovery‑based regime, so DocketMath only asks for this when the selected claim type makes it relevant.

4. Acknowledgments and part‑payments

For some debt and contract claims, limitation can be restarted if there is:

  • A written acknowledgment signed by the debtor, or
  • A part‑payment of principal or interest

Typical inputs:

  • Date of each acknowledgment
  • Date and amount of each part‑payment
  • Whether the acknowledgment clearly recognises the debt

DocketMath will treat each valid event as potentially resetting the clock from that date, applying the Singapore rules configured for the calculator.

5. Fraud, error, or concealment flags

Where applicable under the Limitation Act, limitation may be postponed if:

  • The action is based on fraud
  • The right of action is concealed by fraudulent concealment
  • The action is for relief from the consequences of a error

You may need to indicate:

  • Whether fraud / concealment / error is alleged
  • When the claimant discovered the fraud or error
  • When the claimant could with reasonable diligence have discovered it

DocketMath uses these to compute a postponed start date where the statute allows.

6. Procedural and “buffer” preferences

DocketMath’s calculator focuses on the substantive limitation period, but you can optionally configure:

  • Preferred filing buffer (e.g., “treat 14 days before the last day as my internal target”)
  • Service‑related assumptions
    • E.g., whether you want the deadline framed as “issue by” or “serve by” where local rules make this distinction

This doesn’t change the underlying statutory deadline, but it changes the recommended internal date that DocketMath shows.

How the calculation works

DocketMath’s Singapore statute‑of‑limitations calculation is a sequence of explicit steps. You can inspect them in detail using Explain++ from within the statute‑of‑limitations tool.

Here’s the high‑level logic.

DocketMath applies the Singapore rule set to the inputs, then runs the calculation in ordered steps. It validates the trigger date, applies rate or cap logic, and produces a breakdown you can audit. If you change any one variable, the tool recalculates the downstream outputs immediately.

Step 1: Identify the applicable limitation regime

Based on your claim type and jurisdiction = SG, DocketMath:

  1. Maps the claim to a default limitation provision (e.g., “simple contract → 6 years”).
  2. Checks whether any special regimes may be flagged (e.g., personal injury rules vs general tort).
  3. Selects:
    • The base limitation length (e.g., 6 years, 3 years, 12 years)
    • The default accrual rule (e.g., breach date vs damage date vs judgment date)

If you’re unsure of classification, you can run multiple variants (e.g., “as contract” vs “as tort”) and compare timelines.

Step 2: Determine the accrual date

DocketMath then calculates the accrual date:

  • If you specify a breach or damage date, it uses that.
  • If multiple dates are possible, it may:
    • Use the earliest one as a conservative default, or
    • Ask you to select which to treat as legally determinative.

For discovery‑based or postponed‑accrual scenarios (fraud, error, concealment), the tool applies the Singapore‑specific rule, for example:

  • Accrual is postponed until the claimant discovered (or could reasonably discover) the fraud / error / concealment, subject to any long‑stop where applicable.

The chosen accrual date is clearly shown in the calculation breakdown.

Step 3: Apply postponement or special rules

Next, DocketMath checks for any postponement triggers you’ve indicated:

  • Fraud or concealment
  • Relief from error
  • Certain personal injury knowledge rules (if configured)

If triggered, the calculator:

  1. Computes a postponed start date (e.g., date of discovery).
  2. Applies any statutory caps or long‑stops (e.g., cannot extend beyond a certain outer limit, if such a rule applies in the configured scenario).
  3. Selects the effective start date as the later of:
    • The original accrual date, and
    • The postponed start date (subject to statutory constraints).

If no postponement applies, the effective start date is just the original accrual date.

Step 4: Factor in acknowledgments and part‑payments

For claims where Singapore law allows restarting limitation via acknowledgment or part‑payment, DocketMath:

  1. Lists all acknowledgment and part‑payment dates you entered.
  2. Filters them to those that:
    • Occur before the then‑current limitation expiry; and
    • Meet the basic validity criteria (per the configuration).
  3. If valid events exist, it:
    • Takes the latest valid event date as a new effective start date.
    • Recomputes the limitation period from that date.

The breakdown will show something like:

  • “Base period: 6 years from 15 Mar 2018 → 15 Mar 2024”
  • “Acknowledgment on 10 Jan 2022 (valid) → new period: 6 years from 10 Jan 2022 → 10 Jan 2028”

If no valid events are entered, this step has no effect.

Step 5: Add the limitation period

Once DocketMath has the final effective start date, it:

  1. Adds the statutory period (e.g., 6, 3, or 12 years) according to the SG rule set.
  2. Applies any rules about:
    • Whether the start date is excluded from the computation
    • How to treat leap years and end‑of‑month issues

The output is an estimated last day on which proceedings may be commenced, e.g.:

  • “Estimated last day to commence proceedings: 15 March 2024 (inclusive)”

The Explain++ view will show the date arithmetic step‑by‑step.

Step 6: Adjust for procedural preferences

Finally, DocketMath layers on your internal practice preferences:

  • If you set a buffer (e.g., 14 days), it will display:
    • Statutory last day: 15 March 2024
    • Internal target filing date (with 14‑day buffer): 1 March 2024

Common pitfalls

  • using the wrong cause-of-action period
  • skipping tolling or suspension windows
  • treating discovery as accrual without support
  • missing choice-of-law constraints

Capture the source for each input so another team member can verify the same result quickly.

When rules change, rerun the calculation with updated inputs and store the revision in the matter record.

Sources and references

Start with the primary authority for Singapore and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

If an assumption is uncertain, document it alongside the calculation so the result can be re-run later.

Next steps

Use the Statute Of Limitations tool to produce a first pass, then share the output with the team for review. You can start directly in DocketMath: Open the calculator.

If an assumption is uncertain, document it alongside the calculation so the result can be re-run later.

Related reading