MT700 Field 53 and Its Relationship with UCP 600 Articles
Introduction
SWIFT MT700 Field 53 designates the reimbursing bank authorized to settle claims between the nominated bank and the issuing bank. This field operates at the intersection of SWIFT message formatting and UCP 600's reimbursement framework. When practitioners misunderstand how Field 53 relates to specific UCP 600 articles, reimbursement failures and interbank disputes follow.
Failure Modes
1. Field 53 Omits Reimbursement Bank Despite UCP 600 Article 13 Requirement
When Field 53 is left blank and the credit's reimbursement clause references Article 13, the nominated bank has no SWIFT-level instruction identifying the reimbursing bank. This creates operational uncertainty about where to direct reimbursement claims.
2. Field 53 Names a Bank Not Authorized Under the Credit's Reimbursement Clause
If the credit's text (separate from the SWIFT message) names one reimbursing bank but Field 53 names another, the nominated bank faces a conflict between the documentary credit instrument and the electronic transmission.
3. Field 53 References a Bank That Has No SWIFT Connectivity
A valid BIC code in Field 53 does not guarantee that the named bank participates in the SWIFT reimbursement network. If the bank cannot receive or process reimbursement messages, the nominated bank must seek alternative arrangements.
4. Field 53/Article 13 Interaction Creates Timing Risk
UCP 600 Article 13(a) places reimbursement risk on the nominated bank. If Field 53 names a reimbursing bank that becomes insolvent before honoring a claim, the nominated bank bears the loss. This risk is often underestimated when Field 53 is populated without due diligence on the reimbursing bank's creditworthiness.
Resolution Steps
-
Map Field 53 content to UCP 600 Articles 12 and 13 during the credit review process. Confirm that the reimbursing bank named in Field 53 is consistent with the credit's reimbursement clause.
-
Verify the reimbursing bank's SWIFT connectivity before relying on Field 53. Check the SWIFT BIC directory and confirm that the bank is an active participant.
-
When Field 53 is omitted, review the credit's reimbursement clause to determine whether the nominated bank can claim reimbursement directly from the issuing bank under Article 13(b).
-
Include a Field 53 risk assessment in your trade finance due diligence process. Evaluate the reimbursing bank's financial standing and operational capability.
-
Coordinate with the confirming bank (if any) to ensure that Field 53 aligns with the confirmation arrangement. Under Article 8(c), the confirming bank's reimbursement rights depend on a functional Field 53.
-
Document all Field 53-related decisions in your credit file, including the rationale for accepting or rejecting the named reimbursing bank.
-
Establish a fallback process for situations where the Field 53 bank cannot act, including direct reimbursement claims to the issuing bank under UCP 600 Article 13(b).
Conclusion
Field 53 is the SWIFT-level mechanism that activates UCP 600's reimbursement framework. Misunderstanding its relationship with Articles 8, 12, and 13 leads to reimbursement failures that can cascade through the entire documentary credit chain. Practitioners must treat Field 53 as a high-priority element requiring careful construction, validation, and ongoing monitoring.
Frequently Asked Questions
Q1: Which UCP 600 articles most directly govern Field 53?
Articles 8 (Confirming Bank Undertaking), 12 (Nomination), and 13 (Bank-to-Bank Reimbursement Arrangements) are the primary articles that interact with Field 53.
Q2: Can Field 53 be implied rather than explicitly stated?
No. SWIFT requires explicit field content. If Field 53 is blank, the reimbursing bank is not identified at the SWIFT level, regardless of what the credit text may say.
Q3: What is the relationship between Field 53 and Field 71a?
Field 71a specifies charge allocation, while Field 53 identifies the reimbursing bank. They are functionally separate but operationally linked, as the reimbursing bank's charges must be accounted for in Field 71a.
Q4: Does UCP 600 require a reimbursing bank to be named?
No. Article 13 provides that if no reimbursing bank is named, the nominated or claiming bank may claim reimbursement from the issuing bank. However, SWIFT practice strongly favors identifying a reimbursing bank in Field 53.
Q5: How should banks handle Field 53 when transferring a credit under UCP 600 Article 38?
When a credit is transferred, the transferring bank must ensure that Field 53 in the transferred MT702 reflects the appropriate reimbursing arrangement for the partial transfer.
Source Notes
The following sources were consulted as context only:
- Trade Finance Global, "Understanding MT 720: transfer of a documentary credit" (Jun 2024)
- 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, "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)
UCP 600 Article 8(c) states that a confirming bank is irrevocably bound as of the time it adds its confirmation, and its reimbursement rights depend on a functioning reimbursement chain.
| Regulation | Article / Section | Requirement | Consequence |
|---|---|---|---|
| UCP 600 | Article 12 | Nomination | Binary determination (compliant/discrepant) |
| UCP 600 | Article 13 | Bank-to-Bank Reimbursement Arrangements | Binary determination (compliant/discrepant) |
| UCP 600 | Article 8 | Confirming Bank Undertaking | Binary determination (compliant/discrepant) |
| UCP 600 | Article 38 | Transferable Credits | 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 53 and Its Relationship with UCP 600 Articles — 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