Unpaid on a Bangladesh Infrastructure Project? Protecting Claims Before Deadlines Expire

Summary

An unpaid certificate is rarely just an accounts-receivable problem. On a Bangladesh infrastructure project it can become a notice problem, an evidence problem and, eventually, a jurisdiction problem. The contract may require a notice within days, a substantiated claim within a longer period, certification by a named engineer, escalation through a project board, and arbitration or court proceedings before a contractual or statutory deadline. Missing one step can change leverage even where the work was performed and the amount appears commercially obvious. This article explains how EPC contractors, engineering companies and subcontractors can preserve claims for payment certificates, variations, delay and disruption. It also examines suspension, termination, security, contemporaneous records and the effect of Bangladesh’s current procurement framework as at 23 September 2026.

The commercial problem is not only non-payment

A contractor who has not been paid may be tempted to send a demand for the outstanding invoice and wait. That response can be too narrow. A payment certificate may sit inside a certification machinery that governs when the amount becomes due. The same contract may require notice of a variation, notice of delay, particulars of prolongation cost, substantiation of records, and a formal referral to an engineer, employer’s representative, dispute board, adjudicator or arbitrator. A demand that ignores those steps may not preserve the wider claim.

The first task is therefore to identify the claim architecture. Separate the certified sum from disputed measurement. Separate approved change from a change instructed informally. Separate delay entitlement from the cost of keeping people, plant and finance on site. Then map each issue against its contractual notice, certification, escalation and limitation provisions. The objective is not to make every position sound contentious. It is to prevent an avoidable procedural failure from obscuring a potentially recoverable entitlement.

Bangladesh’s general contract framework remains anchored in the Contract Act, 1872. Section 73 recognises compensation for loss that naturally arises in the usual course or was within the parties’ contemplation, while excluding remote and indirect loss.[1] Section 74 addresses stipulated sums and penalties by allowing reasonable compensation up to the amount named, rather than automatically awarding the contractual figure.[2] Those provisions matter, but they do not replace the contract’s own machinery. A clause that conditions entitlement on notice, certification or records can determine the evidence that must be assembled before a statutory damages argument is useful.

This is a source-led overview, not a view on any particular contract or entitlement. The governing law, dispute clause, funding arrangements, public-procurement status, project documents and factual record must be reviewed together.

Start with the contract, not the unpaid ledger

Build a document hierarchy

Infrastructure disputes often involve a signed agreement, conditions of contract, employer’s requirements, technical specifications, bills of quantities, schedules, drawings, addenda, letters of acceptance, amendments, subcontracts, purchase orders and meeting minutes. There may also be a financing agreement, a government approval, a public-private partnership instrument or a development-partner procurement document. The document called “contract” may not be the whole contract.

Create a controlled register showing the date, title, issuer, recipient, contractual status and relevant clause for each document. Check precedence provisions. A later letter may be an instruction, a waiver, an amendment, a progress assessment or merely a proposal. An email from a site representative may prove that a problem was known without proving that the representative had authority to vary price or time. That distinction can decide whether a claim is treated as an agreed adjustment, a claim requiring notice, or an unpriced risk.

The register should also identify who can bind each party. This matters where a project manager directs additional work but the contract reserves variation authority to the employer, engineer or authorised representative. It also matters when a subcontractor receives an instruction from a main contractor’s site team and later needs to show that the instruction fell within the main contract risk allocation or was independently compensable under the subcontract.

Map every deadline

Prepare a live claims calendar. At minimum, record:

• the date of the event or instruction;
• the date on which the contractor knew, or should have known, of its effect;
• the contractual notice deadline;
• the date for full particulars and supporting records;
• the certification and payment dates;
• the time for challenging a rejection or assessment;
• escalation or negotiation periods;
• the date on which arbitration or court proceedings may be commenced; and
• any expiry, renewal or standstill agreement affecting security or a guarantee.

Do not assume that a “final account” process automatically preserves every disputed item. Do not assume that continuing non-payment means time never starts. The Limitation Act, 1908 contains a general rule requiring late suits to be dismissed and provisions dealing with written acknowledgement, payment on account and continuing breaches.[3] Section 19 can create a fresh period where, before expiry, the liable party gives a signed written acknowledgement; section 20 addresses payment on account in defined circumstances; and section 23 addresses continuing breaches. These provisions are not a substitute for calculating the applicable period. A statutory limitation analysis is claim-specific, and a contract may impose shorter notice or referral periods.

