Statute of Limitations for Written Contract in Pakistan

7 min read

Published March 22, 2026 • By DocketMath Team

This article is for informational purposes only and does not constitute legal advice. Laws change frequently — verify all citations with current official sources.

Overview

In Pakistan, the time window for suing on a written contract is governed by the Limitation Act, 1908. For people using DocketMath’s statute-of-limitations tool, the practical question is usually straightforward:

You have a written contract (e.g., a signed agreement, loan agreement, supply contract).
You want to know how long you have to file a claim in court after the relevant “starting point.”

For limitation purposes, Pakistan law generally treats “written contract” claims as contractual claims and measures the time limit from the cause of action—the event that makes the claim enforceable (commonly, a breach or failure to pay/perform when due).

Note: Limitation rules control timeliness of court filing, not whether you “deserve” the claim. Even strong contracts can be dismissed if filed outside the statutory window.

DocketMath’s calculator helps you operationalize those rules by turning the statute into a date-driven output. You’ll input a few facts (like the breach/payment due date), and the tool estimates the last date to file under the written-contract limitation framework.

To use the relevant tool: DocketMath — Statute of Limitations

Limitation period

The core rule for written contracts (contractual claims)

Under the Limitation Act, a claim based on a written contract is typically treated as a claim with a specified limitation period. The period is measured from when the right to sue first accrues.

In practice, that “accrues” date often lines up with one of these:

Failure to pay by the agreed due date (for money due under the written contract).
Failure to deliver/perform by the contract’s performance date.
Repudiation or refusal to perform (where the contract or conduct makes the breach clear).

How to choose the right starting point

To avoid mistakes, map your situation to the correct factual trigger:

If payment was due on a fixed date: start from that due date once payment is missed.
If performance was due after notice / installments: start from the due date of the specific installment or the date notice required performance elapsed.
If there was a written demand: a demand can be relevant, but the Limitation Act period runs from when the cause of action accrued—so you still need to connect it to breach timing under the contract terms.

Quick checklist: written contract timing inputs

When you’re preparing to use DocketMath, gather:

Key exceptions

Pakistan’s limitation law includes mechanisms that can extend or pause time in specific circumstances. These do not “rewrite” your contract—they adjust the timeline under the Limitation Act.

1) Acknowledgment of liability (fresh start effect)

If the debtor acknowledges the debt/liability in a manner recognized by limitation rules, the clock can be affected. Common examples include:

Practical impact for DocketMath: if you have a valid acknowledgment date after breach, you may need to input it so the calculator can adjust the “fresh starting” date (depending on the tool’s mapping of legal categories to limitation effect).

Warning: Not every message counts. Informal statements without clear admission of liability may not produce the limitation effect you expect. Track wording and context carefully.

2) Part-payment of a debt

Sometimes, part-payment can shift limitation calculations—particularly where the payment is made in a way that is consistent with acknowledging the debt.

Practical impact: if you made or received a part-payment and you can document the payment date and reference to the same contractual obligation, that date can become critical.

3) Disability of the claimant (legal disability provisions)

The Limitation Act contains provisions for people under certain disabilities. For example, claims by minors or certain persons with legal disability can have special treatment.

Practical impact: the starting point and total limitation period may be affected by the disability and its end date.

4) Procedural moves and how they interact with limitation

While limitation is substantive, real-world litigation involves procedural steps—like issuing notices, correspondence, mediation, and even prior suits.

DocketMath’s calculator is focused on the statute-driven timeline; it can’t replace a full procedural review of your case history, but it will still anchor the key dates for limitation analysis.

Statute citation

The limitation for suits on written contracts in Pakistan is provided by the Limitation Act, 1908. The key provisions are located in:

Limitation Act, 1908 — Schedule (Articles), particularly the article covering suits for breach of written contract.

For the written-contract category, the relevant schedule article is commonly cited as:

Limitation Act, 1908, Article 115 (suit for compensation for breach of contract in writing registered or in writing)

Note: Courts and practitioners often cite the Schedule/Articles as the authoritative source for the “period” and “time from which period begins to run.” When using DocketMath, your inputs should align with the factual trigger that starts the clock under the relevant Article.

Use the calculator

Use DocketMath’s statute-of-limitations tool to convert the statutory timeline into dates you can act on.

Suggested inputs (what you’ll typically provide)

Because written-contract limitation depends on the cause of action timing and possible “reset” events, the calculator generally works best when you enter:

Contract type: Written contract
Claim type: Breach / payment due / performance due
Breach or due date (when the obligation became overdue)
Optional: acknowledgment date and/or part-payment date (if you’re relying on these to affect limitation)
Jurisdiction: **Pakistan (PK)

How outputs change with your inputs

Here’s what usually happens when you change key dates:

Input you change	Typical effect on limitation result
You move the due/breach date earlier	Earlier “clock start,” so the last filing date moves earlier
You move the due/breach date later	Later “clock start,” so the last filing date moves later
You add a valid acknowledgment/part-payment date	Potentially creates a later limitation trigger, extending the last filing date
You remove acknowledgment/part-payment data	The calculator likely uses the original breach/due date only

Practical workflow

Confirm the contract is written and the obligation is clearly stated.
Identify the earliest date your claim became enforceable (breach/due date).
Gather acknowledgment/part-payment dates if they exist and are clearly linked to the same obligation.
Run the DocketMath calculator with the selected written-contract category.
Capture the latest date to file and work backward:

Pitfall: People often input the date they sent a demand notice rather than the date the contract obligation actually became due or was breached. The limitation clock is tied to the cause of action accrual, not just the day you became aware.

Output you should expect

DocketMath’s tool is designed to provide:

A calculated limitation period endpoint (last date to file, based on the statute framework)
A clear explanation of which date(s) were treated as the trigger(s)

If you receive an output that seems surprising, revisit:

whether the contract qualifies as written,
the exact breach/due date,
and whether any acknowledgment/part-payment truly relates to the same liability.