ISBP 745: Two or More Languages — When Multi-Language Documents Violate the Credit

Introduction

The trade finance industry operates under a persistent illusion: that presenting documents in two or more languages is inherently safer than presenting in one. This illusion collapses into a binary failure mode when a confirming bank or nominated bank exercises its right to restrict acceptable languages, or when data inserted in an unauthorized language creates a conflict that triggers refusal. The multi-language trap is deterministic—it operates through ISBP 745 paragraph A21's six sub-paragraphs, each of which truncates or expands the bank's examination obligation in precise, non-negotiable ways.

This guide compiles the deterministic rules governing language compliance, isolates the three primary failure modes that mutate multi-language presentations into discrepant ones, and provides a numbered resolution architecture that eliminates ambiguity in practice.

Failure Mode Analysis

Failure Mode 1: The Confirming Bank Language Restriction

The most common failure mode occurs when the credit states "documents in English or French acceptable" and the beneficiary prepares all documents in both languages. The confirming bank, upon receiving the credit, exercises its right under ISBP 745 paragraph A21(c)(i) to restrict acceptable languages to English only. The restriction is communicated to the beneficiary via the advising bank, but the beneficiary's documents are already prepared. The presentation arrives with French-language data throughout. The bank refuses. The beneficiary's argument—that the credit allowed French—is irrelevant. The confirming bank's restriction operates as a condition of its engagement, and the beneficiary's obligation is to comply with that condition. The restriction is deterministic: once exercised, it truncates the credit's language allowance unilaterally.

Failure Mode 2: The Dual-Language Conflict

This failure mode isolates presentations where the credit allows multiple languages and the bank does not restrict, but the data in the two languages conflicts. A commercial invoice shows "10 metric tons" in English and "10 tonnes métriques" in French. The terms appear equivalent but the numerical values differ due to a translation error—English shows 10,000 kg while French shows 10,500 kg. Under ISBP 745 paragraph A21(c)(ii), the bank must examine data in both languages. Under UCP 600 article 14(d), the conflict between the two language versions triggers refusal. The beneficiary's position is that the French version is merely supplementary. The bank's position is deterministic: both versions are data, both must be examined, and a conflict between them is a discrepancy.

Failure Mode 3: The Unauthorized Language Assumption

This failure mode occurs when the credit is silent on language (A21(b)) and the beneficiary presents documents in three languages, assuming all three will be examined. The bank examines only the language it deems primary. Data in the third language—containing a quantity that conflicts with the primary language—is not examined under A21(d). The beneficiary later discovers the error, but the bank has already honoured based on the data it examined. The beneficiary's recourse against the third-language party is outside the credit's framework. The bank's examination obligation was limited to what it was required or allowed to examine—and a third language beyond the credit's scope falls outside that obligation.

Deterministic Resolution Architecture

1. Pre-Presentation Language Audit. Before preparing documents, determine whether the credit stipulates a language (A21(a)), is silent (A21(b)), or allows multiple languages. If the credit allows multiple languages, check whether the confirming or nominated bank has communicated a restriction under A21(c)(i). This restriction may arrive via the advising bank's cover letter, SWIFT message, or direct communication. If a restriction exists, prepare all data in the restricted language only.

2. Single-Language Data Protocol. When the credit allows multiple languages and no bank restriction exists, prepare data in a single language per document. Avoid embedding the same data in two languages within the same document. This eliminates the dual-language conflict surface area entirely. Use the credit's stipulated language as the primary data language.

3. Pre-Printed Text Isolation. Recognize that pre-printed field headings, stamps, endorsements, and names are exempt from the credit's language requirement under A21(e). Do not translate these elements. Do not treat their presence in a non-credit language as a discrepancy. Isolate them from the data examination scope.

4. Silent Credit Default. When the credit is silent on language (A21(b)), select a single language for all data and maintain consistency across all stipulated documents. Do not assume the bank will examine data in multiple languages. Under A21(d), the bank is not required to examine data in languages beyond what the credit requires or allows.

5. Multi-Language Conflict Scan. When a document legitimately contains data in two or more acceptable languages, perform a pre-presentation conflict scan. Verify that numerical values, quantities, weights, dates, and amounts are identical across all language versions. Any discrepancy between language versions will trigger refusal under UCP 600 article 14(d), regardless of which language the bank considers primary.

6. Confirming Bank Restriction Monitoring. For confirmed credits, monitor the advising bank's communication for any restriction exercised under A21(c)(i). The restriction operates as a condition of the confirming bank's engagement. If the restriction arrives after document preparation, determine whether re-preparation is feasible within the presentation window. If not, consider presenting only to the issuing bank (which has not restricted), accepting the risk of the confirming bank's restriction.

7. Post-Refusal Language Analysis. When a bank refuses and cites a language-related discrepancy, verify whether the bank's examination was consistent with A21(c)(ii) (examination of all acceptable languages) or A21(d) (non-examination of unauthorized language data). If the bank failed to examine data in an acceptable language it did not restrict, the refusal may be invalid under the ISBP framework. If the bank refused based on data in an unauthorized language, the refusal may be invalid under A21(d).

Conclusion

The multi-language document regime under ISBP 745 paragraph A21 is a deterministic system with binary outcomes. The credit's language stipulation, the confirming bank's restriction right, and the examination obligations under A21(c)(ii) and A21(d) operate as independent constraints that truncate or expand the presenter's obligations in precise, non-negotiable ways. The pre-printed text exception under A21(e) is the sole carve-out, and it is narrowly scoped. Trade finance practitioners who treat multi-language documents as inherently safer than single-language documents are compiling conflict risk into their transaction architecture by design.

FAQ

Q1: Can a confirming bank restrict languages after the beneficiary has already prepared documents?

A: Yes. Under ISBP 745 paragraph A21(c)(i), the confirming bank's restriction operates as a condition of its engagement. The restriction may be communicated at any time—there is no deadline tied to the credit's issuance or the beneficiary's document preparation. The beneficiary must comply with the restriction at the time of presentation, regardless of when it was communicated.

Q2: Does the bank have to examine data in all languages if the credit allows multiple languages?

A: Only if the confirming or nominated bank has not exercised its restriction right under A21(c)(i). If the bank does not restrict, then under A21(c)(ii), it must examine data in ALL acceptable languages appearing in the documents. If the bank has restricted, only data in the restricted language(s) is examined.

Q3: What happens if a document contains data in a language not allowed by the credit?

A: Under ISBP 745 paragraph A21(d), the bank does not examine data inserted in a language additional to that required or allowed in the credit. However, if that unauthorized-language data creates a visible conflict with data in an authorized language, the bank may still detect and refuse the discrepancy under UCP 600 article 14(d).

Q4: Are stamps, endorsements, and field headings subject to the credit's language requirement?

A: No. Under ISBP 745 paragraph A21(e), the name of a person or entity, any stamps, legalization, endorsements, and pre-printed text (including field headings) may be in a language other than that required in the credit. These elements are part of the document's format, not the presenter's data.

Q5: If the credit is silent on language, can the bank refuse documents because they are not in the bank's preferred language?

A: No. Under ISBP 745 paragraph A21(b), when the credit is silent regarding language, documents may be issued in any language. The bank has no basis to refuse based on language preference. The bank's examination is limited to data consistency under UCP 600 article 14(d), not language choice.