You are using an outdated browser and your browsing experience will not be optimal. Please update to the latest version of Microsoft Edge, Google Chrome or Mozilla Firefox. Install Microsoft Edge

December 2, 2011

The Thailand Floods: Can Force Majeure Excuse Your Liability?

Bangkok Post, Corporate Counsellor Column

Force majeure is an event that occurs beyond your reasonable control or anticipation. When that event prevents you from performing your contractual obligations, you are ordinarily released from liability for damages caused by that breach. The rationale is that it would not be just to blame you for breach of contract when the contract became impossible to perform through no fault of your own.

The massive flood arriving in early October from northern Thailand has attacked at least seven industrial estates, including Saha Rattana Nakorn, Rojana, Hi-Tech, Bang Pa-in, Factoryland, Nava Nakorn, and Bangkadi in Ayutthaya and Pathum Thani. The Ministry of Industry estimated that the flood affected 9,859 factories in eight provinces, with the total value of damages amounting to approximately THB 237 billion as of November 21. The floods have upset supply chains worldwide, and made it difficult or even impossible for many businesses to perform their ordinary contract obligations.

After the flood recedes, a large amount of litigation may ensue over the damages caused directly and indirectly by the flooding and the resulting contract liabilities. A typical defendant may have failed to deliver goods or services to the plaintiff in time because the defendant’s facility was directly affected by the flood, or perhaps because the defendant’s own supply chain was interrupted by the floods that hit its suppliers. Whether or not the defendant’s contract with the plaintiff has a force majeure clause, it may be possible to avoid liability on grounds of force majeure, but the outcome is not a foregone conclusion and will depend on the facts surrounding each situation.

Meaning of Force Majeure

Many commercial contracts contain force majeure clauses that include an itemized list of events that the parties have agreed will constitute force majeure. Oftentimes “floods” or other “acts of God” are included in that list. A typical force majeure clause might read as follows: “A party’s failure to perform any term or condition of this Agreement as a result of conditions beyond its control such as, but not limited to, war, strikes, fires, floods, terrorism, power failures, or damage or destruction of any network facilities or servers, shall not be deemed a breach of this Agreement.” A clause of this nature provides a contractual definition of force majeure, plus a contractual allocation of risk when such an event prevents performance.

It is always preferable to have a clear force majeure clause in a contract, but the general principle of force majeure also applies even when the contract is silent. Under Section 8 of the Civil and Commercial Code (CCC), force majeure is defined as “any event the happening or pernicious result of which could not be prevented even though a person against whom it happened or threatened to happen takes such appropriate care as might be expected from him in his situation and in such condition.” Thereafter, Sections 205 and 219 of the CCC provide that a debtor is relieved from his contractual obligations if performance becomes impossible because a circumstance for which he is not responsible occurs after creation of the obligation.

These provisions (and others scattered throughout the CCC) relieve a party of liability for many breaches of contract if the breach is caused by force majeure, even if the contract does not include a force majeure clause. That said, force majeure is not always a magic wand that will prevent a party’s liability for failure to perform an obligation.

Force majeure necessarily includes two important conditions: (1) the event cannot be prevented; and (2) the use of proper care. To examine whether these conditions existed at the time of breach, the breaching party needs to assemble information, evidence, and witnesses to confirm that he had professionally-appropriate mitigation plans in place before, during, and after the flood arrived. If he can establish that he had appropriate plans in place and that he implemented those plans, he can reasonably argue that the speed and size of the flood could not have been anticipated and was overwhelming even in the face of such measures.

Once a particular flood situation is proven to be force majeure, the breaching party still needs to prove that the flood prevented him for performing the contractual obligation. Inconvenience is probably not an excuse. For example, if flooding prevented a supplier from delivering parts to a manufacturer, the supplier might be forgiven on grounds of force majeure, but it is unlikely the manufacturer will be released from its downstream obligations unless the manufacturer tried without success to obtain the same inputs elsewhere. While the Thailand flooding has affected supply chains worldwide, it is unlikely that all parties in the supply chains will be able to blame the floods in Thailand if there was any reasonable means available to mitigate the disruption.

