UCP 600 Article 16: Notice of Refusal — State All Discrepancies in the Notice

Introduction

Article 16(b)(ii) of UCP 600 requires that each discrepancy for which the bank refuses a presentation must be stated in the refusal notice. This is not a recommendation — it is a mandatory requirement with severe consequences for non-compliance. The preclusion rule under Article 16(f) permanently bars the bank from raising discrepancies not included in the original notice. This guide examines the all-discrepancies requirement, common errors in discrepancy enumeration, and strategies for ensuring completeness.

Failure Mode Analysis

Failure Mode 1: Examination Fatigue Omission

Risk: The examining officer identifies discrepancies systematically but, after reviewing 15+ documents, omits a discrepancy in the packing list that was identified earlier in the process.

Impact: The bank is precluded from raising the packing list discrepancy. If it was material, the bank must honour a presentation it would otherwise have refused.

Failure Mode 2: Categorisation Error

Risk: The bank groups related documents (e.g., all transport documents) and examines them together. In doing so, it misses a discrepancy in one bill of lading because attention focused on another.

Impact: The missed discrepancy triggers preclusion. Categorisation errors are a common source of omissions in complex presentations with multiple document sets.

Failure Mode 3: Overreliance on Applicant Input

Risk: The bank asks the applicant to identify discrepancies. The applicant identifies some but not all. The bank uses the applicant's list as the basis for the refusal notice.

Impact: The bank is responsible for its own examination under Article 14. Relying on the applicant's incomplete list results in omissions and preclusion.

Failure Mode 4: Cross-Reference Failure

Risk: The bank identifies a discrepancy between two documents (e.g., invoice quantity differs from bill of lading quantity) but does not cite it because neither document is individually non-complying.

Impact: Under ISBP 745, documents must be internally consistent. The cross-document discrepancy is valid and must be cited. Omitting it triggers preclusion.

Deterministic Resolution Architecture

Resolution 1: Document-by-Document Examination Matrix

Create a matrix that maps each required document against each credit condition. For every cell in the matrix, determine whether the document complies. This systematic approach ensures no document-condition combination is missed.

Resolution 2: Dual-Examiner Verification

Assign two officers to examine the same presentation independently. Each produces a discrepancy list. Compare the lists and merge them. Any discrepancy identified by either examiner appears in the final notice. This provides redundancy against individual oversight.

Resolution 3: Discrepancy Classification System

Categorise discrepancies by type:
- Document-internal: Error within a single document (e.g., wrong date on invoice)
- Cross-document: Inconsistency between two documents (e.g., different quantities)
- Document-credit mismatch: Document does not match a credit term (e.g., wrong Incoterm)
- ISBP 745 violation: Document does not meet ISBP 745 standards (e.g., unsigned)

This classification ensures each category is reviewed systematically.

Resolution 4: Final Review Gate

Before issuing the refusal notice, conduct a final review that asks: "Is there any discrepancy we have not listed?" This review should be performed by a different person than the examiner, providing fresh perspective.

Resolution 5: Discrepancy Evidence Package

For each discrepancy, prepare a supporting evidence package:
- The specific document page and clause
- The credit term or ISBP 745 paragraph that is violated
- A brief explanation of why the document fails

This evidence package serves dual purposes: it ensures the discrepancy is valid and it provides a complete record for the refusal notice.

Resolution 6: Applicant Feedback as Supplement, Not Source

If the applicant identifies discrepancies, add them to the bank's own list — but do not use the applicant's list as the sole source. The bank must conduct its own examination. Applicant input supplements but does not replace bank examination.

Resolution 7: Post-Refusal Audit

After issuing the refusal notice, conduct an audit within 24 hours. Review the notice against the full examination record to verify that every identified discrepancy is listed. If a discrepancy was identified but not listed, assess whether preclusion has occurred and take appropriate action.

Conclusion

The all-discrepancies requirement under Article 16(b)(ii) is a strict liability standard. The bank does not need to intend to omit a discrepancy — mere omission triggers preclusion. The only reliable approach is systematic, redundant examination with multiple verification layers. Every discrepancy must be identified, validated, and included in the single refusal notice.

Frequently Asked Questions

1. What if the bank discovers a discrepancy after issuing the refusal notice?

The bank is precluded from raising it. Article 16(f) bars the bank from claiming the documents are non-complying for any discrepancy not stated in the original notice.

2. Can the bank list discrepancies in general categories instead of individually?

No. Article 16(b)(ii) requires each discrepancy to be stated. General categories like "transport document discrepancies" are insufficient. Each specific discrepancy must be enumerated.

3. Does the bank need to explain why each discrepancy is non-complying?

Article 16(b)(ii) requires each discrepancy to be stated, but does not require a detailed explanation. However, including the credit clause or ISBP 745 paragraph that is violated adds clarity and reduces disputes.

4. Can the presenter waive discrepancies after receiving the refusal notice?

Yes. The applicant (through the issuing bank) or the presenter can waive discrepancies. However, the waiver must be communicated before the bank returns the documents under Article 16(g).

5. What happens if the bank lists an invalid discrepancy?

An invalid discrepancy does not trigger preclusion. The bank can withdraw a cited discrepancy if it is proven to be unfounded. However, listing invalid discrepancies may damage the bank's credibility.

Source Notes

Context only. This guide is based on UCP 600 Articles 16(b)(ii) and 16(f) (ICC Publication No. 600), ISBP 745 (ICC Publication No. 745), and ICC Opinion TA736rev. Source references in the search results pointed to general ICC Academy pages on documentary credits, which provided contextual framing but not article-specific text.