ISBP 745

ISBP 745 Section A: Data Conflicts in Different Documents

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

Introduction

Data conflicts across documents are among the most common reasons for refusal in documentary credit practice. ISBP 745 Section A establishes that data appearing in one document must not conflict with data in another stipulated document or the credit itself. When the invoice shows one quantity, the transport document shows another, and the packing list shows a third, the bank must refuse the presentation. This guide explains the ISBP 745 A2 principle, examines the types of data conflicts that arise, and provides a systematic approach to identifying and resolving them.

Failure Mode Analysis

FM1: Quantity Conflict Between Invoice and Transport Document

The invoice shows 500 units, but the bill of lading shows 480 units. This is a direct conflict under ISBP 745 A2. The bank will refuse the presentation because the data in the invoice conflicts with the data in the transport document.

FM2: Price Conflict Between Invoice and Credit

The invoice shows a unit price of USD 10.50, but the credit specifies USD 10.00. The resulting total amount differs from the credit amount. This is a conflict between the invoice and the credit.

FM3: Description Conflict Between Invoice and Certificate of Origin

The invoice describes the goods as "cotton yarn, 40/1 count." The certificate of origin describes the goods as "cotton thread, 40/2 count." The descriptions differ in both the type of product and the count. Under ISBP 745 A2, this is a discrepancy.

FM4: Port of Loading Conflict Between Invoice and Transport Document

The invoice states the port of loading is "Shanghai, China," but the bill of lading shows the port of loading as "Ningbo, China." The ports do not match. This is a conflict under A2.

FM5: Shipper/Consignee Conflict Between Transport Document and Credit

The credit names the beneficiary as the shipper. The transport document names a third party as the shipper. Unless the credit permits this, it is a conflict between the transport document and the credit.

Deterministic Resolution Architecture

Step 1: Create a Data Extraction Matrix

For each stipulated document, extract key data points:
- Description of goods
- Quantity
- Unit price and total amount
- Currency
- Port of loading and discharge
- Shipper, consignee, notify party
- Dates (invoice date, shipment date, insurance date)
- Weight and measurement
- Country of origin

Step 2: Map Each Data Point Across Documents

Compare each data point across all documents. Identify any discrepancies:
- Same data point, different values across documents: conflict.
- Same data point, same values across documents: consistent.

Step 3: Compare Document Data Against the Credit

For each data point, compare the document data against the credit requirements:
- Identical or substantively equivalent: compliant.
- Different or conflicting: discrepant.

Step 4: Apply the "Need Not Be Identical" Principle

Under A2, data need not be identical across documents — it must not conflict. Minor differences in wording that convey the same meaning (e.g., "cotton yarn" vs. "yarn made of cotton") are not conflicts. However, substantive differences (e.g., "cotton yarn" vs. "polyester yarn") are conflicts.

Step 5: Assess Within-Document Conflicts

If a single document contains internally inconsistent data (e.g., the invoice header shows 500 units but the invoice body shows 480 units), this is a within-document conflict under ISBP 745 A3.

Step 6: Determine Whether the Conflict Is Material

Under UCP 600 and ISBP 745, any data conflict — regardless of materiality — is a discrepancy. Banks do not assess whether a conflict is "immaterial" or "technical." The conflict exists, and the presentation is refused.

Step 7: Issue the Refusal Notice

State the specific conflict: "Invoice shows [X] but transport document shows [Y], a conflict contrary to ISBP 745 A2 and UCP 600 Art 14(d)."

Conclusion

Data conflicts across documents are a leading cause of discrepancy. ISBP 745 A2 establishes the principle that data need not be identical but must not conflict. Practitioners should advise beneficiaries to prepare all documents simultaneously and cross-check data points before presentation. A systematic approach — extracting and comparing key data across all documents — eliminates most conflicts before they reach the examining bank.

FAQ

Q1: What if the invoice says "about 500 units" and the transport document says "495 units"?

The "about" tolerance under ISBP 745 B12 allows 10% more or less. 495 units is within the 10% tolerance of 500. However, the transport document should show the actual quantity shipped. If the transport document shows the actual quantity and it falls within the tolerance, there is no conflict.

Q2: Can the bank refuse if the descriptions are slightly different but clearly refer to the same goods?

Under ISBP 745 A2, data "need not be identical" but "must not conflict." If the descriptions convey the same meaning (e.g., "Grade A rice" vs. "Rice, Grade A"), this is not a conflict. If they convey different meanings (e.g., "Grade A rice" vs. "Grade B rice"), it is a conflict.

Q3: Does the bank need to compare every data point across all documents?

The bank examines each document on its face and in the context of the credit and other documents (UCP 600 Art 14(a)). The bank is not required to perform an exhaustive data-matching exercise, but obvious conflicts must be identified.

Q4: What if the beneficiary offers to explain the conflict?

Under UCP 600, the bank examines documents on their face. The beneficiary's explanation does not change the documents' data content. If a conflict exists, the bank must refuse.

Q5: Can a conflict be cured after the refusal notice?

Yes, if the credit has not expired and the beneficiary can obtain corrected documents before the expiry date. The bank may also accept a waiver from the applicant under UCP 600 Art 16(b).

Source Notes

Context only — no direct article text was extracted from these sources during research:

Did You Know?

ISBP 745 A2 and UCP 600 Art 14(d).

Regulatory Reference Table
RegulationArticle / SectionRequirementConsequence
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 5 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 ISBP 745 Section A — 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