MT700 Field 53 and Its Relationship with UCP
Introduction
SWIFT MT700 Field 53 specifies the reimbursing bank — the institution authorized to process reimbursement claims between banks involved in a documentary credit transaction. Understanding how Field 53 connects to the Uniform Customs and Practice for Documentary Credits (UCP) is essential for preventing reimbursement failures and ensuring that the bank-to-bank payment chain operates without interruption.
Failure Modes
1. Field 53 Names a Bank That Cannot Act as Reimbursing Bank
Not all banks are authorized or equipped to serve as reimbursing banks. If Field 53 references an institution without the necessary SWIFT connectivity or internal authorization, the reimbursement claim cannot be processed.
2. UCP Reimbursement Clause and Field 53 Disagree
The credit's text may specify one reimbursement arrangement while Field 53 transmits a different one. Since UCP 600 Article 1(a) treats the credit as separate from the underlying contract, the SWIFT message and the credit text can create conflicting obligations.
3. Field 53 Omission Leaves Reimbursement Unspecified
When Field 53 is left blank and no alternative reimbursement mechanism is specified in the credit, the nominated bank must determine whether it can claim directly from the issuing bank under UCP Article 13(b).
4. Confirmation and Field 53 Interaction Gap
If a confirming bank adds its confirmation but Field 53 does not identify a reimbursing bank, the confirming bank's reimbursement rights under UCP Article 8 are functionally impaired.
Resolution Steps
-
Before issuing the MT700, confirm that the institution named in Field 53 is an active SWIFT participant with reimbursement capabilities.
-
Cross-reference the credit's reimbursement clause with Field 53 to ensure both specify the same reimbursing bank.
-
When Field 53 is blank, document the reimbursement arrangement explicitly in the credit's additional conditions (Field 47A) to avoid ambiguity.
-
Coordinate with confirming banks to ensure they are aware of and comfortable with the Field 53 designation before adding confirmation.
-
Implement a Field 53 validation step in your MT700 creation workflow. This step should verify the BIC, confirm SWIFT connectivity, and check alignment with the credit's reimbursement clause.
-
Establish a direct reimbursement fallback for situations where the Field 53 bank is unable to act, ensuring compliance with UCP Article 13(b).
-
Maintain records of all Field 53-related decisions to support audit trails and regulatory compliance.
Conclusion
Field 53 is the operational bridge between UCP reimbursement theory and SWIFT message practice. Banks that treat Field 53 as a mere formality risk reimbursement failures that cascade through the documentary credit chain. Proper alignment between Field 53 and the UCP articles that govern reimbursement is a foundational requirement for sound trade finance operations.
Frequently Asked Questions
Q1: Is Field 53 always required in an MT700?
No. Field 53 is optional under SWIFT rules. However, its omission may create reimbursement uncertainty, particularly when the credit does not specify an alternative reimbursement mechanism.
Q2: What UCP articles are most relevant to Field 53?
Articles 2 (Definitions), 12 (Nomination), and 13 (Bank-to-Bank Reimbursement Arrangements) are the primary UCP provisions that interact with Field 53.
Q3: Can the nominated bank change the Field 53 bank after issuance?
No. Only the issuing bank can change Field 53 through an MT707 amendment. The nominated bank must seek an amendment if the Field 53 bank is unsuitable.
Q4: How does Field 53 interact with Field 49?
Field 49 provides instructions to the paying/accepting/negotiating bank, while Field 53 identifies the reimbursing bank. They should be consistent but serve different functions in the payment chain.
Q5: What risk does the nominated bank assume under UCP Article 13 if Field 53 names an unreliable bank?
Under Article 13(a), the nominated bank bears the risk that the reimbursing bank may be unable or unwilling to honor the claim. Due diligence on the Field 53 bank is therefore essential.
Source Notes
The following sources were consulted as context only:
- Trade Finance Global, "UCP 600 – ultimate 2026 guide" (Jun 2020)
- Trade Finance Global, "Understanding MT 720: transfer of a documentary credit" (Jun 2024)
- 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)
Article 13 establishes the bank-to-bank reimbursement framework and specifies the obligations of the reimbursing bank.
| Regulation | Article / Section | Requirement | Consequence |
|---|---|---|---|
| UCP 600 | Article 2 | Definitions | Binary determination (compliant/discrepant) |
| 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 1 | Scope of the Rules | Binary determination (compliant/discrepant) |
| UCP 600 | Article 8 | Confirming Bank Undertaking | 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 — 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