MT700 Field 53 — Contradictions with Other Fields
Introduction
SWIFT MT700 Field 53 identifies the reimbursing bank — the institution authorized to honor reimbursement claims from the nominated or confirming bank. When Field 53 contains information that conflicts with other fields in the same MT700 message, the reimbursement chain breaks down, causing payment delays and interbank disputes. This guide examines how Field 53 contradictions arise and how to resolve them.
Failure Modes
1. Field 53 Names a Bank Different from Field 49's Reimbursement Direction
Field 49 may direct reimbursement through one bank while Field 53 names another. The nominated bank receiving conflicting instructions faces an impossible choice between two authoritative fields.
2. Field 53 BIC Code Does Not Match the Bank Named in Field 49
Even when both fields reference the same institution, a mismatched BIC code (due to data entry error) creates a technical contradiction that SWIFT's validation layer may not catch if the BIC is structurally valid but refers to a different branch.
3. Field 53 Is Populated but Field 49 Omits Reimbursement Instructions
When Field 53 specifies a reimbursing bank but Field 49 is silent on reimbursement, the nominated bank must determine whether Field 53 alone is sufficient authorization to claim reimbursement.
4. Field 53 Contradicts Field 32B (Currency and Amount)
If Field 53 references a reimbursement in a currency different from the credit currency in Field 32B, the reimbursing bank may refuse the claim on currency mismatch grounds.
Resolution Steps
-
Validate Field 53 against Field 49 during the MT700 construction process. Both fields should reference the same reimbursing institution and method.
-
Verify the BIC code in Field 53 against SWIFT's BIC directory to confirm it resolves to the intended bank and branch.
-
When Field 53 is populated, ensure Field 49 either explicitly references the same reimbursement arrangement or does not contain contradictory instructions.
-
Upon receiving an MT700 with a Field 53/Field 49 contradiction, send an MT799 clarification request to the issuing bank before initiating reimbursement.
-
Maintain a reimbursing bank verification database that cross-references bank names, BIC codes, and SWIFT connectivity status. Use this to validate Field 53 entries.
-
Include Field 53 in your document examination checklist. Ensure that reimbursement instructions are consistent across all relevant fields before processing.
-
Establish escalation procedures for Field 53 contradictions that cannot be resolved through standard interbank communication channels.
Conclusion
Field 53 contradictions disrupt the reimbursement chain that underpins documentary credit operations. They typically arise from data entry errors, incomplete message construction, or failure to maintain consistency across instructional fields. Rigorous validation and clear interbank communication are essential to preventing and resolving these contradictions.
Frequently Asked Questions
Q1: Is Field 53 mandatory in an MT700?
No. Field 53 is optional. However, when included, its content must be consistent with other instructional fields. An omitted Field 53 does not prevent reimbursement but may require the nominated bank to seek alternative arrangements.
Q2: What happens if the reimbursing bank named in Field 53 refuses to act?
Under UCP 600 Article 13(a), the nominated or confirming bank bears the risk if the reimbursing bank is unable or unwilling to reimburse. The bank should seek direct reimbursement from the issuing bank.
Q3: Can Field 53 be amended after the credit is issued?
Yes, through an MT707 amendment. The issuing bank sends the amendment, and it becomes effective upon the beneficiary's acceptance (unless the credit states otherwise).
Q4: Does Field 53 override Field 49 on reimbursement matters?
There is no established hierarchy. When the two fields conflict, the receiving bank should seek clarification from the issuing bank rather than assuming one field controls.
Q5: How does Field 53 interact with Field 71a (Charges)?
Field 71a specifies who bears the charges. If Field 71a states that all charges are for the beneficiary's account but Field 53 directs reimbursement through a bank that charges the applicant, a cost allocation contradiction may arise.
Source Notes
The following sources were consulted as context only:
- Trade Finance Global, "UCP 600 – ultimate 2026 guide" (Jun 2020)
- 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, "Understanding MT 720: transfer of a documentary credit" (Jun 2024)
- Trade Finance Global, "ICC briefing addresses the topic of reducing discrepancy rates" (Aug 2022)
Article 13(a) states that banks are not obligated to honor a reimbursement claim if the reimbursing bank named in the credit is unable or unwilling to act.
| Regulation | Article / Section | Requirement | Consequence |
|---|---|---|---|
| UCP 600 | Article 13 | Bank-to-Bank Reimbursement Arrangements | 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 — 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