What is an EDI File? EDI Formats Guide

In this blog, we cover:

• What is an EDI File?
• Key Features of an EDI file
• How EDI Files Work
• How EDI File Formats Work
• 5 Most Common EDI File Format Standards
• Choose the Right Solution for Your EDI Files
   

EDI standards are the core rules that dictate how B2B documents—like purchase orders, invoices, and order responses—are formatted and structured for seamless data exchange. These standards are also foundational for supply chain orchestration, where standardized documents plus real-time data help keep end-to-end processes aligned across a multi-enterprise network.

These strict guidelines ensure that documents are consistently structured, allowing businesses to communicate clearly and efficiently. Once formatted, these documents are transmitted using EDI protocols to trading partners or service providers, automating transactions and reducing errors. This is typically executed using an EDI tool or cloud EDI solution.

What is an EDI File?

An EDI file (Electronic Data Interchange file) is a standardized format used for exchanging business documents electronically between companies. These files are structured in a specific way, following predefined rules that enable different systems to understand and process the data automatically without manual intervention.

In summary, an EDI file facilitates the automatic exchange of structured data between business partners, streamlining transactions and reducing errors.
 

Key Features of an EDI File:

Standardized Format: EDI files use standardized formats like ANSI X12 (used in North America) or EDIFACT (used internationally), which define how data is organized and what each segment represents.

Document Types: EDI files can represent a wide range of business documents such as purchase orders, invoices, shipping notices, and payment instructions.

Segments and Elements: An EDI file is composed of segments (like lines in a document) and elements (pieces of information within each segment). For example, a segment could represent an invoice, and its elements could be the invoice number, date, amount, etc.

Machine-Readable: EDI files are designed to be machine-readable so that they can be processed automatically by systems with minimal human intervention.

Encryption and Security: EDI files often contain sensitive business information, so they are typically transmitted over secure communication channels like AS2 (Applicability Statement 2) or SFTP (Secure File Transfer Protocol).

How EDI File Formats Work

EDI file formats follow strict standards to ensure that systems receiving these files can interpret the information accurately. Each element within the file is placed in a predefined location, allowing the receiving machine to recognize and process the data correctly. Without such standards, systems wouldn’t be able to identify which part of the message corresponds to which data, making automated exchange impossible.

Although EDI documents might look like a string of seemingly random letters, numbers, and symbols, they adhere to a well-defined structure. This structure is typically based on four key principles:

• Syntax: Syntax rules govern the specific characters and symbols that can be used in an EDI file and their proper order.
• Codes: Codes are employed to represent common information, such as currency codes, country abbreviations, or date formats, ensuring consistent interpretation.
• Message Designs: Each type of EDI document, like an invoice or a purchase order, follows a specific message design. This design defines how the document is structured and which rules from the syntax are applied.
   

Identification Values: Data in an EDI file is identified based on its position or through the use of separators. The way these values are recognized can vary depending on the EDI standard in use.

In addition to these principles, most EDI standards are made up of three core components:

• Elements: These are the smallest units of data, representing individual values like "50," "USD," or "Product A."
• Segments: Segments are collections of elements that convey a more comprehensive piece of information, such as "50 units of Product A in USD."
• Transaction Sets: A transaction set is a full document, such as an invoice or purchase order, made up of multiple segments.

Different EDI standards function like different languages. Just as languages have distinct words and sentence structures, EDI standards use specific formats and rules to organize and convey business information across systems.

The 5 Most Common EDI File Format Standards

1) UN/EDIFACT

The UN/EDIFACT standard (United Nations rules for Electronic Data Interchange for Administration, Commerce, and Transport) is the most widely used EDI format outside North America. It is adopted across various industries, with subsets like EANCOM (used in retail) automating industry-specific data exchanges.

EDIFACT documents are recognized by six-letter codes, such as ORDERS (purchase orders), INVOIC (invoices), and DESADV (dispatch advice). Each message follows a structured sequence of segments:

UNA – defines separators, delimiters, and special characters for interpreting software
UNB – file header (paired with UNZ, the file end, to form an envelope)
UNG – group start
UNH – message header
UNT – message end
UNE – group end
UNZ – file end
EDIFACT also includes transmission guidelines, ensuring that the structure of message exchanges is consistent. For more details, see our blog on EDIFACT file structure.

2) TRADACOMS

The TRADACOMS standard, introduced before EDIFACT, is primarily used in UK domestic trade, especially in the retail industry. TRADACOMS consists of 26 message types, each identified by a six-letter reference.

A transmission includes multiple messages, such as:

ORDHDR – Order Header
ORDERS – Individual Orders
ORDTLR – Order Trailer
Segments used for ease of translation include:

STX – Start of Interchange
MHD – Message Header
MTR – Message Trailer
END – End of Interchange

3) ANSI ASC X12

ANSI ASC X12 (American National Standards Institute Accredited Standards Committee X12) was developed in 1979 to standardize EDI across North America. Today, it is used by nearly half a million businesses worldwide.

X12 files are identified by three-digit codes, such as 810 for invoices. X12 also includes subsets tailored for different industries, such as:

AIAG – Automotive Industry Action Group
CIDX – Chemical Industry Data Exchange
EIDX – Electronics Industry Data Exchange Group (CompTIA)
HIPAA – Health Insurance Portability and Accountability Act
PIDX – American Petroleum Institute
UCS – Uniform Communication Standard
VICS – Voluntary Interindustry Commerce Standards (used in retail)
X12 documents consist of mandatory segments such as:

ISA – Start of interchange
GS – Start of functional group
ST – Start of transaction set
SE – End of transaction set
GE – End of functional group
IEA – End of interchange
These segments are made up of elements that define specific data within the document. For more details, refer to our article on the structure of X12 documents.

4) VDA

The Verband der Deutschen Automobilindustrie (VDA), or Association of the Automotive Industry, developed the VDA EDI standard in 1977, making it older than EDIFACT. VDA message types are identified by four-digit codes, like 4905 for delivery forecasts.

VDA documents use a fixed-length format rather than segments and separators. Each data element has a set length, and when the transmitted data is shorter, spaces are used to fill the gaps. This format limits the amount of data that can be sent and complicates conversion to other standards.

While VDA standards are still in use, they are gradually being replaced by EDIFACT in the automotive sector. Transition guidelines from VDA to EDIFACT have been published to help with this shift.

5) UBL

Universal Business Language (UBL) is an XML-based EDI standard developed by OASIS (Organization for the Advancement of Structured Information Standards). UBL documents are easier to read compared to traditional EDI formats, though their file sizes are larger due to the XML structure. This is less of a concern today thanks to broadband internet.

Initially, UBL had seven file formats in 2003. By version 2.2 (released in 2018), this had grown to over 80 document types. UBL is one of two syntaxes compliant with new EU e-invoicing regulations set by CEN/TC434, which is why its usage is expected to increase, particularly with the rise of PEPPOL.

UBL message types are organized into higher-level categories like pre-award sourcing, post-award sourcing, procurement, and transportation. UBL also supports tools like validators, generators, parsers, and authoring software.

Each of these EDI standards serves distinct industries and purposes, ensuring the efficient exchange of business data.

Choose the Right Solution for Your EDI Files

Most businesses are not all that well-versed in EDI or EDI integration, and it's why so many today are moving toward EDI solutions. By refocusing your employees' time on core business initiatives and leaving the tedium of EDI to the experts, you'll be able to more quickly execute on your important business goals.

Cleo Integration Cloud modernizes your EDI by connecting, integrating, and analyzing the end-to-end data flows across your ecosystem and internal systems. Cleo also helps teams extend EDI beyond file exchange by supporting supply chain orchestration, so partners, documents, and key processes stay aligned as requirements change.With cloud-based EDI from Cleo, modern enterprises can:

• Accelerate EDI partner onboarding
• Say "yes" to new integration requirements
• Scale to meet changing market demands
• Drive more revenue

Contact Cleo today to set up a demo to learn how Cleo Integration Cloud can solve your EDI challenges.