UCP 600

MT700 Field 59 and Its Relationship with UCP 600 Articles

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

Introduction

SWIFT MT700 Field 59 identifies the beneficiary of the documentary credit — the party whose name appears on the credit and who is entitled to payment upon compliant document presentation. The field's relationship with UCP 600 articles that define beneficiary rights, document examination standards, and amendment procedures is fundamental to the entire documentary credit mechanism.

Failure Modes

1. Field 59 Does Not Match the Beneficiary Underlying Article 2 Definition
If Field 59 names an entity that is not the actual party entitled to payment under the underlying sales contract, the credit's connection to the commercial transaction is broken, creating compliance and legal risks.

2. Field 59 Contradicts Article 8 Confirmation Scope
When Field 58 names a confirming bank but Field 59 names a beneficiary that the confirming bank has not agreed to cover, the confirmation's scope under Article 8 is uncertain.

3. Field 59 Inconsistency Affects Article 14 Document Examination
If Field 59 names a beneficiary whose name appears differently on the commercial invoice (required under Article 18(a)), the Article 14(a) examination standard is triggered, and the bank must determine whether the variation constitutes a discrepancy.

4. Field 59/Article 16 Refusal Risk
When Field 59 contains an error that makes the beneficiary name inconsistent with presented documents, the bank may invoke Article 16 to refuse the documents, causing payment delays.

Resolution Steps

  1. Verify that Field 59 accurately identifies the entity entitled to payment under the underlying commercial contract. Use the exact legal name as registered.

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

  3. When Field 59 is amended, confirm that the confirming bank (Field 58) consents to the amendment under Article 10 and that the new beneficiary name is consistent with all other fields.

  4. Implement a Field 59 validation step that checks the name against the beneficiary's KYC records, the sales contract, and the advising bank's records.

  5. When a Field 59-related discrepancy is raised under Article 16, assess whether ISBP 745 paragraph A13 provides a basis for accepting the variation.

  6. Maintain a record of all Field 59 changes throughout the credit lifecycle, including amendments and their Article 10 consent status.

  7. Train operators on the UCP articles that most directly interact with Field 59, including Articles 2, 6, 8, 14, 16, and 18.

Conclusion

Field 59 is the beneficiary's identification at the SWIFT level. Its accuracy determines whether UCP 600's beneficiary-related provisions — from confirmation to document examination to payment refusal — operate as intended. Banks that treat Field 59 as a simple data field rather than a legal identifier risk creating discrepancies that disrupt the entire documentary credit process.

Frequently Asked Questions

Q1: Which UCP articles most directly interact with Field 59?
Articles 2 (Definitions), 6 (Transferable Credits), 8 (Confirming Bank), 14 (Standard for Examination), 16 (Discrepant Documents), and 18 (Commercial Invoice) are the primary articles that interact with Field 59.

Q2: Can Field 59 name a trust or nominee?
UCP 600 does not prohibit this, but banks may apply additional scrutiny. The named entity must be identifiable and capable of presenting documents.

Q3: How does Field 59 interact with transferable credits under Article 38?
When a credit is transferred, the second beneficiary's name replaces the first beneficiary's name in Field 59 of the MT702. The transferring bank manages this process.

Q4: What if Field 59 contains a name that has since changed?
The issuing bank should send an MT707 amendment to update Field 59 to the current legal name. Presenting documents under the old name risks refusal under Article 16.

Q5: Can Field 59 be used to identify a government entity as beneficiary?
Yes. Government entities can be named as beneficiaries, but additional documentary requirements may apply under local regulations.

Source Notes

The following sources were consulted as context only:

Did You Know?

Article 6(c) states that a credit must not be issued 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 600 Articles — 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