---
title: "UN/EDIFACT explained: the UN standard for EDI | Quantlix"
description: "UN/EDIFACT is the United Nations standard for EDI messages such as ORDERS, INVOIC and DESADV. Learn how the syntax, directories and subsets work in practice."
canonical: "https://quantlix.com/en/standards/un-edifact/"
last-updated: 2026-11-16
---

Source: https://quantlix.com/en/standards/un-edifact/
Language: en
Description: UN/EDIFACT is the United Nations standard for EDI messages such as ORDERS, INVOIC and DESADV. Learn how the syntax, directories and subsets work in practice.

**UN/EDIFACT** [Product, trade and travel data](https://quantlix.com/en/standards/#exchange)

# UN/EDIFACT: the United Nations standard for EDI messages

UN/EDIFACT is the United Nations standard for electronic data interchange, with syntax rules and message directories that companies, carriers and customs authorities use to exchange orders, invoices and transport data.

[Discuss your project](https://quantlix.com/en/contact/) [Read the key points](https://quantlix.com/en/standards/un-edifact/#standard-overview)

## At a glance

**Full name**

United Nations rules for Electronic Data Interchange for Administration, Commerce and Transport (UN/EDIFACT)

**Published by**

UN/CEFACT, the UN Centre for Trade Facilitation and Electronic Business at UNECE; the syntax rules are published by ISO as ISO 9735 (ISO/TC 154)

**Type**

International EDI standard: syntax rules, message and code directories, and design guidelines

**Current version**

Syntax version 4 in the ISO 9735 series (Part 1 is ISO 9735-1:2002, confirmed by ISO); directories are issued as dated UNTDID releases, such as D.24A in 2024

**Applies to**

Manufacturers, retailers, carriers, ports, customs authorities and service providers that exchange structured trade and transport messages

**Last reviewed**

November 16, 2026 (2026-11-16)

## In plain terms

### Key points

- UN/EDIFACT has three layers: ISO 9735 syntax rules, the UNTDID directories of messages and codes, and guidelines for using them.
- Messages have six-letter names, such as ORDERS for a purchase order, INVOIC for an invoice and DESADV for a despatch advice.
- Directories are released under names like D.01B, and trading partners agree which one they use.
- Most real exchanges follow a subset or partner guide, such as GS1 EANCOM for retail, rather than the full message.

### What is UN/EDIFACT?

UN/EDIFACT is **the United Nations standard for exchanging business documents as structured electronic messages**. It defines how a purchase order, an invoice, a shipping notice or a customs declaration is laid out, so one company’s system can send it and another company’s system can read it without anyone retyping data.

UN/CEFACT, the UN Centre for Trade Facilitation and Electronic Business, maintains the directories, while the syntax rules are published by ISO as the ISO 9735 series. The standard has carried international trade data since the late 1980s and is still the default electronic data interchange (EDI) language in many supply chains. Its value is neutrality: a shared, public message catalog means a manufacturer in one country and a carrier or customs office in another can agree on a format without either one inventing it.

### What UN/EDIFACT covers

- **Syntax rules.** ISO 9735 defines interchanges, messages, segments, composite and simple data elements, separators and character sets. Syntax version 4 added parts for interactive exchange and for security services.
- **Directories.** The United Nations Trade Data Interchange Directory (UNTDID) lists the standard messages, segments, data elements and code lists, issued as dated releases.
- **Messages.** A large catalog of message types with six-letter names, from ORDERS, INVOIC and DESADV to IFTSTA for transport status and CUSDEC for customs declarations.
- **Envelopes.** UNB and UNZ wrap an interchange, UNH and UNT wrap each message, and an optional UNA segment declares the separators in use.
- **Acknowledgments.** The CONTRL message reports whether an interchange was received and passed syntax checks.
- **Design guidelines.** Rules for designing new messages and for implementing the syntax consistently.

### Directories, subsets and partner guides

Each directory release is named by year and sequence, for example D.01B or D.24A, and **partners must agree on the same directory and message version before anything works**. Because changing a directory means retesting every connection, mature communities often stay on an older one for years.

Few companies implement a full message. Industry groups publish subsets that keep only the segments and codes their sector needs: GS1 EANCOM for retail and consumer goods (built on D.01B and using [GTINs](https://quantlix.com/en/standards/gs1-gtin/) and location numbers), plus other subsets for automotive, container shipping and electronics. Large trading partners then publish their own guides on top, listing mandatory fields and code values. In North America, the equivalent role is played by [ANSI X12](https://quantlix.com/en/standards/ansi-x12/).

### How it shows up in software projects

- **Mapping.** Each partner’s guide is mapped to internal ERP or warehouse fields, with code lists translated in both directions.
- **Envelope and control numbers.** Interchange and message references are generated, stored and checked so duplicates and gaps are caught.
- **Validation and acknowledgments.** Inbound files are checked against the agreed directory and subset, with CONTRL or functional responses sent back.
- **Transport.** Messages travel over AS2, SFTP, a value-added network or an EDI provider, each with its own monitoring.
- **Partner onboarding.** Test exchanges, sample files and a sign-off record for each new partner and message type.

### How we work with UN/EDIFACT

We build and modernize EDI integrations: partner mappings into [ERP solutions](https://quantlix.com/en/services/erp-solutions/), validation and monitoring, acknowledgment handling and the move from aging translators to maintainable services. A lot of this work supports [logistics and supply chain](https://quantlix.com/en/industries/logistics-and-supply-chain/) companies, where EDIFACT still carries daily orders and transport events.

Each trading partner decides whether your messages meet its guide, usually through test cycles it runs. We prepare for those tests carefully, keep the mappings documented and versioned, and make failures easy to trace back to the field that caused them.

## Where it applies

Industries where this standard often shapes the work.

- ### [Logistics & Supply Chain](https://quantlix.com/en/industries/logistics-and-supply-chain/)

  Demand forecasting, inventory visibility and transport planning

## Related standards

[All standards](https://quantlix.com/en/standards/)

- ANSI X12

  ### [North American EDI transactions](https://quantlix.com/en/standards/ansi-x12/)

  ANSI X12 is the EDI standard maintained by X12, an ANSI-accredited organization, defining transaction sets such as the 850 purchase order, 856 ship notice and 837 health care claim used across North America.
- GS1 GTIN

  ### [Global product identification numbers](https://quantlix.com/en/standards/gs1-gtin/)

  GS1 GTIN is the Global Trade Item Number, the identifier a brand owner assigns to each product or service it prices, orders or invoices, carried in retail barcodes and product data around the world.
- ISO 20022

  ### [Financial messaging standard](https://quantlix.com/en/standards/iso-20022/)

  ISO 20022 is the international standard for building financial messages from a shared business model. It is now used for cross-border payments on Swift and by major high-value payment systems.

## Services that support this work

The services we usually bring to projects that involve this standard.

[View all services](https://quantlix.com/en/services/)

### [Enterprise applications](https://quantlix.com/en/services/enterprise-applications/)

Quantlix designs and builds enterprise applications for internal workflows, business rules and system integration, with clear access controls and maintainable architecture.

### [ERP solutions](https://quantlix.com/en/services/erp-solutions/)

Quantlix develops and integrates ERP solutions that connect operational records, business processes and reporting across enterprise functions.

### [Legacy modernization](https://quantlix.com/en/services/legacy-modernization/)

Quantlix modernizes existing systems through targeted changes, integration and staged migration, preserving essential business behavior while addressing technical constraints.

## Questions, answered

What teams usually ask us about this standard.

**What is the difference between UN/EDIFACT and ANSI X12?**

Both are EDI standards with similar ideas but different syntax, message names and governance. UN/EDIFACT is maintained internationally by UN/CEFACT and is widely used in Europe, Asia and global transport, while X12 is maintained by the ANSI-accredited X12 organization and dominates North American EDI.

**Which EDIFACT directory version should we use?**

The one your trading partner or community guideline names. Older directories stay in use for many years because changing them means retesting every partner; GS1 EANCOM 2002, for example, is based on directory D.01B.

**Is UN/EDIFACT free to use?**

The UN/EDIFACT directories can be downloaded from the UNECE website at no cost. The ISO 9735 syntax standard is sold by ISO and national standards bodies, and industry subsets such as EANCOM are published by their own organizations.

**What does the UNA segment do?**

UNA is the service string advice at the start of an interchange. It states which characters the file uses as separators, decimal mark and release character, so a parser does not have to assume the defaults.

**Is EDIFACT being replaced by APIs and XML?**

Gradually and unevenly. UN/CEFACT also publishes XML-based standards built from its Core Component Library, and many partners now offer APIs, yet a large share of trade and transport traffic still runs on EDIFACT because it works and is deeply embedded.

## Official sources

Read the official text before relying on any detail. What applies to you depends on your role, your location and the version in force.

- [Introducing UN/EDIFACT (UNECE)](https://unece.org/trade/uncefact/introducing-unedifact)
- [UN/EDIFACT directories download (UNECE)](https://unece.org/trade/uncefact/unedifact/download)
- [ISO 9735-1:2002 (ISO/TC 154)](https://www.isotc154.org/standards/iso-9735-12002/)

These guides explain each standard in plain terms. They are not legal advice, and they do not state that any product or organization conforms to a standard.

## Planning software around this standard?

Tell us which systems are involved and what you need to show. We will help you build the requirements in from the start.

[Discuss your project](https://quantlix.com/en/contact/)
