ISBP 745: What Changed from the Previous Publication

Introduction

Many trade finance practitioners assume that ISBP 745 is merely a refresh of the previous ISBP publication with cosmetic edits. This illusion collapses on the first audit: ISBP 745 introduced structural reorganizations, new paragraphs addressing electronic documents and electronic signatures, expanded guidance on non-documentary conditions, and explicit codification of previously ambiguous examination standards. Banks still applying the old ISBP logic under the current regime will generate discrepant-document claims that cannot survive scrutiny—the failure is systemic, not cosmetic.

This guide isolates the operative changes between the predecessor publication (ICC Publication 645) and the current ISBP 745 (ICC Publication 745), maps them to the relevant UCP 600 articles, and provides deterministic resolution pathways for practitioners who must comply with the current standard.

Failure Mode Analysis

Failure Mode 1: Misapplication of Original Document Standards Under Legacy Logic

The predecessor ISBP paragraph 16 stated that a document "bearing an apparently original signature, mark, stamp or label of the issuer" would be considered an original. ISBP 745 paragraph A27) expands this: "A document bearing an apparently original signature, mark, stamp or label of the issuer will be considered to be an original unless it states that it is a copy. Banks do not determine whether such a signature, mark, stamp or label of the issuer has been applied in a manual or facsimile form and, as such, any document bearing such method of authentication will satisfy the requirements of UCP 600 article 17."

The key mutation is the addition of the negative condition "unless it states that it is a copy." Under the predecessor standard, practitioners could argue that a document marked "copy" but bearing an original stamp was still an original. ISBP 745 truncates this ambiguity. The document's own declaration of copy status now overrides the physical appearance of authentication. Banks that fail to apply this binary test—does the document state it is a copy?—will misclassify documents and generate erroneous discrepancy claims.

Failure Mode 2: Non-Documentary Condition Treatment

The predecessor ISBP addressed non-documentary conditions in paragraph 12, providing that "a condition in a credit without stipulating a document to indicate compliance with the condition will be disregarded." ISBP 745 paragraph A26) refines this: "When a credit contains a condition without stipulating a document to indicate compliance therewith ('non-documentary condition'), compliance with such condition need not be evidenced on any stipulated document. However, data contained in a stipulated document are not to be in conflict with the non-documentary condition."

The operative language shift is significant. The predecessor's "will be disregarded" suggested total inapplicability. ISBP 745 acknowledges that non-documentary conditions exist and can still generate conflicts with stipulated documents. This is not a theoretical distinction—it isolates a failure mode where banks reject documents because data on a stipulated document conflicts with a non-documentary condition in the credit, even though the condition itself requires no documentary evidence.

Failure Mode 3: Certification and Authentication Standards

The predecessor ISBP provided limited guidance on how corrections and alterations should be authenticated across different document types. ISBP 745 paragraphs A7) through A9) establish a comprehensive framework: corrections in documents issued by the beneficiary "need not be authenticated," while corrections in documents issued by third parties "are to appear to have been authenticated by the issuer or an entity acting as agent, proxy or for [or on behalf of] the issuer."

This decoupling of beneficiary-issued versus third-party-issued document correction standards was absent from the predecessor. Banks applying the older standard either over-authenticate (requiring unnecessary stamps on beneficiary invoices) or under-authenticate (accepting unauthenticated corrections on carrier-issued documents). Both errors violate the current examination framework.

Deterministic Resolution Architecture

1. Audit existing document-checking procedures against ISBP 745 paragraph numbering. ISBP 745 reorganized paragraph references entirely. An examination checklist referencing "ISBP paragraph 16" is referencing the predecessor publication and is non-compliant. Recompile all internal procedures using ISBP 745's letter-numbered system (A1 through Q11).

2. Reclassify original-document determination. Apply ISBP 745 A27) as a binary gate: does the document state it is a copy? If yes, it is a copy regardless of stamps or signatures. If no, and it bears an apparently original signature/mark/stamp/label of the issuer, it is an original. No intermediate analysis is required.

