UCP 600

UCP 600 Article 6: Common Errors and Discrepancies in Availability and Expiry

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

Introduction

Date-related discrepancies are among the most frequent causes of documentary credit refusal. Article 6 defines the expiry date and latest shipment date — the two temporal boundaries that govern every presentation. When practitioners misread these dates, misunderstand their relationship, or fail to track amendment-driven changes, the result is a discrepancy that is entirely preventable.

This guide catalogs the most common date-related errors, explains why each produces a discrepancy, and provides a deterministic method for avoiding them.

Failure Mode Analysis

Failure Mode 1: Presenting After the Expiry Date

The beneficiary presents documents after the expiry date. Under Article 14(c), the presentation is non-complying. The bank is discharged. No exceptions.

Root cause: The beneficiary miscounts days, miscalculates banking days, or does not track the expiry date.

Failure Mode 2: Transport Document Dated After Latest Shipment Date

The bill of lading is dated after the credit's latest shipment date. Under ISBP 745 A14, this is a discrepancy. The shipment date on the transport document must be on or before the latest shipment date.

Root cause: The beneficiary ships late and obtains a bill of lading with the actual (late) shipment date.

Failure Mode 3: Invoice Dated After Expiry Date

The commercial invoice is dated after the expiry date. Under ISBP 745, the invoice date must not be later than the expiry date (unless the credit states otherwise).

Root cause: The beneficiary issues the invoice after the expiry date because the shipment was delayed.

Failure Mode 4: Certificate Dated After Expiry Date

A required certificate (quality, origin, inspection) is dated after the expiry date. Under ISBP 745, certificate dates must be on or before the expiry date unless the credit states otherwise.

Root cause: The certificate is issued after the expiry date because the inspection was delayed.

Failure Mode 5: Confusing Expiry Date with Shipment Date

The beneficiary treats the expiry date as the shipment deadline and ships on the expiry date. The bill of lading is dated the expiry date, but the presentation is not made until after the expiry. The presentation is late.

Root cause: The beneficiary conflates the two dates — the shipment must occur before the expiry, and the presentation must occur on or before the expiry.

Failure Mode 6: Amendment Extends Shipment Date But Not Expiry

The credit is amended to extend the latest shipment date. The expiry date remains unchanged. If the new shipment date is after the original expiry, the credit contains an inconsistency. The beneficiary ships within the new shipment window but presents after the expiry.

Root cause: The amendment creates an internal inconsistency in the credit's dates.

Failure Mode 7: Weekend/Holiday Miscalculation

The expiry date falls on a weekend or holiday. Under Article 29(a), if the expiry date falls on a non-banking day, the expiry date is extended to the first following banking day. The beneficiary miscalculates and presents on the wrong day.

Root cause: The beneficiary does not apply Article 29(a) correctly.

Deterministic Resolution Architecture

  1. Extract the operative dates. From the credit (or latest amendment), extract: (a) the expiry date, (b) the latest shipment date, (c) the availability type.

  2. Verify date consistency. Confirm the latest shipment date is on or before the expiry date. If not, the credit contains an inconsistency — request clarification.

  3. Map document dates against operative dates. For each required document, identify its date. Compare against the expiry date and the latest shipment date as applicable.

  4. Apply ISBP 745 date standards. Under ISBP 745 A14, examine dates on transport documents, invoices, and certificates. Confirm each date is on or before the relevant credit date.

  5. Track amendment-driven date changes. For each amendment, record the original and amended dates. Determine which dates govern based on beneficiary consent.

  6. Apply Article 29(a) for non-banking days. If the expiry date falls on a non-banking day, the expiry extends to the first following banking day. Verify this applies.

  7. Calculate presentation timing. Confirm the presentation date is on or before the operative expiry date (including any Article 29(a) extension).

  8. Compile the date examination record. Record: (a) the operative dates, (b) each document's date, (c) the comparison result, and (d) the final compliance determination.

Conclusion

Date-related discrepancies are deterministic — they arise from a specific document bearing a specific date that fails a specific credit requirement. The resolution is equally deterministic: extract the operative dates, compare document dates against them, and apply ISBP 745 standards. The most common failure modes are preventable with proper date tracking and amendment management.

FAQ

What happens if the expiry date falls on a Saturday?
Under Article 29(a), if the expiry date falls on a non-banking day, the expiry extends to the first following banking day. The beneficiary may present on that day.

Can an invoice be dated after the expiry date?
Under ISBP 745, the invoice date must not be later than the expiry date unless the credit states otherwise. If the credit does not address invoice dates, the invoice must be dated on or before the expiry.

Does the bill of lading date have to match the latest shipment date exactly?
No. The bill of lading date must be on or before the latest shipment date. It can be earlier — the shipment may occur before the deadline.

What if the credit does not state a latest shipment date?
Under Article 6(c), the credit must stipulate a latest shipment date or state that shipment is not later than a specified period before the expiry date. If neither is stated, the credit is non-compliant.

How does Article 29(a) interact with the expiry date?
Article 29(a) extends the expiry date to the first following banking day if the expiry falls on a non-banking day. This is an automatic extension — no amendment required.

Source Notes

Did You Know?

Article 29(a) correctly.

Regulatory Reference Table
RegulationArticle / SectionRequirementConsequence
UCP 600Article 6Availability, Expiry Date and Place for PresentationBinary determination (compliant/discrepant)
UCP 600Article 14Standard for Examination of DocumentsBinary determination (compliant/discrepant)
UCP 600Article 29Extension of Expiry Date or Last Day for PresentationBinary 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
Presenting After the Expiry DateThe beneficiary presents documents after the expiry date. Under Article 14(c), the presentation i...
Transport Document Dated After Latest Shipment DateThe bill of lading is dated after the credit's latest shipment date. Under ISBP 745 A14, this is ...
Invoice Dated After Expiry DateThe commercial invoice is dated after the expiry date. Under ISBP 745, the invoice date must not ...
Certificate Dated After Expiry DateA required certificate (quality, origin, inspection) is dated after the expiry date. Under ISBP 7...
Confusing Expiry Date with Shipment DateThe beneficiary treats the expiry date as the shipment deadline and ships on the expiry date. The...

← 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 UCP 600 Article 6 — 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