MT700 Field 50 — Contradictions with Other Fields

Introduction

SWIFT MT700 Field 50 identifies the applicant for the documentary credit — the buyer or importer who initiates the credit. When the applicant details in Field 50 contradict information in other fields of the same message, the resulting ambiguity can obstruct document examination, delay payment, and create compliance exposure. This guide examines the most common contradiction patterns and provides actionable steps to resolve them.

Failure Modes

1. Applicant Name Mismatch Between Field 50 and Commercial Invoice
The commercial invoice must identify the applicant as the buyer (UCP 600 Article 18(a)(iv)). If Field 50 in the MT700 uses a trading name or abbreviation while the invoice uses the full legal name, the presenting bank may raise a discrepancy even though both references point to the same entity.

2. Field 50 Address Inconsistent with Field 43P or 43Q (Partial Shipment / Transshipment Rules)
While these fields address shipping logistics, an applicant address in a different country than the destination port may create confusion about Incoterms applicability and customs clearance requirements, indirectly affecting document compliance.

3. Field 50 Contradicts Field 47A (Additional Conditions)
If Field 47A contains conditions that reference the applicant by a different name or entity than Field 50, the nominated bank cannot determine which party holds the obligation to provide additional documents or satisfy specific conditions.

4. Applicant Data in Field 50 Does Not Match Bank's Know-Your-Customer Records
When the receiving bank's KYC records show the applicant under a different name or registration number than Field 50, anti-money laundering compliance teams may flag the transaction, causing processing delays.

Resolution Steps

1. Standardize applicant naming conventions across your organization's documentary credit templates. Use the exact legal entity name as registered, avoiding trading names or abbreviations.

2. Cross-check Field 50 against Field 47A before transmitting the MT700. Ensure all references to the applicant in additional conditions match the name and details in Field 50.

3. Maintain a centralized applicant database that maps legal names, trading names, and registration numbers for all counterparties. Use this database as the authoritative source for Field 50 entries.

4. When discrepancies are detected post-issuance, issue an MT707 amendment to align Field 50 with the correct entity information. Do not rely on informal understandings between banks.

5. Include Field 50 validation in your pre-transmission SWIFT quality checks. Automated name-matching algorithms can flag potential mismatches between Field 50 and other fields.

6. Coordinate with your compliance team to ensure that Field 50 data aligns with current KYC records. Update KYC profiles whenever applicant details change.

7. Educate beneficiaries that they should verify the applicant name in Field 50 against their commercial agreement before preparing documents. Early detection of mismatches prevents presentation-day surprises.

Conclusion

Field 50 contradictions are among the most common sources of documentary credit discrepancies. They often stem from inconsistent naming conventions, incomplete data updates, or poor coordination between trade operations and compliance teams. Systematic validation and standardized naming practices are the most effective defenses.

Frequently Asked Questions

Q1: Can a documentary credit be issued with a Field 50 that uses a trading name instead of the full legal name?
UCP 600 does not explicitly prohibit trading names, but SWIFT validation rules and bank compliance policies require the full legal name in most cases. Using a trading name increases the risk of discrepancies.

Q2: What should the beneficiary do if Field 50 appears incorrect?
The beneficiary should contact the advising bank immediately to request clarification from the issuing bank. Presenting documents under a credit with an incorrect applicant name risks refusal.

Q3: How does Field 50 interact with Field 59 (Beneficiary)?
There is no direct legal requirement for these fields to match, but the beneficiary should ensure that the applicant named in Field 50 corresponds to their counterparty in the underlying sales contract.

Q4: Can Field 50 be amended after issuance?
Yes, via an MT707 amendment. The issuing bank must send the amendment through SWIFT, and the beneficiary must accept the amendment for it to take effect under UCP 600 Article 10.

Q5: Are there regional variations in how Field 50 contradictions are handled?
Yes. Banks in some jurisdictions apply stricter interpretation rules, while others allow more flexibility. When dealing with unfamiliar jurisdictions, seek explicit confirmation from the issuing bank.

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)