title: "UCP 600 Article 9: Advising Bank — Verifying Authenticity"
date: 2026-07-15
batch: 28
topic_family: ucp
status: approved

UCP 600 Article 9: Advising Bank — Verifying Authenticity

Introduction

The authenticity verification obligation is the cornerstone of the advising bank's Article 9 duties. Before advising any credit, the bank must take "reasonable care" to ascertain that the credit's apparent authenticity is accurate. This standard is neither trivial nor impossible — it requires the advising bank to apply professional judgment based on the information available, without conducting a forensic investigation of the credit's origin. Getting this balance right is essential: too little verification exposes the bank to liability for advising fraudulent credits; too much verification delays the advice and burdens the process with unnecessary friction.

Failure Modes

Failure Mode 1: No SWIFT Authentication Check

An advising bank receives a credit by SWIFT but does not verify the sender's BIC or authentication data. The credit turns out to be from an unauthorized party impersonating a known issuing bank. The bank's failure to perform a basic SWIFT check falls below the Article 9(a) standard.

Failure Mode 2: Reliance on Visual Appearance Only

An advising bank examines the credit's visual presentation — the format, the logo, the language — but does not verify SWIFT authentication. Visual appearance alone is insufficient to establish apparent authenticity in modern practice.

Failure Mode 3: Advising Despite Authentication Warnings

An advising bank's SWIFT system flags an authentication anomaly, but the bank advises the credit anyway, reasoning that the issuing bank is a known correspondent. The authentication warning should trigger escalation, not override.

Failure Mode 4: Failing to Verify Non-SWIFT Credits

A credit arrives by courier with no SWIFT authentication. The advising bank accepts it at face value without contacting the issuing bank to confirm. Non-SWIFT credits require alternative verification — acceptance without verification falls below the Article 9(a) standard.

Failure Mode 5: Delayed Verification Causes Missed Deadline

An advising bank performs a thorough authenticity check but takes too long, causing the advice to reach the beneficiary after the credit's shipment window has closed. Thoroughness must be balanced with timeliness under Article 9's "without undue delay" requirement.

Resolution Strategies

Resolution 1: Mandatory SWIFT Authentication Verification

Every credit arriving by SWIFT must have its sender BIC and authentication data verified against the bank's internal records before advice is transmitted. This verification should be a mandatory step in the examination checklist.

Resolution 2: Non-SWIFT Credit Verification Protocol

Advising banks should maintain a specific protocol for non-SWIFT credits that includes direct contact with the issuing bank, verification against known formats, and escalation to compliance for unusual cases.

Resolution 3: Authentication Anomaly Escalation

When the SWIFT system flags an authentication anomaly, the advising bank should follow a mandatory escalation protocol that includes compliance review, possible contact with the issuing bank, and a decision to advise or decline based on the investigation outcome.

Resolution 4: Balance Thoroughness with Timeliness

Advising banks should design their authenticity verification process to be both thorough and efficient. Standard verification steps should be routine and fast, with additional investigation reserved for cases that raise concerns.

Resolution 5: Maintain Updated Issuing Bank Records

Advising banks should maintain current records of known issuing banks, including their BIC codes, SWIFT authentication keys, and any known indicators of impersonation risk. These records support accurate and timely verification.

Resolution 6: Staff Training on Authentication Procedures

All staff involved in credit advisory functions should receive training on SWIFT authentication procedures, non-SWIFT verification methods, and the escalation protocol for authentication anomalies. This training should be refreshed regularly.

Resolution 7: Post-Verification Documentation

Every authenticity verification should be documented, including the verification method used, the outcome, and any anomalies identified. This documentation provides evidence of Article 9(a) compliance if the advising bank's performance is later questioned.

Conclusion

Authenticity verification under Article 9(a) is the advising bank's first line of defense — both for the bank itself and for the beneficiary. The standard of "reasonable care" requires a professional, systematic approach that employs SWIFT authentication, maintained records, and clear escalation procedures. Banks that invest in robust verification processes protect themselves, their beneficiaries, and the integrity of the documentary credit system.

Frequently Asked Questions

Q1: What does "reasonable care" mean in the context of authenticity verification?

Reasonable care means applying the level of diligence that a prudent banking professional would exercise in similar circumstances. It includes verifying SWIFT authentication, cross-referencing the issuing bank's identity, and escalating anomalies. It does not require forensic investigation or guarantee of authenticity.

Q2: Can the advising bank be held liable for advising a fraudulent credit?

Liability depends on whether the bank met the Article 9(a) standard of reasonable care. If the bank performed standard verification and the fraud was not detectable through those measures, liability is limited in most cases. If the bank skipped or rushed verification, it may be liable.

Q3: How does the advising bank handle credits from unknown issuing banks?

Credits from unknown issuing banks require additional verification. The advising bank should contact the issuing bank directly, verify through correspondent banking channels, or escalate to compliance before advising. Credits from unknown banks carry higher risk and require more rigorous verification.

Q4: What is the advising bank's obligation when SWIFT authentication fails?

When SWIFT authentication fails or raises anomalies, the advising bank should not advise the credit until the issue is resolved. The bank should contact the issuing bank through alternative channels to verify the credit's authenticity. If authenticity cannot be verified, the bank should decline to advise.

Q5: Does the advising bank need to verify the issuing bank's financial condition?

No. Article 9(a) requires verification of the credit's apparent authenticity, not the issuing bank's solvency. The advising bank verifies that the credit appears genuine, not that the issuing bank can pay. Financial assessment is outside the scope of authenticity verification.

Source Notes

Context only: This guide references the ICC UCP 600 (Uniform Customs and Practice for Documentary Credits), the ICC Academy educational materials on documentary credits, the ICC ISBP 745 (International Standard Banking Practice), and related ICC publications. All regulatory references are drawn from publicly available ICC materials. Source URLs and titles are catalogued in the provenance batch metadata for this guide (batch 28).