UCP 600

Late Presentation Under UCP 600 Article 14(c): The 21-Day Default Trap and How to Survive It

📅 2026-07-15 10 min read UCP 600 / ISBP 745

Introduction

Most trade finance practitioners treat the 21-day presentation window as a simple countdown — ship the goods, count three weeks, file the documents. This assumption is a systemic failure waiting to mutate into a discrepancy notice. The reality is that UCP 600 sub-article 14(c) creates a binary compliance boundary: either the presentation arrives within the mandated period and before the credit expiry, or it does not. There is no intermediate state, no grace period, no negotiation. When this rule is violated, the entire payment mechanism decouples from the beneficiary's control, and the issuing bank's obligation to honour evaporates under Article 16. This guide isolates the exact regulatory mechanics, identifies three named failure modes that produce late presentations, and compiles a deterministic resolution architecture to prevent and remediate them.

Failure Mode Analysis

Failure Mode 1: The Shipment-Date Miscalculation

The 21-calendar-day window starts from the "date of shipment as described in these rules." Under UCP 600, the date of shipment is determined by the transport article applicable to the document presented:

The failure occurs when the beneficiary uses the wrong date as the starting point. A common mutation: the carrier stamps an on-board date later than the bill of lading issuance date. The beneficiary counts 21 days from issuance, when the on-board date is the operative date. This produces a presentation that is one or more days late — a binary failure with no remedy.

Root cause: Confusing the document issuance date with the shipment date. Under ISBP 745 paragraph A13, "a document indicating a date of issuance and a later date of signing is deemed to have been issued and signed on that later date." The signing date controls.

Failure Mode 2: The Expiry-Date Collision

A presentation can be timely under the 21-day window yet still violate the expiry date. Consider: a credit expires on 15 June. Shipment occurs on 1 June. The 21-day window runs through 22 June. But the credit expires on 15 June, which is earlier. The beneficiary has only 14 days, not 21.

This failure mode is particularly insidious because the beneficiary may believe they have ample time. The credit's expiry date is an independent constraint that truncates the 21-day window. ISBP 745 paragraph A14(b)(ii) clarifies that "presentation to be made within credit validity (or credit expiry)" where the expiry date is 14 May means 14 May is the absolute last day.

Root cause: Failure to compare the 21-day window end date against the credit expiry date and use whichever is earlier.

Failure Mode 3: The Document-Type Misclassification

The 21-calendar-day default under sub-article 14(c) applies only to original transport documents subject to UCP 600 articles 19–25. If the credit requires only non-transport documents (commercial invoices, certificates of origin, inspection certificates), the 21-day rule does not apply. Conversely, if the credit requires an original transport document and the beneficiary omits it from the presentation, the 21-day rule still applies to the overall presentation if it includes transport documents.

ISBP 745 paragraph A6(c) makes explicit that copies of transport documents are excluded from the 21-day calculation. Paragraph A18(b)(ii) confirms that the default period applies only to original transport documents under articles 19–25.

The failure occurs in two directions:

  1. Over-compliance: The beneficiary applies the 21-day rule to presentations that do not include original transport documents, truncating their own available time unnecessarily.
  2. Under-compliance: The beneficiary assumes the 21-day rule does not apply because the credit "doesn't really require" transport documents, when in fact the credit does require an original transport document, triggering the 21-day constraint.

Root cause: Incorrect classification of whether the presentation includes original transport documents subject to articles 19–25.

Deterministic Resolution Architecture

1. Pre-Shipment: Isolate the Expiry-Date Constraint

Before shipment occurs, calculate two dates and compare:

The effective presentation deadline is the earlier of Date A and Date B. Document this in the beneficiary's internal compliance checklist. If Date B is earlier, the beneficiary must truncate their logistics timeline to ensure documents are compiled and presented before the expiry date, not the 21-day window end.

2. Shipment: Compile the Operative Date

At the moment of shipment, compile the operative shipment date from the transport document. Specifically:

Record this date immediately. Do not rely on the commercial invoice date, the packing list date, or any other non-transport document date.

3. Calculate the Presentation Window

Using the operative shipment date, calculate:

Add a buffer of at least 3 business days to account for document compilation, bank processing, courier transit, and time zone differentials. The calculation is deterministic: there is no ambiguity in the arithmetic, only in the inputs.

4. Monitor for Article 29 Extension Eligibility

If the effective deadline falls on a non-banking day at the nominated bank or issuing bank, sub-article 29(a) extends the presentation date to the first following banking day. However:

5. Pre-Validate: Apply the Article 14(c) Compliance Check