Thai Court Interpretations Regarding Floods

The Thai courts do not agree that every flood is considered an event of force majeure. In Supreme Court Case 1194/2531, a contractor sued an owner to recover the late fees that the owner withheld due to the contractor’s failure to complete a pipeline project on time. The contractor argued that one delay occurred because heavy rains caused damage to a bridge en route to the construction site, interrupting the delivery of machinery and materials. The contractor argued that another delay occurred when rains made the river level too high to complete construction.

The Court agreed that the bridge incident was an event of force majeure because it could not be reasonably anticipated and prevented. But the Court did not agree that high water level during the rainy season constituted force majeure, because one should anticipate that water levels will rise dramatically during the rainy season. The Court dismissed the contractor’s claim.

In Supreme Court Case 2377/2542, an insurance company sued a warehouse for damages caused to cargo that the insurer’s customer was storing in the warehouse at the Bangkok port. A heavy rain caused flooding at the warehouse and flood damage to the cargo inside. The Court ruled that the flood was not an event of force majeure, because the warehouse was engaged in a professional service and bore a warehouseman’s duty to provide facilities that keep its customers’ cargo in good condition. The defendant should have designed and constructed safeguards against this particular type and magnitude of flooding at its facility, and the Court ordered the warehouse to pay for the flood damage to the cargo.

When contracts do not include a force majeure clause, a party arguing that the recent Thailand flooding is an event of force majeure will bear the burden of proving that he took preventive measures at an appropriate level considering the person’s profession, and in spite of these measures the floods were too sudden and extreme to be prevented. That party will need to establish that it planned and implemented preventive measures before and during the flooding, plus mitigation efforts after the flooding. All of these issues will be considered when determining whether a party is relieved of liability due the recent Thailand floods or other catastrophes that arguably amount to force majeure.

RELATED INSIGHTS​ 

