UCP 600 Article 16: Omitting Discrepancies from Refusal Notices

Introduction

UCP 600 Article 16(b) requires that a refusal notice state "each discrepancy" for which the bank refuses to honour or negotiate. This requirement is not a formality — it is a substantive obligation that, if not met, can convert a valid refusal into a deemed acceptance. Banks that omit discrepancies from their refusal notices, or that group multiple discrepancies under vague catch-all phrases, expose themselves to claims that the refusal was invalid. This guide examines the regulatory framework, identifies the common errors in refusal notice drafting, and provides a resolution framework for practitioners.

Failure Modes

1. Grouping Multiple Discrepancies Under a Single Catch-All Phrase

The refusal notice states "documents do not comply with credit terms" without specifying which documents are discrepant or what the specific discrepancies are. This fails the Article 16(b) requirement to state "each discrepancy."

2. Omitting a Known Discrepancy from the Notice

The examining bank identifies three discrepancies during examination but includes only two in the refusal notice, omitting the third. Under Article 16(f), the bank may be precluded from raising the omitted discrepancy in subsequent proceedings.

3. Using Internal Codes Instead of Plain-Language Discrepancy Descriptions

The refusal notice uses internal bank codes (such as "DISC-14A") instead of plain-language descriptions of each discrepancy. The presenter cannot determine what the discrepancy is, rendering the notice deficient under Article 16(b).

4. Failing to Identify the Specific Document in Which the Discrepancy Occurs

The refusal notice states "invoice amount exceeds credit amount" but does not specify which invoice or which credit. While this may seem obvious to the examining bank, the presenter may have submitted multiple invoices or the notice may be unclear to downstream parties.

5. Issuing a Preliminary Refusal and Promising to Send a Final Notice Later

The examining bank issues a preliminary notice stating that discrepancies have been identified but promising to provide a detailed list later. Article 16(b) requires the notice to state each discrepancy — a preliminary notice does not satisfy this requirement.

Resolution

1. Use a standardised refusal notice template. Create a template that requires the examiner to enumerate each discrepancy individually, identify the specific document, and reference the applicable UCP 600 article or ISBP 745 paragraph.

2. Require dual sign-off before dispatch. Implement a workflow where the refusal notice is reviewed by a second officer before dispatch. This reduces the risk of omissions and ensures that each discrepancy is adequately described.

3. Enumerate each discrepancy separately. List each discrepancy as a separate item, with its own description, document reference, and regulatory basis. Avoid grouping discrepancies or using catch-all phrases.

4. Reference specific documents and data. When describing a discrepancy, identify the specific document (e.g., "commercial invoice dated 15 March 2026") and the specific data point that is discrepant (e.g., "states amount of USD 100,500, exceeding the credit amount of USD 100,000").

5. Include all identified discrepancies. Before dispatching the notice, compare the list of discrepancies in the notice against the examiner's working notes to ensure that no discrepancy has been omitted.

6. Avoid internal codes in the notice. Use plain-language descriptions that the presenter can understand without reference to internal bank documentation.

7. Issue the complete notice within the five-day window. Do not issue a preliminary notice with a promise to follow up — issue the complete, Article 16(b)-compliant notice within the five banking day window.

8. Archive the notice and supporting documentation. Retain a copy of the refusal notice, the examiner's working notes, and any supporting documentation to create an auditable record of the refusal process.

Conclusion

Article 16(b) is a strict requirement: each discrepancy must be stated individually and specifically. Banks that omit discrepancies, group them under vague phrases, or use internal codes instead of plain language risk losing their right to refuse. By using standardised templates, requiring dual sign-off, and enumerating each discrepancy separately, banks can ensure their refusal notices comply with Article 16(b) and withstand scrutiny in any subsequent dispute.

Frequently Asked Questions

Q1: What does "each discrepancy" mean under Article 16(b)?
Each discrepancy must be stated as a separate item, with a clear description of the specific document and the specific data point or condition that is discrepant. Grouping multiple discrepancies under a single phrase does not satisfy this requirement.

Q2: Can a bank add discrepancies to a refusal notice after it has been dispatched?
No. Once the refusal notice has been dispatched, the bank cannot add new discrepancies. Under Article 16(f), any discrepancy not included in the original notice is precluded.

Q3: What happens if the refusal notice is vague?
A vague refusal notice may be treated as non-compliant with Article 16(b). If the presenter argues that the notice does not state "each discrepancy" with sufficient specificity, the bank may be precluded from relying on the refusal.

Q4: Should the refusal notice reference UCP 600 articles or ISBP 745 paragraphs?
It is best practice to reference the applicable regulatory provision for each discrepancy, as this provides clarity and supports the bank's position in any subsequent dispute. However, UCP 600 does not expressly require this.

Q5: Can a bank issue multiple refusal notices on different days?
No. Article 16 requires a "single notice." The bank must consolidate all discrepancies into one communication issued within the five-day window.

Source Notes

Context only — the following sources informed the factual basis of this guide. No text was copied from them.

1. 25 Tips to Avoid Common Documentary Credit Issues — ICC Academy. Published April 2025. Provides context on common documentary credit pitfalls, including refusal notice errors.
   - URL: https://www.icc.academy

2. Evolution of UCP 600 and Its Impact on Documentary Credits — ICC Academy. Published June 2025. Offers historical context on how Article 16 has evolved and been interpreted.
   - URL: https://www.icc.academy

3. Understanding "CONFIRM" vs. "MAY ADD" in Documentary Credits Under UCP 600 — ICC Academy. Published August 2025. Provides context on how confirmation affects refusal obligations.
   - URL: https://www.icc.academy

4. Incoterms® Rules — ICC. Published March 2023. Offers context on how Incoterms rules interact with documentary credit requirements and refusal processes.
   - URL: https://www.iccwbo.org

5. Certified UCP 600 Specialist (CUCP) — ICC Academy. Published July 2025. Provides context on the competency standards for UCP 600 practitioners.
   - URL: https://www.icc.academy