UCP 600

UCP 600 Article 34: Bank Not Liable for Accuracy of Information in Documents

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

Introduction

A core protection for banks operating under UCP 600 is the disclaimer found in Article 34. Among its provisions, Article 34(e) states that a bank is not responsible for the accuracy, completeness, genuineness, or legal effect of documents, or for the terms and conditions stated in documents. This guide examines the scope of this disclaimer, the failure modes that arise when banks or applicants assume a higher level of bank responsibility, and the resolution framework that clarifies each party's obligations.

Failure Mode Analysis

Failure Mode 1: Applicant Claims the Bank Should Have Detected Fraud in a Document

The beneficiary submits a commercial invoice with inflated values. The issuing bank pays against a complying presentation. The applicant later discovers the inflated values and claims the bank should have detected the fraud. Article 34(a) and (e) relieve the bank of this responsibility.

Failure Mode 2: Applicant Argues the Bank Should Have Verified the Legal Effect of a Document

The credit requires a certificate of origin, but the certificate's language does not clearly establish the origin of the goods as required by local customs law. The applicant claims the bank should have verified the document's legal effect. Article 34(e) states the bank is not responsible for the legal effect of documents.

Failure Mode 3: Nominated Bank Translates a Document and the Translation Contains Errors

A nominated bank, at the presenter's request, translates a document from a foreign language. The translation contains an error that affects the apparent compliance of the document. Under Article 34(f), the bank is not responsible for translation errors.

Failure Mode 4: Applicant Relies on the Bank to Authenticate Documents Beyond Face-Value Examination

The applicant expects the issuing bank to authenticate signatures, verify the originality of documents, or confirm the accuracy of data against external databases. Article 34(a) and (e) establish that the bank's examination is limited to the documents' face.

Deterministic Resolution Architecture

Resolution 1: Clearly Communicate the Bank's Limited Responsibility
In the applicant agreement and in pre-issuance communications, explain that the bank's obligation is to examine documents on their face against the credit's terms, not to verify accuracy, genuineness, or legal effect.

Resolution 2: Maintain a Strict Face-Value Examination Protocol
The examining team must restrict its analysis to what appears on the documents' face. No external verification of content, no contact with third parties, and no assessment of legal effect should be part of the examination.

Resolution 3: Refuse Requests to Translate or Interpret Documents
If a presenter asks the bank to translate or interpret a document, the bank should decline and advise the presenter to arrange independent translation. Under Article 34(f), the bank is not responsible for translation errors.

Resolution 4: Use Documentary Credit Conditions to Require Specific Content
If the applicant requires a particular level of accuracy or content in a document, the credit should specify exactly what is required. This places the compliance burden on the beneficiary and the examination focus on the bank's face-value review.

Resolution 5: Document the Examination as Face-Value Only
Every examination record should state that the review was conducted on the basis of the documents alone. This protects the bank if the applicant later claims the bank should have looked deeper.

Resolution 6: Advise the Applicant to Pursue External Due Diligence
If the applicant is concerned about the accuracy or genuineness of documents, the bank should advise the applicant to conduct its own due diligence (e.g., background checks on the beneficiary, independent verification of goods) before or outside the credit process.

Resolution 7: Distinguish Between Document Examination and Fraud Detection
Fraud detection is not a bank's obligation under UCP 600. The fraud exception is a legal doctrine that applies in extreme circumstances and requires a high evidentiary standard. Banks should not be expected to act as fraud investigators.

Conclusion

Article 34's disclaimer on accuracy, genuineness, and legal effect is one of the most important protections in UCP 600. It defines the boundary of the bank's responsibility and limits the bank's exposure to claims arising from the content of documents. Practitioners who understand and apply this boundary avoid disputes that stem from misplaced expectations about the bank's role.

Frequently Asked Questions

Q1: If a document is forged, is the bank liable?
Under Article 34(a), the bank is not liable for the genuineness of documents. However, if the bank has actual knowledge of forgery and proceeds to pay, the fraud exception may apply in some jurisdictions.

Q2: Can the bank verify the authenticity of a signature on a document?
UCP 600 does not require banks to verify signatures. Article 34(a) relieves the bank of responsibility for genuineness. Some banks may voluntarily verify signatures, but this is not a UCP obligation.

Q3: What if the credit requires a "legal opinion" — is the bank responsible for its legal effect?
No. Article 34(e) states the bank is not responsible for the legal effect of documents. If the credit requires a legal opinion, the bank examines the document on its face to determine whether it appears to be a legal opinion.

Q4: Does the bank have any obligation to verify data in a document against external sources?
No. Article 14(a) limits examination to the documents alone. The bank does not verify data against shipping databases, customs records, or any other external source.

Q5: How does eUCP address the accuracy disclaimer?
eUCP Version 2.1 preserves Article 34's disclaimers. Electronic records are treated as documents, and the bank's responsibility for accuracy, completeness, and genuineness is limited in the same manner as for paper documents.

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.

Did You Know?

Article 34(e) states that a bank is not responsible for the accuracy, completeness, genuineness, or legal effect of documents, or for the terms and conditions stated in documents.

Regulatory Reference Table
RegulationArticle / SectionRequirementConsequence
UCP 600Article 34Disclaimers on DocumentsBinary 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
Applicant Claims the Bank Should Have Detected Fraud in a DocumentThe beneficiary submits a commercial invoice with inflated values. The issuing bank pays against ...
Applicant Argues the Bank Should Have Verified the Legal Effect of a DocumentThe credit requires a certificate of origin, but the certificate's language does not clearly esta...
Nominated Bank Translates a Document and the Translation Contains ErrorsA nominated bank, at the presenter's request, translates a document from a foreign language. The ...
Applicant Relies on the Bank to Authenticate Documents Beyond Face-Value ExaminationThe applicant expects the issuing bank to authenticate signatures, verify the originality of docu...

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