Late Presentation Under UCP 600 Article 14(c): Deterministic Failure Modes and Resolution Architecture
Introduction
Late presentation under documentary credits is not a procedural inconvenience — it is a binary failure mode that terminates the beneficiary's right to draw. When documents arrive outside the presentation window defined in UCP 600 sub-article 14(c), the issuing bank faces a single deterministic outcome: refusal. There is no discretion, no waiver mechanism, and no cure. The 21-calendar-day default and the hard expiry-date cap create a dual constraint that, once violated, cannot be undone by subsequent action. This guide isolates the operative rules, mutates the common failure patterns, and compiles a resolution architecture that eliminates ambiguity.
Failure Mode Analysis
Failure Mode 1: Calendar Day Calculation Error
Beneficiaries and nominated banks frequently miscalculate the 21-calendar-day window by conflating "calendar days" with "banking days." UCP 600 sub-article 14(c) specifies calendar days — weekends and public holidays count. A shipment on March 1 requires presentation by March 22, regardless of how many non-banking days fall in between. The error is systemic: banks applying banking-day logic to the presentation window produce false compliance determinations that collapse on issuing-bank examination.
Symptom: Documents presented on the 21st banking day after shipment, which is the 25th or 26th calendar day. The presentation is late. No waiver under Article 16(b) can cure this — the applicant's waiver does not extend the presentation period (Article 16(b) explicitly states "This does not, however, extend the period mentioned in sub-article 14 (b)").
Failure Mode 2: Date-of-Shipment Ambiguity
The 21-day clock starts from "the date of shipment as described in these rules." For bills of lading (Article 20), this is the date of onboard notation if the B/L does not otherwise indicate a shipment date. For airwaybills (Article 23), it is the date of issuance or, if an on-board notation appears, the date of that notation. When the transport document contains multiple dates — issuance date, "received for shipment" date, and on-board date — the wrong date selection truncates or extends the window incorrectly.
Symptom: The beneficiary calculates from the "received for shipment" date rather than the on-board date. The actual window is shorter than believed. Presentation falls outside the valid period. The discrepancy is raised, and the beneficiary has no recourse.
Failure Mode 3: Expiry Date as Hard Cap Misunderstanding
When the credit expires on, say, April 15 and the 21-day window runs to April 20, the beneficiary must present by April 15 — not April 20. Conversely, when the credit expires on May 30 and the 21-day window runs to April 10, the April 10 deadline controls. The harder failure occurs when the beneficiary relies on Article 29's extension provision to cure an expiry-date collision, without recognizing that Article 29 extends only the expiry/presentation date — not the shipment date (Article 29(c)). A late shipment cannot be rescued by bank closure.
Symptom: Beneficiary presents on the first banking day after expiry, relying on Article 29, but the underlying transport document shows a shipment date that already exhausted the 21-day window before expiry. Two independent violations exist: late shipment-date calculation and (potentially) late presentation. Article 29 does not cure either.
Deterministic Resolution Architecture
Step 1: Isolate the Presentation Window at Credit Issuance
Before the credit is issued, the applicant and issuing bank must:
- Determine whether the credit requires original transport documents subject to Articles 19–25. If yes, the 21-day rule is automatically engaged.
- Verify that the credit's expiry date provides sufficient runway. A credit expiring 15 days after expected shipment date will truncate the 21-day window.
- If the applicant intends to relax the 21-day window, include "stale documents acceptable" (ISBP 745 A19(b)) — but recognize this only extends to expiry, not beyond.
Step 2: Decouple Date-of-Shipment Calculation from Transport Document Type
Different transport documents define "date of shipment" differently:
| Transport Document | Date of Shipment |
|---|---|
| Bill of Lading (Art. 20) | On-board date (or issuance date if no on-board notation) |
| Non-Negotiable Sea Waybill (Art. 21) | On-board date (or issuance date if no on-board notation) |
| Airwaybill (Art. 23) | Date of issuance (or on-board date if notation exists) |
| Road/Rail/Inland Waterway (Art. 24) | Date of issuance or notation, as applicable |
| Multimodal Transport Document (Art. 19) | Date of taking in charge or on-board date, as applicable |
| Charter Party B/L (Art. 22) | Date of shipment as stated on the document |
The beneficiary must identify the correct date for the specific document type. Misidentifying this date is a systemic failure that no downstream action can correct.
Step 3: Compile a Presentation-Date Compliance Check
Before presentation, the presenter must verify:
- Identify the date of shipment per the applicable article.
- Add 21 calendar days (not banking days).
- Compare the result against the credit expiry date.
- Take the earlier of the two dates as the hard deadline.
- Verify that the presentation date falls on or before that deadline.
- If the deadline falls on a non-banking day, confirm that Article 29 applies (bank closed for non-force-majeure reasons).
Step 4: Mutate the Process for Stale-Document Credits
When "stale documents acceptable" appears in the credit:
- The 21-day default is overridden (ISBP 745 A19(b)).
- The only remaining constraint is the expiry date.
- If a specific presentation period is also stated (e.g., "documents to be presented within 30 days of shipment"), that period controls — "stale documents acceptable" does not nullify an express period; it only relaxes the default.
Step 5: Isolate Force Majeure from Bank Closure
Article 36 (force majeure) and Article 29 (bank closure) create different regimes:
- Article 29: Bank closed for non-force-majeure reasons → expiry/presentation date extends to next banking day. Shipment date does NOT extend.
- Article 36: Force majeure event → bank is excused from performance. No extension of any date. The beneficiary's obligation to present within the window remains.
Confusing these two provisions is a failure mode that produces erroneous compliance determinations.
Conclusion
Late presentation under UCP 600 Article 14(c) is not a negotiable condition. The 21-calendar-day rule and the expiry-date cap form a binary constraint: either the presentation falls within the window, or it does not. No waiver, no bank closure extension, and no force majeure event can resurrect a violated presentation period. The only contractual relaxation is "stale documents acceptable" under ISBP 745, and even that is bounded by expiry. Every other scenario terminates in refusal. Deterministic compliance requires isolating the correct date of shipment, computing the window in calendar days, and truncating at expiry. The architecture is not complex — but its failure modes are systemic, and each one is terminal.
FAQ
Q1: Does Article 29 extend the 21-day presentation window when the bank is closed on the 21st day?
No. Article 29 extends the expiry date or the last day for presentation — which, under Article 14(c), is the earlier of 21 days after shipment or the credit expiry. If the 21st calendar day falls on a non-banking day, the presentation date extends to the next banking day under Article 29(a). But the 21-day calculation itself is not affected. The window still runs 21 calendar days from shipment; only the deadline for physical presentation shifts if it coincides with a bank closure.
Q2: Can an applicant waive a late presentation under Article 16(b)?
No. Article 16(b) permits the issuing bank to approach the applicant for a waiver of discrepancies, but explicitly states: "This does not, however, extend the period mentioned in sub-article 14 (b)." Late presentation is not a discrepancy that can be waived — it is a failure to make a complying presentation within the required timeframe. The applicant's waiver covers document discrepancies, not temporal violations.
Q3: Does the "stale documents acceptable" condition eliminate the 21-day rule entirely?
Yes, but only the default 21-day rule. Under ISBP 745 A19(b), "stale documents acceptable" means documents may be presented later than 21 calendar days after shipment, provided they arrive before the credit's expiry date. If the credit also states a specific presentation period (e.g., "30 days after shipment"), that express period controls — "stale documents acceptable" relaxes the default, not an express stipulation.
Q4: What happens if the transport document shows two different dates — issuance and on-board?
For bills of lading (Article 20) and non-negotiable sea waybills (Article 21), the on-board date is the date of shipment. If the document contains an on-board notation dated later than issuance, the on-board date governs the 21-day calculation. For airwaybills (Article 23), the date of issuance governs unless an on-board notation appears, in which case the notation date governs. The beneficiary must identify which date is the "date of shipment" for the specific document type.
Q5: Is force majeure under Article 36 an excuse for late presentation?
No. Article 36 excuses the bank from obligations arising from force majeure events (war, civil commotion, natural disaster, etc.). It does not extend any presentation deadlines. If a force majeure event prevents the beneficiary from presenting documents within the 21-day window or before expiry, the beneficiary's right to draw is extinguished. The bank is excused from performing, but the beneficiary is not excused from presenting on time.
article 14(c) specifies calendar days — weekends and public holidays count.
| Regulation | Article / Section | Requirement | Consequence |
|---|---|---|---|
| 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 36 | Force Majeure | Binary determination (compliant/discrepant) |
| UCP 600 | Article 16 | Discrepant Documents, Waiver and Notice | Binary determination (compliant/discrepant) |
| UCP 600 | Article 20 | Bill of Lading | Binary determination (compliant/discrepant) |
| UCP 600 | Article 23 | Air Transport Document | 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 |
|---|---|
| Calendar Day Calculation Error | Beneficiaries and nominated banks frequently miscalculate the 21-calendar-day window by conflatin... |
| Date-of-Shipment Ambiguity | The 21-day clock starts from "the date of shipment as described in these rules." For bills of lad... |
| Expiry Date as Hard Cap Misunderstanding | When the credit expires on, say, April 15 and the 21-day window runs to April 20, the beneficiary... |
← 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