UCP 600

UCP 600 Article 29: Extension of Dates — Complete Interpretation Guide

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

Introduction

This guide provides a consolidated interpretation of all date extension provisions in UCP 600 Article 29, covering both the automatic extension for non-banking days (Article 29(a)) and the auto-extension clause mechanism (Article 29(b)). It synthesizes the regulatory framework, examines each provision's scope and limitations, and provides a unified resolution architecture for date extension issues.

Failure Mode Analysis

Failure 1: Confusing Article 29(a) and 29(b)

A credit expires on a non-banking day (triggering Article 29(a)) and also contains an auto-extension clause (triggering Article 29(b)). The beneficiary is unsure which provision governs. Both may apply simultaneously — Article 29(a) extends the expiry to the next banking day, and the auto-extension clause provides additional extension beyond that.

Root cause: The beneficiary did not analyze each provision independently.

Failure 2: Issuing Bank Fails to Track Auto-Extension Credits

An issuing bank has multiple credits with auto-extension clauses. The bank fails to monitor the expiry dates and does not send non-extension notices before the deadlines. Under Article 29(b), the credits extend automatically.

Root cause: The issuing bank lacked a systematic process for monitoring and managing auto-extension credits.

Failure 3: Beneficiary Presents After Extended Auto-Extension Period

A credit auto-extends for 30 days. The beneficiary presents 45 days after the original expiry, missing the 30-day auto-extension window. The credit has expired.

Root cause: The beneficiary miscounted the auto-extension period or was unaware of the extension's limits.

Failure 4: Confirming Bank and Issuing Bank Disagree on Extension

The issuing bank sends a non-extension notice under Article 29(b), but the confirming bank does not. The beneficiary is uncertain whether the credit is extended. Article 29(b) allows either the issuing bank or the confirming bank to provide the notice. If either provides a timely notice, the credit is not extended from that bank's perspective.

Root cause: The parties did not coordinate their positions on the auto-extension.

Deterministic Resolution Architecture

Step 1: Analyze Article 29(a) and 29(b) Independently

For each credit, determine whether Article 29(a) applies (non-banking day), Article 29(b) applies (auto-extension clause), or both apply. Analyze each provision separately.

Step 2: Apply Article 29(a) First

If the expiry falls on a non-banking day, apply Article 29(a) to extend the expiry to the first following banking day. This extension is automatic.

Step 3: Apply Article 29(b) if Applicable

If the credit contains an auto-extension clause, determine whether a timely non-extension notice was given. If not, the credit extends for the stated period.

Step 4: Calculate the Combined Extension

If both provisions apply, the credit extends first under Article 29(a) to the next banking day, and then under Article 29(b) for the auto-extension period from that extended date.

Step 5: Verify Non-Extension Notice Compliance

For Article 29(b), verify that the non-extension notice was (a) from the issuing bank or confirming bank, (b) timely (before the expiry date), and (c) substantive (stating the bank will not extend).

Step 6: Confirm the Beneficiary's Position

Verify the beneficiary's awareness of the extension and their planned presentation timing. Ensure the beneficiary understands which dates are extended and which are not.

Step 7: Document the Extension Framework

Record the analysis of both provisions, the extended dates, and the parties' positions. This record supports subsequent compliance determinations.

Step 8: Establish Monitoring Procedures

For banks managing multiple credits, establish systematic procedures for monitoring auto-extension clauses, tracking expiry dates, and issuing non-extension notices when required.

Conclusion

Article 29's date extension provisions — both the automatic extension for non-banking days and the auto-extension clause mechanism — require independent analysis. Each provision has its own scope, requirements, and limitations. Understanding how they interact, and how they differ from the credit's other date requirements, is essential for compliance.

FAQ

Q1: Can both Article 29(a) and 29(b) apply to the same credit?
Yes. If the credit expires on a non-banking day and contains an auto-extension clause, both provisions may apply. Article 29(a) extends the expiry to the next banking day, and the auto-extension clause provides additional extension.

Q2: Does the auto-extension period start from the original expiry date or the extended date?
The auto-extension period starts from the date the credit would otherwise expire. If Article 29(a) extends the expiry to Monday, and the auto-extension is for 30 days, the 30 days run from Monday.

Q3: Can the issuing bank revoke an auto-extension clause through an amendment?
Yes, under Article 10. The issuing bank can amend the credit to remove or modify the auto-extension clause. The amendment requires the beneficiary's agreement.

Q4: What if the issuing bank sends a non-extension notice but the beneficiary does not receive it?
This is a factual dispute. If the bank can prove the notice was sent timely, the credit is not extended. If the beneficiary can prove non-receipt due to the bank's error, the beneficiary may argue the credit was extended.

Q5: Is there a standard form for non-extension notices?
There is no prescribed form under Article 29(b). However, the notice must be clear, unambiguous, and state that the bank will not extend the credit. SWIFT MT707 or a formal letter is commonly used.

Source Notes

Did You Know?

Article 29(b) allows either the issuing bank or the confirming bank to provide the notice.

Regulatory Reference Table
RegulationArticle / SectionRequirementConsequence
UCP 600Article 29Extension of Expiry Date or Last Day for PresentationBinary determination (compliant/discrepant)
UCP 600Article 36Force MajeureBinary 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