The practical rule is simple: treat every contractual deadline as real unless competent advice confirms otherwise, and calculate statutory limitation independently. A request for a meeting is not necessarily a notice. A reservation of rights is not necessarily compliant particulars. A promise to “review payment next month” is not necessarily an acknowledgement that restarts time.

Identify the payment trigger

An “unpaid certificate” can describe different legal positions. The engineer may have certified the amount but the employer may have failed to pay. The contractor may have submitted an application that has not been certified. The certificate may have been issued subject to deductions, retention, set-off, liquidated damages or missing documents. A subcontractor may have a valid claim against the main contractor even though the employer has not paid upstream, unless the subcontract contains a properly effective pay-when-paid or equivalent risk provision and the applicable law permits it.

For each certificate, record the work measured, the certification date, the due date, the notice requirements, deductions, tax or withholding treatment, security and retention, payment account, bank evidence, and all objections. Send a focused notice that identifies the amount, contractual basis, due date, non-payment, interest or financing consequences if available, and the next procedural step. Avoid turning a payment notice into an argumentative narrative that buries the amount and the requested action.

An employer’s silence may be commercially frustrating, but it is not automatically acceptance. Conversely, a contemporaneous assessment, partial payment or written admission may be important evidence. Preserve the complete chain, including attachments and metadata where possible.

Payment certificates: preserve the sum and the route

A certificate is evidence, not always the final entitlement

Certification may be binding for interim purposes while remaining subject to correction in the final account. It may also be a condition to payment rather than conclusive proof of debt. The contract may distinguish between the engineer’s certificate, the employer’s payment obligation and the contractor’s right to challenge a wrongful assessment. Read those provisions together.

If a certified sum is unpaid, make the demand granular. Identify the certificate number, value, certification date, due date, amount received, balance, contractual interest if any, and the specific response sought. Ask for the contractual reason for any withholding. If the employer asserts defects, back charges or set-off, require those items to be identified rather than allowing an unexplained net figure to become the account.

If certification has not occurred, the remedy may be different. The contractor may need to show that it submitted a compliant application, that the certifier failed to act, or that an employer-side obstruction prevented certification. The claim may be framed as a debt, breach of the certification obligation, wrongful prevention, or a contractual claim for the value of work. The label should follow the contract and facts, not replace them.

Separate payment, retention and security

Retention is not the same as an unpaid certified amount. A retention release may depend on taking-over, completion, the defects-liability period, a completion certificate or submission of security. A performance security, advance-payment guarantee and retention bond have distinct functions. A contractor should not casually threaten to call or withhold a security instrument as leverage for an ordinary payment dispute. The instrument’s wording, independence and expiry require separate analysis.

A payment dispute may also interact with a financing arrangement. Assignment of receivables, lender step-in rights, direct agreements and notices of assignment can affect who must be paid and who can issue instructions. Check whether the contract restricts assignment and whether any consent or notice has been obtained. The account should show gross entitlement, certified amount, retention, tax, set-off, security and net cash separately.

Subcontractors need an upstream and downstream record

A subcontractor should not rely only on the main contractor’s explanations about the employer. Track the subcontract’s own payment application, certification, due date, notice provisions, back-to-back language, set-off rights, suspension clause and dispute procedure. Compare the subcontract scope with the main contract only to the extent the subcontract incorporates it validly. A main contractor’s failure to recover upstream does not necessarily answer whether it must pay downstream.

If the subcontractor is being asked to continue despite prolonged non-payment, seek a documented position on payment and programme. Keep the record factual. A cooperative project meeting can preserve a working relationship, but it should not waive a notice or silently accept a new allocation of risk.

Variations: the work may be clear while the price is not

Capture the instruction at the point of change

Variations arise through formal instructions, revised drawings, field directions, design development, quantities, acceleration requests, substitutions, regulatory requirements and employer changes. The first question is not “what is the price?” It is “what changed, who instructed it, and under what authority?”

When an instruction arrives, issue a prompt confirmation stating the original requirement, the changed work, assumptions, likely time and cost effect, and the reservation of rights. If the contract requires notice within a short period, comply even where the parties are discussing the instruction informally. State that work will proceed, where required for safety or programme, without waiving valuation or time entitlement. If the instruction is not authorised, ask for confirmation through the contractual channel while recording the operational reason for acting.

