ISBP 745 Section A4: Same Field, Same Data

Introduction

ISBP 745 Paragraph A4 addresses the requirement that when a credit requires documents to indicate data content, the same field across different documents must contain the same data. This principle of data consistency is fundamental to documentary credit compliance. This guide examines the regulatory framework governing same field/same data requirements, common failure modes in practice, and the steps required to achieve compliance.

Failure Mode Analysis

Failure Mode 1: Inconsistent Data Across Documents

The most common failure occurs when the same data point appears differently across multiple documents. For example, if the credit requires the applicant's name on the invoice, bill of lading, and certificate of origin, but the name is spelled differently on each document, the discrepancy will be flagged.

Failure Mode 2: Date Discrepancies

Dates that appear on multiple documents must be consistent. If the invoice date, shipment date, and certificate date do not align in a way that is logically consistent, banks may reject the documents. This includes scenarios where the invoice predates the shipment date.

Failure Mode 3: Quantity and Weight Inconsistencies

When the same quantity or weight appears on multiple documents, the figures must match. Discrepancies between the invoice quantity, bill of lading quantity, and packing list quantity can lead to rejection, even if the differences are minor.

Failure Mode 4: Description Conflicts

The description of goods on different documents must be consistent. If the invoice describes goods as "Widget Model A" but the bill of lading refers to "Widget Model B," the conflict will be flagged even if both refer to the same product.

Deterministic Resolution Architecture

1. Review the credit terms to identify all data points that must appear on multiple documents
2. Create a master data sheet containing all required data points with exact values to be used across all documents
3. Prepare each document using the exact data values from the master data sheet
4. Cross-check each data point across all documents to ensure consistency
5. Verify that dates on all documents are logically consistent (e.g., invoice date precedes shipment date)
6. Confirm that quantities and weights match across all documents that report these figures
7. Ensure that descriptions of goods, services, or performance are identical across all documents
8. Check that party names (applicant, beneficiary, consignee) are spelled consistently across all documents
9. Verify that amounts and currencies match across all financial documents
10. Document the compliance rationale for each key decision to create an audit trail

Conclusion

Compliance with ISBP 745 Section A4 requirements for same field/same data consistency demands meticulous coordination across all documents in the set. Banks apply strict compliance standards, and any inconsistency in data across documents can result in rejection. The key to success is establishing a systematic approach to data management, using a master data sheet, and cross-checking all documents before presentation. The deterministic path forward is to verify every data point against the credit terms and across all documents in the set, ensuring complete consistency throughout.

FAQ

What level of consistency is required for same field/same data?
ISBP 745 requires that data be consistent across all documents. While minor formatting differences (e.g., date formats) may be acceptable, substantive differences in data values will be flagged as discrepancies.

Can I use abbreviations on some documents and full terms on others?
Abbreviations should be used consistently across all documents. If a credit requires a specific term, use that exact term on all documents that reference it.

What if a discrepancy is identified after presentation?
Once documents are presented, they cannot be corrected or substituted. The bank must examine documents as presented and give notice of refusal within five banking days if discrepancies are found.

How does the bank handle data that appears in different formats?
If the same data appears in different formats (e.g., "January 1, 2026" vs. "01/01/2026"), banks typically accept both formats as long as the underlying data is the same. However, using consistent formatting across all documents is recommended.

What if the credit requires data on documents that do not normally contain that data?
If the credit requires data on a document that does not normally contain that information, the beneficiary must ensure the data is included. The absence of required data will be flagged as a discrepancy.

Source Notes

The cost of a comma: Documentation errors are the 'hidden tax' on Bangladesh's exports
- Source: The Daily Star
- URL: https://www.thedailystar.net
- Published: 2023
- Context: This article discusses the impact of documentation errors on trade finance, including discrepancies in data across documents. It provides context on the practical challenges of maintaining data consistency but does not constitute professional advice for specific transactions.