MT700 Field 72 and Its Relationship with UCP
Introduction
SWIFT MT700 Field 72 carries sender-to-receiver information — free-format text that transmits supplementary instructions or information between banks. While this field is not governed by a specific UCP article, its content frequently interacts with the Uniform Customs and Practice for Documentary Credits (UCP) in ways that affect document examination, discrepancy handling, and interbank communication.
Failure Modes
1. Field 72 Uses Free-Format Text to Override UCP Provisions
If Field 72 contains instructions that effectively negate a UCP provision (e.g., stating that documents need not comply with the credit), the instruction may be unenforceable if not properly framed under Article 1(a).
2. Field 72 Contains Ambiguous Language That Contradicts UCP Certainty
Vague or unclear content in Field 72 creates interpretation problems that Article 14(a)'s examination standard cannot resolve, leading to inconsistency in how different banks handle the same credit.
3. Field 72 References ISBP or Other Rules Inconsistently
If Field 72 references ISBP 745 provisions but does so inaccurately, the resulting instruction may conflict with the actual ISBP content.
4. Field 72 Contains Instructions Intended for Only One Bank
When Field 72 carries instructions meant for a specific bank but the message is received by multiple parties, the other parties may misinterpret instructions not intended for them.
Resolution Steps
-
Treat Field 72 as supplementary to the UCP, not as a replacement for it. Use the field to clarify or add to UCP provisions, not to contradict them.
-
When Field 72 excludes or modifies a UCP provision, ensure the exclusion follows Article 1(a)'s requirements and is clearly worded.
-
Cross-reference Field 72 content against the UCP and ISBP to verify accuracy before transmission.
-
Label Field 72 content by intended recipient (e.g., "TO ADVISING BANK:" or "INFORMATION ONLY:") to prevent misinterpretation.
-
Establish a Field 72 content standard for your organization that specifies acceptable use cases and prohibited content.
-
When Field 72 contradicts the UCP, issue an MT707 amendment to resolve the conflict rather than relying on Field 72's informal character.
-
Document all Field 72-related decisions in the credit file, including the rationale for content that modifies or supplements UCP provisions.
Conclusion
Field 72's relationship with the UCP is defined by its supplementary nature. When used correctly, Field 72 clarifies the UCP's application to specific transactions. When used incorrectly, Field 72 creates contradictions that undermine the UCP framework. Banks that establish clear content standards and validation protocols for Field 72 can harness its flexibility without compromising the UCP's integrity.
Frequently Asked Questions
Q1: Can Field 72 be used to modify UCP 600 Article 14(a)?
Under Article 1(a), parties can agree to exclude or modify certain UCP provisions. Field 72 can communicate such modifications, but they must be clearly stated and agreed upon by all parties.
Q2: How does Field 72 interact with ISBP 745?
Field 72 can reference ISBP 745 provisions, but the references must be accurate. Incorrect ISBP references in Field 72 can create confusion about applicable standards.
Q3: Is Field 72 binding on the receiving bank?
Field 72 content is informational. Unlike Field 49 or Field 78, Field 72 does not carry mandatory instructional authority. However, receiving banks should treat it as indicative of the issuing bank's intent.
Q4: Can Field 72 contain SWIFT system messages?
Yes. Field 72 is commonly used for SWIFT-related information, such as message authentication data or system-generated notes.
Q5: What is the risk of leaving Field 72 blank?
A blank Field 72 is permissible and creates no inherent risk. However, if the credit requires Field 72 content (e.g., for special instructions), omitting it may cause processing issues.
Source Notes
The following sources were consulted as context only:
- Trade Finance Global, "UCP 600 – ultimate 2026 guide" (Jun 2020)
- Trade Finance Global, "Modifications and exclusions in commercial Letters of Credit Issued under UCP 600" (Oct 2021)
- Trade Finance Global, "SWIFT Messaging Types | TFG 2026 Guide" (Apr 2020)
- ICC, "ICC's new rules on documentary credits now available" (Mar 2023)
- Trade Finance Global, "ICC briefing addresses the topic of reducing discrepancy rates" (Aug 2022)
Article 1(a) allows parties to exclude or modify UCP provisions, and Field 72 is sometimes used to communicate such exclusions.
| Regulation | Article / Section | Requirement | Consequence |
|---|---|---|---|
| UCP 600 | Article 1 | Scope of the Rules | Binary determination (compliant/discrepant) |
| UCP 600 | Article 14 | Standard for Examination of Documents | Binary determination (compliant/discrepant) |
| UCP 600 | Article 16 | Discrepant Documents, Waiver and Notice | Binary determination (compliant/discrepant) |
← Scroll horizontally to see all columns
Quick Reference Summary
- No reference captured.
Compliance Checklist
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 MT700 Field 72 and Its Relationship with UCP — 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