A variation register should link each instruction to drawings, quantities, labour, plant, materials, procurement, testing, programme logic, invoices and payment status. Do not combine unrelated changes merely because they occurred in the same month. Distinct causation and valuation make a later claim easier to test.

Value the change under the agreed method first

Use the contract’s order of valuation: existing rates, analogous rates, agreed new rates, cost-plus provisions or reasonable valuation, as applicable. Preserve quotations and actual cost evidence. A claim built only on a lump-sum estimate may fail when the contract requires records of labour, plant or materials.

If the employer directs work before price is agreed, state the basis on which the work will be recorded and valued. If the contract permits provisional rates or interim valuation, use that mechanism. Avoid accepting a payment that is described as “full and final” unless the commercial intention is clear and authorised. Under section 63 of the Contract Act, a promisee may remit performance, extend time or accept another satisfaction.[4] A settlement email, signed measurement or payment receipt can therefore have consequences beyond the immediate cash flow.

Do not confuse a variation with a claim for disruption

The direct cost of changed work is distinct from disruption to unchanged work. A revised sequence, restricted access, late design, multiple work fronts or repeated remobilisation may reduce productivity without appearing as a separate measured item. Record the baseline method, planned sequence, labour and plant assumptions, actual sequence, productivity, access condition and cause. A disruption claim needs more than a total cost divided by the contract price; it needs a credible causal bridge.

Delay and prolongation: notice, causation and mitigation

Establish the baseline

A delay claim begins with the accepted programme and its updates. Identify the critical path, planned access and approvals, design release dates, procurement lead times, calendars, resources and interfaces. Then identify the event, the contractual relief, the affected activities, the period of effect, concurrent events, mitigation and the actual cost.

Common project events include late possession, delayed drawings, employer instructions, utility relocation, approval delay, interference by another contractor, suspension, exceptional weather, changes in law, force majeure events and payment-related slowdown. Their treatment depends on the contract. A delay may give time but not cost; a payment default may support suspension but not every consequential loss; an employer instruction may be a variation but not an excuse for unrelated inefficiency.

Give notices even while impact is developing

A contractor may know the event before knowing the final number of days or taka. A compliant early notice can preserve the claim, followed by updated particulars as the effect develops. Identify the event, date, relevant clause, current effect, expected effect, mitigation steps and records to follow. Update the programme and cost forecast rather than waiting for the end of the project.

Delay costs commonly include site overheads, extended supervision, accommodation, equipment, security, insurance, finance and subcontractor prolongation. Each item needs a contractual basis and contemporaneous support. Keep project-specific costs separate from head-office overhead. If a contractual formula applies, use it consistently and explain inputs. If the claim is for damages under general law, section 73’s natural-loss and remoteness principles remain relevant, but the contract may allocate delay risk more specifically.[1]

Mitigation is not an admission

Mitigation can include resequencing, alternative procurement, additional shifts, changed access arrangements or partial demobilisation. Document the decision, expected saving, cost of implementing it and constraints. A reasonable mitigation step does not necessarily concede that the employer was not responsible. Conversely, failing to mitigate can allow the employer to argue that avoidable loss should not be recovered.

Do not create records retrospectively. A later expert report can analyse programme logic and quantum; it cannot reliably replace a missing daily record of who was on site, what work was available and why resources remained.

Contemporaneous evidence is the claim’s operating system

Preserve facts before positions harden

The most useful evidence is often ordinary project administration: daily reports, timesheets, plant logs, delivery tickets, photographs, inspection requests, drawing registers, requests for information, site instructions, minutes, test results, weather records, access logs, invoices, payroll, bank statements, procurement records and programme updates. Preserve versions rather than only the final file. Keep a note of who created a record, when and for what operational purpose.

A project record should allow a reviewer to answer five questions: what was required; what happened; who knew; what did it cost; and what was done next. If a record answers only one of those questions, link it to other records. A photograph should carry a date, location and description. A meeting minute should record decisions, open actions and reservations, not only attendance.

Protect the audit trail

