Skip to content

Glossary EDI

What is EDI? Electronic data interchange explained

Definition

EDI (electronic data interchange) is the exchange of business documents such as purchase orders, ship notices and invoices between the computer systems of different companies, in a structured format both sides have agreed on. The receiving system processes the data without anyone keying it in again. Its standards include UN/EDIFACT, published by the United Nations, and ANSI X12, maintained in the United States.

Two company systems, one on each side; structured documents in fixed fields travel between them: an orange one goes from left to right and a blue one comes back from right to left; at the top, a paper letter with a dashed border and an orange cross, on a dark blue ground.
On this page 14
  1. Origin of the term
  2. History and development
  3. How it works
  4. Types and variants
  5. Examples
  6. Advantages and disadvantages
  7. How it differs from related concepts
  8. Tools
  9. Criticism and limits
  10. Legal framework
  11. How to apply it, step by step
  12. Best practices
  13. Common mistakes
  14. How this entry was made
In brief

EDI, electronic data interchange between companies: how it works, EDIFACT and X12 messages, e-invoicing rules and how EDI differs from APIs and BMEcat.

Two company systems, one on each side; structured documents in fixed fields travel between them: an orange one goes from left to right and a blue one comes back from right to left; at the top, a paper letter with a dashed border and an orange cross, on a dark blue ground.

Origin of the term

The European Commission defined EDI in 1994 as "the electronic transfer, from computer to computer, of commercial and administrative data using an agreed standard to structure an EDI message" (Recommendation 94/820/EC). The same text says that an agreed standard includes, but is not limited to, UN/EDIFACT: the parties may agree on other standards. EDIFACT itself stands for "Electronic Data Interchange for Administration, Commerce and Transport". X12 describes itself as chartered by the American National Standards Institute (ANSI) for more than 40 years.

History and development

  • 1987: the Council of the European Communities sets up the TEDIS programme; its first phase (1988 to 1989) produces a draft European model EDI agreement.
  • July 1988: ISO publishes the first edition of ISO 9735, the EDIFACT syntax rules.
  • 1994: Commission Recommendation 94/820/EC on the legal aspects of EDI.
  • 2002: second edition of ISO 9735 (syntax version 4), last reviewed and confirmed by ISO in 2024.
  • July 2005: RFC 4130 defines AS2, a way to send X12 or EDIFACT messages securely over HTTP.
  • 16 April 2014: Directive 2014/55/EU on electronic invoicing in public procurement.
  • 18 April 2019: contracting authorities in the EU must accept e-invoices that follow the European standard.
  • 1 January 2025: every business in Germany must be able to receive e-invoices.
  • May 2026: a new version of part 1 of the European standard EN 16931 is published, according to the European Commission.

How it works

The buyer's ERP creates a purchase order. A converter, also called a translator, maps the internal fields to the agreed format, for example an X12 850 or an EDIFACT ORDERS message. The message travels to the supplier over a secure channel such as AS2, where the receiver confirms delivery with a signed receipt (MDN), or through an EDI service provider. On the supplier's side a second converter maps the message into its own ERP, which books the order without manual entry.

The reply follows the same path in the opposite direction: order acknowledgment, ship notice and invoice. Because each document refers to the previous one, the buyer's system can match invoice, delivery and order line by line.

Where an EDI order travels, and which documents go in each direction

Types and variants

StandardPublished byExample messages
UN/EDIFACTUNECE (United Nations)ORDERS (purchase order), ORDRSP (order response), DESADV (despatch advice), INVOIC (invoice)
ANSI X12X12, chartered by ANSI850 (purchase order), 855 (acknowledgment), 856 (ship notice/manifest), 810 (invoice)
GS1 EANCOMGS1A subset of UN/EDIFACT with only the elements GS1 users need

Source: UNECE, D.24A message directory; X12, "Transaction Sets"; GS1, "EANCOM", accessed 19.11.2026.

