Statute of Limitations for UCC / Sale of Goods in Bangladesh
7 min read
Published March 22, 2026 • By DocketMath Team
Overview
In Bangladesh, time limits for bringing claims tied to commercial sales can turn on the type of transaction and the legal basis you’re using (for example, a contract claim versus a claim framed as “for goods”). For many business disputes involving payment, delivery, or breach of sale terms, the practical starting point is the statute of limitations under the Limitation Act (Bangladesh)—not a UCC-style code.
Bangladesh’s commercial sales framework is not a “UCC” system. Still, businesses often use “UCC” as shorthand for sales-of-goods rules and time limits. In practice, you should treat the timeline as governed by the Limitation Act, 1908 (Bangladesh), with common claims frequently falling into provisions covering breach of contract and certain actions on account of goods.
Note: A “UCC” search may pull up U.S. concepts that don’t directly map to Bangladesh. For Bangladesh timelines, the Limitation Act provisions (and the specific cause of action) are what control the filing deadline.
DocketMath’s statute-of-limitations calculator helps you model the limitation period once you identify the relevant cause of action (e.g., breach of a written contract, a contract for goods, or a different category).
Limitation period
The Limitation Act framework (what drives the deadline)
Bangladesh applies a fixed limitation period measured from a specified starting event, commonly:
- the date the cause of action accrues, and/or
- the date of breach or default, and/or
- in certain categories, the date of refusal, demand, or payment due.
For sales-related disputes, businesses typically deal with one or more of these fact patterns:
- Non-payment after an invoice due date
- Failure to deliver goods as promised
- Damaged goods or breach tied to quality/specifications
- Repudiation (one party treats the contract as ended)
- Wrongful withholding or refusal to accept goods
Typical “moving parts” you should pin down
To compute the limitation period correctly in DocketMath, you generally need to identify:
- Nature of the claim
- Contract breach for sale/payment terms
- Claim involving “goods” (where applicable under the Limitation Act category)
- Key date
- Accrual date (often linked to breach/default)
- Particulars affecting the start date
- Demand/refusal (if the legal category requires it)
How outputs change based on inputs (quick guide)
Use this as a checklist when entering facts into DocketMath:
- If your claim is framed as breach of contract, the “accrual/breach date” usually matters most.
- If the category requires a demand or refusal, the calculator shifts the clock to the demand/refusal date.
- If your matter involves written vs. oral terms, some Limitation Act entries can differ by how the contract is categorized (your claim heading matters).
Below is a practical table of “input → effect” to help you predict the calculator outcome:
| If your claim category is… | Then the key date you enter is usually… | What the calculator changes |
|---|---|---|
| Breach of contract for sale/payment | Date of breach/default (e.g., payment due + non-payment) | Limitation end date moves with the breach date |
| Goods-related claim tied to refusal/demand | Date of demand/refusal/withholding (if required by the category) | Limitation end date may shift later than the invoice due date |
| Any category where “accrual” is defined by law | Date cause of action accrues | Limitation end date is computed from accrual, not from contract signing |
Key exceptions
Bangladesh limitation rules do not just involve “years on the clock.” Certain legal doctrines can affect timing.
1) Exclusion of time (procedural time considerations)
Some periods may be excluded if they are recognized by the Limitation Act or related rules (for example, time spent in certain legal proceedings). Since the details depend heavily on the procedural history, use DocketMath to compute the base deadline first, then adjust for any recognized exclusions only if the facts match the legal category.
2) Sufficient cause / condonation-type concepts (where available)
Bangladesh practice can include provisions allowing courts to entertain late filings in specified circumstances (commonly tied to sufficient cause for delay). Whether you can use such relief depends on the statutory category and the procedural posture.
Warning: Don’t assume that “delay can always be excused.” Relief for late filing depends on the specific Limitation Act provision and the facts. A mismatch between your claim category and the remedy provision can leave the deadline unchanged.
3) Acknowledgment / part-payment effects
In some limitation regimes, acknowledgment of liability or part-payment can reset or affect limitation calculations. Whether that applies in your case depends on how the Limitation Act treats the type of acknowledgment and the claim category.
4) Fraud or concealment (rarely presumed)
If a dispute involves alleged fraud or concealment, limitation outcomes can differ. Courts often require concrete factual pleading for delayed discovery theories. In practice, this is one of the most litigated areas—verify that the facts satisfy the category’s legal triggers before relying on delayed accrual.
Statute citation
The governing statute is the Limitation Act, 1908 (Bangladesh).
For sale-of-goods/commercial claims, the relevant entries typically appear in the Act’s Schedule (which lists different “descriptions of suits” with corresponding limitation periods and time-to-start rules). In a practical DocketMath workflow, you map your dispute to the correct Schedule entry (e.g., contract/breach-related vs. goods-related), then apply the Act’s start-date rule.
Because the schedule structure matters, the calculator should be your reference point for choosing the correct category: it is designed to compute the limitation end date based on the Limitation Act schedule logic and the event date you provide.
Use the calculator
DocketMath’s statute-of-limitations calculator helps you compute the limitation deadline using your case facts and the chosen claim category. Start here:
- Primary CTA: **/tools/statute-of-limitations
What you’ll enter (and what it changes)
Check these inputs against your facts:
- Jurisdiction: Bangladesh (BD)
- Claim category: select the limitation period bucket that matches your cause of action (the calculator’s category options reflect Limitation Act schedule entries)
- Start date: the date the legal clock begins for that category
- For payment disputes: commonly the breach/default or when payment became due and wasn’t made
- For refusal/demand-driven categories: the demand/refusal date
- (Optional) Notes on factual triggers: if your interface supports it, use it to match the schedule’s start-date trigger
How to interpret outputs
The calculator typically produces:
- Limitation end date (the deadline to file within the limitation period)
- Whether a proposed filing date falls within or after the period (if you provide a filing date)
Use this workflow:
- Compute the base deadline first.
- Confirm your “start date” aligns with the schedule entry’s trigger.
- Only then consider whether any exception-like adjustments could apply (e.g., exclusion rules or other statutory relief).
Pitfall: The most common calculation error is using the contract signing date instead of the breach/default date (or the demand/refusal date when the category requires it). That one change can shift your limitation end date by months or years.
Quick scenario walkthrough
- If a seller issues an invoice for BDB 5,000,000 with a 30-day payment term, and buyer doesn’t pay:
- Many breach-of-contract timelines will start at the point payment was due and unpaid.
- If your claim category requires a demand/refusal trigger, you must enter the date of demand/refusal instead.
DocketMath helps you avoid manual miscalculation by tying the end date to the selected schedule logic and your chosen start date.
Related reading
- Choosing the right statute of limitations tool for Vermont — Tool comparison
- Choosing the right statute of limitations tool for Connecticut — Tool comparison
