UCP 600 Article 36: Bank Not Liable for Events Beyond Its Control
Introduction
Force majeure — events beyond a party's control — can disrupt the documentary credit process at any stage. Article 36 of UCP 600 provides that a bank is not liable or responsible for the consequences of interruption of its business by force majeure events such as acts of God, riots, civil commotion, insurrections, wars, strikes, or lock-outs, or for any other causes beyond its control. This guide examines the scope of this protection, the failure modes that arise when force majeure events affect the documentary credit lifecycle, and the resolution architecture that enables parties to respond effectively.
Failure Mode Analysis
Failure Mode 1: Bank Closed Due to Civil Unrest, Expiry Date Not Extended
The issuing bank is closed for several days due to civil unrest. The beneficiary's presentation, which was made on the last day the bank was open, is now affected. Under Article 36, the bank is not liable for the interruption. Article 29 does not extend the expiry date because the closure is due to force majeure, not a routine holiday.
Failure Mode 2: War or Sanctions Prevent Document Transmission
A war or sanctions regime prevents the nominated bank from transmitting documents to the issuing bank. Article 36 relieves the bank of responsibility for the delay. The beneficiary must assess whether the documents can be transmitted through alternative channels.
Failure Mode 3: Natural Disaster Destroys the Bank's Records
A flood or earthquake destroys the issuing bank's records, including documents received under a credit. Article 36 relieves the bank of responsibility. The beneficiary must re-present documents and the bank must reconstruct its records.
Failure Mode 4: Strike at the Courier Company Prevents Delivery
A strike at the courier company prevents documents from being delivered to the issuing bank. Article 36 may apply if the strike is beyond the bank's control. The presenter must find alternative means of delivery.
Deterministic Resolution Architecture
Resolution 1: Monitor the Bank's Operational Status
During force majeure events, monitor the affected bank's operational status. If the bank is closed or operating on limited capacity, adjust presentation plans accordingly.
Resolution 2: Maintain Alternative Transmission Channels
Identify alternative courier services, electronic submission channels, or banking relationships that can be used if the primary channel is disrupted. Redundancy in transmission options reduces the impact of force majeure.
Resolution 3: Understand the Difference Between Article 29 and Article 36
Article 29 extends the expiry date when the bank is closed for non-force-majeure reasons. Article 36 applies when the closure is due to force majeure. The two articles have different consequences. Force majeure closures do not trigger the Article 29 extension.
Resolution 4: Re-Create and Re-Present After the Event
If documents are destroyed or lost due to force majeure, the beneficiary must re-create and re-present them. The credit's terms and expiry date must be considered in the context of the force majeure event.
Resolution 5: Document the Force Majeure Event
Maintain records of the force majeure event (news reports, government notices, bank communications) to support any future claims or disputes.
Resolution 6: Contact the Issuing Bank for Guidance
During a force majeure event, contact the issuing bank (if operational) to discuss the impact on the credit and any steps that can be taken to preserve the beneficiary's rights.
Resolution 7: Consider the ICC Force Majeure Clause for Future Credits
For future transactions, consider incorporating the ICC Force Majeure Clause or similar provisions into the credit to address force majeure events explicitly.
Conclusion
Article 36 of UCP 600 provides banks with essential protection against liability for force majeure events. The rule recognises that banks, like all parties, are subject to events beyond their control. The resolution architecture above — monitoring, redundancy, clear understanding of Article 29 versus Article 36, and proactive communication — enables parties to navigate force majeure events while preserving their rights to the greatest extent possible.
Frequently Asked Questions
Q1: What qualifies as a force majeure event under Article 36?
Article 36 lists acts of God, riots, civil commotion, insurrections, wars, acts of terrorism, strikes, lock-outs, and any other causes beyond the bank's control. The list is illustrative, not exhaustive.
Q2: If the bank is closed due to force majeure, does Article 29 extend the expiry date?
No. Article 29 expressly applies to closures for reasons other than force majeure. Force majeure closures are governed by Article 36, which does not provide for an automatic expiry-date extension.
Q3: Can the beneficiary claim against the bank for losses caused by force majeure?
No. Article 36 relieves the bank of liability. The beneficiary's recourse is through insurance, the underlying contract, or other legal avenues independent of the credit.
Q4: Does force majeure affect the bank's obligation to reimburse?
If the issuing bank is unable to reimburse due to force majeure, Article 36 protects it. The nominated bank's recourse is against the applicant or through other contractual arrangements.
Q5: How does Article 36 interact with eUCP electronic records?
Article 36 covers interruptions to the bank's business, including those affecting electronic systems. If a force majeure event disrupts the bank's electronic infrastructure, the bank is not liable for the consequences.
Source Notes
Context Only: The following source titles informed the development of this guide. No text was copied from these sources. All regulatory citations reference published ICC rules.
- ICC Academy — Certified UCP 600 Specialist (CUCP)
- ICC Academy — ICC Uniform Rules for Demand Guarantees (URDG 758) - eBook
- ICC — Commentary on UCP 600
- ICC Academy — International Standard Demand Guarantee Practice (ISDGP) for URDG 758
- ICC — ICC Guide to Incoterms® 2020
five-day examination period is counted from the day of presentation.
| Regulation | Article / Section | Requirement | Consequence |
|---|---|---|---|
| UCP 600 | Article 36 | Force Majeure | Binary determination (compliant/discrepant) |
| UCP 600 | Article 29 | Extension of Expiry Date or Last Day for Presentation | Binary determination (compliant/discrepant) |
| UCP 600 | Article 34 | Disclaimers on Documents | Binary determination (compliant/discrepant) |
| UCP 600 | Article 16 | Discrepant Documents, Waiver and Notice | Binary determination (compliant/discrepant) |
← Scroll horizontally to see all columns
Quick Reference Summary
- No reference captured.
Compliance Checklist
| ✓ What Banks Expect | ✗ What Beneficiaries Often Do Wrong |
|---|---|
| Bank Closed Due to Civil Unrest, Expiry Date Not Extended | The issuing bank is closed for several days due to civil unrest. The beneficiary's presentation, ... |
| War or Sanctions Prevent Document Transmission | A war or sanctions regime prevents the nominated bank from transmitting documents to the issuing ... |
| Natural Disaster Destroys the Bank's Records | A flood or earthquake destroys the issuing bank's records, including documents received under a c... |
| Strike at the Courier Company Prevents Delivery | A strike at the courier company prevents documents from being delivered to the issuing bank. Arti... |
← Scroll horizontally to see all columns
Get the Full LC Compliance Checklist
15-point pre-submission checklist covering UCP 600, ISBP 745, and SWIFT MT700 fields. Free PDF download.
No spam. Unsubscribe anytime.
DraftLC generates compliant UCP 600 Article 36 — so you never face this failure mode.
DraftLC drafts your LC with UCP 600-compliant terms and flags conflicts during drafting — before documents reach the bank.
No credit card required · See how DraftLC drafts compliant credits