There are three ways to connect. Direct EDI links the two systems, each with its own converter. EDI through a service provider hands the routing and translation to a third party, which receives, converts and forwards messages. Web-EDI lets a small partner without a converter fill in or download documents on a web portal. For invoices there is also the Peppol network, a four-corner model in which buyer and supplier each connect through an accredited Peppol service provider; OpenPeppol, a non-profit association under Belgian law, runs it. In the United States, X12 lists health care and insurance among its member industries.

Examples

A distributor orders 200 boxes of screws from a manufacturer (illustrative case, no real companies):

  • The distributor's ERP sends an 850 purchase order with item number, quantity and requested delivery date.
  • The manufacturer answers with an 855 acknowledgment that confirms quantity and date.
  • When the truck leaves, it sends an 856 ship notice that lists the contents of each carton.
  • After delivery it sends an 810 invoice. The distributor's ERP matches it against the order and the ship notice before releasing payment.

In EDIFACT the same sequence is ORDERS, ORDRSP, DESADV and INVOIC.

Advantages and disadvantages

Data is entered once, at the source. The receiving system checks every field against the agreed format, so a wrong quantity or a missing tax number shows up on arrival. Order, ship notice and invoice refer to each other, which makes an automatic three-way match possible.

The cost sits in the setup. Each partner needs its own mapping and test cycle, because a shared standard still leaves the version, the segments used and the code lists to be agreed between two companies. For a small supplier with few orders the effort can outweigh the gain, and Web-EDI exists for that case.

How it differs from related concepts

BMEcat describes what can be bought: it is an XML format for exchanging product catalogue data between businesses. EDI handles what has been bought: order, ship notice and invoice. A company can use both, the catalogue to load items into the buyer's system and EDI for each transaction that follows. For catalogues, UN/EDIFACT also has the PRICAT message.

An API is defined by whoever offers it and answers each request at the moment it is made:

AspectEDIAPI
What is exchangedComplete business documents in an agreed standardRequests and responses in a format set by the API provider
TimingWhen the document is issuedWhen the other system asks
PartnersOne message format serves every partner using the standardEach interface has its own format
EffortMapping and tests per partnerDevelopment per interface

Source: Recommendation 94/820/EC and ISO 9735-1, accessed 19.11.2026; comparison by ZDS.

Tools

  • EDI converter or translator software: maps between the ERP and the standard.
  • EDI service provider: receives, translates and forwards messages.
  • Web-EDI portal: for partners without their own converter.
  • Peppol service provider: connects a company to the Peppol network.
  • Public e-invoicing platform of the Spanish Tax Agency, regulated by Order HAC/1028/2026.

Criticism and limits

EDI is still maintained and in use. X12 maintains its transaction sets through its Accredited Standards Committee, UNECE released the EDIFACT directory D.24A in 2024, and GS1 updated EANCOM in 2022. Spain's Royal Decree 238/2026 admits the EDIFACT invoice message for mandatory B2B e-invoicing, citing its "elevada penetración en un buen número de sectores económicos" (high penetration in a good number of economic sectors).

In practice, every new partner means agreeing on the format, mapping it and testing it. A mapping has to be updated whenever one side changes its ERP. A company that hands its messages to a service provider depends on that provider for routing and archiving.

How to apply it, step by step

  • Ask the partner which standard, version and messages it uses, and request its implementation guide.
  • Map each ERP field to the matching segment of the message.
  • Agree on the channel: direct connection, AS2, service provider or portal.
  • Exchange test messages and check acknowledgments before going live.
  • For invoices, check that the format meets EN 16931 or a syntax the law of the country allows.

Best practices

  • Document the mapping for every partner.
  • Validate outgoing messages before sending them.
  • Monitor acknowledgments; in AS2 they are called MDNs.
  • Keep master data in the ERP clean: item numbers, GTIN codes and addresses.

