UCP 600 Article 10: Amendment After the Credit Expiry Date
Introduction
An amendment received after expiry is not automatically an effective change to the expired credit. The operative questions are separate: when was the amendment issued, when was it advised, whether it was accepted, and whether the underlying credit still had an operative expiry or presentation window. Treating an amendment message as a universal extension mechanism creates a false sense of protection after the credit has already closed.
A current source search returned trade-finance material on MT707 amendment mechanics. That material is operational context. The legal result depends on the credit text and UCP 600 Article 10.
Failure Mode Analysis
Failure Mode 1: Amendment message mistaken for an extension
The applicant asks the issuing bank to extend the expiry date, but the amendment is not advised to the beneficiary before the original expiry. The beneficiary presents later assuming the amendment is effective. The credit record and the presentation timeline do not support that assumption.
Failure Mode 2: Acceptance assumed from silence
The beneficiary receives an amendment but does not clearly accept or reject it. The parties then act as though the amended terms govern. Article 10’s acceptance mechanics must be assessed; silence is not a universal substitute for acceptance across every amendment scenario.
Failure Mode 3: Partial acceptance treated as complete acceptance
The beneficiary accepts the extended expiry but rejects a reduced amount or new document condition. The parties must identify which amendment terms were accepted and which were not. Operational systems that store only “amendment accepted” lose the distinction.
Deterministic Resolution Architecture
- Record the original credit expiry and last presentation date.
- Record the amendment issuance, advice, and acceptance timestamps separately.
- Identify every amended term; never store acceptance as a single undifferentiated flag.
- Confirm the amendment was advised through the relevant bank channel.
- Obtain clear beneficiary acceptance or rejection for each material amendment.
- Do not present after the original expiry unless the amended expiry is effective and evidenced.
- If timing is disputed, request written confirmation from the issuing/advising bank before shipment or presentation.
Conclusion
An amendment is a controlled change to a documentary credit, not a post-expiry repair token. Article 10 controls amendment mechanics; Article 6 controls expiry. A defensible process records advice and acceptance explicitly and refuses to treat an unconfirmed amendment as an operative extension.
FAQ
Does an amendment issued by the applicant automatically extend the credit?
No. The applicant’s instruction is not itself an effective amendment to the beneficiary’s operative credit.
Can a beneficiary accept only the expiry extension?
The amendment terms must be reviewed and the acceptance position recorded precisely. Do not treat a partial response as complete acceptance without confirming the applicable mechanics.
What if the amendment arrives after expiry?
Do not assume it revives the credit. Obtain bank confirmation and review the original and amended timelines before presentation.
Is an MT707 message alone enough?
The message format does not replace proper advice, authentication, and the legal amendment mechanics under the credit and applicable rules.
Source Notes
- Canonical authority: UCP 600 Articles 6 and 10.
- Live context: current search result for “Understanding MT 707: Amendment to a Documentary Credit [UPDATED 2026]” via Google News RSS. Operational context only.
UCP 600 Article 6(d) requires a credit to state an expiry date for presentation, and Article 6(e) requires presentation on or before expiry except where Article 29 applies.
| Regulation | Article / Section | Requirement | Consequence |
|---|---|---|---|
| UCP 600 | Article 10 | Amendments | Binary determination (compliant/discrepant) |
| UCP 600 | Article 6 | Availability, Expiry Date and Place for Presentation | Binary determination (compliant/discrepant) |
| UCP 600 | Article 29 | Extension of Expiry Date or Last Day for Presentation | Binary determination (compliant/discrepant) |
| UCP 600 | Article 14 | Standard for Examination of Documents | 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 |
|---|---|
| Amendment message mistaken for an extension | The applicant asks the issuing bank to extend the expiry date, but the amendment is not advised t... |
| Acceptance assumed from silence | The beneficiary receives an amendment but does not clearly accept or reject it. The parties then ... |
| Partial acceptance treated as complete acceptance | The beneficiary accepts the extended expiry but rejects a reduced amount or new document conditio... |
← 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 UCP 600 Article 10 — 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