MT700 Field 59 — Beneficiary Name Exact Match

Introduction

SWIFT MT700 Field 59 identifies the beneficiary of the documentary credit — the party entitled to receive payment upon compliant document presentation. The beneficiary name in Field 59 must match exactly across all credit documents, particularly the commercial invoice and bill of lading. Even minor deviations in spelling, punctuation, or entity designation can trigger discrepancies that delay or prevent payment.

Failure Modes

1. Beneficiary Name in Field 59 Does Not Match Commercial Invoice
The most common discrepancy. If Field 59 uses "ABC Trading LLC" but the commercial invoice reads "ABC Trading Co., LLC," banks may raise a discrepancy even though both references identify the same entity.

2. Beneficiary Name in Field 59 Contains Typographical Error
A misspelling in Field 59 (e.g., "Ltd" instead of "Ltd.") creates a technical discrepancy that may be difficult to resolve after the credit is issued.

3. Beneficiary Name Mismatch Between Field 59 and Bill of Lading Consignee
If the bill of lading consignee references a different entity name than Field 59, the presenting bank may question whether the shipment was made for the credit's intended beneficiary.

4. Beneficiary Name Change Not Reflected in Amendment
When a beneficiary undergoes a legal name change (e.g., due to merger or rebranding), an MT707 amendment should update Field 59. Failure to do so creates a persistent discrepancy.

Resolution Steps

1. Use the beneficiary's exact legal name in Field 59, matching the name as registered with the relevant corporate authority.

2. Include a name-matching instruction in the credit's additional conditions (Field 47A) that specifies acceptable variations, such as abbreviations or trading names.

3. Pre-verify the Field 59 name against the beneficiary's KYC records and the underlying sales contract before transmitting the MT700.

4. When a discrepancy is raised for a minor name variation, invoke ISBP 745 paragraph A13 to argue that the variation does not affect the document's compliance.

5. Establish a beneficiary name-change protocol that includes an MT707 amendment workflow to update Field 59 when the beneficiary's legal name changes.

6. Maintain a beneficiary name database that maps legal names, trading names, and common abbreviations for each counterparty.

7. Train operators on the importance of exact name matching in Field 59 and the supporting documents, emphasizing that UCP 600 requires strict compliance for commercial invoices.

Conclusion

Field 59 beneficiary name exact matching is one of the most frequent sources of documentary credit discrepancies. The rigidity of the matching requirement, combined with the prevalence of name variations in international trade, creates a persistent challenge. Systematic name verification and proactive amendment procedures are the most effective tools for managing this risk.

Frequently Asked Questions

Q1: Does UCP 600 require an exact match between Field 59 and the commercial invoice?
Yes. Article 18(a) requires the commercial invoice to be issued by the beneficiary and to conform to the credit terms. The beneficiary name must match.

Q2: Can ISBP 745 paragraph A13 save me from a beneficiary name discrepancy?
Paragraph A13 allows for certain variations that do not affect the document's compliance. However, it is not a blanket exception. Minor variations (e.g., "Ltd" vs. "Limited") are typically acceptable, but significant variations (e.g., different legal entity) are not.

Q3: What should I do if Field 59 has a typo?
Request an MT707 amendment to correct Field 59. Presenting documents under a credit with an incorrect beneficiary name risks refusal.

Q4: Can multiple beneficiaries be named in Field 59?
No. Field 59 identifies a single beneficiary. If multiple beneficiaries are needed, consider a transferable credit under UCP Article 38 or multiple separate credits.

Q5: How does Field 59 interact with transferable credits?
When a credit is transferred under Article 38, the second beneficiary's name replaces the first beneficiary's name in Field 59 of the MT702 transfer message.

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)
• 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)