UCP 600 Article 14: Examination — Data Consistency Across the Document Set

Introduction

Data consistency across the document set is a mandatory requirement under Article 14(e) of UCP 600. The provision requires that data in one document must not conflict with data in another stipulated document. This requirement ensures that the document set, as a whole, presents a coherent and consistent picture of the transaction. A discrepancy in data consistency — even a minor numerical mismatch — can result in document refusal and non-payment.

The data consistency requirement applies across all stipulated documents: commercial invoices, transport documents, insurance certificates, packing lists, inspection certificates, certificates of origin, and any other documents required by the credit. The standard is strict literal comparison — the examining bank reads the data on each document and compares it against the data on all other documents. There is no tolerance for commercial equivalence or practical substitution.

This guide examines the regulatory framework for data consistency under Article 14(e) during the examination process, identifies the common consistency failure modes, and provides a resolution architecture for achieving consistency across the document set.

Failure Mode Analysis

Failure 1: Quantity Mismatch Between Invoice and Transport Document

The most common data consistency discrepancy is a quantity mismatch between the commercial invoice and the bill of lading. Even a minor difference (e.g., 1,000 kg on the invoice vs. 998 kg on the bill of lading) constitutes a discrepancy under Article 14(e).

Failure 2: Goods Description Inconsistency

The goods description on the commercial invoice must be consistent with the description on the transport document, packing list, and other documents. Using different terminology or abbreviations across documents creates a discrepancy.

Failure 3: Weight Discrepancies Across Documents

Weight data must be consistent across the invoice, bill of lading, packing list, and inspection certificate. Discrepancies in net weight, gross weight, or tare weight between any two documents are discrepancies.

Failure 4: Date Inconsistencies

Dates on different documents must be consistent. The shipment date on the bill of lading must not conflict with the inspection certificate date (which must not be later than the shipment date for pre-shipment inspections under ISBP 745 paragraph A12(d)).

Failure 5: Party Name Inconsistencies

Party names must be consistent across all documents. A misspelling or abbreviation on one document that differs from another document's version creates a discrepancy.

Deterministic Resolution Architecture

Step 1: Establish the Data Anchor

Select one document as the primary data anchor — typically the commercial invoice. Use the invoice data as the baseline against which all other documents are compared.

Step 2: Create a Data Consistency Matrix

Build a matrix mapping key data fields (quantity, weight, description, dates, party names, currency, amount) across all documents. For each field, verify that the data is consistent across all documents.

Step 3: Compare Quantity Data

Verify that the quantity stated on the invoice matches the quantity on the bill of lading, packing list, and any other documents that state quantity.

Step 4: Compare Weight Data

Verify that net weight, gross weight, and tare weight are consistent across the invoice, bill of lading, packing list, and inspection certificate.

Step 5: Compare Goods Descriptions

Verify that the goods description on the invoice is consistent with descriptions on the transport document, packing list, and other documents. Use the same terminology and units of measure.

Step 6: Compare Dates

Verify that all dates are consistent: shipment date (bill of lading), inspection date (inspection certificate), issuance date (certificate of origin). Confirm that no date conflicts with another.

Step 7: Compare Party Names

Verify that party names (applicant, beneficiary, consignee, notify party) are spelled identically across all documents. Resolve any abbreviations or naming variations.

Step 8: Conduct a Final Cross-Document Review

After resolving all individual data fields, perform a final review of the complete document set to confirm that no new inconsistencies have been introduced during the correction process.

Conclusion

Data consistency under Article 14(e) requires exact literal matching across all stipulated documents. The examining bank applies strict comparison without considering commercial equivalence or practical tolerances. The most common consistency failures — quantity mismatches, description inconsistencies, weight discrepancies, date conflicts, and party name variations — are all preventable through systematic cross-document verification. A structured approach that establishes a data anchor, builds a consistency matrix, and verifies each data field across the document set eliminates data consistency discrepancies.

FAQ

Q1: Does "not conflict" mean the data must be identical?

Consistent means the data must not conflict. Data can be more detailed on one document than another, as long as the additional detail does not contradict the other document's data. For example, an invoice stating "1,000 kg of Premium Grade Wheat Flour, packed in 20 bags" is consistent with a bill of lading stating "1,000 kg wheat flour."

Q2: What if the bill of lading states "approximately 1,000 MT" and the invoice states "998 MT"?

If the credit uses "approximately" or "about" in the quantity, Article 30(a) provides a 10% tolerance. If the credit states a precise quantity without tolerance, the discrepancy is identified.

Q3: Can the packing list use different units of measure than the invoice?

The packing list data must not conflict with the invoice data under Article 14(e). If the packing list uses "pounds" and the invoice uses "kilograms," the bank will expect the values to be equivalent. A unit mismatch that creates apparent inconsistency is a discrepancy.

Q4: What if the certificate of origin uses a different goods description than the invoice?

The certificate of origin data must not conflict with the invoice data. If the descriptions differ, the discrepancy is identified. The beneficiary should ensure all documents use the same or consistent descriptions.

Q5: Does the examining bank check data consistency between the insurance certificate and other documents?

Yes. Article 14(e) applies to all stipulated documents, including the insurance certificate. The insured amount, goods description, and shipment details on the insurance certificate must be consistent with the other documents.

Source Notes

• Source file: 2026-07-14_ucp-600-article-14-examination-data-consistency-across-document-set.md
• Query: ucp 600 article 14 examination data multi-family documentary credit site:iccwbo.org
• Source results (17):
• "Incoterms® 2020" — ICC (2023-03-29): Incoterms 2020 overview. Context only.
• "11 Questions that will help you master documentary credits" — ICC Academy (2024-08-08): DC mastery questions. Context only.
• "Certified UCP 600 Specialist (CUCP)" — ICC Academy (2025-07-12): UCP 600 specialist certification. Context only.
• "Uniform Rules for Documentary Credits (UCP 600) - eBook" — ICC Academy (2024-12-12): UCP 600 reference ebook. Context only.
• "UCP 600 - Uniform Rules and Practice for Documentary Credits" — ICC (2023-07-31): Official UCP 600 publication. Context only.