SWIFT

MT700 Field 59 and Its Relationship with UCP

📅 2026-07-13 4 min read UCP 600 / ISBP 745

Introduction

SWIFT MT700 Field 59 identifies the beneficiary — the party in whose favor a documentary credit is issued and who is entitled to payment upon presenting complying documents. The relationship between Field 59 and the Uniform Customs and Practice for Documentary Credits (UCP) determines the beneficiary's legal position, the banks' examination obligations, and the overall enforceability of the credit.

Failure Modes

1. Field 59 Does Not Identify the True Beneficiary Under Article 2
If Field 59 names a party other than the one entitled to payment under the underlying contract, the UCP's beneficiary protections do not apply to the correct party. This creates legal uncertainty and potential fraud risk.

2. Field 59/Article 18(a) Commercial Invoice Mismatch
Article 18(a) requires the commercial invoice to be issued by the beneficiary. If Field 59 and the invoice name differ, the bank must determine whether the variation constitutes a discrepancy under Article 14(a).

3. Field 59 Contradicts Article 16 Discrepancy Handling
When Field 59 contains an error that causes document discrepancy notices under Article 16, the beneficiary must decide whether to accept the refusal or negotiate with the applicant.

4. Field 59/Article 38 Transfer Failure
When a transferable credit is transferred under Article 38, Field 59 in the MT702 must accurately identify the second beneficiary. Errors in this field can prevent the transfer from taking effect.

Resolution Steps

  1. Confirm that Field 59 identifies the party entitled to payment under the underlying commercial contract. Use the exact legal name as registered with the relevant authority.

  2. Cross-reference Field 59 against Article 18(a) requirements by verifying that the beneficiary name on the commercial invoice will match Field 59 exactly.

  3. When Field 59 is amended, verify that the amendment is properly transmitted via MT707 and that all parties (issuing bank, advising bank, confirming bank) receive the amendment.

  4. Establish a Field 59 validation protocol that checks the name against the beneficiary's KYC records, the sales contract, and the advising bank's records before transmitting the MT700.

  5. When a discrepancy is raised based on Field 59 data, assess whether ISBP 745 paragraph A13 provides a basis for accepting the variation.

  6. For transferable credits, ensure that Field 59 in the MT702 accurately identifies the second beneficiary and that the transfer complies with Article 38 requirements.

  7. Maintain a Field 59 audit trail that records all changes throughout the credit lifecycle, including amendments and their consent status.

Conclusion

Field 59 is the operational foundation for the UCP's beneficiary provisions. Its accuracy determines whether the beneficiary can claim the protections that documentary credits are designed to provide. Banks and beneficiaries who understand the relationship between Field 59 and the relevant UCP articles are better positioned to avoid discrepancies and ensure timely payment.

Frequently Asked Questions

Q1: Can Field 59 name a natural person rather than a legal entity?
Yes. UCP 600 does not restrict the beneficiary to legal entities. Natural persons can be named as beneficiaries, though banks may apply additional due diligence.

Q2: How does Field 59 interact with UCP Article 14(h) regarding data inconsistency?
Article 14(h) states that if a credit calls for a document other than a transport, insurance, or commercial invoice, the data content need not match the credit. However, the beneficiary name on the commercial invoice must match Field 59 under Article 18(a).

Q3: Can Field 59 be used to identify a branch or division of a company?
Yes, but the branch or division must be identifiable and capable of presenting documents. Using a branch name that differs from the legal entity name may create discrepancies.

Q4: What is the relationship between Field 59 and Field 50 (Applicant)?
Field 59 identifies the seller/beneficiary, while Field 50 identifies the buyer/applicant. They represent the two parties to the underlying commercial transaction.

Q5: How does Field 59 interact with sanctions screening?
Banks screen Field 59 data against sanctions lists. A match or near-match may trigger compliance holds that delay the credit's transmission or the beneficiary's payment.

Source Notes

The following sources were consulted as context only:

Did You Know?

Article 6(c) prohibits credits available by drafts drawn on the applicant.

Regulatory Reference Table
RegulationArticle / SectionRequirementConsequence
UCP 600Article 2DefinitionsBinary determination (compliant/discrepant)
UCP 600Article 6Availability, Expiry Date and Place for PresentationBinary determination (compliant/discrepant)
UCP 600Article 8Confirming Bank UndertakingBinary determination (compliant/discrepant)
UCP 600Article 14Standard for Examination of DocumentsBinary determination (compliant/discrepant)
UCP 600Article 16Discrepant Documents, Waiver and NoticeBinary determination (compliant/discrepant)
UCP 600Article 18Commercial InvoiceBinary determination (compliant/discrepant)

← Scroll horizontally to see all columns

Quick Reference Summary

  • No reference captured.

Compliance Checklist

0 of 5 completed

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 Compliance Engine

DraftLC generates compliant MT700 Field 59 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