Use a controlled document repository with permissions, version history and a naming protocol. Preserve original emails and attachments. Avoid changing the wording of old records to make them more persuasive. When preparing a claim, maintain a separate working copy and identify analysis, assumptions and privileged legal advice. Do not label ordinary commercial communications “privileged” as a substitute for legal advice.

A party anticipating a dispute should also consider preservation obligations, confidentiality, personal data and cross-border transfer restrictions applicable to its business. Those issues can affect the way employee, payroll and subcontractor data are collected, but they should not be used as a reason to destroy or withhold relevant project material. Obtain advice on an appropriate legal hold and disclosure strategy.

Build a claim matrix

A practical claim matrix can have these fields: issue, contract clause, event date, notice due, notice sent, entitlement, quantum method, supporting documents, counterparty response, certification status, unresolved assumption, escalation deadline and owner. Link the matrix to the payment and variation registers. Update it after every instruction, certificate, meeting and decision.

The matrix is not a pleading. Its purpose is to expose gaps while they can still be fixed. A claim that has no identified clause, no event date or no causal record needs attention before a formal demand is sent.

Suspension: leverage with consequences

Check the contractual preconditions

Non-payment may entitle a contractor to suspend or slow work, but only if the contract grants that right and the required notices are served. The clause may require an overdue amount that is undisputed, a notice of intention, a cure period, continued protection of the works, or compliance with an engineer’s determination. A contractor that suspends without satisfying those conditions may face allegations of abandonment, delay, defective performance or wrongful repudiation.

Separate a contractual suspension from a practical reduction of resources. If work becomes unsafe or impossible, record the cause and the operational decision. If the decision is financial, state the contractual basis and the steps required for resumption. Continue critical protection, security, preservation and safety duties where required. Identify the effects on subcontractors and suppliers before issuing a site-wide instruction.

Preserve payment and time consequences

A suspension notice should identify the payment default, amount, due date, prior notices, contractual right, proposed effective date, scope of suspension, steps to protect the works, expected cost and conditions for resumption. It should reserve rights to time and cost while avoiding an unnecessarily broad statement that all performance has ended.

If the employer pays or agrees a cure plan, document whether the contractor resumes and on what basis. A return to work can be evidence of waiver if it is not accompanied by a reservation. Section 39 of the Contract Act recognises that conduct may amount to acquiescence in continuation after a refusal to perform, while still permitting compensation for damage in the illustration given by the statute.[5] The statutory provision is not a complete construction-suspension code, but it reinforces why conduct and communications must be controlled.

Termination: decide what survives

Termination does not erase accrued claims

Termination may trigger valuation of work performed, payment for materials, demobilisation, return of equipment, release of security, defects obligations, confidentiality, insurance and dispute provisions. A contractor should identify accrued certificates, instructed changes, delay and disruption up to the termination date, termination costs, loss of profit where contractually available, and any set-off or counterclaim.

The termination notice itself must be checked for contractual basis, authority, notice period, cure opportunity and factual accuracy. A notice that says “termination for convenience” may have different consequences from termination for contractor default. An employer’s failure to pay may support a contractor termination right only where the contract and applicable law allow it, and after the required process.

Under section 39, a promisee may put an end to a contract where the other party has refused or disabled itself from performing its promise in its entirety, unless the promisee has signified acquiescence in continuation.[5] Whether that principle applies to a particular infrastructure termination depends on the contract, the alleged breach and the surrounding conduct. It should not be treated as a shortcut around contractual termination provisions.

Protect the handover record

At termination, create a joint or independently witnessed record of work status, materials, equipment, defects, drawings, test results, permits, access, safety controls and outstanding instructions. Confirm the date on which access was given or withdrawn. Record what the contractor removed and what remained. Preserve communications with subcontractors and suppliers, particularly where their claims may be passed through.

Do not allow a termination meeting to become an unrecorded settlement. If a commercial discussion is intended to be without prejudice or subject to contract, use appropriate wording and keep operational directions separate from settlement proposals. If the parties agree a final account or release, identify precisely which claims are released and which remain open.

Dispute procedures shape recovery

Follow the agreed ladder

The contract may require an engineer’s decision, employer review, dispute adjudication, dispute board, senior-management negotiation, mediation, arbitration or court proceedings. These stages are not interchangeable. A party may lose a contractual right by missing a referral period, commencing in the wrong forum, or treating a non-final assessment as a final award.

