MT700 Field 72 and Its Relationship with UCP 600 Articles

Introduction

SWIFT MT700 Field 72 carries sender-to-receiver information — free-format text that transmits supplementary instructions or information between banks. While Field 72 is not governed by a specific UCP article, its content frequently interacts with UCP provisions on document examination, discrepancy handling, and charge allocation. Understanding these interactions is essential for preventing Field 72 content from undermining the UCP framework.

Failure Modes

1. Field 72 Content Contradicts Article 14(a) Examination Standard
If Field 72 instructs the examining bank to apply a different standard than Article 14(a) (e.g., requiring examination beyond the documents alone), the instruction conflicts with the UCP.

2. Field 72 References Article 16 Discrepancy Procedures Incorrectly
If Field 72 contains instructions that deviate from Article 16's five options for handling discrepant documents, the receiving bank cannot determine the correct course of action.

3. Field 72 Contains Force Majeure References Inconsistent with Article 36
If Field 72 includes force majeure provisions that contradict Article 36's treatment of impediments, the parties may disagree on their rights and obligations during a force majeure event.

4. Field 72/Article 37 Third-Party Document Instruction Conflict
If Field 72 requires third-party documents but contradicts Article 37's requirements for such documents, the beneficiary may present documents that are technically compliant with Field 72 but non-compliant with Article 37.

Resolution Steps

1. Review Field 72 content against all applicable UCP articles before transmitting the MT700. Ensure no instruction contradicts the UCP framework.

2. When Field 72 references a specific UCP article, verify that the reference is accurate and the instruction is consistent with the article's actual content.

3. Reserve Field 72 for content that supplements the UCP rather than contradicts or overrides it. The UCP's comprehensive framework should be the primary reference for credit terms.

4. When a Field 72/UCP contradiction is detected, issue an MT707 amendment to resolve the conflict before the credit becomes operative.

5. Establish a Field 72 content review step in your MT700 creation workflow, conducted by an operator familiar with UCP 600 provisions.

6. Maintain a list of prohibited Field 72 content that is known to conflict with UCP provisions, and use this list as a pre-transmission checklist.

7. Train operators on the UCP articles that Field 72 content most commonly interacts with, including Articles 14, 16, 36, and 37.

Conclusion

Field 72's lack of direct UCP assignment makes it the most flexible and potentially problematic field in the MT700 message. Banks that treat Field 72 as a supplementary information field — rather than a vehicle for substantive credit terms — can avoid contradictions that undermine the UCP framework. Careful content review and operator training are essential safeguards.

Frequently Asked Questions

Q1: Does UCP 600 address Field 72 directly?
No. UCP 600 does not assign a specific article to Field 72. The field is a SWIFT convention for free-format information exchange.

Q2: Can Field 72 contain terms that override the UCP?
UCP 600 Article 1(a) allows parties to exclude or modify certain UCP provisions. Field 72 could contain such exclusions, but they must be clearly stated and consistent with the UCP's permissive exclusion framework.

Q3: How does Field 72 interact with Field 47A?
Field 72 and Field 47A both carry additional conditions. Field 47A is the primary field for credit conditions; Field 72 is supplementary. They should be consistent.

Q4: Can Field 72 contain legal references or jurisdiction clauses?
Yes. Field 72 is commonly used to specify governing law or jurisdiction. However, these references must be consistent with the credit's terms and the UCP.

Q5: What is the best practice for Field 72 content length?
SWIFT allows up to 35 x 50 characters in Field 72. However, shorter, clearer content reduces the risk of errors and contradictions. Avoid unnecessary verbosity.

Source Notes

The following sources were consulted as context only:

• Trade Finance Global, "UCP 600 – ultimate 2026 guide" (Jun 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)
• Trade Finance Global, "SWIFT Messaging Types | TFG 2026 Guide" (Apr 2020)
• Trade Finance Global, "Modifications and exclusions in commercial Letters of Credit Issued under UCP 600" (Oct 2021)