Late Presentation Under UCP 600 Article 14(c): The 21-Day Trap and How to Escape It
Introduction
The letter of credit industry operates under a pervasive illusion: that once goods ship and documents are prepared, the beneficiary has ample time to present. This illusion collapses into a binary failure mode when the 21-calendar-day presentation window closes. Late presentation is not a discrepancy that can be waived—it is a structural violation that decouples the beneficiary from the issuing bank's undertaking entirely. The issuing bank's obligation to honour evaporates, the confirming bank's undertaking dissolves, and the beneficiary is left with recourse only to the underlying contract, which UCP 600 article 4 explicitly isolates from the credit.
This guide compiles the deterministic rules governing presentation timing, isolates the three primary failure modes that truncate beneficiary rights, and provides a numbered resolution architecture that eliminates ambiguity in practice.
Failure Mode Analysis
Failure Mode 1: The Calendar Drift Mutation
The most common failure mode occurs when the beneficiary calculates the 21-day window from the bill of lading issuance date rather than the date of shipment. Under UCP 600 article 20(a)(ii), the date of shipment is the on board date if a separate on board notation exists—not the issuance date. When the on board date precedes the issuance date by several days, the beneficiary's internal calendar drifts forward, consuming days that do not exist. The presentation arrives on day 22 or 23, and the bank's refusal is mechanically inevitable.
Failure Mode 2: The Expiry Date Collision
This failure mode isolates presentations where the 21-day window has not yet closed, but the expiry date intervenes. A credit with a short validity period—common in volatile commodity trades—creates a collision between the shipment date and the expiry date. The beneficiary ships on day 1, the 21-day window extends to day 22, but the credit expires on day 15. The presentation on day 14 is timely under article 14(c) but violates article 6(e). The bank refuses. The beneficiary's counsel argues the 21-day rule should govern. The bank's position is deterministic: the expiry date is absolute.
Failure Mode 3: The Force Majeure Expiration
This failure mode is rare but catastrophic. A bank closes due to force majeure—war, pandemic lockdown, civil commotion—and the credit expires during the closure. Under normal circumstances, article 29(a) would extend the expiry date to the first following banking day. But article 36 explicitly carves out force majeure from article 29's extension mechanism. The credit expires during the closure. No extension applies. The beneficiary's documents, already prepared and waiting for presentation, become worthless under the credit.
Deterministic Resolution Architecture
1. Calendar Anchoring Protocol. Isolate the date of shipment from the transport document. For bills of lading subject to UCP 600 article 20, the date of shipment is the on board date if a separate dated on board notation exists (ISBP 745 paragraph E6(a)). If no separate notation exists, the issuance date governs. Anchor the 21-day count to this date, not to the date the document was physically received by the beneficiary.
2. Dual-Constraint Mapping. Before counting forward from the shipment date, compile both constraints: the 21-day window AND the expiry date. Plot both on a timeline. The earlier of the two truncation points is the operative deadline. If the expiry date falls before day 22, the expiry date governs—regardless of the 21-day calculation.
3. Stale Document Clause Insertion. When structuring credits for trades where document preparation inherently exceeds 21 days, insert "stale documents acceptable" in the credit. Under ISBP 745 paragraph A19(b), this eliminates the 21-day constraint while preserving the expiry date as the sole boundary. This is the only sanctioned mechanism for extending the presentation window beyond 21 days.
4. Article 29 Monitoring. Track the banking calendar of the presentation bank. If the last day for presentation falls on a non-banking day, article 29(a) automatically extends the deadline to the first following banking day. Document this on the covering schedule per article 29(b): "Presentation made within the time limits extended in accordance with sub-article 29(a)."
5. Force Majeure Contingency. For credits in jurisdictions with elevated force majeure risk, consider requiring presentation to a confirming bank or a nominated bank in a stable jurisdiction. If the issuing bank closes due to force majeure and the credit expires during closure, the beneficiary's recourse shifts to the underlying contract—outside UCP 600's framework entirely.
6. Document-Type Scope Verification. Verify whether the presentation includes original transport documents subject to UCP 600 articles 19-25. If the presentation consists solely of documents outside this scope—delivery notes, cargo receipts, forwarder's certificates—the 21-day default does not apply (ISBP 745 paragraph A18(b)(ii)). Presentation may occur at any time before expiry.
7. Copy vs. Original Isolation. Copies of transport documents subject to articles 19-25 are not subject to the 21-day default (ISBP 745 paragraph A6(c)). When a credit requires both originals and copies, the copies may be presented independently of the 21-day constraint, provided the credit does not explicitly establish a separate presentation period for copies.
Conclusion
Late presentation under UCP 600 article 14(c) is not a matter of interpretation—it is a deterministic system with binary outcomes. The 21-day window and the expiry date operate as independent constraints that truncate simultaneously. The only sanctioned escape mechanisms are the "stale documents acceptable" clause, the article 29 bank-closure extension (excluding force majeure), and the structural exclusion of non-transport documents from the 21-day scope. Every other scenario produces a mechanical refusal. Trade finance practitioners who treat presentation timing as flexible are compiling failure into their transaction architecture by design.
FAQ
Q1: Does the 21-day presentation period count from the bill of lading issuance date or the on board date?
A: Under UCP 600 article 20(a)(ii), if the bill of lading contains a separate dated on board notation, the date in that notation is deemed to be the date of shipment and governs the 21-day count. If no separate on board notation exists, the issuance date is deemed to be the date of shipment (ISBP 745 paragraph E6(a)). The beneficiary must identify which date applies before calculating the presentation window.
Q2: Can the issuing bank waive a late presentation discrepancy?
A: Under UCP 600 article 16(b), the issuing bank may approach the applicant for a waiver of discrepancies, but this does not extend the period mentioned in sub-article 14(b)—the five banking days for examination. More critically, a late presentation is not merely a discrepancy that can be waived through the article 16 mechanism. The beneficiary's right to compel honour depends on a complying presentation having been made within the prescribed time limits. Late presentation mutates the transaction from a credit claim to an underlying contract claim.
Q3: What happens if the expiry date falls on a weekend and the 21-day window has not yet closed?
A: Under UCP 600 article 29(a), if the expiry date falls on a day when the bank is closed, the expiry date extends to the first following banking day—provided the closure is not due to force majeure (article 36). The presentation must still satisfy both constraints: within 21 days of shipment AND on or before the extended expiry date.
Q4: Is there any scenario where force majeure extends the presentation deadline?
A: No. UCP 600 article 36 explicitly states that a bank will not honour or negotiate under a credit that expired during a force majeure interruption. The article 29(a) extension mechanism does not apply to force majeure closures. The credit expires during the interruption, and the beneficiary's recourse shifts to the underlying sale contract outside the UCP framework.
Q5: Does "stale documents acceptable" eliminate the expiry date constraint?
A: No. Under ISBP 745 paragraph A19(b), "stale documents acceptable" eliminates the 21-day presentation period constraint but the documents must still be presented no later than the expiry date of the credit. The expiry date remains the absolute boundary regardless of the stale documents clause.
article 14(c) but violates article 6(e).
| Regulation | Article / Section | Requirement | Consequence |
|---|---|---|---|
| UCP 600 | Article 14 | Standard for Examination of Documents | Binary determination (compliant/discrepant) |
| UCP 600 | Article 4 | Credits v. Contracts | Binary determination (compliant/discrepant) |
| UCP 600 | Article 6 | Availability, Expiry Date and Place for Presentation | Binary determination (compliant/discrepant) |
| UCP 600 | Article 29 | Extension of Expiry Date or Last Day for Presentation | Binary determination (compliant/discrepant) |
| UCP 600 | Article 36 | Force Majeure | Binary determination (compliant/discrepant) |
| UCP 600 | Article 20 | Bill of Lading | 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 |
|---|---|
| The Calendar Drift Mutation | The most common failure mode occurs when the beneficiary calculates the 21-day window from the bi... |
| The Expiry Date Collision | This failure mode isolates presentations where the 21-day window has not yet closed, but the expi... |
| The Force Majeure Expiration | This failure mode is rare but catastrophic. A bank closes due to force majeure—war, pandemic lock... |
← 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 Late Presentation Under UCP 600 Article 14(c) — 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