Read the dispute clause with the payment, variation, notice, governing-law, jurisdiction and escalation clauses. Confirm the seat, language, number and appointment method for an arbitral tribunal, institutional rules if incorporated, service method, interim-relief provisions and enforcement locations. If a government entity or project company is involved, check authority, approvals, immunity arguments and any public-procurement requirements.

Bangladesh’s Arbitration Act, 2001 is the principal domestic arbitration statute, and BIAC provides an English and Bangla copy of the Act for reference.[6] The Act’s operation, the arbitration agreement, court support, interim measures, award challenge and enforcement must be analysed against the clause and facts. A foreign seat, foreign award or assets outside Bangladesh adds a cross-border layer. The New York Convention and the law of the enforcement jurisdiction may then become relevant; no single route is automatic.

Do not let negotiation consume the deadline

Negotiation may protect the commercial relationship and produce an acknowledgement, payment or standstill. It may also continue until the contractual referral period or statutory limitation period has expired. Put any extension or standstill in signed writing with clear dates, claims and parties. Do not assume that a meeting, mediation invitation or “subject to discussion” email stops time.

The Limitation Act provisions on acknowledgement and payment have technical conditions.[3] A contractor should not draft a concession or acknowledgement without considering whether it changes the claim, starts a fresh period, admits a counterclaim or compromises security. The safest commercial practice is to calendar the deadline independently while negotiations proceed.

Public procurement requires an additional layer

For public works, identify whether the project is governed by the Public Procurement Act, 2006, the current Public Procurement Rules, standard tender documents, development-partner rules or a project-specific regime. The Bangladesh Public Procurement Authority states that the Public Procurement Rules, 2025 (PPR 2025) became effective simultaneously with corresponding amendments to the Act on 28 September 2025.[7] This is the operative current procurement position identified by the competent authority as at the checked date. It is not evidence of a separate September 2026 change.

BPPA’s rules index also preserves the PPR 2008 materials and identifies PPR 2025. The applicable version must be checked against the contract’s date, tender documents, funding source and transitional provisions.[8] A standard document may contain its own payment, variation, extension, suspension, termination and dispute clauses. Those clauses should be read as the project’s operative machinery rather than replaced with a generic construction-law assumption.

A public contractor should preserve procurement records, approval trails, measurement books, certificates, correspondence with the procuring entity and any required administrative complaint or review. A contractual claim and a procurement complaint are not necessarily the same route. The Public Procurement Act includes provisions on contract management and records, and its official text identifies complaint and appeal structures in the statutory framework.[9] The question is which provision applies to the post-award claim, not whether every payment dispute can be converted into a tender challenge.

The BPPA e-PW3 standard works document shows how demanding the claim machinery can be in practice. It requires early written warning of an event likely to affect quality, price or time, and provides a 14-day notice period for an extension-of-time request after the contractor becomes aware of the event.[10] Its variation provisions require written notice of the background and likely cost implications no later than the seventh working day after awareness and state that late notice bars the claim.[11] The contractor’s general claim clause is stricter in a different way: notice of an extension or additional-payment claim must be given as soon as practicable and no later than 28 days after awareness, followed by a fully detailed claim within 42 days unless another period is approved.[12] These are standard-document terms, not a universal statutory deadline, but they illustrate why a final account cannot safely be the first claim document.

The same standard document separates certification from payment. Monthly statements are checked and certified by the project manager; certified amounts are payable within 28 days after the certificate, subject to contractual adjustments; and late-payment interest is calculated at the rate stated in the particular conditions.[13] It also gives a route for payment and time consequences after an instructed suspension, while preserving the contractor’s burden to notify and substantiate cost.[14] A contractor should therefore identify whether the project is at the application, certification, due-date, default or dispute stage before choosing a remedy.

Termination has its own trapdoors. In the e-PW3 model, failure to pay a certified amount within 84 days of the project manager’s certificate is listed as a fundamental breach, but the default procedure still requires a first notice identifying the breach and proposed termination, a 21-day opportunity for clarification or remedy, and then a final notice if the response is inadequate.[15] The document also provides for amicable settlement, adjudication and, if unresolved, arbitration under the Arbitration Act 2001.[16] A contractor should not convert a potentially recoverable payment claim into an alleged abandonment by skipping that sequence.

