UCP 600

UCP 600 Article 35: Bank Not Liable for Delay in Transmission

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

Introduction

When documents are transmitted between banks — from nominated bank to issuing bank, or from advising bank to confirming bank — delays can and do occur. Article 35 of UCP 600 provides a clear disclaimer: banks assume no liability or responsibility for the consequences arising out of delay in the transmission of any message, or for delays in the mail. This guide examines the scope of this protection, the failure modes that arise when transmission delays affect the documentary credit lifecycle, and the resolution steps that keep the process moving despite inevitable logistical challenges.

Failure Mode Analysis

Failure Mode 1: Documents Delayed in Courier Delivery, Causing Expiry-Date Issues

The beneficiary dispatches documents by courier three days before the expiry date. Due to customs delays in the destination country, the documents arrive at the issuing bank two days after the expiry date. The issuing bank argues the presentation is late. Under Article 35, the bank is not responsible for the delay, but the question is whether the presentation date is the dispatch date or the receipt date.

Failure Mode 2: SWIFT Message Delayed, Affecting the Examination Timeline

The issuing bank sends a SWIFT message to the nominated bank, but the message is delayed due to network issues. The nominated bank receives the message two banking days later than expected. Article 35 relieves the bank of responsibility for the delay, but the practical impact on the examination timeline must be managed.

Failure Mode 3: Documents Lost in Transit

The nominated bank dispatches documents to the issuing bank by registered mail. The documents are lost in transit. Under Article 35, the bank is not responsible for the loss. However, the beneficiary must take steps to obtain duplicate documents and re-present.

Failure Mode 4: Electronic Record Corruption During Transmission

Under eUCP, an electronic record is transmitted from one bank to another, but the record becomes corrupted during transmission. Article 35's disclaimer covers errors arising from electronic communication. The transmitting bank is not responsible for the corruption.

Deterministic Resolution Architecture

Resolution 1: Dispatch Documents Well in Advance of the Expiry Date
The single most effective mitigation for transmission delays is to dispatch documents with sufficient lead time. A minimum of five to seven business days before the expiry date provides a buffer for most courier and mail delays.

Resolution 2: Use Trackable Courier Services with Delivery Confirmation
When dispatching documents physically, use a courier service that provides real-time tracking and proof of delivery. This allows the presenter to confirm receipt and resolve any disputes about when the documents were delivered.

Resolution 3: Understand the Presentation Date Rule
The presentation date is when the documents are received by the examining bank during normal banking hours. Dispatching documents is not the same as presenting them. The presenter must account for transit time.

Resolution 4: Maintain Duplicate Document Sets
Keep copies of all documents dispatched under a credit. If the original documents are lost in transit, the presenter can re-issue and re-present from the copies, provided the original documents are re-created in compliance with the credit's terms.

Resolution 5: Use Electronic Channels When Available
SWIFT-based or other electronic submission channels reduce transit time and the risk of physical loss. Where the bank offers electronic submission, use it to minimise delay risk.

Resolution 6: Monitor SWIFT Message Receipt
After sending a SWIFT message, confirm receipt with the receiving bank if the message is time-sensitive. This prevents misunderstandings about when a message was received.

Resolution 7: Document the Dispatch and Tracking Information
Maintain records of the dispatch date, courier tracking number, and delivery confirmation. This evidence is essential if a dispute arises about when the presentation was made.

Conclusion

Article 35 of UCP 600 provides banks with essential protection against the consequences of transmission delays. The rule places the responsibility for timely dispatch on the presenter, not the receiving bank. By dispatching documents early, using trackable services, and maintaining duplicate document sets, presenters can minimise the impact of delays and protect their rights under the credit.

Frequently Asked Questions

Q1: If documents are delayed in transit and arrive after the expiry date, can the beneficiary still present?
This depends on the credit's terms and the jurisdiction's law. Under UCP 600, the presentation date is the date of receipt by the examining bank. If the documents arrive after the expiry date, the presentation may be late. However, Article 29 may extend the expiry date if the bank was closed.

Q2: Is the courier liable for lost documents?
The courier's liability is a separate contractual matter between the presenter and the courier. UCP 600 does not address courier liability. The presenter should pursue claims against the courier independently.

Q3: Does Article 35 apply to electronic submissions under eUCP?
Yes. Article 35 expressly covers electronic communication. The bank is not responsible for delays, errors, or corruption in electronic transmissions.

Q4: If a SWIFT message is delayed, does the examining bank get additional time?
Under Article 14(b), the examining bank has five banking days following the day of presentation. The day of presentation is determined by when the documents are received, not when the SWIFT message was sent.

Q5: Can the presenter claim against the issuing bank for a delay caused by the courier?
No. Article 35 explicitly states that banks assume no liability for delays in the mail or from other means of transmission. The presenter's recourse is against the courier.

Source Notes

Context Only: The following source titles informed the development of this guide. No text was copied from these sources. All regulatory citations reference published ICC rules.

Regulatory Reference Table
RegulationArticle / SectionRequirementConsequence
UCP 600Article 35Disclaimers on Transmission and TranslationBinary determination (compliant/discrepant)
UCP 600Article 16Discrepant Documents, Waiver and NoticeBinary determination (compliant/discrepant)
UCP 600Article 2DefinitionsBinary determination (compliant/discrepant)
UCP 600Article 29Extension of Expiry Date or Last Day for PresentationBinary determination (compliant/discrepant)
UCP 600Article 14Standard for Examination of DocumentsBinary 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
Documents Delayed in Courier Delivery, Causing Expiry-Date IssuesThe beneficiary dispatches documents by courier three days before the expiry date. Due to customs...
SWIFT Message Delayed, Affecting the Examination TimelineThe issuing bank sends a SWIFT message to the nominated bank, but the message is delayed due to n...
Documents Lost in TransitThe nominated bank dispatches documents to the issuing bank by registered mail. The documents are...
Electronic Record Corruption During TransmissionUnder eUCP, an electronic record is transmitted from one bank to another, but the record becomes ...

← 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 35 — 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