Worked example: Statute Of Limitations in Philippines

7 min read

Published April 15, 2026 • By DocketMath Team

Example inputs

Below is a worked example showing how DocketMath can compute a statute of limitations (prescription period) for a Philippines case using jurisdiction-aware rules (PH). This is a practical walkthrough of how the calculator thinks, not a substitute for legal advice.

Scenario (Philippines, PH)

You’re evaluating whether a civil action to collect an unpaid debt filed in court is timely.

  • Jurisdiction: Philippines (PH)
  • Claim type (civil): Collection of sum of money based on a written contract
  • Contract date (event start): 15 January 2020
  • Action date (filing date): 20 February 2025
  • Tolling / interruption facts: None assumed for the baseline run
  • Outcome you’re testing: Whether the claim is prescribed (time-barred) on the filing date

What the tool needs you to enter

In DocketMath’s statute-of-limitations calculator, you’ll generally enter:

  • Jurisdiction code: PH
  • Cause/claim category: (here: written contract / obligation arising from contract—collection of sum of money)
  • Start date: the date from which prescription begins running for that category (we’ll use the contract date for this example)
  • Filing date: the date the case is filed

Note: The “start date” is the most sensitive input. In Philippines prescription analysis, prescription often begins when the right of action accrues (for example, when payment becomes due). If your contract has a due-date clause, that clause may control the start date.

Example input set (baseline)

  • PH
  • Claim category: Written contract – collection of sum of money
  • Start date: 2020-01-15
  • Filing date: 2025-02-20
  • Interruption/tolling: None

Example run

Here’s an end-to-end run using the above facts. For the primary action, use this link to try the same calculation: /tools/statute-of-limitations.

Run the Statute Of Limitations calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.

Step 1: Run the baseline calculation (no interruption)

Inputs:

  • Jurisdiction: PH
  • Category: Written contract – collection of sum of money
  • Start: 15 Jan 2020
  • Filing: 20 Feb 2025

How the tool computes (conceptually):

  1. It identifies the prescription period for the claim category using Philippines-specific rules.
  2. It adds that period to the start date to produce the deadline date.
  3. It compares the filing date to the deadline date.
  4. It reports:
    • whether the claim is prescribed
    • any calculated time remaining/overdue (if available)
    • key dates used in the computation

Step 2: Baseline result (worked example)

For a written contract action to collect money, a commonly applied civil-law prescription period in the Philippines is 10 years under prescription rules for actions based on a written contract.

  • Start date: 15 Jan 2020
  • Prescription period: 10 years
  • Deadline: 15 Jan 2030
  • Filing date: 20 Feb 2025

Result: Not prescribed (filed well before 15 Jan 2030)

Quick date math summary (what DocketMath is doing)

ItemDate
Start date (accrual for this example)15 Jan 2020
Prescription period (written contract)10 years
Deadline date15 Jan 2030
Filing date20 Feb 2025
Timeliness outcomeTimely (not prescribed)

Interpretation for your filing timeline

This baseline supports timeliness because:

  • Filing occurs less than 10 years after the start date.
  • The gap from 15 Jan 2020 to 20 Feb 2025 is about 5 years and 1 month.

Pitfall: A written contract’s “accrual” date may not be the contract signing date. If the contract says payment was due on 15 July 2021, then the clock could start then—shrinking the available time by ~2.5 years in this example.

Step 3: Capture what matters for evidence

Even in a non-advice walkthrough, you can use the tool output to build a checklist of what to confirm:

  • The contract is actually written and enforceable
  • The due date (when the obligation became due) versus the signing date
  • Whether any event legally interrupts prescription

Sensitivity check

Now let’s stress-test the result by changing the inputs that usually swing prescription outcomes: (1) the start date and (2) filing date, plus a conceptual interruption check.

To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.

Sensitivity A: Start date shifts to the due date

Assume the contract states payment was due 15 July 2021, and default occurs if unpaid. For prescription analysis, you might treat 15 July 2021 as the start for the creditor’s right of action (depending on the contract terms and facts).

Modified inputs:

  • Start date: 2021-07-15 (instead of 2020-01-15)
  • Filing date: 2025-02-20
  • Everything else unchanged

Expected effect:

  • Deadline shifts from 15 Jan 2030 to 15 Jul 2031 (still later than filing)
  • The action remains not prescribed in this scenario
ItemBaselineSensitivity A
Start date15 Jan 202015 Jul 2021
Deadline (10 years)15 Jan 203015 Jul 2031
Filing date20 Feb 202520 Feb 2025
OutcomeNot prescribedNot prescribed

Takeaway: In this example, even shifting the start date by ~18 months still keeps the claim timely under a 10-year written-contract frame.

Sensitivity B: Filing occurs later (edge timing)

Let’s move the filing date to test the edge:

  • Filing date: 2030-01-20 (5 days after the baseline deadline of 15 Jan 2030)

Inputs (using baseline start date 15 Jan 2020):

  • Start date: 2020-01-15
  • Filing date: 2030-01-20
  • No interruption/tolling

Outcome:

  • Deadline: 15 Jan 2030
  • Filing: 20 Jan 2030
  • The filing is after the deadline, so it should be treated as prescribed under the straightforward 10-year rule.

Warning: Prescription edge cases can be affected by legally recognized interruptions and by what the law recognizes as the operative accrual date. A few days can matter, but the factual timeline matters more than the calendar alone.

Sensitivity C: Interruption (conceptual toggle)

If you learn there was an event that interrupted prescription, DocketMath’s inputs should reflect that—if the calculator supports interruption fields/toggles.

Because interruption rules depend heavily on the nature of the act and the evidence, treat this sensitivity test as a logic check:

  • If prescription was legally interrupted and the interruption date is within the limitation period,
  • then the “clock” effectively restarts or the computation changes,
  • then a filing that would otherwise be late might become timely.

Use the tool to:

  • compare results with vs. without interruption flags
  • record the interruption date(s) you plan to substantiate with documents or sworn statements

Your practical checklist (quick use)

Use these checkboxes to tighten your inputs before trusting the computed deadline:

Where other DocketMath tools fit

If you’re mapping a timeline of events across documents, you may find it useful to cross-check the chronology with other workflow tools before running the limitations calculator. For example, you can build your event list in a timeline-oriented tool at /tools/timeline and then feed the confirmed dates into /tools/statute-of-limitations.

Related reading