August 18, 2026
The Bank of Thailand (BOT) is seeking public comment on proposed amendments that would significantly expand know-your-customer (KYC) and customer due diligence (CDD) requirements for cash-related transactions at financial institutions (FIs) and specialized financial institutions (SFIs). Released on August 5, 2026, the proposed regulation would supersede BOT Notification No. 16/2569, which focused primarily on cash withdrawal transactions. The public comment period is open through September 3, 2026. The amendments reflect concerns that FIs and SFIs may be used to facilitate the movement, concealment, and conversion of criminal proceeds, potentially damaging institutional operations and public confidence in the financial system. Expanded Scope of Covered Transactions The most significant change is the broadening of the definition of “cash-related transactions.” Previously, the regulation covered only cash withdrawals and uncrossed check withdrawals. The amended regulation extends coverage to include: Cash deposits, check deposits, or receipt of funds from the public not in the form of deposit accounts; Thai baht (THB) banknote exchange (different denominations); Receipt of cash for issuing checks and drafts; and Purchase, sale, or exchange of foreign banknotes. Mandatory Identity Verification and Risk Management For all cash-related transactions, FIs and SFIs must require customers, or authorized or delegated persons, to present identification or verify their identity before every transaction, including one-time (walk-in) transactions. Specific identification requirements vary by transaction type, customer nationality, and channel (branch vs. electronic). FIs and SFIs must also establish comprehensive risk management processes and procedures for cash-related transactions. These requirements include identifying customers or authorized representatives in accordance with transaction-specific verification standards, analyzing customer behavior, implementing risk-management measures proportionate to the customer’s risk profile, and recording abnormal behavior in relevant systems. The BOT also encourages institutions to proactively guide customers toward transaction channels that offer greater traceability than cash. For corporate customers in high-risk business sectors—including foreign
August 18, 2026
Securing a favorable judgment is often only the midpoint of a dispute. For businesses and investors, the more important commercial question is whether that judgment can be converted into actual recovery. In Thailand, this typically requires the judgment creditor to enforce the judgment through the Legal Execution Department by seizing, attaching, auctioning, or otherwise executing against the judgment debtor’s assets. Thailand’s schedule of these enforcement fees was last revised by an amendment to the Civil Procedure Code that took effect in September 2025. The Civil Procedure Code Amendment Act (No. 33) B.E. 2568 (2025) updated the schedule of execution officer fees listed in table 5 of the Civil Procedure Code. While the amendment did not eliminate the costs associated with enforcement, it lowered several key execution officer fees and abolished certain fees that previously applied even where enforcement did not ultimately result in the sale or disposition of assets. The reform is intended to reduce the financial burden associated with judgment enforcement and remove unnecessary obstacles to settlement once enforcement proceedings have commenced. As a result, it has practical implications not only for judgment creditors seeking to maximize recovery, but also for debtors considering settlement after enforcement has begun and for businesses and investors assessing litigation and credit risk in Thailand. Key Changes The amendment introduced several changes to the execution officer fee structure. First, where seized or attached assets are sold by public auction or otherwise disposed of, the execution officer fee has been reduced from 3% to 2% of the sale or disposition proceeds. This fee remains separate from announcement costs and other out-of-pocket expenses incurred during the enforcement process. Second, where seized or attached funds are paid to a judgment creditor, the execution officer fee has been reduced from 2% to 1% of the amount recovered.
August 11, 2026
Cambodia’s Ministry of Justice has launched a new platform on its official website to publish notices of forced sales issued by each municipal and provincial court of first instance. The platform’s stated purpose is to inform the public and facilitate greater participation in forced-sale auctions conducted in connection with court-ordered enforcement proceedings. How the Platform Works The platform publishes forced-sale notices from courts of first instance across Cambodia’s municipalities and provinces and includes a link where the public can view properties currently subject to forced sale. To participate in a forced-sale auction, individuals can download Khmer-language bidding application forms through links provided on the platform. The form typically requires the applicant’s name, sex, year of birth, identity card number and issue date, and address, together with details identifying the immovable property (including its ownership certificate number), the relevant enforcement case number and date, and the reference to the public auction or tender announcement issued by the court. Completed application forms must be submitted directly to the specific municipal or provincial court that issued the forced sale. For further inquiries about a particular forced sale, interested parties should likewise contact the relevant municipal or provincial court. Forced Sale of Immovable Property in Cambodia The publication of these notices relates to the forced sale procedure for immovable property under Cambodia’s Code of Civil Procedure (CPC). Unlike property seizure by a court, a forced sale is a compulsory execution proceeding—a subsequent enforcement step that arises only after an underlying dispute has been adjudicated and a debtor fails to pay the debt or outstanding amount due under a final and binding judgment or other enforceable title of execution. For the purposes of this procedure, the term “immovable property” under the CPC refers to land, registered buildings, jointly held shares of such property, registered
August 6, 2026
Every month, VAT-registered businesses in Thailand calculate their output and input VAT and file a return to pay the net amount due or claim a refund. Yet a common and costly dispute arises when a business that has paid input VAT to its supplier—and done everything asked of it—later finds that input VAT rejected on the grounds that the tax invoice was issued by “a person not entitled to issue tax invoices.” In these cases, a buyer may have confirmed the supplier’s VAT registration on the Revenue Department’s website, paid through the banking system, received a complete tax invoice, and kept full payment and inventory records. Even so, if the Revenue Department later determines that the supplier did not genuinely make the sale or collected the VAT without remitting it, the department can disallow the input VAT and assess additional tax, surcharge, and penalty—often more than a year after the transaction. A new article from tax and dispute resolution specialists at Tilleke & Gibbins in Bangkok examines how the Revenue Department and the courts approach these disputes, including two recent Supreme Court (Tax Division) decisions confirming that the taxpayer bears the burden of proving a supplier genuinely sold and delivered the goods and received payment. It considers why the VAT registration system offers no legal safe harbor, why the evidentiary burden falls hardest on online and cross-border transactions where buyers and sellers never meet, and how the Revenue Department’s own digital infrastructure could detect non-remitting suppliers at the source rather than shifting the loss to good-faith buyers. The article also sets out practical guidance: how to build a comprehensive “know-your-supplier” file at the time of a transaction, the procedural steps and strict deadlines for challenging a VAT assessment, and why dispute readiness belongs alongside tax planning at the center