MT700 Field 59 — Contradictions with Other Fields

Introduction

SWIFT MT700 Field 59 identifies the beneficiary — the party entitled to payment under the documentary credit. When Field 59 contains information that contradicts other fields in the MT700 message, the credit's integrity is compromised, creating uncertainty about who is entitled to payment and under what conditions. This guide examines the most common Field 59 contradiction patterns and how to resolve them.

Failure Modes

1. Field 59 Names an Entity Different from Field 50's Implied Counterparty
If Field 50 names an applicant in Country A but Field 59 names a beneficiary in Country B with no apparent commercial relationship, the credit may be flagged for potential trade-based money laundering.

2. Field 59 Contradicts Field 48 (Presentation Period)
Field 48 may specify a presentation period based on a shipment date that implies a different beneficiary than the one named in Field 59, creating logistical confusion.

3. Field 59 BIC or Address Data Conflicts with Field 41 (Available With/By)
If Field 41 names a nominated bank that is not the beneficiary's bank, the payment routing may be inconsistent with the beneficiary's identity and location.

4. Field 59 Contradicts Field 77b (Amendments)
When an amendment (MT707) changes the beneficiary name in Field 59 but does not update related fields, the credit contains contradictory beneficiary information.

Resolution Steps

1. Cross-reference Field 59 against Field 50 to confirm a logical commercial relationship between the applicant and the beneficiary.

2. Verify Field 59 details against the beneficiary's KYC records to ensure the name, address, and country information are consistent.

3. When Field 59 is amended via MT707, review all other fields for consistency and issue additional amendments if contradictions arise.

4. Upon detecting a Field 59 contradiction, issue an MT799 clarification request to the issuing bank before processing the credit.

5. Maintain a Field 59 validation checklist that includes cross-referencing against Fields 41, 43P, 43Q, 47A, and 50.

6. Document all Field 59-related contradictions and resolutions in the credit file for audit and compliance purposes.

7. Implement automated field-consistency checks in your SWIFT messaging system that flag potential Field 59 contradictions before transmission.

Conclusion

Field 59 contradictions undermine the documentary credit's core function: ensuring that the correct party receives payment for compliant document presentation. Systematic validation, interbank communication, and amendment management are essential to maintaining Field 59 accuracy.

Frequently Asked Questions

Q1: Can Field 59 be blank in an MT700?
No. Field 59 is mandatory in all MT700 issuance messages. The beneficiary must always be identified.

Q2: What happens if Field 59 contradicts the beneficiary's bank records?
The beneficiary should contact the advising bank immediately to request clarification from the issuing bank before preparing documents.

Q3: Can Field 59 be changed after the credit is confirmed?
Yes, through an MT707 amendment. However, the confirming bank must consent to the amendment under Article 10.

Q4: How does Field 59 interact with Field 58 (Confirming Bank)?
Field 59 identifies the beneficiary, while Field 58 identifies the confirming bank. They serve different functions but must be consistent in the context of the credit.

Q5: Can Field 59 contain special characters or formatting?
SWIFT Field 59 supports standard alphanumeric characters. Special characters may cause processing issues and should be avoided.

Source Notes

The following sources were consulted as context only:

• Trade Finance Global, "UCP 600 – ultimate 2026 guide" (Jun 2020)
• Trade Finance Global, "ICC briefing addresses the topic of reducing discrepancy rates" (Aug 2022)
• The Daily Star, "The cost of a comma: Documentation errors are the 'hidden tax'" (Mar 2026)
• Trade Finance Global, "SWIFT Messaging Types | TFG 2026 Guide" (Apr 2020)
• ICC, "Examination of Documents, Waiver of Discrepancies and Notice" (Mar 2023)