UCP 600 Article 14: Conflicting Document Data Across Articles

Introduction

Article 14(e) of UCP 600 establishes one of the most mechanically unforgiving provisions in documentary credit practice: data in a stipulated document must not conflict with data in any other stipulated document. This provision does not evaluate materiality. It does not assess whether the conflict is trivial or consequential. A data conflict between any two documents in the set produces a discrepancy — regardless of whether the conflict affects the goods, the shipment, the amount, or any other substantive element.

In practice, conflicting data across documents is the single most common source of discrepancies in documentary credit transactions. The conflict may be as subtle as a date difference of one day between the bill of lading and the insurance certificate, or as obvious as a goods description mismatch between the invoice and the transport document. The examining bank applies Article 14(e) mechanically: if data conflicts, the presentation is discrepant.

Failure Mode Analysis

Failure Mode 1: Goods Description Mismatch Between Invoice and Transport Document

The commercial invoice describes goods as "Hot rolled steel coils, grade A, width 1200mm." The bill of lading describes goods as "Steel coils, HR, 1200mm." The abbreviations on the bill of lading ("HR" for hot rolled) create ambiguity about whether the same product is described. Under Article 14(e), the data must not conflict. If the abbreviations create doubt about consistency, the examining bank treats the inconsistency as a discrepancy.

Failure Mode 2: Date Conflict Between Bill of Lading and Insurance Certificate

The bill of lading shows a shipment date of 15 June 2026. The insurance certificate is dated 17 June 2026. The credit requires insurance to be effective from the date of shipment. The insurance certificate's date after the shipment date suggests the goods were uninsured during the initial transit period. This date conflict produces a discrepancy under Article 14(e).

Failure Mode 3: Amount Mismatch Between Invoice and Draft

The commercial invoice shows an amount of USD 100,000. The draft is drawn for USD 101,500, including an alleged commission. The credit does not authorise the addition of commissions to the invoice amount. The amount mismatch between the invoice and the draft produces a discrepancy.

Failure Mode 4: Country of Origin Mismatch Across Documents

The certificate of origin states "Made in Vietnam." The commercial invoice states "Origin: Vietnam." The bill of lading shows the port of loading as "Ho Chi Minh City, Vietnam." The phytosanitary certificate states "Country of origin: Republic of Vietnam." While all references point to Vietnam, the variation in naming ("Vietnam" vs. "Republic of Vietnam") may be treated as a conflict if the examining bank applies a strict interpretation.

Failure Mode 5: Weight Discrepancy Between Bill of Lading and Weight Certificate

The bill of lading shows a weight of 25,000 MT. The weight certificate shows 24,850 MT. The variance is 0.6% — within the Article 30 tolerance. However, the two documents show different numbers. Under Article 14(e), the data must not conflict. Whether the 150 MT variance constitutes a "conflict" depends on the examining bank's interpretation. A conservative examiner treats any numerical difference as a conflict.

Deterministic Resolution Architecture

Step 1: Establish a Canonical Data Set

Before preparing any document, establish a single, canonical set of data elements that will appear on every document: goods description (verbatim from field 45A), amounts, dates, weights, countries, parties, and reference numbers. Every document must use these exact data elements without variation.

Step 2: Map Every Data Element to Every Document

Create a matrix that maps each data element to every document in the set. The matrix shows the goods description on the invoice, the bill of lading, the packing list, the certificate of origin, and every other document. Any cell where the data element differs from the canonical value is a potential discrepancy.

Step 3: Verify Date Consistency Across All Documents

Map every date in the document set: invoice date, shipment date, bill of lading date, insurance certificate date, certificate of origin date, inspection date. Verify that no date conflicts with another. Verify that all dates fall within the credit's constraints (latest shipment date, document presentation date, insurance coverage period).

Step 4: Verify Amount Consistency

Compare the amount on the commercial invoice, the draft, the bill of lading (if it shows value), and any other document that references the transaction amount. The amounts must be consistent. If the credit specifies a tolerance under Article 30, verify the variance falls within the tolerance.

Step 5: Verify Country and Origin Consistency

Compare the country of origin data on the certificate of origin, the phytosanitary certificate (if applicable), the bill of lading (port of loading), and the commercial invoice. All references must be consistent. Use the same country name format across all documents.

Step 6: Verify Party Name Consistency

Compare the applicant, beneficiary, consignee, and notify party names across all documents. Minor variations (e.g., "Ltd." vs. "Limited," "Co." vs. "Company") may be treated as conflicts under a strict interpretation. Use the exact names as they appear in the credit.

Step 7: Run a Final Cross-Document Consistency Check

Before submission, run a final consistency check across the entire document set. Compare every data element on every document against every other document. Any inconsistency — however minor — is a potential discrepancy under Article 14(e).

Step 8: Document the Consistency Verification

Record the consistency verification, including the matrix of data elements and documents, and the results of the cross-document check. This record is the documentary evidence of compliance preparation if a dispute arises after presentation.

Conclusion

Article 14(e) is a mechanical provision: data must not conflict across documents. The provision does not evaluate materiality, does not assess intent, and does not provide tolerance for minor variations. A goods description abbreviation, a date difference of one day, a country name variation, or a weight discrepancy of 0.6% each produce a potential discrepancy.

The resolution architecture is deterministic: establish a canonical data set, map it to every document, verify consistency across dates, amounts, countries, and parties, and run a final cross-document check. When every data element is identical across every document, Article 14(e) is satisfied. When any data element varies, Article 14(e) is violated. There is no middle ground.

FAQ

Q1: Does ISBP 745 provide any tolerance for minor data variations?
ISBP 745 does not establish a general tolerance for data variations. The paragraph A1 standard requires data consistency across documents. Minor variations (abbreviations, formatting differences) may be acceptable if they do not create ambiguity, but the examining bank makes this determination on a case-by-case basis.

Q2: Can a goods description abbreviation (e.g., "HR" for "hot rolled") produce a discrepancy?
Yes. If the abbreviation is not defined on the document, the examining bank may treat it as inconsistent with the full description on another document. To avoid this risk, use the full goods description on every document.

Q3: What happens if the weight on the bill of lading differs from the weight on the weight certificate?
The examining bank determines whether the difference constitutes a "conflict" under Article 14(e). A difference within the Article 30 tolerance (5%) may not be treated as a discrepancy, but a conservative examiner may still flag it. To avoid risk, reconcile weights before submission.

Q4: Is a party name variation (e.g., "Ltd." vs. "Limited") a discrepancy?
Under a strict interpretation, a name variation may be treated as a conflict. Under a liberal interpretation, "Ltd." and "Limited" are equivalent. The examining bank's interpretation determines the outcome. To eliminate risk, use the exact name as it appears in the credit on every document.

Q5: Does Article 14(e) apply to documents not stipulated in the credit?
No. Article 14(e) applies to "stipulated documents" — documents required by the credit. Extra documents that the beneficiary chooses to present are not subject to Article 14(e)'s cross-document consistency requirement.

Source Notes

Context Only: The source dossier referenced ICC Academy publications on documentary credit examination standards and ICC Banking Commission technical advisory briefings. No text from those sources has been reproduced. This guide was composed from first principles using the UCP 600 text, ISBP 745, and independent analysis.