Common mistakes

  • Treating a PDF as an e-invoice.
  • Confusing Spain's VeriFactu with mandatory B2B e-invoicing.
  • Copying one partner's mapping to another without testing it.
  • Assuming that public authorities must accept EDIFACT: Directive 2014/55/EU only requires them to accept the European standard in UBL or CII.

How this entry was made

This entry was written in November 2026 with AI assistance. The facts come from EUR-Lex, the Spanish Official Gazette (BOE), the Spanish Tax Agency, Germany's Federal Ministry of Finance, UNECE via the Internet Archive, ISO, X12, GS1, OpenPeppol and RFC 4130, accessed 19.11.2026. It was checked before publication and contains no customer data.

Manuel Riveiro Rodriguez CEO & Digital Strategist

A technical audit covers this and everything else in one pass.

Request an audit

Frequently asked

What does EDI stand for?

Electronic data interchange: the exchange of business documents between computer systems in a structured, agreed format.

What are EDI transactions?

The individual business documents sent by EDI. In X12 each one is a numbered transaction set, such as 850 purchase order, 855 acknowledgment, 856 ship notice and 810 invoice.

What is the difference between EDI and API?

EDI sends complete documents in a standard shared by many partners. An API is defined by its provider and answers each request in real time.

Is EDI still used?

Yes. X12, UNECE and GS1 still maintain their standards, Spain admits the EDIFACT invoice message for B2B e-invoicing, and Germany allows EDIFACT for e-invoices by agreement.

What is the difference between EDIFACT and X12?

UN/EDIFACT is the international standard published by UNECE, with named messages such as ORDERS and INVOIC. X12 is the standard chartered by ANSI in the United States, with numbered transaction sets such as 850 and 810.

Sources

  1. EUR-Lex, Commission Recommendation 94/820/EC of 19 October 1994 relating to the legal aspects of electronic data interchange.
  2. Internet Archive, UNECE, "Introducing UN/EDIFACT", capture of 1 October 2025.
  3. Internet Archive, UNECE, "UN/EDIFACT Directories: 2021-2024", capture of 1 October 2025.
  4. Internet Archive, UNECE, "UN/EDIFACT D.24A - Message Type Directory", capture of 7 February 2026.
  5. ISO, "ISO 9735:1988 - Electronic data interchange for administration, commerce and transport (EDIFACT), Application level syntax rules".
  6. ISO, "ISO 9735-1:2002", EDIFACT syntax rules, part 1.
  7. X12, "About".
  8. X12, "X12 Transaction Sets".
  9. GS1, "GS1 EANCOM".
  10. RFC Editor, RFC 4130, "MIME-Based Secure Peer-to-Peer Business Data Interchange Using HTTP, Applicability Statement 2 (AS2)", July 2005.
  11. OpenPeppol, "About".
  12. EUR-Lex, Directive 2014/55/EU of the European Parliament and of the Council of 16 April 2014 on electronic invoicing in public procurement.
  13. EUR-Lex, Commission Implementing Decision (EU) 2017/1870 of 16 October 2017.
  14. EUR-Lex, Council Directive (EU) 2025/516 of 11 March 2025 as regards VAT rules for the digital age.
  15. BOE, Ley 18/2022, de 28 de septiembre, de creación y crecimiento de empresas (in Spanish).
  16. BOE, Real Decreto 238/2026, de 25 de marzo, mandatory e-invoicing between businesses (in Spanish).
  17. BOE, Orden HAC/1028/2026, de 2 de octubre, public e-invoicing platform (in Spanish).
  18. Agencia Tributaria, "Solución Pública de Facturación Electrónica (SPFE)" (in Spanish).
  19. BOE, Real Decreto 1007/2023, de 5 de diciembre, invoicing software requirements (in Spanish).
  20. Bundesfinanzministerium, "Fragen und Antworten zur Einführung der obligatorischen (verpflichtenden) E-Rechnung zum 1. Januar 2025" (in German).
  21. European Commission, "Obtaining a copy of the European standard on eInvoicing".