A decision sequence for an unpaid project

When cash flow has become critical, the following sequence can reduce avoidable errors.

First, stabilise the facts. Obtain the signed contract, amendments, payment schedule, certificates, applications, instructions, programme, notices, correspondence, accounts and security instruments. Confirm the contracting parties and authority to act.

Second, isolate the entitlement. Divide certified amounts, uncertified applications, variations, delay and disruption, financing or interest, retention, termination costs and counterclaims. Do not present one unverified global number as if every component had the same legal basis.

Third, protect notices. Serve any overdue payment, variation, delay, suspension or termination notice required by the contract. Use the prescribed address and method. State that particulars will be updated if the effect is still developing.

Fourth, build the record. Preserve daily and financial records, secure programme analysis, verify quantities, and link every cost to an event. Ask technical and quantum specialists to explain assumptions rather than simply issue a total.

Fifth, choose the commercial posture. Decide whether the immediate objective is payment, certification, a cure plan, safe suspension, negotiated close-out, adjudication, arbitration, court relief or protection of a guarantee. The choice should account for project continuity and enforceability, not only the merits of one invoice.

Sixth, calendar recovery. Track contractual referral periods and the statutory limitation position while negotiating. Obtain a signed standstill or acknowledgement where appropriate; do not infer one from goodwill.

Seventh, protect the exit. If termination is considered, verify authority, cure periods, handover, security, demobilisation, subcontractor exposure and the claims that survive. Do not create a repudiation argument through an overbroad or inaccurate notice.

What to do next

An unpaid Bangladesh infrastructure claim is easier to protect before the record becomes fragmented and before a notice or referral period expires. The immediate deliverable should be a contract-and-claims map that identifies each amount, event, clause, deadline, document and proposed route. That map can then support a focused negotiation, a compliant notice, a suspension or termination decision, or formal dispute preparation.

For a non-confidential starting point, see TRW & Co’s Construction Business & Project Delivery, Infrastructure Projects & PPP, and Dispute Resolution pages. A contractor, engineering company or subcontractor considering a Bangladesh-related payment or claims issue may use the TRW contact route to identify the next conversation. Do not send privileged, confidential or time-sensitive material through an initial web enquiry.

Frequently asked questions

1. What should a contractor do first when a Bangladesh project payment certificate is unpaid?

Secure the contract and payment record, confirm the certificate and due date, identify any contractual notice or escalation requirement, and send a focused written default notice using the contract’s prescribed method. Preserve the wider variation, delay and cost claims separately rather than treating the certificate as the whole dispute.

2. Can a contractor claim a variation if the employer gave only a site instruction?

Possibly, but the answer depends on the contract’s authority and notice provisions, the instruction’s content, the parties’ conduct and the evidence of value and time effect. Confirm the instruction promptly, reserve rights, comply with any notice deadline and record the changed work and its cost. A site instruction is not automatically an agreed price.

3. Are delay and prolongation costs recoverable in Bangladesh?

They may be recoverable where the contract or applicable law supports the entitlement and the contractor proves cause, effect, contractual responsibility, notice, mitigation and quantum. Section 73 of the Contract Act addresses loss that naturally arises or was within the parties’ contemplation, but remote or indirect loss is excluded and project-specific clauses may allocate delay risk differently.[1]

4. Can non-payment justify suspension of Bangladesh infrastructure works?

It can in some contracts, but suspension should follow the contractual preconditions, notice period and cure process. A premature or overbroad suspension may expose the contractor to delay, abandonment or termination allegations. The notice should identify the default, contractual right, effective date, protection measures, reservation of time and cost rights, and conditions for resumption.

5. Does termination end a contractor’s accrued payment and variation claims?

Not necessarily. Accrued certificates, measured work, authorised variations, delay up to termination and permitted termination costs may survive, subject to the contract, applicable law, set-off and releases. The termination notice and handover record can materially affect recovery. Review security, final-account, defects, confidentiality and dispute provisions at the same time.

6. Does negotiation stop a Bangladesh construction claim deadline?

Not automatically. Contractual referral periods and statutory limitation continue unless the contract or a signed agreement changes the position. The Limitation Act contains technical rules on written acknowledgement, payment on account and continuing breaches, but their application is fact-specific.[3] Calendar the deadline independently and document any standstill, extension or settlement precisely.