UCP 600 Article 16: How SWIFT Message Code 72 Communicates Refusal Reasons

Introduction

In documentary credit practice, SWIFT Message Category 7 ( documentary credits) includes specific message types used for communicating refusal information. SWIFT Message Code 72 (Sender to Receiver Information) is the field where banks transmit the reasons for refusing a presentation under UCP 600 Article 16. This field is the industry-standard mechanism for communicating discrepancies, and its proper use is essential for compliance with Article 16(b)'s requirement that each discrepancy be stated in the refusal notice.

This guide maps the regulatory framework governing the use of SWIFT Code 72 in refusal communications, identifies common failure modes, and provides a step-by-step resolution architecture.

Failure Mode Analysis

Failure Mode 1: Using Field 72 for Vague or Generic Discrepancy Statements

Banks sometimes populate Field 72 with generic statements such as "documents discrepant" or "please refer to covering letter" without enumerating individual discrepancies. Article 16(b) requires each discrepancy to be stated.

Consequence: The refusal notice fails to satisfy Article 16(b). The presenter may argue the notice is non-compliant, and under Article 16(f), the bank may be precluded from raising discrepancies.

Failure Mode 2: Exceeding Field 72 Character Limits

SWIFT Field 72 has character limits that may truncate lengthy discrepancy descriptions. Banks sometimes fail to account for this, resulting in incomplete or cut-off discrepancy statements.

Consequence: If the truncation results in missing discrepancies, the notice may be incomplete under Article 16(b). Banks should use continuation lines or supplementary messages to ensure all discrepancies are communicated.

Failure Mode 3: Using MT 799 Instead of MT 734 for Refusals

Some banks use MT 799 (Free Format) instead of MT 734 (Refusal) for communicating refusals. While MT 799 is technically permissible, it lacks the structured fields of MT 734 and may create confusion about the message's purpose.

Consequence: The presenter may not recognise the MT 799 as a formal refusal notice, leading to delays in response. Best practice is to use MT 734 for all refusal communications.

Failure Mode 4: Sending the Refusal Notice to the Wrong BIC

Article 16(a) requires the notice to be given to the party from which the presentation was received. If the bank sends the MT 734 to the applicant instead of the nominated bank, the notice does not satisfy Article 16(a).

Consequence: The refusal notice is not properly served. The bank may be precluded from raising discrepancies under Article 16(f) if the correct party did not receive the notice.

Deterministic Resolution Architecture

Step 1: Confirm the Correct Recipient

Before sending the MT 734, verify the BIC (Bank Identifier Code) of the party from which the presentation was received. This is typically the nominated bank or the presenter's bank.

Step 2: Draft Discrepancies with Specificity

Each discrepancy must be enumerated individually in Field 72. Use clear, specific language that identifies the document, the discrepancy, and the relevant UCP 600 or ISBP 745 provision. Avoid generic catch-all phrases.

Step 3: Structure the Field 72 Content Appropriately

Use the standard SWIFT format for discrepancy descriptions. Separate individual discrepancies with line breaks or semicolons. If the description exceeds Field 72 limits, use continuation lines or a supplementary MT 799 message.

Step 4: Include the Disposition Statement

Field 72 should also include the Article 16(c) disposition statement: whether documents are held at the presenter's disposal or returned. This is required in addition to the discrepancy list.

Step 5: Send Within the Five-Day Window

Transmit the MT 734 before the close of the fifth banking day following presentation. SWIFT transmission time is the dispatch time, not the receipt time.

Step 6: Retain the SWIFT Confirmation

Archive the SWIFT transmission confirmation, which includes the message content, timestamp, and recipient BIC. This serves as proof of timely and proper notice.

Step 7: Monitor for Presenter Response

After sending the MT 734, monitor for a response from the presenter — whether a request for waiver, a new presentation, or an acknowledgment. Document all communications.

Step 8: Implement a SWIFT Refusal Checklist

Create a checklist for drafting and sending MT 734 messages that includes: correct recipient BIC, enumerated discrepancies, disposition statement, character limit review, and transmission timing. This prevents procedural errors.

Conclusion

SWIFT Field 72 is the industry-standard mechanism for communicating refusal reasons under Article 16. Its proper use requires specific, enumerated discrepancies, correct recipient identification, and timely transmission. Banks that treat Field 72 as a free-text field for generic statements risk non-compliance with Article 16(b) and preclusion under Article 16(f). The resolution is structured: draft discrepancies with specificity, structure the Field 72 content appropriately, and transmit within the five-day window.

Frequently Asked Questions

Q1: Can a bank use MT 799 instead of MT 734 for refusal notices?

While MT 799 is technically permissible, MT 734 is the industry standard for refusal communications. Using MT 799 may create confusion and is not recommended best practice.

Q2: What if the Field 72 character limit cuts off a discrepancy description?

Use continuation lines within Field 72 or send a supplementary MT 799 message with the complete discrepancy description. Ensure all discrepancies are communicated in full.

Q3: Can the bank send the refusal notice by email instead of SWIFT?

Article 16(d) permits telecommunication or other expeditious means. Email is permissible, though SWIFT is the industry norm. If email is used, ensure it is sent to the correct address and retain proof of transmission.

Q4: Does the SWIFT transmission time count as the notice date?

Yes. The SWIFT transmission time is the dispatch time, which is the operative event for Article 16(d) compliance. The notice is timely if dispatched before the close of the fifth banking day.

Q5: Can the bank list all discrepancies on a single line in Field 72?

Yes, but each discrepancy must be individually identifiable. Using separators (semicolons, line breaks) between discrepancies is recommended for clarity and to satisfy Article 16(b)'s requirement to state each discrepancy.

Source Notes

The following sources are provided as context only and were not used as textual source material for this guide.

• ICC Academy, "Incoterms® 2020 — FCA and DAP: Answers to some common queries regarding contract of carriage" (December 2021)
• ICC Academy, "ICC Guide to Incoterms® 2020 — eBook" (November 2025)
• ICC, "UCP 600 — Uniform Rules and Practice for Documentary Credits, Including eUCP Version 2.1" (July 2023)
• ICC Academy, "Uniform Rules for Documentary Credits (UCP 600) — eBook" (December 2024)
• ICC Academy, "Documentary credits: Rules, guidelines & terminology" (July 2025)