Statute of Limitations for Oral Contract in Indonesia

7 min read

Published March 22, 2026 • Updated April 8, 2026 • By DocketMath Team

Overview

Run this scenario in DocketMath using the Statute Of Limitations calculator.

In Indonesia, a claim based on an oral contract is typically evaluated under the Civil Code framework for civil claims arising from contractual obligations. In many practical analyses, these contract-based limitation periods are treated as applying a 5-year limitation period (KUHPerdata), though the exact rule can depend on how the claim is legally characterized.

Because an oral agreement isn’t always supported by a signed writing, disputes often turn on (1) when the breach occurred and (2) how clearly the parties can prove the contract’s existence and the relevant performance terms (e.g., what was promised, and when it was due).

DocketMath’s statute-of-limitations calculator can help you estimate the deadline once you know the key date(s)—for example, the due date of performance or the date the other party refused to perform / repay. This is best thought of as a deadline-estimation tool, not a substitute for reviewing your specific legal classification and evidence.

Note: A frequent reason deadlines are missed in civil disputes is using the wrong “start” date—limitation analysis commonly depends on when the claim becomes due (for instance, when payment should have been made, or when performance was refused).

Limitation period

In practice, the most commonly referenced limitation period for contract-based civil claims in Indonesia is 5 years under the Civil Code approach applied to contractual obligations (KUHPerdata).

What you need to calculate

To estimate the limitation period for an oral contract claim, identify the timing facts that best support the date the right to sue became due:

  • Contract formation date (useful context, but often not the trigger)
  • Due date of performance
    • If the contract requires payment or delivery on a specific date, the due date often anchors the analysis.
  • Breach date
    • For example, the date non-payment occurred after the due date.
  • Key “clock start” date you will use
    • Common options: due date of payment, breach date, or refusal/demand date (depending on your factual timeline)
  • Any date that affects running time
    • Some events may affect the limitation period depending on legal characterization (covered next in “Key exceptions”).

How the deadline shifts with different dates

Because the limitation endpoint changes depending on what date you choose as the start, consider these practical scenarios:

Scenario (oral contract)Key date you use as the startEstimated limitation endpoint (5 years)
Payment was due on 2023-01-15 and not paid2023-01-152028-01-15
Payment was not due on a fixed date; creditor demands payment and debtor refusesDate of refusal / refusal after demand5 years from refusal
Performance was due in installments; last unpaid installment triggers later breachDate last installment became due5 years from that last due date

Practical tip for oral contracts

Oral agreements can increase evidentiary pressure. Even when the limitation framework is “5 years,” you usually still need a defensible story for:

  1. What the parties agreed to (testimony, receipts, witnesses, correspondence), and
  2. When the promised performance became due and when the breach occurred.

DocketMath can help you standardize the “start date” step so you can compare deadlines across alternative timelines.

Key exceptions

Although many oral contract disputes follow the general 5-year civil limitation framework, the way time runs can change based on the facts and on how the claim is framed.

1) Events that can stop or affect the running of time

Certain civil-law concepts may affect the limitation clock (for example, formal demands, acknowledgments, or other events with legally recognized effects). In practice, the key is to connect the timeline facts to recognized Civil Code concepts—rather than relying on informal “we talked about it” dates.

Common real-world triggers litigants may attempt to rely on include:

  • Formal demand for payment/performance (if you can tie it to a legally meaningful event)
  • Acknowledgment of debt or obligation
    • For example, partial payment or a written admission
  • Restructuring or settlement discussions
    • These may become important if they can be tied to the legal timing arguments

Pitfall: If your timeline is vague (e.g., “sometime in 2024 they promised to pay”), you may end up arguing both breach timing and limitation interruption/impact, which can be harder if the link to a legally relevant event isn’t clear.

2) How claim characterization changes the analysis

Not every dispute about an “oral agreement” will be litigated as a straightforward contractual breach. Parties may frame claims as, for example:

  • Debt recovery tied to the agreement
  • Contract performance / non-performance and damages
  • Other civil theories (depending on the facts), such as enrichment-type arguments

Different characterizations can affect which limitation rule applies, and therefore which “clock start” date makes sense for your model.

3) Multiple obligations and installment logic

Oral agreements often involve installments or ongoing performance. In these cases, limitation analysis may depend on:

  • Whether you argue the limitation clock runs from the due date of each installment, or
  • Whether there is a clear repudiation/refusal that affects future performance, making the refusal date more important.

This is why it’s crucial to document the “last due event” (or the refusal/repudiation date) with whatever evidence you have.

Statute citation

Indonesia’s Civil Code (KUHPerdata) contains the general rules governing civil claims and, in practice, is commonly referenced for limitation periods applicable to civil actions—including contract-based claims.

Because limitation analysis can depend on how the claim is pleaded and classified, treat KUHPerdata as your starting point for estimation, and confirm the most fitting statutory characterization against your specific facts.

Note: This page uses KUHPerdata as a general reference point for estimation. It does not determine your exact legal classification or applicable article for every fact pattern.

Use the calculator

Use DocketMath’s statute-of-limitations calculator to estimate your limitation deadline based on your chosen “start” date and a modeled limitation framework.

Inputs to provide (practical checklist)

  • Jurisdiction: Indonesia
  • Claim type: oral contract / contractual obligation (modeled as a contract-based civil claim for estimation)
  • Start date: the date your claim is considered to have become due (common options):
    • due date of performance/payment
    • breach date
    • refusal/demand date (depending on how the right to sue became due)
  • Limitation framework: choose the contractual civil limitation framework aligned with the KUHPerdata approach (often modeled as 5 years for estimation)
  • Event date(s) affecting timing (if supported by your workflow):
    • any date you believe may affect running time (e.g., acknowledgment or legally relevant demand)

What outputs you’ll get

Depending on the calculator workflow, you should expect:

  • Estimated limitation end date (start date + limitation period under the modeled framework)
  • Sensitivity/scenario comparison if you rerun with a different start date (e.g., “breach date” vs “refusal date”)

Example workflow

  1. Pick the breach date as your start date (e.g., non-payment after the due date).
  2. Run DocketMath.
  3. If the due date is unclear or the debtor’s refusal happened later, rerun using the refusal date as the start date.
  4. Compare which modeled timeline is more defensible based on your evidence.

To run DocketMath, use: /tools/statute-of-limitations

Related reading