Digital Trade

eUCP Electronic Document Format Standards

📅 2026-07-13 7 min read UCP 600 / ISBP 745

Introduction

When electronic documents are presented under a credit subject to eUCP, they must comply with format standards that enable the examining bank to open, read, and examine the documents. Unlike paper documents, which are universally readable with the naked eye, electronic documents require specific software and file formats for examination. This guide examines the regulatory framework governing electronic document format standards under eUCP 2.1, identifies the failure modes that arise from format non-compliance, and provides a deterministic resolution architecture.

The format of an electronic document determines whether the bank can fulfil its examination obligations under UCP 600 and eUCP 2.1. A document that cannot be opened or read fails at the first step of examination, regardless of its substantive content.

Failure Mode Analysis

Failure Mode 1: Incompatible File Format

The electronic document is presented in a format that the bank's systems cannot open — for example, a proprietary format, an encrypted file without decryption key, 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 2: 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 with eUCP.

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

Failure Mode 3: 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 4: Multiple Documents in Single File

The presenter combines multiple required documents into a single electronic file (e.g., a multi-page PDF containing the invoice, packing list, and certificate of origin). Under eUCP 2.1, each electronic record is a separate document. Combining documents may create examination difficulties and may not comply with the credit's document-by-document requirements.

Root cause: The presenter consolidates documents for convenience, not understanding that each document must be a separate electronic record under eUCP.

Failure Mode 5: Format Does Not Preserve Signatures

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. A format that strips the signature destroys this functionality.

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, electronic documents are not governed by eUCP format rules.

Step 2: Verify Data Carrier Identification

Under eUCP 2.1 Article e3, each electronic record must identify the data carrier. Confirm that the data carrier is identified and that the bank can access it.

Step 3: 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 4: 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 5: Check for Additional Format Requirements in the Credit

If the credit specifies additional format requirements (e.g., "electronic documents must be in PDF/A format"), confirm that the presented documents comply. Under eUCP 2.1 Article e4, additional formatting requirements stated in the credit must be met.

Step 6: Separate Combined Documents

If the presenter has combined multiple documents into a single file, request that each document be presented as a separate electronic record. Under eUCP 2.1, each document is a separate electronic record that must be examined individually.

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

Electronic document format standards under eUCP 2.1 are governed by Articles e2, e3, e4, e6, and e9, which require that electronic records be identifiable, readable, and capable of examination. The framework — eUCP 2.1 Articles e2–e9; UCP 600 Articles 14(a) and 14(b); and ISBP 745 Paragraphs A1–A3 and A22 — does not prescribe specific file formats but requires that the format preserve the document's functional content. The key risks are format incompatibility, data carrier identification failure, format degradation during transmission, and signature stripping. A systematic format verification process ensures that electronic documents can be examined within the UCP 600 five-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 that 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 happens if the bank's software cannot open the 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. The presenter must resubmit in a format the bank can examine.

Q3: Can the credit require a specific format like PDF/A?
Yes. Under eUCP 2.1 Article e4, the credit may specify additional formatting requirements. If the credit requires PDF/A and the presenter submits a standard PDF, this is a format discrepancy.

Q4: Is it acceptable to combine multiple documents in one 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: 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. A format that strips the signature fails this requirement.

Q6: Can the bank convert the electronic document to a readable format?
No. Under UCP 600 Article 14(a), banks act on the basis of documents alone. The bank examines the document as presented. It is not the bank's obligation to convert or repair the presenter's documents.

Source Notes

Did You Know?

Article 16(c) and eUCP 2.

Regulatory Reference Table
RegulationArticle / SectionRequirementConsequence
UCP 600Article 14Standard for Examination of DocumentsBinary determination (compliant/discrepant)
UCP 600Article 16Discrepant Documents, Waiver and NoticeBinary determination (compliant/discrepant)

← Scroll horizontally to see all columns

Quick Reference Summary

  • No reference captured.

Compliance Checklist

0 of 5 completed
Bank Expectations vs Common Beneficiary Mistakes
✓ What Banks Expect✗ What Beneficiaries Often Do Wrong
Incompatible File FormatThe electronic document is presented in a format that the bank's systems cannot open — for exampl...
Data Carrier Not IdentifiedThe electronic document is presented without identifying the data carrier as required by eUCP 2.1...
Format Degradation During TransmissionThe electronic document is transmitted in a format that degrades during transmission — for exampl...
Multiple Documents in Single FileThe presenter combines multiple required documents into a single electronic file (e.g., a multi-p...
Format Does Not Preserve SignaturesThe 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 Compliance Engine

DraftLC generates compliant eUCP Electronic Document Format Standards — 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