UCP 600

UCP 600 Article 35: Examining Certificates of Origin

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

Introduction

Certificates of origin are among the most frequently discrepant documents in documentary credit presentations. They serve a dual purpose: proving the national origin of goods for tariff and regulatory compliance, and satisfying the credit's documentary requirements. UCP 600 Article 35 establishes that banks examine documents on their face and do not accept liability for the form, sufficiency, or legal effect of those documents. For certificates of origin, this means the bank checks that the document exists, matches the credit's description of goods, and is consistent with other documents — not that it is factually accurate or legally binding. The most common disputes arise when banks reject certificates of origin for naming errors, missing stamps, or inconsistency with other documents, even when the document substantially satisfies the credit.

Failure Mode Analysis

Failure 1: Country of origin inconsistent with invoice. When the certificate of origin states goods originate from Country A, but the commercial invoice describes the goods as manufactured in Country B, the documents conflict under Article 14(d). This is a common discrepancy when intermediaries source goods from third countries but the certificate of origin does not reflect the actual origin.

Failure 2: Certificate of origin signed by an entity not specified in the credit. If the credit requires a certificate of origin issued by the chamber of commerce, and the document is signed by the exporter or a trade association, banks reject it under Article 14(a) because the document was not issued by the stipulated entity. Article 14(e) applies when the credit does not specify the issuing authority.

Failure 3: Certificate of origin missing or incomplete data fields. Many certificates of origin include fields for HS code, gross weight, and packing details. When these are blank or incomplete, banks may reject the document if the credit requires them to be completed, or if the omission creates a conflict with other documents under Article 14(d).

Failure 4: Document dated after shipment date. A certificate of origin bearing a date later than the bill of lading date raises a timing question. While UCP 600 does not explicitly require a certificate of origin to be dated before shipment, the inconsistency can create doubt about whether the goods described on the certificate were actually shipped on the stated date.

Failure 5: Stamp or endorsement missing. Certificates of origin often require an official stamp or endorsement from an issuing authority. When this stamp is absent, banks may reject the document under Article 14(a) on the grounds that it does not appear on its face to be the document called for by the credit.

Deterministic Resolution Architecture

  1. Read the credit's certificate-of-origin clause carefully. Determine whether the credit specifies the issuing authority, data fields, language, and any particular wording. The credit terms control what constitutes compliance.

  2. Cross-check the country of origin against the commercial invoice. Ensure the certificate of origin states the same country of origin as the invoice. Inconsistency triggers Article 14(d).

  3. Verify the issuing authority. If the credit specifies a chamber of commerce, confirm that the certificate was issued by that entity. If the credit is silent, Article 14(e) applies and the document is accepted if it fulfils the function of a certificate of origin.

  4. Confirm all required data fields are complete. Check HS codes, gross weight, package count, and goods description against the invoice and packing list. Blank fields are only acceptable if the credit does not require them.

  5. Compare the certificate date with the shipment date. While not a strict compliance rule, a certificate of origin dated after the shipment date can create doubt. Document the dates and note any concern.

  6. Verify stamps, signatures, and endorsements. Confirm the document bears the required official stamp, signature, or endorsement from the issuing authority. If missing, classify the document as discrepant.

  7. Document the examination result. Record the certificate number, issuing authority, country of origin, date, and any discrepancies found. Preserve the examination record with the presentation file.

Conclusion

Certificates of origin under UCP 600 Article 35 are subject to the same facial-examination standard as all other documents. The bank checks for consistency with the credit and other documents, verifies the issuing authority, and confirms data completeness. Discrepancies most often arise from country-of-origin mismatches, incorrect issuing authorities, and incomplete data fields. A systematic cross-referencing process against the credit terms and the commercial invoice eliminates most avoidable rejections.

FAQ

Can a bank reject a certificate of origin for a factual error? No. Article 35 states banks assume no liability for the accuracy or legal effect of documents. The bank examines the document on its face for consistency with the credit, not for factual accuracy.

What if the credit does not specify an issuing authority for the certificate of origin? Under Article 14(e), banks accept the document as presented if its content appears to fulfil the function of the required document. The certificate is accepted regardless of who issued it.

Does ISBP 745 require a certificate of origin to be on a specific form? ISBP 745 does not prescribe a standard form for certificates of origin. The credit terms control the format. If the credit specifies a form, that form must be used.

Can a certificate of origin be presented electronically? Under eUCP Version 2.1, Article e7, an electronic certificate of origin is acceptable when the credit permits electronic presentation or does not preclude it.

What if the certificate of origin lists different goods than the invoice? This creates a conflict under Article 14(d). The bank must refuse the presentation because the data in the certificate of origin does not match the data in the commercial invoice.


Source Notes

Context only — no deep source text was extracted from the original research feeds.

Did You Know?

UCP 600 Article 35 establishes that banks examine documents on their face and do not accept liability for the form, sufficiency, or legal effect of those documents.

Regulatory Reference Table
RegulationArticle / SectionRequirementConsequence
UCP 600Article 35Disclaimers on Transmission and TranslationBinary determination (compliant/discrepant)
UCP 600Article 14Standard for Examination of DocumentsBinary determination (compliant/discrepant)
UCP 600Article 21Non-Negotiable Sea WaybillBinary determination (compliant/discrepant)

← Scroll horizontally to see all columns

Quick Reference Summary

  • No reference captured.

Compliance Checklist

0 of 7 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 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