UCP 600

UCP 600 Article 29: Extension of Dates — Common Errors and Discrepancies

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

Introduction

Date extension errors under Article 29 are among the most frequently occurring discrepancies in documentary credit practice. These errors arise from misunderstandings about what Article 29 extends, when it applies, and how it interacts with other credit provisions. This guide catalogues the most common errors and discrepancies related to Article 29's extension mechanism, providing both the regulatory basis and practical corrective measures.

Failure Mode Analysis

Failure 1: Beneficiary Assumes All Dates Extend

A credit expires on a Saturday. The beneficiary assumes Article 29(a) extends all dates in the credit — expiry, shipment, and insurance. In fact, only the presentation deadline extends. The beneficiary ships on Monday, exceeding the original shipment date.

Root cause: The beneficiary generalized the extension to all credit dates rather than limiting it to the presentation deadline.

Failure 2: Presentation Made After Extended Date

A credit expires on a non-banking day and extends to Monday. The beneficiary presents on Tuesday, believing they have an additional day. Article 29(a) extends to the first following banking day only, not beyond.

Root cause: The beneficiary miscalculated the extended date or believed the extension was for more than one day.

Failure 3: Non-Extension Notice Delivered by Wrong Party

The issuing bank instructs the nominated bank to send the non-extension notice under Article 29(b). However, Article 29(b) requires the notice from the issuing bank or confirming bank, not the nominated bank.

Root cause: The issuing bank delegated the notice obligation to a party not authorized under Article 29(b) to give it.

Failure 4: Auto-Extension Notice States "Credit Will Expire"

The issuing bank sends a notice stating "the credit will expire on [date]" rather than "the bank will not extend the credit." Article 29(b) requires an affirmative statement that the bank will not extend. A neutral statement of expiry does not satisfy this requirement.

Root cause: The issuing bank's notice template used general expiry language rather than the specific non-extension language required by Article 29(b).

Failure 5: Presentation on Extended Date With Dated-After-Shipment Documents

The beneficiary presents on the extended date with transport documents showing shipment on the extended date. While the presentation is timely, the shipment date exceeds the credit's original latest shipment date.

Root cause: The beneficiary treated the extended presentation deadline as authority for late shipment.

Failure 6: Beneficiary Relies on Auto-Extension After Amendment Removes It

A credit originally contained an auto-extension clause. The issuing bank amends the credit to remove the clause. The beneficiary is unaware of the amendment and believes the credit will still auto-extend.

Root cause: The beneficiary did not track amendments to the credit and continued to rely on a provision that was removed.

Deterministic Resolution Architecture

Step 1: Identify the Specific Extension Provision

Determine whether Article 29(a) (non-banking day extension) or Article 29(b) (auto-extension clause) applies to the credit. Each has different requirements and scope.

Step 2: Verify the Extension Is Applicable

For Article 29(a): confirm the bank was closed on the expiry date and the closure was not due to force majeure. For Article 29(b): confirm the credit contains an auto-extension clause and no timely non-extension notice was given.

Step 3: Determine the Extended Date

For Article 29(a): the first following banking day. For Article 29(b): the end of the stated extension period.

Step 4: Confirm Which Dates Are Affected

Article 29(a) extends the expiry date and presentation deadline only. It does not extend the shipment date, insurance date, or other credit dates. Article 29(b) extends the expiry date for the stated period.

Step 5: Verify Non-Extension Notice Compliance

For Article 29(b): verify that any non-extension notice was (a) given by the issuing bank or confirming bank, (b) provided before the expiry date, and (c) stated that the bank will not extend the credit.

Step 6: Assess Presentation Timing

Verify the presentation was made on or before the extended date. Presentations after the extended date are late.

Step 7: Document the Extension Analysis

Record the extension analysis, the extended date, and the impact on the credit's terms. Note any discrepancies identified.

Step 8: Prepare the Discrepancy Notice

If discrepancies exist, cite the specific Article 29 provision and the deficiency. Provide corrective guidance.

Conclusion

Date extension errors under Article 29 are predictable and preventable. The most common failures involve extending dates beyond Article 29's scope, miscalculating the extended date, and failing to comply with non-extension notice requirements. A systematic approach to extension analysis prevents these errors.

FAQ

Q1: Can the beneficiary request a further extension beyond Article 29(a)?
The beneficiary can request an amendment under Article 10 to extend the credit further. Article 29(a) provides only one automatic extension to the first following banking day.

Q2: What if the issuing bank closes for a public holiday that falls on the extended date?
If the extended date (the first following banking day) is also a non-banking day, Article 29(a) would extend again to the next banking day. However, this scenario is unusual because the extended date should be a day the bank is open.

Q3: Does the non-extension notice need to be in writing?
Article 29(b) does not specify a form for the notice. However, a written notice (SWIFT message, letter, or other documentary form) provides the best evidence of compliance.

Q4: Can the beneficiary waive the non-extension notice?
The beneficiary can reject the non-extension notice by treating the credit as extended. However, Article 29(b) is designed to give the bank the right to prevent extension, and the beneficiary's waiver may not override this right.

Q5: What if the non-extension notice is sent by fax but not received?
Under Article 29(b), the notice must be "provided" to the beneficiary. If the notice was sent but not received due to a communication failure, the bank may argue it provided the notice. The beneficiary may argue non-receipt. This dispute is fact-specific.

Source Notes

Did You Know?

Article 29(b) provides for automatic extension of credits with auto-extension clauses, subject to the non-extension notice requirement.

Regulatory Reference Table
RegulationArticle / SectionRequirementConsequence
UCP 600Article 29Extension of Expiry Date or Last Day for PresentationBinary determination (compliant/discrepant)
UCP 600Article 14Standard for Examination of DocumentsBinary determination (compliant/discrepant)
UCP 600Article 10AmendmentsBinary 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 UCP 600 Article 29 — 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