ISBP 745

ISBP 745 Section A11: Document Dates, Sequence, and Consistency

📅 2026-07-19 4 min read UCP 600 / ISBP 745

Introduction

The assumption that a date on a document is merely a chronological marker is a systemic fallacy. In trade finance, a date is a deterministic trigger for compliance. When dates across a presentation fail to isolate correctly or violate the logical sequence of a documentary credit, the result is a binary failure mode: payment or refusal. Most practitioners treat dates as static entries, ignoring that they mutate based on the document's function—issuance, shipment, effectiveness, or presentation. This guide deconstructs the regulatory architecture governing document dates to ensure your presentation compiles with the rigorous standards of UCP 600 and ISBP 745.

Failure Mode Analysis

Failure to manage dates correctly results in three primary failure modes:

  1. The Chronological Violation: Presenting a document dated after the date of presentation. Under UCP 600 Article 14(i), this is a binary refusal. Even if the goods have shipped, a future-dated inspection certificate isolates the bank's obligation to refuse.
  2. The Effectiveness Gap: In insurance documents, failing to isolate the date of issuance from the date of effectiveness. Under ISBP 745 Section A11(a)(ii), if a policy is issued on January 10th but coverage only begins on January 15th, the bank must decouple these dates to determine if coverage was active during the shipment period.
  3. The Reference Failure: When a document uses a cross-reference (e.g., "date as per bill of lading number xxx") under ISBP 745 Section A11(b), any inconsistency in the referenced document mutates the date of the referencing document. This creates a systemic chain of discrepancy.

Deterministic Resolution Architecture

To prevent these failure modes, apply the following resolution architecture:

  1. Map the Credit Requirements: Identify every document requiring a date per ISBP 745 Section A11.
  2. Verify the Presentation Window: Cross-reference all dates against UCP 600 Article 14(i). Any document dated after the presentation date is an immediate refusal.
  3. Decouple Issuance from Effectiveness: For insurance and transport documents, verify that the date of issuance does not conflict with the required "on board" or "effectiveness" dates.
  4. Audit Cross-References: If a document references another document's date, ensure the data in the referenced document is identical. Any conflict violates the consistency required by UCP 600 Article 14(d).
  5. Validate the Temporal Sequence: For pre-shipment events (ISBP 745 Section A12), ensure the document's date is mathematically less than or equal to the shipment date.

Conclusion

Document dates are not clerical details; they are the temporal spine of a documentary credit. By applying a deterministic approach to date verification and understanding the systemic implications of ISBP 745 Section A11, practitioners can isolate and resolve discrepancies before they lead to refusal. Compliance is not about flexibility; it is about the binary adherence to the rules.

FAQ

Q1: Does ISBP 745 Section A11 require every document to have a date of issuance?
A: Yes, for drafts, insurance documents, and transport documents, Section A11(a) mandates a date of issuance even if the credit is silent. For other documents, Section A11(b) allows for a date of occurrence or a cross-reference to another document's date.

Q2: Can a document be dated after the date of shipment but before the date of presentation?
A: Under ISBP 745 Section A12(a), certain documents like certificates of analysis or inspection can be dated later than the shipment date. However, UCP 600 Article 14(i) strictly prohibits any document from being dated later than the date of presentation.

Q3: What happens if the date on a certificate of origin conflicts with the bill of lading date?
A: This is a violation of UCP 600 Article 14(d), which states that data in a document must not conflict with data in any other stipulated document. While not all documents must match exactly, conflicting dates create a discrepancy that must be rejected.

Q4: How should a bank handle a document that references a "date of inspection" on an attached list?
A: Under ISBP 745 Section A11(b), this is deterministically acceptable if the reference clearly points to a specific date appearing on a stipulated document within the same presentation.

Q5: Is a document dated prior to the issuance of the credit acceptable?
A: Yes, UCP 600 Article 14(i) explicitly permits documents to be dated prior to the issuance of the credit, provided they are not dated later than the date of presentation.

Did You Know?

Article 14(i) establishes the fundamental boundary for all dates: "A document may be dated prior to the issuance date of the credit, but must not be dated later than its date of presentation.

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 A11 — 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