UCP 600

UCP 600 Analysis: SWIFT MT 754 Messages in International Trade Transactions

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

Introduction

The SWIFT MT 754 message—Advice of Acceptance/Negotiation—is a key communication in the documentary credit lifecycle. It notifies the issuing bank that the nominated or confirming bank has accepted documents and will negotiate or forward them for reimbursement. Under UCP 600, the MT 754 serves as the bridge between document presentation and payment, but its proper construction and interpretation are essential to avoid disputes about when payment obligations mature and who bears the risk during the examination and negotiation process.

This guide examines the role of MT 754 messages in UCP 600 transactions, identifies the common failure points that arise from improper messaging, and provides guidance for ensuring that MT 754 communications support rather than undermine UCP 600 compliance.

Failure Modes

1. Incorrect Amount in MT 754

If the amount specified in the MT 754 differs from the amount of the complying presentation, the issuing bank may refuse to reimburse the nominated bank. This discrepancy creates a payment gap that the nominated bank must resolve, often at its own cost.

Root cause: Data entry errors or miscalculations when constructing the MT 754 message.

2. Missing or Incomplete Narrative Description

Article 16 requires that any refusal or conditional acceptance be clearly communicated with specific details. If the MT 754's narrative fields do not accurately reflect the nominated bank's assessment of the documents, the issuing bank may challenge the reimbursement claim.

Root cause: Inadequate attention to the narrative fields in the MT 754 message.

3. Timing Discrepancies Between MT 754 and Reimbursement Requests

The MT 754 is typically sent before the reimbursement request, but timing discrepancies—where the reimbursement request arrives before the issuing bank has processed the MT 754—can create confusion about the sequence of obligations.

Root cause: The asynchronous nature of SWIFT messaging and bank processing systems.

4. Failure to Notify of Discrepancies in MT 754

When the nominated bank negotiates under reserve or with discrepancies, the MT 754 should reflect this. If the MT 754 indicates clean negotiation when discrepancies exist, the issuing bank may refuse reimbursement, claiming misrepresentation.

Root cause: Pressure on nominated banks to negotiate quickly, leading to incomplete or inaccurate MT 754 messages.

Resolution Steps

  1. Implement double-check procedures: Establish procedures for reviewing MT 754 messages before transmission, verifying that all fields—particularly the amount and narrative description—are accurate and complete.

  2. Standardize MT 754 templates: Create standardized MT 754 templates that ensure all required fields are populated, reducing the risk of missing or incomplete information.

  3. Coordinate timing of MT 754 and reimbursement requests: Establish protocols for coordinating the timing of MT 754 transmission and reimbursement requests, ensuring that the issuing bank receives both in the correct sequence.

  4. Include clear reserve or discrepancy language: When negotiating under reserve or with discrepancies, include clear language in the MT 754's narrative fields that accurately reflects the nominated bank's position.

  5. Monitor reimbursement claim processing: Track the issuing bank's processing of reimbursement claims, following up promptly if the MT 754 or reimbursement request encounters delays.

  6. Train staff on MT 754 construction: Develop training programs that cover MT 754 message construction, including best practices for field population, narrative description, and error prevention.

  7. Establish reconciliation procedures: Implement reconciliation procedures that verify the correspondence between the MT 754 message and the actual documents negotiated, identifying and correcting any discrepancies before they become disputes.

Conclusion

The MT 754 message is a key link in the documentary credit payment chain. Its accurate construction and proper interpretation are essential to ensuring that nominated banks receive timely reimbursement and that issuing banks can confirm compliance with their UCP 600 obligations. Banks that invest in MT 754 quality—through templates, training, and reconciliation—reduce their risk of payment disputes and improve the efficiency of their trade finance operations.

FAQ

Q1: What is an MT 754 message?
An MT 754 is a SWIFT message type used by the nominated or confirming bank to notify the issuing bank that documents have been accepted and negotiated. It triggers the issuing bank's reimbursement obligation under UCP 600.

Q2: When should the MT 754 be sent?
The MT 754 should be sent promptly after the nominated bank has examined and accepted the documents. The specific timing depends on the credit's terms and the bank's internal procedures, but it should be sent before or concurrent with the reimbursement request.

Q3: Can the issuing bank refuse reimbursement based on the MT 754?
The issuing bank may challenge the reimbursement claim if the MT 754 contains errors or inconsistencies. However, the issuing bank's obligation to reimburse is based on the actual documents presented, not solely on the MT 754 message.

Q4: What should the narrative field in the MT 754 contain?
The narrative field should accurately describe the negotiation, including the date of negotiation, any reserves or discrepancies, and any other relevant information. It should be consistent with the actual documents negotiated.

Q5: How does the MT 754 interact with UCP 600 Article 7?
Article 7 defines the issuing bank's obligation to honour. The MT 754 notifies the issuing bank that the nominated bank has negotiated, triggering the issuing bank's reimbursement obligation. The MT 754 is the communication mechanism through which this trigger is communicated.

Source Notes

Context only. The following source titles informed the background for this guide but no text has been reproduced from them.

Did You Know?

Article 16 requires that any refusal or conditional acceptance be clearly communicated with specific details.

Regulatory Reference Table
RegulationArticle / SectionRequirementConsequence
UCP 600Article 2DefinitionsBinary determination (compliant/discrepant)
UCP 600Article 7Issuing Bank UndertakingBinary determination (compliant/discrepant)
UCP 600Article 8Confirming Bank UndertakingBinary determination (compliant/discrepant)
UCP 600Article 12NominationBinary determination (compliant/discrepant)
UCP 600Article 16Discrepant Documents, Waiver and NoticeBinary 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 UCP 600 Analysis — 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