Pre-Advice vs. Operative Credit: When the Issuing Bank's Binding Obligation Commences Under UCP 600 Article 11
Introduction
A beneficiary receives an SWIFT message from the issuing bank. It states the credit amount, the goods description, and the expiry date. The beneficiary ships the goods, compiles the document set, and presents it to the nominated bank. The nominated bank forwards the documents. The issuing bank refuses. Its reason: the message received was a pre-advice, not the operative credit. No binding obligation existed. The beneficiary's entire shipment — and its cost — is now exposed.
This is not a hypothetical. It is a systemic failure mode that recurs across documentary credit practice. The confusion between a pre-advice and an operative teletransmission is one of the most damaging misapprehensions in trade finance. The distinction is binary: one message creates an irrevocable undertaking; the other creates a commitment to create an undertaking. The beneficiary who conflates the two violates a foundational principle of UCP 600 — that a bank's obligation arises only from the operative credit, not from preliminary communications.
Failure Mode Analysis
Failure Mode 1: Treating a Pre-Advice as the Operative Credit
The beneficiary receives a SWIFT message (often MT 799 or MT 798 — free-format messages, not the MT 700 operative format) containing credit terms. The beneficiary ships. The documents are presented. The issuing bank refuses, citing the absence of an operative credit.
Root cause: The beneficiary failed to verify whether the message was the operative credit or a pre-advice. The use of free-format SWIFT messages (MT 799) rather than the structured MT 700 format is a binary signal: MT 700 is the operative instrument; MT 799 is not. The beneficiary who ignores this distinction assumes an obligation that does not exist.
Impact: The beneficiary bears the full cost of shipment, insurance, and document preparation with no recourse against the issuing bank. The only recourse is against the applicant under the underlying contract — a fundamentally different and weaker legal position.
Failure Mode 2: "Full Details to Follow" Treated as Non-Binding
The issuing bank transmits an MT 700 containing the phrase "FULL DETAILS TO FOLLOW" in Field 79 (narrative). The beneficiary assumes the MT 700 is operative because it uses the correct SWIFT message type. The beneficiary ships. The issuing bank later issues the operative credit with different terms — a later expiry date, a different goods description, or a reduced amount.
Root cause: The "full details to follow" language in Article 11(a) is a statutory carve-out that mutates an otherwise operative teletransmission into a non-operative announcement. The SWIFT message type (MT 700) is necessary but not sufficient for operative status. The narrative content determines operative status.
Impact: The beneficiary's presentation may comply with the pre-advice but not with the subsequent operative credit. The issuing bank is within its rights to refuse. The beneficiary's protection is Article 11(a)'s requirement that the operative credit be issued "in terms not inconsistent with the teletransmission" — but "not inconsistent" is a narrower constraint than "identical." The operative credit may differ in non-inconsistent ways that nonetheless invalidate the beneficiary's documents.
Failure Mode 3: Pre-Advice Received but Operative Credit Never Issued
The issuing bank sends a pre-advice. The beneficiary waits. Days pass. Weeks pass. The operative credit never arrives. The beneficiary contacts the advising bank, which confirms it has received nothing further.
Root cause: The issuing bank has violated Article 11(b)'s commitment to issue the operative credit "without delay." The pre-advice creates an irrevocable commitment — but the beneficiary has no direct mechanism under UCP 600 to compel issuance. The beneficiary's remedy is contractual (against the applicant) and potentially through ICC's DOCDEX dispute resolution process, but not through the documentary credit mechanism itself.
Impact: The beneficiary's commercial position deteriorates. The delay may cause the beneficiary to miss production deadlines, lose warehouse space, or breach the underlying contract. The pre-advice, while binding on the issuing bank to issue the operative credit, provides the beneficiary with no payment mechanism in the interim.
Deterministic Resolution Architecture
1. Verify the SWIFT message type before acting. The operative credit is transmitted via MT 700 (or MT 701 for续展). Free-format messages (MT 799, MT 798) are pre-advices or ancillary communications, not operative instruments. This is a binary determination — MT 700 is operative; everything else is not.
2. Scan the teletransmission for "full details to follow" or equivalent language. If present in Field 79 (narrative) or any other field, the teletransmission is not operative regardless of the SWIFT message type. Article 11(a) is explicit: the presence of this language truncates the operative effect of the teletransmission.
3. Confirm the operative credit has been issued before shipping. The beneficiary should not ship goods until it has received and verified the operative credit. If a pre-advice is received, the beneficiary should contact the advising bank to confirm receipt of the operative credit. The pre-advice's "without delay" requirement (Article 11(b)) is a commitment on the issuing bank, but the beneficiary's commercial risk is not mitigated by that commitment until the operative credit exists.
4. Cross-reference the operative credit against the pre-advice. Article 11(b) requires the operative credit to be issued "in terms not inconsistent with the pre-advice." The beneficiary should compare the two documents. Material differences — different expiry dates, different amounts, different goods descriptions — that are "not inconsistent" (i.e., the operative credit adds terms or modifies non-essential details) may still invalidate the beneficiary's pre-advice-based understanding. The beneficiary must comply with the operative credit, not the pre-advice.
5. Preserve the pre-advice as evidence of the issuing bank's commitment. If the issuing bank fails to issue the operative credit within a reasonable time, the pre-advice is evidence of the bank's irrevocable commitment under Article 11(b). This evidence supports a DOCDEX claim or contractual remedy against the issuing bank. Archive the SWIFT message with its transmission timestamp and BIC (Bank Identifier Code).
6. Do not present documents against a pre-advice. A presentation requires an operative credit. Presenting documents against a pre-advice is a fundamental error — the pre-advice does not constitute an undertaking to honour. The examining bank will refuse the presentation, and the refusal is correct under UCP 600.
Conclusion
The distinction between a pre-advice and an operative credit is not a matter of banking convention — it is a statutory determination under UCP 600 Article 11. The operative teletransmission creates a binding obligation; the pre-advice creates a binding commitment to create an obligation. These are two different legal states, and the beneficiary who conflates them assumes commercial risk with no corresponding documentary credit protection. The resolution architecture is deterministic: verify the SWIFT message type, scan for "full details to follow," confirm the operative credit exists, and never present documents against a pre-advice.
FAQ
Q: Is a pre-advice enforceable if the issuing bank fails to issue the operative credit?
A: Yes, but not through the documentary credit mechanism. Article 11(b) states the issuing bank is "irrevocably committed to issue the operative credit or amendment, without delay, in terms not inconsistent with the pre-advice." This commitment is enforceable through ICC's DOCDEX dispute resolution (ICC Publication 811) or through the underlying contractual relationship. However, the pre-advice itself does not constitute an undertaking to pay — the beneficiary cannot present documents against it.
Q: Can the beneficiary ship goods based on a pre-advice?
A: The beneficiary may commercially choose to ship, but it does so without documentary credit protection. The pre-advice does not create an undertaking to honour. If the operative credit is never issued, or is issued with different terms, the beneficiary's recourse is limited to the underlying contract and the issuing bank's commitment under Article 11(b). Prudent practice requires confirmation of the operative credit before committing to shipment.
Q: What SWIFT message types constitute a pre-advice versus an operative credit?
A: The operative credit is transmitted via MT 700 (Issue of a Documentary Credit) or MT 701 (Issue of a Documentary Credit — Multiple Messages). Pre-advices are typically transmitted via MT 799 (Free Format Message) or MT 798 (Free Format Message for Banks). The SWIFT message type is a strong indicator, but Article 11(a) looks to the content, not the message type: an MT 700 containing "full details to follow" is not operative.
Q: What does "in terms not inconsistent with the pre-advice" mean in practice?
A: The operative credit must not contradict the pre-advice. The issuing bank may add terms, increase coverage, or extend the expiry — but it cannot reduce the amount below the pre-advice amount, shorten the expiry date, or change the goods description in a way that contradicts the pre-advice. "Not inconsistent" is a negative constraint: it prohibits contradiction, not deviation. The operative credit may differ from the pre-advice in ways that are merely non-identical, as long as they are not contradictory.
Q: Can the beneficiary request that the pre-advice be upgraded to an operative credit?
A: The beneficiary can request, but the issuing bank is not obligated to convert a pre-advice into an operative credit at the beneficiary's request. Article 11(b) places the obligation on the issuing bank to issue the operative credit "without delay" — this is a bank-side commitment, not a beneficiary-initiated process. The beneficiary's appropriate course of action is to contact the advising bank to confirm the operative credit has been received.
Article 11(b) requires the operative credit to be issued "in terms not inconsistent with the pre-advice.
| Regulation | Article / Section | Requirement | Consequence |
|---|---|---|---|
| UCP 600 | Article 11 | Teletransmission and Pre-Advice | Binary determination (compliant/discrepant) |
| UCP 600 | Article 7 | Issuing Bank Undertaking | Binary determination (compliant/discrepant) |
← Scroll horizontally to see all columns
Quick Reference Summary
- No reference captured.
Compliance Checklist
| ✓ What Banks Expect | ✗ What Beneficiaries Often Do Wrong |
|---|---|
| Treating a Pre-Advice as the Operative Credit | The beneficiary receives a SWIFT message (often MT 799 or MT 798 — free-format messages, not the ... |
| "Full Details to Follow" Treated as Non-Binding | The issuing bank transmits an MT 700 containing the phrase "FULL DETAILS TO FOLLOW" in Field 79 (... |
| Pre-Advice Received but Operative Credit Never Issued | The issuing bank sends a pre-advice. The beneficiary waits. Days pass. Weeks pass. The operative ... |
← Scroll horizontally to see all columns
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 generates compliant Pre-Advice vs. Operative Credit — 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