3. Rebuild non-documentary condition handling. Adopt ISBP 745 A26) as the sole standard. Non-documentary conditions are not disregarded—they are conditions that do not require documentary evidence, but whose requirements must not be contradicted by data in stipulated documents. Train examiners to cross-reference non-documentary conditions against all stipulated document data.

4. Implement differential correction authentication. Separate the examination workflow into two tracks: (a) beneficiary-issued documents—corrections need no authentication per A7)(a)(i); (b) third-party-issued documents—corrections must be authenticated by issuer or authorized agent per A7)(b)(i). Over-authenticating beneficiary documents is a failure mode; under-authenticating third-party documents is a failure mode.

5. Update SWIFT message templates. Ensure that MT700 and MT769 messages referencing ISBP reflect the current publication number. A credit stating "subject to ISBP" without specifying 745 is ambiguous; best practice is to state "subject to UCP 600 and ISBP 745."

6. Establish a quarterly review cadence. ISBP 745 is a living publication subject to ICC Banking Commission Opinions and DOCDEX decisions. Schedule quarterly reviews of ICC Opinions affecting ISBP 745 interpretation to ensure examination procedures remain current.

Conclusion

The transition from the predecessor ISBP to ISBP 745 was a structural overhaul, not a version bump. The changes in original-document determination, non-documentary condition treatment, and correction-authentication standards introduced new compliance obligations that did not exist under the older standard. Banks and practitioners still operating under legacy procedures face a binary outcome: comply with ISBP 745 or generate discrepant-document claims that will not withstand ICC review.

The resolution is deterministic. Recompile internal procedures against ISBP 745's paragraph structure. Train examiners on the specific failure modes documented above. Establish a review cadence to track ICC Opinions. The illusion that ISBP 745 is "mostly the same" as the predecessor is the failure mode itself.

FAQ

Q1: Can a credit still reference the predecessor ISBP publication?

No. The predecessor ISBP ceased to have operative force upon ISBP 745's effective date (1 July 2013). Any credit subject to UCP 600 that references ISBP must reference ISBP 745. A credit referencing the predecessor would create ambiguity about which examination standards apply, and this ambiguity would be resolved in favor of the current publication—ISBP 745.

Q2: How does ISBP 745 change the treatment of copies of transport documents?

ISBP 745 paragraph A6) provides that when a credit requires a copy of a transport document covered by UCP 600 articles 19-25, "the relevant article is not applicable, as these articles only apply to original transport documents." The copy is examined only "to the extent expressly stated in the credit, otherwise according to UCP 600 sub-article 14 (f)." Additionally, copies of transport documents are "not subject to the default presentation period of 21 calendar days stated in UCP 600 sub-article 14 (c)." This treatment was not explicitly codified in the predecessor publication.

Q3: Does ISBP 745 require invoices to be signed?

No. ISBP 745 paragraph C10) states: "An invoice need not be signed or dated." This is consistent with UCP 600 article 18(a)(iv), which states a commercial invoice "need not be signed." The predecessor did not explicitly address this point in the invoice section.

Q4: How are corrections on drafts handled differently under ISBP 745?

ISBP 745 paragraph B16) states: "Any correction of data on a draft is to appear to have been authenticated with the addition of the signature or initials of the beneficiary." This is stricter than the general correction rule for beneficiary-issued documents (A7)(a)(i)), which states corrections "need not be authenticated." Drafts occupy a separate category requiring explicit beneficiary authentication of corrections. The predecessor did not make this distinction as clearly.

Q5: What does ISBP 745 say about misspellings and typing errors?

ISBP 745 paragraph A23) provides: "A misspelling or typing error that does not affect the meaning of a word or the sentence in which it occurs does not make a document discrepant." The example given: "mashine" instead of "machine" would not be a conflict under UCP 600 sub-article 14(d). However, "model 123" instead of "model 321" would be a conflict. This codified a principle that was inconsistently applied under the predecessor publication.