UCP 600

Best Practices for Complying with UCP 600 Article 16: Notice of Refusal

📅 2026-07-14 6 min read UCP 600 / ISBP 745

Introduction

The Article 16 refusal notice is one of the most consequential documents in trade finance. A well-drafted notice protects the bank's right to refuse. A poorly drafted notice — one that is late, vague, or procedurally deficient — can trigger preclusion under Article 16(d), obligating the bank to pay even for discrepant documents. This guide outlines the best practices that ensure Article 16 compliance and reduce the risk of disputes.

Failure Modes

1. Issuing the refusal notice after the five-banking-day deadline. This is the most common and most costly error. Even a single day late triggers preclusion. The bank must pay the full credit amount regardless of how severe the discrepancies are.

2. Listing discrepancies without adequate specificity. A refusal notice that says "documents are discrepant" or "documents do not comply" without listing individual discrepancies fails Article 16(c). The presenter must be told exactly what is wrong with each document so they can understand the refusal and, where possible, cure the discrepancies.

3. Including discrepancies in a supplementary notice after the initial refusal. Article 16(c) requires a single notice. If the bank sends an initial refusal on day four and a supplementary notice on day five adding new discrepancies, the supplementary discrepancies may be considered untimely and therefore waived.

4. Failing to communicate the refusal by the required means. Article 16(c) requires "telecommunication or, if that is not possible, by other expeditious means." A refusal notice sent by regular mail, delivered by hand without tracking, or communicated only by telephone does not satisfy this requirement.

5. Not tracking the refusal notice through delivery confirmation. The bank should confirm that the refusal notice was received by the presenter. An undelivered refusal notice does not fulfill Article 16(c). Using SWIFT MT734 provides automatic delivery confirmation. For non-SWIFT communications, delivery confirmation (e.g., courier tracking, read receipt) is essential.

Resolution

1. Implement a deadline-tracking system that alerts examiners at least two days before the Article 16(d deadline. Automated alerts reduce the risk of missing the deadline. The alert should identify the presentation date, calculate the deadline, and notify both the examiner and a supervisor.

2. Draft the refusal notice as discrepancies are identified. Rather than waiting until the examination is complete to draft the notice, document each discrepancy as it is found. By the time the examination is complete, the notice should be substantially drafted.

3. Use SWIFT MT734 for all refusal notices when possible. SWIFT provides a standardized format, automatic delivery confirmation, and a time-stamped record. It satisfies the Article 16(c) telecommunication requirement and eliminates questions about whether the notice was sent by expeditious means.

4. Include the following elements in every refusal notice: (a) credit reference number, (b) date of presentation, (c) each discrepancy with reference to the relevant document and credit term, (d) statement that the bank refuses to honour or negotiate, and (e) disposition of documents (held, returned, etc.). This structure ensures all Article 16(c) requirements are met.

5. Train examiners to describe discrepancies in plain language. A discrepancy notice should be understandable to the beneficiary, who may not be a trade finance specialist. Avoid internal jargon. Describe the discrepancy, identify the document, and reference the credit term that is not satisfied.

6. Review the refusal notice before sending. A second pair of eyes — a supervisor or peer — should review the notice before it is sent. This catches omissions, errors, and ambiguities that the original examiner may have missed.

7. Maintain a refusal notice archive with examination records. Every refusal notice should be accompanied by the examination notes that support the discrepancy findings. This archive serves as evidence of reasonable examination practice if a dispute arises.

Conclusion

Article 16 compliance is a matter of discipline: identify all discrepancies, describe them specifically, issue the notice by expeditious means, and do it within five banking days. The best practices outlined here — deadline tracking, draft-as-you-examine workflow, SWIFT usage, peer review, and record retention — institutionalize the habits that prevent the most common Article 16 errors.

FAQ

Q: What if the bank issues the refusal notice on time but the presenter does not receive it?
A: The bank's obligation under Article 16(c) is to give the notice by telecommunication or other expeditious means. If the notice was properly sent (e.g., via SWIFT) and the presenter's system failed to receive it, the bank has typically fulfilled its obligation. However, the bank should confirm delivery and take reasonable steps to ensure the presenter is informed.

Q: Can the bank refuse部分 documents and accept others?
A: UCP 600 does not provide for partial acceptance of a presentation. The bank either finds the entire presentation complying (Article 15) or refuses the entire presentation (Article 16). The refusal notice covers all discrepancies across all documents.

Q: What if the bank identifies a discrepancy that was not in the original refusal notice?
A: Under Article 16(c), the refusal notice must specify each discrepancy. Discrepancies not listed in the notice are typically considered waived. The bank cannot issue a supplemental refusal notice adding new discrepancies after the initial notice.

Q: Can the presenter appeal a refusal notice?
A: UCP 600 does not provide for an appeal process within the rules themselves. However, the presenter can request clarification, attempt to cure and re-present (if the credit is still valid), or pursue DOCDEX dispute resolution or legal proceedings.

Q: Does the refusal notice need to be signed?
A: UCP 600 does not specifically require a signature on the refusal notice. However, the notice should clearly identify the issuing bank and the examiner. SWIFT MT734 messages carry the sender's identification, which serves this purpose.

Source Notes

Context only — the following sources were consulted for background context during research. No text was reproduced from these sources.

Did You Know?

Article 16(c) requires a single notice.

Regulatory Reference Table
RegulationArticle / SectionRequirementConsequence
UCP 600Article 16Discrepant Documents, Waiver and NoticeBinary determination (compliant/discrepant)
UCP 600Article 15Complying PresentationBinary 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 Best Practices for Complying with UCP 600 Article 16 — 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