eUCP Examination Rules for Electronic Records

Introduction

When a documentary credit is subject to eUCP, the examining bank must apply specific rules to evaluate electronic records that differ from — but supplement — the UCP 600 examination framework for paper documents. The examination of electronic records requires the bank to confirm format compliance, data carrier identification, content readability, and signature verification before it can assess substantive compliance. This guide examines the regulatory framework governing examination rules for electronic records under eUCP 2.1, identifies the failure modes that arise during electronic examination, and provides a deterministic resolution architecture.

The examination of electronic records is more complex than the examination of paper documents because electronic records require technical infrastructure (software, platforms, verification tools) that paper documents do not. The bank's examination obligation is content-based — it examines what the electronic record contains, not the technology that produced it — but the bank must first be able to open and read the record before content examination can begin.

Failure Mode Analysis

Failure Mode 1: Data Carrier Not Identified

The electronic record is presented without identifying the data carrier as required by eUCP 2.1 Article e3. The bank cannot determine what data carrier the record is stored on and may treat the presentation as non-compliant.

Root cause: The presenter does not understand the eUCP data carrier requirement, or the credit does not clearly specify eUCP application.

Failure Mode 2: Electronic Record Cannot Be Opened

The bank attempts to open the electronic record but the file is corrupted, encrypted without a key, or in a format not supported by the bank's software. Under eUCP 2.1 Article e9, the bank is not obliged to act on an electronic record it cannot examine.

Root cause: File corruption during transmission, incompatible software, or unsupported file format.

Failure Mode 3: Content Is Readable but Incomplete

The electronic record can be opened but the content is truncated, missing pages, or partially rendered. The bank cannot confirm that the data content fulfils the function of the required document because the content is incomplete.

Root cause: File size limitations, rendering issues, or incomplete file transfer.

Failure Mode 4: Electronic Signature Cannot Be Verified

The electronic record bears a digital signature, but the bank's systems cannot verify it — for example, the certificate authority is not recognised, or the signature format is not supported. Under eUCP 2.1 Article e10, the bank must confirm that the signature identifies the signer and indicates approval.

Root cause: Incompatible signature standards, expired certificates, or lack of verification tools.

Failure Mode 5: Multiple Electronic Records Create Conflicts

The presenter submits multiple electronic records that contain conflicting data — for example, an invoice showing "500 units" and a packing list showing "480 units." Under UCP 600 Article 14(d), data in documents must not conflict. The bank must identify and document each conflict.

Root cause: The presenter does not reconcile data across documents before submission.

Deterministic Resolution Architecture

Step 1: Confirm eUCP Applicability

Under eUCP 2.1 Article e1, the eUCP applies only when the credit indicates it. If the credit does not reference eUCP, standard UCP 600 examination rules apply to paper documents.

Step 2: Verify Data Carrier Identification

Under eUCP 2.1 Article e3, confirm that each electronic record identifies the data carrier. If the data carrier is not identified, request that the presenter resubmit with proper identification.

Step 3: Open and Render Each Electronic Record

Open each electronic record using the bank's standard software. Confirm that the file opens successfully, the content is readable, and no pages or data are missing. If a record cannot be opened, document the failure under eUCP 2.1 Article e9.

Step 4: Verify Electronic Signatures

Under eUCP 2.1 Article e10, check each electronic record for a signature. Confirm that the signature identifies the signer and appears to indicate approval of the data content. Attempt verification using available tools. Document any verification limitations.

Step 5: Examine Content Against Credit Requirements

Apply UCP 600 Article 14(b) examination standards to the data content of each electronic record. Confirm that the content appears to fulfil the function of the required document (eUCP 2.1 Article e6). Check for: correct document type, matching descriptions, correct amounts, consistent data across documents.

Step 6: Check for Data Conflicts

Under UCP 600 Article 14(d), compare data across all electronic records and against the credit. Identify any conflicts — mismatched quantities, different descriptions, inconsistent dates — and document each conflict.

Step 7: Issue a Refusal Notice for Examination Discrepancies

If any electronic record fails examination — format issues, signature problems, content conflicts, or data inconsistencies — issue a refusal notice under UCP 600 Article 16(c) and eUCP 2.1 Article e7. The notice must specify each discrepancy with clarity.

Conclusion

The examination rules for electronic records under eUCP 2.1 build upon the UCP 600 examination framework while addressing the unique challenges of electronic documents. The regulatory framework — eUCP 2.1 Articles e3, e5, e6, e7, e9, and e10; UCP 600 Articles 14(a), 14(b), 14(d), and 14(e); and ISBP 745 Paragraphs A1–A3 and A22 — establishes a content-based examination standard. Banks must first confirm format compliance and data carrier identification before examining the substantive content of electronic records. The five-banking-day examination timeframe applies equally to electronic records, and format failures do not extend this period. A systematic examination process — data carrier verification, file opening, signature checking, content examination, and conflict detection — ensures that electronic records are processed with the same rigor as paper documents.

FAQ

Q1: Does the bank need to verify the technical infrastructure that produced the electronic record?
No. Under eUCP 2.1 Article e6, the bank examines the data content, not the underlying infrastructure. The bank confirms that the electronic record appears to fulfil the function of the required document without verifying the technology that produced it.

Q2: What happens if the bank cannot open the electronic record?
Under eUCP 2.1 Article e9, if the electronic record cannot be examined due to format incompatibility or data carrier unavailability, the bank is not obliged to honour or negotiate. The bank should notify the presenter and request a readable version.

Q3: Is the five-banking-day examination timeframe different for electronic records?
No. Under UCP 600 Article 14(b), the five-banking-day timeframe applies from the date of presentation. For electronic records, the date of presentation is when the record is received by the bank (eUCP 2.1 Article e5). Format issues do not extend the timeframe.

Q4: Can the bank accept an electronic record without a signature?
If the credit requires a signed document and the electronic record bears no signature, the bank should refuse the presentation. Under eUCP 2.1 Article e10, the signature must identify the signer and indicate approval. Without a signature, the requirement is not met.

Q5: How does the bank handle electronic records that conflict with each other?
Under UCP 600 Article 14(d), data in documents must not conflict. The bank must identify each conflict and include it in the refusal notice under UCP 600 Article 16(c).

Q6: Does the bank need special software to examine electronic records?
The bank must have the capability to open and read the electronic records it receives. If the bank lacks the necessary software, it may not be able to examine the record under eUCP 2.1 Article e9. Banks are expected to maintain systems capable of handling common electronic document formats.

Source Notes

• eUCP Version 2.1 (ICC Supplement to UCP 600, 2019 revision) — Articles e1, e3, e5, e6, e7, e9, e10
• UCP 600 (ICC Publication No. 600, 2007 revision) — Articles 14(a), 14(b), 14(d), 14(e), 16(c)
• ISBP 745 (ICC Publication No. 745, 2013) — Paragraphs A1–A3, A22(a)
• ICC Academy — "Certified UCP 600 Specialist (CUCP)" (context only)
• ICC Commentary on UCP 600 (context only)