Before dispatching documents, apply a binary compliance check:

This check must be repeated for every presentation. No exceptions, no assumptions.

6. If Late: Invoke Article 16 Protocol

If a presentation is determined to be late (violating the 21-day window or the expiry date), the issuing bank must follow the Article 16 refusal protocol:

Failure to issue this notice within the five-day window precludes the bank from claiming non-compliance (Article 16(f)). The beneficiary should monitor this deadline as aggressively as the bank monitors the presentation deadline.

Conclusion

Late presentation under UCP 600 sub-article 14(c) is a binary failure mode: the presentation either satisfies both the 21-calendar-day window and the expiry date, or it does not. There is no partial compliance, no equitable extension, no retroactive waiver. The regulatory framework is deterministic — the operative date is defined by the transport article, the window is fixed by arithmetic, and the expiry date is an absolute ceiling. Practitioners who treat these constraints as advisory rather than mandatory will eventually trigger a refusal under Article 16 that cannot be undone. The resolution architecture presented here compiles the procedural steps to prevent this failure: isolate the expiry constraint, compile the operative date, calculate with buffers, monitor extension eligibility, pre-validate with the compliance check, and know the Article 16 protocol when prevention fails.

FAQ

Q1: Does the 21-calendar-day presentation period include weekends and public holidays?

A: Yes. Sub-article 14(c) specifies "21 calendar days," not "21 banking days." Every day — weekends, public holidays, bank closures — counts toward the 21-day window. The distinction between calendar days and banking days is deliberate. Compare with sub-article 14(b), which specifies "five banking days" for examination — a different unit of measure for a different obligation.

Q2: If a credit contains the phrase "stale documents acceptable," does the 21-day rule still apply?

A: No. ISBP 745 paragraph A19(b) states: "'stale documents acceptable' – documents may be presented later than 21 calendar days after the date of shipment as long as they are presented no later than the expiry date of the credit." The 21-day constraint is nullified, but the expiry date constraint remains. This also applies when the credit specifies a presentation period together with the "stale documents acceptable" condition.

Q3: What happens if the nominated bank is closed on the 21-day window end or the expiry date?

A: Sub-article 29(a) extends the deadline to the first following banking day, provided the bank is closed for reasons other than force majeure (Article 36). The beneficiary must note on the covering schedule that the presentation was made within the extended time limits (Article 29(b)). However, sub-article 29(c) confirms that the latest date for shipment is never extended.

Q4: Does the 21-day rule apply to copies of transport documents?

A: No. ISBP 745 paragraph A6(c) explicitly states: "Copies of transport documents covered by UCP 600 articles 19–25 are not subject to the default presentation period of 21 calendar days stated in UCP 600 sub-article 14(c)." The 21-day default applies exclusively to original transport documents.

Q5: If a bank fails to issue a refusal notice under Article 16 within five banking days, can it later claim the presentation was late?

A: No. Sub-article 16(f) states: "If an issuing bank or a confirming bank fails to act in accordance with the provisions of this article, it shall be precluded from claiming that the documents do not constitute a complying presentation." Late presentation is a discrepancy, and the Article 16 refusal protocol applies to all discrepancies. Failure to issue a timely refusal notice extinguishes the bank's right to refuse on any ground, including lateness.

Did You Know?

article 14(c) specifies "21 calendar days," not "21 banking days.

Regulatory Reference Table
RegulationArticle / SectionRequirementConsequence
UCP 600Article 14Standard for Examination of DocumentsBinary determination (compliant/discrepant)
UCP 600Article 16Discrepant Documents, Waiver and NoticeBinary determination (compliant/discrepant)
UCP 600Article 29Extension of Expiry Date or Last Day for PresentationBinary determination (compliant/discrepant)
UCP 600Article 36Force MajeureBinary determination (compliant/discrepant)
UCP 600Article 20Bill of LadingBinary determination (compliant/discrepant)
UCP 600Article 21Non-Negotiable Sea WaybillBinary determination (compliant/discrepant)

← Scroll horizontally to see all columns

Quick Reference Summary

  • No reference captured.

Compliance Checklist

0 of 7 completed
Bank Expectations vs Common Beneficiary Mistakes
✓ What Banks Expect✗ What Beneficiaries Often Do Wrong
The Shipment-Date MiscalculationThe 21-calendar-day window starts from the "date of shipment as described in these rules." Under ...
The Expiry-Date CollisionA presentation can be timely under the 21-day window yet still violate the expiry date. Consider:...
The Document-Type MisclassificationThe 21-calendar-day default under sub-article 14(c) applies **only** to original transport docume...

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

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