Documents

Best Practices: Force Majeure Documentation for Documentary Credits

📅 2026-07-13 6 min read UCP 600 / ISBP 745

Introduction

Force majeure documentation in the documentary credit context requires careful attention to both the timing and content of the evidence presented to banks. While Article 36 of UCP 600 protects banks from the consequences of force majeure events, the party seeking to invoke force majeure — whether beneficiary, applicant, or bank — must substantiate its claim with credible documentation. This guide provides a complementary perspective to the requirements framework, focusing on the practical documentation standards that banks apply when evaluating force majeure claims under documentary credits.

Failure Mode Analysis

Failure 1: Documentation Does Not Establish Causation

A beneficiary provides a government order shutting down ports due to a pandemic. The documentation confirms the port closure but does not establish that the closure directly prevented the beneficiary from shipping within the credit's required period. The bank rejects the claim because the documentation does not demonstrate causation between the event and the specific obligation.

Root cause: The documentation described the event but did not link it to the beneficiary's specific inability to perform.

Failure 2: Documentation Is From an Unreliable Source

A beneficiary presents a news article from a blog as evidence of a force majeure event. The bank requires official documentation: government orders, port authority notices, or certifications from recognised trade bodies. The blog article is insufficient.

Root cause: The beneficiary did not source documentation from credible, independent sources that banks accept as reliable evidence.

Failure 3: Documentation Does Not Address Mitigation

A beneficiary invokes force majeure but provides no evidence of attempts to mitigate the event's impact (e.g., alternative shipping routes, different ports, delayed but still feasible shipment). The bank argues that the beneficiary failed to take reasonable steps to mitigate, weakening the force majeure claim.

Root cause: The documentation did not address the beneficiary's mitigation efforts, creating an impression that the beneficiary did not attempt to overcome the event.

Failure 4: Timing of Documentation Submission Is Late

A beneficiary submits force majeure documentation three months after the event. The bank rejects the submission as untimely under its standard terms and conditions, which require notification within a specified period after the event.

Root cause: The beneficiary did not comply with the bank's documentation submission timeline.

Deterministic Resolution Architecture

Step 1: Review the Bank's Standard Terms and Conditions

Before preparing documentation, review the bank's standard terms and conditions for the force majeure clause. Identify the specific documentation requirements, submission timelines, and notification procedures.

Step 2: Gather Official Event Documentation

Obtain official documentation of the force majeure event from credible sources: (a) government orders or declarations, (b) port authority or shipping line notices, (c) trade body certifications, (d) meteorological or seismological data (for natural disasters), and (e) embassy or consulate confirmations (for overseas events).

Step 3: Prepare a Causation Statement

Draft a sworn statement that establishes the causal link between the force majeure event and the inability to perform the specific obligation under the credit. Include: (a) the timeline of the event, (b) the specific obligation that could not be performed, (c) the direct connection between the event and the inability, and (d) any alternative performance that was attempted or considered.

Step 4: Document Mitigation Efforts

Record all steps taken to mitigate the event's impact: (a) alternative shipping arrangements, (b) alternative ports or routes, (c) communication with the carrier or other parties, (d) attempts to obtain waivers or extensions from the bank or applicant.

Step 5: Compile the Documentation Package

Assemble the complete package: (a) the causation statement, (b) official event documentation, (c) mitigation evidence, (d) supporting correspondence, and (e) a cover letter summarising the claim.

Step 6: Submit Within the Required Timeframe

Submit the documentation to the bank within the timeframe specified in the credit or the bank's standard terms. If no specific timeframe is stated, submit as promptly as possible after the event.

Step 7: Follow Up and Respond to Bank Queries

Monitor the bank's examination of the documentation. Be prepared to provide additional evidence or clarification. Respond to any queries within the timeframe specified by the bank.

Step 8: Maintain a Complete Record

Retain copies of all documentation submitted, all correspondence with the bank, and the bank's response. This record supports any subsequent dispute resolution proceedings.

Conclusion

Force majeure documentation must do more than describe the event — it must establish causation, demonstrate mitigation, and comply with the bank's submission requirements. The resolution architecture above ensures that the documentation package is complete, credible, and timely, meeting the practical standards that banks apply when evaluating force majeure claims.

FAQ

Q1: What is the difference between the force majeure requirements in this guide and the previous guide?
This guide focuses on the practical documentation standards — what evidence to gather, how to establish causation, and how to comply with bank submission timelines. The previous guide addresses the regulatory framework and the overall process for invoking force majeure.

Q2: Can a beneficiary invoke force majeure if the event was foreseeable?
It depends on the definition of force majeure in the credit or the bank's terms. In most cases, foreseeable events that the party could have planned for may not qualify. However, the COVID-19 pandemic demonstrated that even foreseeable events may qualify if their scale and impact were unforeseeable.

Q3: Is a force majeure declaration by the government sufficient documentation?
It depends on the bank's requirements. A government declaration is strong evidence, but the bank may also require evidence of the specific impact on the beneficiary's ability to perform under the credit.

Q4: Does the bank have to accept force majeure documentation?
No. The bank examines the documentation and determines whether it supports the claim. If the documentation is insufficient, the bank may reject the claim.

Q5: Can the applicant invoke force majeure to avoid its reimbursement obligation?
The applicant's reimbursement obligation is separate from the credit transaction. A force majeure event affecting the applicant does not relieve the applicant of its obligation to reimburse the issuing bank, unless the underlying contract contains a force majeure clause that applies to the reimbursement obligation.

Source Notes

Regulatory Reference Table
RegulationArticle / SectionRequirementConsequence
UCP 600Article 36Force MajeureBinary determination (compliant/discrepant)
UCP 600Article 26Transport Document Issued by Freight ForwardersBinary determination (compliant/discrepant)

← Scroll horizontally to see all columns

Quick Reference Summary

  • No reference captured.

Compliance Checklist

0 of 5 completed

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 Compliance Engine

DraftLC generates compliant Best Practices — 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