UCP 600 Article 36: Force Majeure vs. Closure — Different Consequences
Introduction
UCP 600 contains two distinct provisions that address situations where a bank is closed or unable to perform: Article 29 (expiry or last day for presentation when the bank is closed) and Article 36 (force majeure interruption). While both provisions deal with bank closures, they apply to fundamentally different situations and produce different consequences. Article 29 applies to ordinary closures — holidays, weekends, and scheduled closures — and provides that the expiry date or last day for presentation is extended to the next banking day. Article 36 applies to extraordinary interruptions beyond the bank's control and provides that credits expired during the interruption are not revived. Confusing these two provisions is the most common error in force-majeure practice. This guide distinguishes the two provisions and maps their different consequences.
Failure Mode Analysis
Failure 1: Applying Article 36 to an ordinary closure. A bank holiday or scheduled closure is an Article 29 event. Applying Article 36 to an ordinary closure will incorrectly suspend examination and may incorrectly refuse a timely presentation.
Failure 2: Applying Article 29 to an extraordinary interruption. A war, strike, or civil commotion that interrupts the bank's business is an Article 36 event. Applying Article 29 to such an event will incorrectly extend the expiry date.
Failure 3: Automatically extending expiry after an Article 36 event. Article 36 expressly states that credits expired during the interruption are not revived. A bank that extends expiry without an amendment from the issuing bank is exceeding its authority.
Failure 4: Failing to classify the closure. The bank does not determine whether the closure was ordinary (Article 29) or extraordinary (Article 36). This creates legal exposure and audit risk.
Failure 5: Applying both provisions simultaneously. The bank applies both Article 29 and Article 36 to the same closure. The provisions are mutually exclusive: a closure is either an Article 29 event or an Article 36 event, not both.
Deterministic Resolution Architecture
-
Classify the closure. Determine whether the closure was ordinary (holiday, weekend, scheduled maintenance) or extraordinary (war, strike, civil commotion, or other cause beyond the bank's control).
-
Apply Article 29 to ordinary closures. If the closure was ordinary, Article 29 applies: the expiry date or last day for presentation is extended to the first following banking day.
-
Apply Article 36 to extraordinary interruptions. If the closure was extraordinary and beyond the bank's control, Article 36 applies: credits expired during the interruption are not revived.
-
Do not apply both provisions simultaneously. A closure is either an Article 29 event or an Article 36 event. Classify and apply the correct provision.
-
Document the classification. Record the type of closure, the provision applied, and the consequences. Preserve the classification with the presentation file.
-
If Article 36 applies, determine the credit's status. Compare the credit expiry date against the interruption period. If the credit expired, Article 36 applies.
-
If Article 29 applies, extend the deadline. Extend the expiry date or last day for presentation to the first following banking day.
Conclusion
Article 29 and Article 36 address different types of closures with different consequences. Article 29 extends deadlines for ordinary closures; Article 36 protects the bank during extraordinary interruptions and rejects automatic revival of expired credits. The defensible method is a documented classification that correctly identifies the type of closure and applies the correct provision. Banks that confuse these two provisions expose themselves to legal challenge and operational risk.
FAQ
What is the difference between Article 29 and Article 36? Article 29 addresses ordinary closures (holidays, weekends, scheduled maintenance) and extends deadlines. Article 36 addresses extraordinary interruptions (war, strikes, civil commotion) and does not extend deadlines.
Can a closure be both an Article 29 and Article 36 event? No. A closure is classified as either ordinary (Article 29) or extraordinary (Article 36). The provisions are mutually exclusive.
Does Article 36 extend the expiry date? No. If the credit expired during the Article 36 interruption, reopening does not require honour or negotiation. The credit expired, and Article 36 does not revive it.
Does Article 29 extend the expiry date? Yes. If the expiry date falls on a day when the bank is closed for ordinary reasons, the expiry date is extended to the first following banking day.
How does eUCP handle both provisions? Under eUCP Version 2.1, Article e8, both Article 29 and Article 36 apply to electronic presentations. The bank must classify the closure and apply the correct provision.
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, "ICC Uniform Rules for Demand Guarantees (URDG 758) — eBook," published 12 Dec 2024.
| 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 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 26 | Transport Document Issued by Freight Forwarders | 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 — 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