UCP 600

UCP 600 Article 3: Credits vs. Contracts — Impact on Document Presentation

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

Introduction

The autonomy principle under UCP 600 Article 3 directly shapes how documents must be prepared, presented, and examined. Because the credit is a separate transaction from the underlying contract, document presentation must satisfy the credit terms alone. This guide examines how the credit-contract separation impacts each stage of document preparation and presentation, and the discrepancies that arise when this separation is not respected.

Failure Mode Analysis

Failure Mode 1: Beneficiary Prepares Documents from the Contract

When a beneficiary prepares documents using the contract as the source document rather than the credit, discrepancies inevitably follow. Contract prices, descriptions, dates, and terms often differ from credit terms. The beneficiary must use the credit as the primary reference document.

Failure Mode 2: Transport Documents Reflecting Contract Terms

Bills of lading, air waybills, and other transport documents that reference contract terms (e.g., "Shipment per Contract No. X") instead of credit-compliant descriptions create examination challenges. The transport document must comply with the credit requirements under Article 20 (bill of lading), Article 21 (non-negotiable sea waybill), Article 22 (charter party bill of lading), or Article 23 (air transport document).

Failure Mode 3: Insurance Documents Referencing the Contract

Insurance certificates or policies that reference the contract rather than the credit amount, coverage type, or insurable interest create discrepancies. The insurance document must comply with Article 28 of UCP 600, which prescribes specific requirements independent of the contract.

Failure Mode 4: Certificates of Origin Stating Contract-Based Information

Certificates of origin that include information specific to the contract (e.g., contract-specific quality grades or custom classifications) rather than standard origin certification may not satisfy the credit's documentary requirements.

Deterministic Resolution Architecture

  1. Credit-as-Source Protocol: Establish a protocol requiring all document preparers to use the credit text as the primary source document. The contract should be used only for commercial context, not for documentary content.

  2. Document-by-Document Verification: For each required document, verify its content against the specific credit clause it must satisfy. Create a checklist mapping each credit clause to the corresponding document and the ISBP 745 paragraph governing its examination.

  3. Description Consistency Check: Verify that the goods description on all documents is consistent with the credit description per ISBP 745 Paragraph B1. Use the credit's goods description as the master text.

  4. Amount and Currency Verification: Confirm that all monetary amounts on all documents are within the credit amount and in the credit currency. Document any tolerance calculations per UCP 600 Article 30 (tolerances).

  5. Transport Document Compliance: Verify that transport documents comply with Articles 19–25 without reference to contract terms. Ensure shipper/consignee/notify party information matches credit requirements, not contract party details.

  6. Insurance Document Compliance: Verify that insurance documents comply with Article 28, including coverage amount (minimum 110% of CIF/CIP value per Article 28(f)), coverage type, and currency.

  7. Presentation Timing: Present documents within the time limits prescribed by the credit (UCP 600 Article 14(c)) and within 21 calendar days of shipment (or as specified in the credit), regardless of contract-based timelines.

Conclusion

Document presentation under a documentary credit must be driven by the credit terms, not the contract terms. Every document must be prepared, verified, and presented with reference to the credit text. The autonomy principle under Article 3 means that the credit is the only standard of comparison. Beneficiaries who internalise this principle dramatically reduce their discrepancy rate and improve their payment security.

FAQ

Q1: If the contract and credit specify different Incoterms, which governs the documents?
A: The credit governs. All documents must comply with the credit's Incoterms. If the credit states "CIF Rotterdam," all documents must reflect CIF Rotterdam, regardless of the contract's Incoterms.

Q2: Can a beneficiary include extra information on documents beyond what the credit requires?
A: Yes, provided the additional information does not conflict with the credit terms or other documents per UCP 600 sub-article 14(d). ISBP 745 confirms that additional data is permitted if it does not create a conflict.

Q3: How should the beneficiary handle conflicting credit and contract dates?
A: The credit dates govern. The beneficiary must present documents within the credit's expiry and shipment dates. Contract dates are irrelevant to document presentation.

Q4: Can a bank refuse a document because it references the contract number?
A: A reference to the contract number on a document does not automatically create a discrepancy, provided the document otherwise complies with the credit terms. However, if the contract reference introduces conflicting data, it may create a discrepancy under Article 14(d).

Q5: What if the credit requires a document that does not exist under the contract?
A: The beneficiary must obtain the document as required by the credit. The credit's requirements are independent of the contract. If the beneficiary cannot obtain the required document, this is a discrepancy under Article 16.

Source Notes

Did You Know?

21 calendar days of shipment (or as specified in the credit), regardless of contract-based timelines.

Regulatory Reference Table
RegulationArticle / SectionRequirementConsequence
UCP 600Article 3InterpretationsBinary determination (compliant/discrepant)
UCP 600Article 14Standard for Examination of DocumentsBinary determination (compliant/discrepant)
UCP 600Article 18Commercial InvoiceBinary determination (compliant/discrepant)
UCP 600Article 20Bill of LadingBinary determination (compliant/discrepant)
UCP 600Article 21Non-Negotiable Sea WaybillBinary determination (compliant/discrepant)
UCP 600Article 22Charter Party Bill of LadingBinary 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
Beneficiary Prepares Documents from the ContractWhen a beneficiary prepares documents using the contract as the source document rather than the c...
Transport Documents Reflecting Contract TermsBills of lading, air waybills, and other transport documents that reference contract terms (e.g.,...
Insurance Documents Referencing the ContractInsurance certificates or policies that reference the contract rather than the credit amount, cov...
Certificates of Origin Stating Contract-Based InformationCertificates of origin that include information specific to the contract (e.g., contract-specific...

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