Statute of Limitations for Oral Contract in Philippines

7 min read

Published March 22, 2026 • By DocketMath Team

Overview

In the Philippines, a contract can be enforceable—but only within a specific window of time. That window is governed by the statute of limitations, which sets the deadline for filing a case in court.

For oral contracts, the rule is mainly traced to the Civil Code provisions on obligations and actions. Practically, that means your “clock” usually starts from the moment a cause of action accrues—often when the breach occurs or when performance becomes due and is not fulfilled.

DocketMath’s statute-of-limitations calculator helps you estimate the timeline based on key dates (like the date of breach). It won’t replace legal counsel, but it can help you organize the facts and sanity-check timelines before you act.

Note: Deadlines for filing are often unforgiving. Even when a claim is strong on the merits, a late-filed case can be dismissed based on prescription.

Limitation period

Default rule for oral contracts (Civil Code framework)

Under Philippine law, actions based on an oral contract are generally treated as actions upon an obligation created by law or based on contract rather than transactions under a written instrument. In the Civil Code, the baseline limitations commonly applied to contract-based actions (including oral ones) is ten (10) years.

So, as a practical starting point:

  • Oral contract claim → commonly counted as 10 years
  • Trigger date typically used in calculations → date of breach or when the obligation became due and was not performed

How to compute the timeline (practical mechanics)

When you use DocketMath, you’ll want to provide the date that starts the clock. The most common inputs are:

  • Date of breach (or default date)
  • Optional context inputs (depending on what the calculator asks), such as:
    • Date the obligation was due
    • Whether there were acknowledgments or partial performances that could affect computation (where applicable)

Then the output usually gives you:

  • Estimated last day to file (prescription deadline)
  • Time remaining (if you input today’s date)
  • A “quick read” summary: start date → limitation period → end date

Checklist: facts that change the output

Use this to avoid common calculation errors:

Each item can change how courts characterize the timing—and thus how the deadline is computed.

Key exceptions

Even when the default limitation period is 10 years, there are situations that can change the timeline. The exceptions below are the ones that most often matter in oral-contract disputes.

1) Different characterization of the action

A claim labeled “oral contract” can still be treated differently depending on what you’re actually suing for. For example:

  • If the case is framed as injury or quasi-delict, the limitations period may differ.
  • If the action is essentially recovery of property or involves a special statutory scheme, another period could apply.

Practical takeaway: the “type” of legal action you file influences the limitation period—not just whether the agreement was oral.

2) Acknowledgment of the obligation

In prescription law, an acknowledgment of the debt or obligation can affect the computation (for instance, by interrupting prescription in certain circumstances). The key practical point is that acknowledgment must generally be attributable to the party obliged.

Examples of fact patterns that may matter:

  • Written messages admitting the obligation
  • Statements in meetings/emails agreeing to pay
  • Conduct that clearly recognizes the obligation as still existing

3) Partial performance (partial payment or performance)

Likewise, partial payment (or partial performance) can be relevant to prescription analysis, because it may be treated as recognition that the obligation is ongoing.

Practical caution: small, ambiguous payments might be argued as unrelated or as something else (e.g., a separate settlement). Your documentation matters.

4) Conditions precedent or when performance becomes due

Oral agreements sometimes require a condition before performance is due. When the obligation becomes actionable depends on whether and when that condition happened.

So the same “contract date” can yield different prescription start points because:

  • the breach may not occur until the condition fails or the due date arrives
  • the cause of action can accrue later than parties expect

Warning: Don’t use the date you talked about the contract. Use the date the cause of action accrued (commonly the date performance became due and wasn’t performed, or the date of breach).

5) Tolling concepts (very fact-dependent)

There are doctrines that can suspend or affect prescription in special circumstances. These typically require close factual matching and legal characterization.

Because this varies with the scenario, DocketMath’s calculator is best used for baseline estimates and timeline planning, not as a definitive legal conclusion.

Statute citation

For oral contracts and related contract-based actions under the Civil Code, the controlling prescription rule most commonly applied is:

  • Civil Code of the Philippines (Republic Act No. 386)Article 1144
    This provision sets a ten (10) year prescriptive period for certain actions, including those based on an obligation created by law or upon an obligation arising from a contract (commonly cited for contract-based actions).

When computing prescription, you also rely on related Civil Code provisions on how prescription runs and how it can be affected (e.g., interruption or tolling concepts), but Article 1144 is the anchor used for the default timeline in contract-based claims.

Use the calculator

DocketMath’s statute-of-limitations tool is designed to convert dates into deadlines quickly.

What you’ll typically enter

  • Contract breach date / due date: the date the other party failed to perform (or the due date that was not met)
  • Jurisdiction: Philippines (PH)
  • Optional: any clarifying fields the calculator provides (such as whether an acknowledgment/partial performance is being considered)

How outputs change when you change inputs

Use these scenarios to understand what drives the result:

ScenarioDate you changeExpected calculator effect
Breach happened later than you thoughtMove start date forwardNew “last day to file” moves forward accordingly
You used the contract signing date instead of due dateReplace signing date with due dateDeadline may shift earlier or later depending on which date is correct
Cause of action accrued after a conditionUse condition-failure dateDeadline shifts to a later start date
You input an earlier breach dateMove start date backwardDeadline becomes earlier; risk of prescription increases

Practical workflow before you rely on the deadline

  1. Identify the exact due date or breach date you can support with records (messages, invoices, delivery dates, demand letters, etc.).
  2. Confirm the claim is contract-based (not framed as a different cause of action).
  3. Run DocketMath’s calculator with the best-supported start date.
  4. Re-run with an alternative date if you have uncertainty—then compare the range.

If the “last day to file” changes materially with different plausible dates, that’s a signal to tighten your fact record before filing.

Primary CTA: Use the statute-of-limitations calculator

Related reading