EDIFACT
Also: UN/EDIFACT · EDIFACT message · EDI format
EDIFACT is an internationally standardised format for exchanging structured business data electronically. Messages such as orders, despatch advices or invoices follow a fixed syntax; which fields a trading partner actually uses and expects is set out in their implementation guideline.
What it is
EDIFACT stands for "United Nations Electronic Data Interchange for Administration, Commerce and Transport". The syntax is standardised in ISO 9735; the UN/EDIFACT directories are maintained under the auspices of UN/CEFACT.
An EDIFACT message is a structured text file. It consists of segments with defined tags, for example BGM for document information, DTM for dates and times, NAD for the parties involved, or LIN for line items. Each segment in turn contains defined data elements.
Service segments structure the transmission: UNB and UNZ delimit an interchange, UNH and UNT an individual message. The message type defines its business meaning, for example ORDERS for purchase orders, DESADV for despatch advices or INVOIC for invoices. A directory version such as D.96A or D.01B is used in addition.
Individual industries have built their own application recommendations on top of this. A well-known example is EANCOM in retail. In the automotive industry, VDA and Odette specifications and procedures are used alongside EDIFACT. EDIFACT defines the message format, not the transmission method; for that, AS2, OFTP2 or SFTP are typically used.
In practice
The standard alone is not enough for a production connection. Many segments and data elements are optional or can be used in different ways. Trading partners therefore specify in implementation guidelines which fields they require, which code lists apply and which business rules must be observed.
Two customers can both ask for "EDIFACT ORDERS D.96A" and still require different mappings. The actual integration work consists of mapping those requirements cleanly onto the ERP, TMS or warehouse management system.
That involves more than field assignments. Units of measure may need converting, partner and internal article numbers mapping, dates normalising, and business plausibility checking. Before going live, messages are usually tested together with the trading partner and signed off.
We integrate the processing so that the message flows into the existing business process as directly as possible. Messages that are faulty or cannot be processed unambiguously are logged and made available for clarification.
When it affects you
Mid-sized companies typically encounter EDIFACT when larger customers or suppliers require structured electronic messages. This is especially widespread in retail, industry, automotive and logistics.
Three things determine the effort: the required message and version, the trading partner's implementation guideline, and the data quality in your own system. A concrete implementation guideline and one or two sample files therefore say considerably more than any general description of the EDIFACT standard.