UCP 600

UCP 600 Article 16: The Five-Day Notice of Refusal Window

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

Introduction

When an issuing bank or confirming bank receives a documentary presentation under a letter of credit, it must act with precision and within defined time limits. UCP 600 Article 16 establishes that a bank wishing to refuse payment must issue its notice of refusal within five banking days following the day of presentation. This strict deadline serves as one of the most consequential procedural safeguards in documentary credit practice. Missing it, even by hours, can convert a valid refusal into a deemed acceptance — with payment obligations falling squarely on the bank regardless of documentary discrepancies.

This guide maps the regulatory architecture governing the notice-of-refusal timeline, identifies common failure modes that lead to disputes, and provides a step-by-step resolution framework for practitioners seeking compliance certainty.

Failure Mode Analysis

Failure Mode 1: Late Issuance of Refusal Notice

The most frequent compliance breach occurs when the issuing bank issues its refusal notice on the sixth banking day — or later — rather than within the five-day window mandated by Article 16(d). This may arise from internal processing delays, understaffing, or misalignment between the receiving office and the examination desk.

Consequence: Under Article 16(f), the bank is precluded from raising discrepancies. The presentation is treated as complying, and the bank must honour or negotiate regardless of the documentary defects.

Failure Mode 2: Vague or Non-Specific Discrepancy Statement

Article 16(b) requires the notice to state "each discrepancy." A notice that groups multiple documents under a single catch-all phrase — for example, "documents do not comply" — fails this requirement. Banks sometimes draft notices using template language that does not enumerate individual discrepancies per document.

Consequence: The presenter may argue the notice is non-compliant on its face, and some ICC opinions and court decisions have found that vague notices do not satisfy Article 16(b), leaving the bank exposed to a claim that the refusal was invalid.

Failure Mode 3: Failure to State Document Disposition

Article 16(c) requires the refusal notice to indicate whether documents are held at the presenter's disposal or returned. Banks occasionally omit this statement or send the documents back without the required accompanying notice, conflating the return of documents with the refusal notice itself.

Consequence: A notice that does not address document disposition is incomplete. ICC Opinion R640 and related practice indicate that an incomplete notice does not trigger the protections of Article 16(f), and the bank may be precluded from refusing.

Failure Mode 4: Incorrect Counting of Banking Days

Banks occasionally miscalculate the five-day window by including the day of presentation as day one, rather than starting the count from the day following presentation. Public holidays, weekends, and jurisdiction-specific banking holidays can also create confusion, particularly in cross-border transactions where the issuing bank and the nominated bank observe different holiday calendars.

Consequence: An incorrect count can cause the bank to believe it has additional time when it does not, or to issue a refusal prematurely. Either outcome creates legal risk.

Deterministic Resolution Architecture

Step 1: Establish the Day of Presentation

Pinpoint the exact date on which the documents were received by the nominated or issuing bank. Under ISBP 745, this is the date on which the bank takes physical or electronic receipt of the documents. Time of day is irrelevant — only the calendar date matters.

Step 2: Identify the Applicable Banking Day Calendar

Determine the banking day calendar of the bank obligated to examine the documents. Article 2 of UCP 600 defines a banking day as any day on which a bank is regularly open at the place at which the act subject to these rules is to be performed. Note that this is the bank's own calendar, not that of the presenter.

Step 3: Count Forward from the Day After Presentation

Start counting from the banking day immediately following the day of presentation. Day one is the first banking day after receipt. Count five consecutive banking days, skipping any day on which the bank is closed (weekends, public holidays, force majeure closures).

Step 4: Draft the Refusal Notice

Prepare a single, consolidated notice that includes: (a) an explicit statement that the bank refuses to honour or negotiate; (b) each discrepancy enumerated individually and specifically; and (c) the disposition of documents — held at disposal or returned.

Step 5: Transmit the Notice Before Close of Day Five

Ensure the notice is dispatched — not merely drafted internally — before the close of the fifth banking day. For telecommunication transmissions (SWIFT, secure portal), dispatch time is the time the message is sent. For courier or registered mail, dispatch is the time the package is handed to the carrier.

Step 6: Retain Evidence of Timely Dispatch

Archive a timestamped copy of the refusal notice and any transmission confirmation (SWIFT confirmation, courier receipt). This creates an auditable record demonstrating compliance with the deadline.

Step 7: Implement a Monitoring Protocol for Subsequent Presentations

After any refusal, establish a review protocol to ensure that the same procedural errors do not recur. This includes calendar-based alerts for the five-day deadline, standardised refusal notice templates pre-populated with all required Article 16 elements, and a sign-off workflow requiring compliance officer review before dispatch.

Conclusion

The five-day notice-of-refusal window under UCP 600 Article 16 is a bright-line rule: miss it, and the bank loses its right to refuse. The consequences are binary — there is no partial compliance. Banks that internalise the deadline, standardise their refusal notice templates, and implement calendar-based monitoring can eliminate the most common procedural failures. The article's design reflects a deliberate policy choice: certainty for exporters and presenting parties outweighs procedural convenience for banks.

Frequently Asked Questions

Q1: Does the five-day clock start on the day documents are received, or the next day?

The clock starts on the banking day immediately following the day of receipt. If documents arrive on Monday, Tuesday is day one.

Q2: What if the fifth banking day falls on a bank holiday?

The notice must be issued on the next banking day that is open. The five-day window extends only for days on which the bank is closed; it does not shorten.

Q3: Can the issuing bank waive discrepancies and still pay within five days?

Yes. The bank may choose to contact the applicant for a waiver under Article 16(b) but must still issue the refusal notice within five days if no waiver is received. If a waiver is received and the bank decides to honour despite discrepancies, it no longer needs to refuse.

Q4: What happens if the notice is sent on day five but received on day six?

Issuance, not receipt, is the operative event. If the notice is dispatched (sent) on the fifth banking day, it is timely regardless of when it arrives at the presenter.

Q5: Is email a valid means of transmitting a refusal notice?

Article 16(d) requires "telecommunication or other expeditious means." Email typically satisfies this standard, though SWIFT is the industry norm for bank-to-bank communications. The key requirement is expeditiousness, not a specific medium.

Q6: Can the bank issue multiple separate notices on different days for different discrepancies?

No. Article 16 requires a "single notice." The bank must consolidate all discrepancies into one communication issued within the five-day window.


Source Notes

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

Did You Know?

UCP 600 Article 16 establishes that a bank wishing to refuse payment must issue its notice of refusal within five banking days following the day of presentation.

Regulatory Reference Table
RegulationArticle / SectionRequirementConsequence
UCP 600Article 16Discrepant Documents, Waiver and NoticeBinary determination (compliant/discrepant)
UCP 600Article 2DefinitionsBinary determination (compliant/discrepant)

← Scroll horizontally to see all columns

Quick Reference Summary

  • No reference captured.

Compliance Checklist

0 of 7 completed
Bank Expectations vs Common Beneficiary Mistakes
✓ What Banks Expect✗ What Beneficiaries Often Do Wrong
Late Issuance of Refusal NoticeThe most frequent compliance breach occurs when the issuing bank issues its refusal notice on the...
Vague or Non-Specific Discrepancy StatementArticle 16(b) requires the notice to state "each discrepancy." A notice that groups multiple docu...
Failure to State Document DispositionArticle 16(c) requires the refusal notice to indicate whether documents are held at the presenter...
Incorrect Counting of Banking DaysBanks occasionally miscalculate the five-day window by including the day of presentation as day o...

← Scroll horizontally to see all columns

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 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