UCP 600 Article 36 (Force Majeure): Key Definitions and Scope
Introduction
UCP 600 Article 36 uses specific language to define the scope of force majeure protection for banks. The key terms — "Acts of God," "riots," "civil commotions," "insurrections," "wars," "terrorism," "strikes," "lockouts," and "other causes beyond its control" — each carry particular meaning in trade finance and commercial law. Understanding these definitions is essential for correctly applying Article 36, because the article's protection extends only to events that fall within its defined scope. This guide maps each defined term, analyzes the catch-all "other causes beyond its control" category, and identifies where the scope intersects with other UCP provisions.
Failure Mode Analysis
Failure 1: Interpreting "other causes beyond its control" too broadly. The catch-all category is not unlimited. The event must be extraordinary, beyond the bank's control, and must have actually interrupted the bank's business. A routine system outage caused by the bank's own negligence does not qualify.
Failure 2: Applying Article 36 to events that merely affect the beneficiary. Article 36 addresses interruptions to the bank's business, not events that affect the beneficiary or the underlying transaction. A port strike that prevents shipment does not trigger Article 36 unless it also interrupts the bank's operations.
Failure 3: Conflating Article 36 with contractual force majeure. Article 36 is a banking rule, not a commercial-law force-majeure clause. The definition of force majeure under Article 36 is narrower than many contractual definitions.
Failure 4: Failing to distinguish Article 36 from Article 34. Article 34 addresses transmission and translation; Article 36 addresses business interruption. They are distinct provisions with different scopes.
Failure 5: Treating every interruption as Article 36. The bank must verify that the event meets all three elements: it is within the enumerated list (or the catch-all), it was beyond the bank's control, and it actually interrupted operations.
Deterministic Resolution Architecture
-
Identify the enumerated events. The Article 36 list includes: Acts of God, riots, civil commotions, insurrections, wars, terrorism, strikes, lockouts.
-
Test the catch-all category. For events not expressly listed, determine whether the event was (a) beyond the bank's control, (b) extraordinary, and (c) actually interrupted the bank's business.
-
Verify the bank was actually interrupted. Article 36 applies only when the event prevented the bank from performing. A threat or general disruption that does not prevent operations does not trigger Article 36.
-
Distinguish from Article 29. Scheduled closures are Article 29 events. Only extraordinary interruptions qualify under Article 36.
-
Distinguish from Article 34. Transmission and translation issues are Article 34; business interruption is Article 36. Apply the correct provision.
-
Document the scope analysis. Record which provision applies, what the bank examined, and what the Article 36 scope covers. Preserve the analysis with the presentation file.
-
Preserve the event record. Maintain a documented record of the event classification and scope analysis for audit and legal purposes.
Conclusion
The scope of Article 36 is defined by its enumerated events and the catch-all "other causes beyond its control" category. The article addresses interruptions to the bank's business, not events that affect the beneficiary or the underlying transaction. The defensible method is a documented scope analysis that tests each element: event classification, bank control, and actual interruption. Banks that over-extend the Article 36 scope expose themselves to legal challenge.
FAQ
Does Article 36 cover events that only affect the beneficiary? No. Article 36 addresses interruptions to the bank's business. Events that affect the beneficiary but do not interrupt the bank's operations are not covered by Article 36.
Is "other causes beyond its control" unlimited? No. The event must be extraordinary, beyond the bank's control, and must have actually interrupted the bank's business. Routine system outages caused by the bank's own negligence do not qualify.
How does Article 36 differ from a contractual force-majeure clause? Article 36 is a banking rule with a specific enumerated list. Contractual force-majeure clauses may have broader or narrower definitions depending on the contract.
Does Article 36 apply to electronic presentations? Yes. Under eUCP Version 2.1, Article e8, the same Article 36 definitions and scope apply to electronic presentations.
How does URDG 758 define force majeure scope? URDG 758, Article 26, uses a similar enumerated list and catch-all. The scope parallels UCP 600 Article 36 but operates within the demand-guarantee context.
Source Notes
Context only — no deep source text was extracted from the original research feeds.
- ICC Academy, "Uniform Rules for Documentary Credits (UCP 600) — eBook," published 12 Dec 2024.
- ICC, "UCP 600 — Uniform Rules and Practice for Documentary Credits — Including eUCP Version 2.1," published 31 Jul 2023.
- ICC, "Commentary on UCP 600," published 01 Aug 2019.
- ICC Academy, "Certified UCP 600 Specialist (CUCP)," published 12 Jul 2025.
- ICC Academy, "UCP 600 and ISP98: Key differences and applications," published 14 Oct 2025.
| Regulation | Article / Section | Requirement | Consequence |
|---|---|---|---|
| UCP 600 | Article 36 | Force Majeure | Binary determination (compliant/discrepant) |
| UCP 600 | Article 2 | Definitions | Binary determination (compliant/discrepant) |
| UCP 600 | Article 6 | Availability, Expiry Date and Place for Presentation | Binary determination (compliant/discrepant) |
| UCP 600 | Article 14 | Standard for Examination of Documents | 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) |
← Scroll horizontally to see all columns
Quick Reference Summary
- No reference captured.
Compliance Checklist
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 (Force Majeure) — 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