eUCP Format Requirements for Electronic Documents
Introduction
When electronic documents are presented under a credit subject to eUCP, they must meet format requirements that enable the examining bank to open, read, and examine them. The format requirements under eUCP 2.1 are designed to ensure that electronic documents are functionally equivalent to paper documents while accommodating the unique characteristics of electronic records. This guide examines the regulatory framework governing format requirements for electronic documents under eUCP 2.1, identifies the failure modes that arise from format non-compliance, and provides a deterministic resolution architecture.
Format is the bridge between the electronic record and the examining bank's ability to fulfil its examination obligations. A perfectly compliant document in an unreadable format is as useless as a missing document. Understanding the format requirements — both the eUCP minimum standards and any additional requirements specified in the credit — is essential for every party in an eUCP transaction.
Failure Mode Analysis
Failure Mode 1: Data Carrier Not Identified
The electronic document is presented without identifying the data carrier as required by eUCP 2.1 Article e3. The bank receives the electronic record but cannot determine what data carrier it is stored on. Without data carrier identification, the bank 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: Format Not Supported by Bank's Systems
The electronic document is in a format that the bank's systems cannot open — for example, a proprietary format, an encrypted file, or 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: The presenter uses a format that is not widely supported, or the bank's systems have not been updated to support the format.
Failure Mode 3: Additional Format Requirements Not Met
The credit specifies additional format requirements (e.g., "electronic documents must be in PDF/A format"), but the presenter submits documents in a different format. Under eUCP 2.1 Article e4, additional format requirements stated in the credit must be met.
Root cause: The presenter does not read the credit's format requirements, or the presenter's systems do not support the required format.
Failure Mode 4: Format Degradation During Transmission
The electronic document is transmitted in a format that degrades during transmission — for example, a compressed image file that loses resolution, a spreadsheet that loses formulae, or a PDF that loses embedded fonts. The bank receives the document but cannot read it properly. Under eUCP 2.1 Article e6, the document must appear to fulfil the function of the required document.
Root cause: Transmission through incompatible systems, compression algorithms that lose data, or file conversion during transmission.
Failure Mode 5: Format Does Not Preserve Electronic Signature
The electronic document is converted to a format that strips or obscures the electronic signature — for example, converting a signed PDF to an image format (JPEG or PNG) that renders the signature non-verifiable. Under eUCP 2.1 Article e10, the signature must identify the signer and indicate approval of the data content.
Root cause: The presenter converts documents to a simpler format for transmission, not understanding that the signature must be preserved.
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 paper-based requirements apply.
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: Check for Additional Format Requirements
Under eUCP 2.1 Article e4, read the credit to determine whether it specifies additional format requirements (e.g., PDF/A, XML, specific standard). Confirm that the presented documents comply with any specified requirements.
Step 4: Attempt to Open the Electronic Record
Open the electronic record using the bank's standard software. If the record cannot be opened due to format incompatibility, document the failure and notify the presenter under eUCP 2.1 Article e9.
Step 5: Verify Content Preservation
Confirm that the electronic record's content is readable and preserved — text is legible, tables are intact, images are clear, and signatures are verifiable. Under eUCP 2.1 Article e6, the data content must appear to fulfil the function of the required document.
Step 6: Verify Signature Format
Under eUCP 2.1 Article e10, confirm that the electronic signature is in a format that the bank can verify. If the signature cannot be verified due to format issues, document the limitation and assess whether the record otherwise appears compliant.
Step 7: Issue a Refusal Notice for Format Discrepancies
If the electronic document fails format verification, issue a refusal notice under UCP 600 Article 16(c) and eUCP 2.1 Article e9. The notice must state the specific format issue (e.g., "electronic record cannot be opened — format not supported").
Conclusion
Format requirements for electronic documents under eUCP 2.1 are governed by Articles e2, e3, e4, e6, e9, e10, e11, and e12, which require that electronic records be identifiable, readable, and capable of examination. The framework — eUCP 2.1 Articles e2–e12; UCP 600 Articles 14(a), 14(b), and 14(e); and ISBP 745 Paragraphs A1–A3, A22, and E11–E18 — does not prescribe specific file formats but requires that the format preserve the document's functional content. The key risks are data carrier identification failure, format incompatibility, additional format requirement non-compliance, format degradation during transmission, and signature stripping. A systematic format verification process ensures that electronic documents can be examined within the UCP 600 five-banking-day timeframe.
FAQ
Q1: Does eUCP specify which file formats are acceptable?
No. eUCP 2.1 Article e3 requires that the electronic record be in a format the bank can open and examine, but it does not prescribe specific formats. The credit may specify additional format requirements under Article e4.
Q2: What if the credit specifies PDF/A but I submit a standard PDF?
Under eUCP 2.1 Article e4, additional format requirements stated in the credit must be met. Submitting a standard PDF when the credit requires PDF/A is a format discrepancy.
Q3: What happens if the bank's software cannot open my electronic document?
Under eUCP 2.1 Article e9, if the electronic record cannot be examined due to format incompatibility, the bank is not obliged to honour or negotiate. You must resubmit in a format the bank can examine.
Q4: Can I combine multiple documents in one electronic file?
No, it is not. Under eUCP 2.1, each electronic record is a separate document. Combining multiple documents into one file may create examination difficulties and may not comply with the credit's requirement for separate documents.
Q5: Is a scanned image of a paper document acceptable as an electronic document?
A scanned image may be acceptable if the bank can open and read it. However, scanned images may not preserve electronic signatures, and the content may be degraded. Under eUCP 2.1 Article e6, the data content must appear to fulfil the function of the required document.
Q6: What if the document is readable but the signature is stripped?
If the credit requires a signed document and the format strips the signature, this is a discrepancy under eUCP 2.1 Article e10. The signature must identify the signer and indicate approval of the data content.
Source Notes
- eUCP Version 2.1 (ICC Supplement to UCP 600, 2019 revision) — Articles e1, e2, e3, e4, e6, e9, e10, e11, e12
- UCP 600 (ICC Publication No. 600, 2007 revision) — Articles 14(a), 14(b), 14(e)
- ISBP 745 (ICC Publication No. 745, 2013) — Paragraphs A1–A3, A22(a), E11–E18
- ICC Commentary on UCP 600 (context only)
- ICC Academy — "Certified UCP 600 Specialist (CUCP)" (context only)
Article 16(c) and eUCP 2.
| Regulation | Article / Section | Requirement | Consequence |
|---|---|---|---|
| UCP 600 | Article 14 | Standard for Examination of Documents | Binary determination (compliant/discrepant) |
| UCP 600 | Article 16 | Discrepant Documents, Waiver and Notice | Binary determination (compliant/discrepant) |
← Scroll horizontally to see all columns
Quick Reference Summary
- No reference captured.
Compliance Checklist
| ✓ What Banks Expect | ✗ What Beneficiaries Often Do Wrong |
|---|---|
| Data Carrier Not Identified | The electronic document is presented without identifying the data carrier as required by eUCP 2.1... |
| Format Not Supported by Bank's Systems | The electronic document is in a format that the bank's systems cannot open — for example, a propr... |
| Additional Format Requirements Not Met | The credit specifies additional format requirements (e.g., "electronic documents must be in PDF/A... |
| Format Degradation During Transmission | The electronic document is transmitted in a format that degrades during transmission — for exampl... |
| Format Does Not Preserve Electronic Signature | The electronic document is converted to a format that strips or obscures the electronic signature... |
← 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 generates compliant eUCP Format Requirements for Electronic Documents — 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