EDI EXPLAINER

Reference module

EDI Navigator

Industries, industry-specific use cases, standards and country rulebooks in one reference.

Industry:

Retail & consumer goods

Order-to-cash replenishment

Retailer sends ORDERS, supplier confirms with ORDRSP, ships with DESADV and SSCC labels, invoices with INVOIC.

Messages

ORDERSORDRSPDESADVRECADVINVOIC

Parties: Retailer ↔ supplier

Practice example

A grocery chain orders 480 brackets and 2 400 bolts for store cluster North. The supplier confirms the full quantity, ships two pallets with SSCC labels and invoices 7 969,20 EUR net 30.

Typical process flow

  1. ORDERS from retailer
  2. ORDRSP confirmation
  3. DESADV with SSCC
  4. RECADV goods receipt
  5. INVOIC settlement

Rule-setting bodies & associations

GS1 AISBL (GS1 Global Office)

International standards organisation

Website

Global identification keys, GDSN master data synchronisation, EPCIS event data and the GS1 healthcare and traceability standards.

Blue Tower, Avenue Louise 326, bte 10, 1050 Brussels, Belgium

+32 2 788 78 00

Rulebooks & documents

Open sample message in validatorLearn in the Academy

Retail & consumer goods

Vendor managed inventory

Stock and sales reports let the supplier plan replenishment instead of the retailer raising orders.

Messages

INVRPTSLSRPTDELFOR

Parties: Supplier plans for retailer

Practice example

A beverage brand receives daily stock and sales reports per store, refills below the agreed minimum and no purchase order is ever raised by the retailer.

Typical process flow

  1. INVRPT stock report
  2. SLSRPT sales report
  3. DELFOR replenishment plan
  4. DESADV delivery

Rule-setting bodies & associations

GS1 AISBL (GS1 Global Office)

International standards organisation

Website

Global identification keys, GDSN master data synchronisation, EPCIS event data and the GS1 healthcare and traceability standards.

Blue Tower, Avenue Louise 326, bte 10, 1050 Brussels, Belgium

+32 2 788 78 00

Rulebooks & documents

Open sample message in validatorLearn in the Academy

Retail & consumer goods

Catalogue & price synchronisation

Article master data, prices and promotions are exchanged before the first order.

Messages

PRICATPARTINGS1 CIN

Parties: Brand ↔ retailer / GDSN pool

Practice example

Before a seasonal launch the brand sends 180 new GTINs with pack hierarchy, list price and promotion window; the retailer only opens ordering after master data validation.

Typical process flow

  1. PARTIN party master data
  2. PRICAT catalogue
  3. Retailer validation
  4. First ORDERS

Rule-setting bodies & associations

GS1 AISBL (GS1 Global Office)

International standards organisation

Website

Global identification keys, GDSN master data synchronisation, EPCIS event data and the GS1 healthcare and traceability standards.

Blue Tower, Avenue Louise 326, bte 10, 1050 Brussels, Belgium

+32 2 788 78 00

Rulebooks & documents

Open sample message in validatorLearn in the Academy

Automotive

Forecast & JIT call-off

Rolling forecast (DELFOR / VDA 4905) refined by fine-grained JIT call-offs (DELJIT / VDA 4915) down to hour slots.

Messages

DELFORDELJITVDA 4905VDA 4915

Parties: OEM ↔ tier-1 supplier

Practice example

A tier-1 supplier receives a 26-week forecast every Monday; daily JIT call-offs then fix the exact quantity per unloading point and two-hour slot.

Typical process flow

  1. DELFOR rolling forecast
  2. DELJIT fine call-off
  3. Sequence call (JIS)
  4. DESADV per delivery

Rule-setting bodies & associations

Odette International Ltd.

European automotive network organisation

Website

Pan-European automotive supply-chain standards: OFTP2 transmission, global transport label (GTL) and EDIFACT automotive subsets.

71 Great Peter Street, London SW1P 2BN, United Kingdom

info@odette.org

Rulebooks & documents

Open sample message in validatorLearn in the Academy

Automotive

ASN & goods receipt

DESADV / VDA 4913 announces each shipment; labels and packaging data must match the physical handling unit.

Messages

DESADVVDA 4913RECADV

Parties: Supplier ↔ OEM plant

Practice example

Each truck carries 12 handling units with VDA 4902 labels; the ASN must arrive before the truck so the plant can book goods receipt by scanning only.

Typical process flow

  1. DESADV / VDA 4913 dispatch
  2. Label scan at gate
  3. RECADV goods receipt
  4. Discrepancy handling

Rule-setting bodies & associations

Odette International Ltd.

European automotive network organisation

Website

Pan-European automotive supply-chain standards: OFTP2 transmission, global transport label (GTL) and EDIFACT automotive subsets.

71 Great Peter Street, London SW1P 2BN, United Kingdom

info@odette.org

Rulebooks & documents

Open sample message in validatorLearn in the Academy

Automotive

Self-billing (credit note procedure)

The OEM creates the settlement document from goods receipts; the supplier reconciles instead of invoicing.

Messages

INVOIC (self-billing)VDA 4908REMADV

Parties: OEM ↔ supplier finance

Practice example

The OEM settles 4 300 received parts from the week's goods receipts and sends a remittance advice; the supplier posts it against open deliveries instead of invoicing.

Typical process flow

  1. Goods receipt basis
  2. Self-billing document
  3. REMADV remittance
  4. Supplier reconciliation

Rule-setting bodies & associations

Odette International Ltd.

European automotive network organisation

Website

Pan-European automotive supply-chain standards: OFTP2 transmission, global transport label (GTL) and EDIFACT automotive subsets.

71 Great Peter Street, London SW1P 2BN, United Kingdom

info@odette.org

Rulebooks & documents

Open sample message in validatorLearn in the Academy

Healthcare & pharma

Hospital procurement

Catalogue-based ordering with contract prices, delivery notes and e-invoicing to public hospitals.

Messages

PRICATORDERSDESADVINVOIC / XRechnung

Parties: Hospital ↔ medtech supplier

Practice example

A university hospital orders implants from a framework catalogue; the invoice must be an XRechnung with the correct Leitweg-ID or the payment run rejects it.

Typical process flow

  1. PRICAT contract catalogue
  2. ORDERS from hospital
  3. DESADV with batch data
  4. XRechnung invoice

Rule-setting bodies & associations

GS1 AISBL (GS1 Global Office)

International standards organisation

Website

Global identification keys, GDSN master data synchronisation, EPCIS event data and the GS1 healthcare and traceability standards.

Blue Tower, Avenue Louise 326, bte 10, 1050 Brussels, Belgium

+32 2 788 78 00

Rulebooks & documents

Open sample message in validatorLearn in the Academy

Healthcare & pharma

Serialisation & traceability

EPCIS events report commissioning, packing and shipping of serialised packs alongside the EDI flow.

Messages

EPCIS eventsDESADVINVRPT

Parties: Manufacturer ↔ wholesaler ↔ pharmacy

Practice example

Every pack carries a unique serial number; commissioning, aggregation and shipping events are reported so a pharmacy can verify authenticity at dispense.

Typical process flow

  1. Commissioning event
  2. Aggregation into cases
  3. Shipping event + DESADV
  4. Dispense verification

Rule-setting bodies & associations

GS1 AISBL (GS1 Global Office)

International standards organisation

Website

Global identification keys, GDSN master data synchronisation, EPCIS event data and the GS1 healthcare and traceability standards.

Blue Tower, Avenue Louise 326, bte 10, 1050 Brussels, Belgium

+32 2 788 78 00

Rulebooks & documents

Open sample message in validatorLearn in the Academy

Transport & logistics

Transport order & status

Shipper books transport (IFTMIN / 204); carrier replies with status events (IFTSTA / 214) until proof of delivery.

Messages

IFTMINIFTMBCIFTSTAX12 204X12 214

Parties: Shipper ↔ carrier

Practice example

A shipper books a partial load Hamburg–Milan; the carrier returns pickup, border and delivery status events that feed the customer's tracking page.

Typical process flow

  1. IFTMIN transport order
  2. IFTMBC booking confirmation
  3. IFTSTA status events
  4. Proof of delivery

Rule-setting bodies & associations

GS1 AISBL (GS1 Global Office)

International standards organisation

Website

Global identification keys, GDSN master data synchronisation, EPCIS event data and the GS1 healthcare and traceability standards.

Blue Tower, Avenue Louise 326, bte 10, 1050 Brussels, Belgium

+32 2 788 78 00

Rulebooks & documents

Open sample message in validatorLearn in the Academy

Transport & logistics

3PL warehouse integration

Stock, inbound and outbound instructions are exchanged with the logistics provider's WMS.

Messages

INVRPTWMS instructions (X12 940/945)RECADV

Parties: Brand owner ↔ 3PL

Practice example

The brand owner releases a warehouse shipping order to its 3PL; the 3PL confirms picking and returns the shipment advice used for the customer ASN.

Typical process flow

  1. 940 warehouse shipping order
  2. 945 shipping advice
  3. 846 stock status
  4. RECADV / returns

Rule-setting bodies & associations

GS1 AISBL (GS1 Global Office)

International standards organisation

Website

Global identification keys, GDSN master data synchronisation, EPCIS event data and the GS1 healthcare and traceability standards.

Blue Tower, Avenue Louise 326, bte 10, 1050 Brussels, Belgium

+32 2 788 78 00

Rulebooks & documents

Open sample message in validatorLearn in the Academy

Public sector

E-invoice to authorities

Supplier issues an EN 16931 compliant invoice (XRechnung UBL/CII) routed via Peppol or a national portal.

Messages

XRechnung (UBL)XRechnung (CII)Peppol BIS Billing 3.0

Parties: Supplier ↔ contracting authority

Practice example

A construction firm invoices a federal agency: XRechnung 3.0, Leitweg-ID in BuyerReference, payment terms and VAT breakdown validated against EN 16931 business rules.

Typical process flow

  1. Invoice creation (UBL/CII)
  2. Schematron validation
  3. Peppol or portal transmission
  4. Message level response

Rule-setting bodies & associations

Koordinierungsstelle für IT-Standards (KoSIT) — Freie Hansestadt Bremen

Public-sector coordination office

Website

Maintains the XRechnung standard, the German CIUS of EN 16931, its business rules (BR-DE) and the validator configuration.

c/o Die Senatorin für Finanzen, Rudolf-Hilferding-Platz 1, 28195 Bremen, Deutschland

+49 421 361-59578

info@kosit.org

Rulebooks & documents

Open sample message in validatorLearn in the Academy

Public sector

Electronic procurement documents

Order, despatch advice and message-level responses accompany the invoice in the Peppol post-award set.

Messages

Peppol OrderPeppol Despatch AdvicePeppol MLR

Parties: Authority ↔ supplier

Practice example

A municipality orders office furniture over Peppol; the supplier answers with a despatch advice and receives a message level response for each transmission.

Typical process flow

  1. Peppol Order
  2. Order response
  3. Despatch advice
  4. Invoice + MLR

Rule-setting bodies & associations

Koordinierungsstelle für IT-Standards (KoSIT) — Freie Hansestadt Bremen

Public-sector coordination office

Website

Maintains the XRechnung standard, the German CIUS of EN 16931, its business rules (BR-DE) and the validator configuration.

c/o Die Senatorin für Finanzen, Rudolf-Hilferding-Platz 1, 28195 Bremen, Deutschland

+49 421 361-59578

info@kosit.org

Rulebooks & documents

Open sample message in validatorLearn in the Academy

Energy & utilities

Supplier switching

UTILMD messages register, confirm or reject a change of supplier for a metering point.

Messages

UTILMDAPERAKCONTRL

Parties: Supplier ↔ grid operator

Practice example

A customer switches supplier: the new supplier requests the metering point master data, the grid operator confirms or rejects within the regulated deadline.

Typical process flow

  1. UTILMD registration
  2. Grid operator check
  3. APERAK confirm/reject
  4. Start of supply

Rule-setting bodies & associations

BDEW Bundesverband der Energie- und Wasserwirtschaft e. V. (EDI@Energy)

Industry association

Website

German energy market communication: UTILMD, MSCONS, INVOIC and APERAK message implementation guides with binding go-live dates.

Reinhardtstraße 32, 10117 Berlin, Deutschland

+49 30 300199-0

info@bdew.de

Rulebooks & documents

Bundesnetzagentur für Elektrizität, Gas, Telekommunikation, Post und Eisenbahnen

Federal regulator

Website

Regulatory decisions (GPKE, MaBiS, WiM) that make the EDI@Energy message formats and deadlines legally binding.

Tulpenfeld 4, 53113 Bonn, Deutschland

+49 228 14-0

info@bnetza.de

Rulebooks & documents

Open sample message in validatorLearn in the Academy

Energy & utilities

Metering data & billing

MSCONS transmits interval consumption which feeds grid usage invoicing (INVOIC) and reconciliation.

Messages

MSCONSINVOICREMADV

Parties: Metering operator ↔ supplier

Practice example

Fifteen-minute load profiles are transmitted daily per metering point and later reconciled against the grid usage invoice.

Typical process flow

  1. MSCONS metering values
  2. Plausibility check
  3. Balancing group settlement
  4. INVOIC grid usage

Rule-setting bodies & associations

BDEW Bundesverband der Energie- und Wasserwirtschaft e. V. (EDI@Energy)

Industry association

Website

German energy market communication: UTILMD, MSCONS, INVOIC and APERAK message implementation guides with binding go-live dates.

Reinhardtstraße 32, 10117 Berlin, Deutschland

+49 30 300199-0

info@bdew.de

Rulebooks & documents

Bundesnetzagentur für Elektrizität, Gas, Telekommunikation, Post und Eisenbahnen

Federal regulator

Website

Regulatory decisions (GPKE, MaBiS, WiM) that make the EDI@Energy message formats and deadlines legally binding.

Tulpenfeld 4, 53113 Bonn, Deutschland

+49 228 14-0

info@bnetza.de

Rulebooks & documents

Open sample message in validatorLearn in the Academy

Food & beverage

Fresh replenishment

Daily orders with catch-weight confirmation and batch/best-before data in the despatch advice.

Messages

ORDERSDESADVINVOICRECADV

Parties: Retailer ↔ producer

Practice example

A dairy delivers to a distribution centre with batch, best-before date and temperature data on every pallet; missing lot data blocks goods receipt.

Typical process flow

  1. ORDERS / DELFOR
  2. DESADV with batch + MHD
  3. RECADV with deviations
  4. INVOIC with weight-based pricing

Rule-setting bodies & associations

GS1 AISBL (GS1 Global Office)

International standards organisation

Website

Global identification keys, GDSN master data synchronisation, EPCIS event data and the GS1 healthcare and traceability standards.

Blue Tower, Avenue Louise 326, bte 10, 1050 Brussels, Belgium

+32 2 788 78 00

Rulebooks & documents

Open sample message in validatorLearn in the Academy

Industrial manufacturing

Consignment stock

Stock reports trigger settlement only on consumption, not on delivery.

Messages

INVRPTSLSRPTINVOIC

Parties: Supplier ↔ plant

Practice example

Consignment stock at the customer plant is reported weekly; only withdrawals are invoiced, so stock reports and settlement must match exactly.

Typical process flow

  1. INVRPT consignment stock
  2. Withdrawal report
  3. Self-billing / INVOIC
  4. Reconciliation

Rule-setting bodies & associations

UNECE — United Nations Centre for Trade Facilitation and Electronic Business (UN/CEFACT)

United Nations body

Website

Owner of the UN/EDIFACT directories, UNTDID code lists and Recommendation 20 unit codes used by every EDIFACT implementation.

Palais des Nations, 8-14 Avenue de la Paix, 1211 Geneva 10, Switzerland

+41 22 917 12 34

Rulebooks & documents

Open sample message in validatorLearn in the Academy

Industrial manufacturing

Catalogue punchout

Buyers shop in the supplier's webshop and return a structured cart into their ERP for approval.

Messages

cXML PunchOutOCIORDERS

Parties: Buyer ERP ↔ supplier shop

Practice example

An engineer configures a drive in the supplier's web shop and returns the cart to the ERP, which turns it into a regular EDI purchase order.

Typical process flow

  1. Punch-out session
  2. Cart transfer to ERP
  3. Approval workflow
  4. ORDERS / X12 850

Rule-setting bodies & associations

UNECE — United Nations Centre for Trade Facilitation and Electronic Business (UN/CEFACT)

United Nations body

Website

Owner of the UN/EDIFACT directories, UNTDID code lists and Recommendation 20 unit codes used by every EDIFACT implementation.

Palais des Nations, 8-14 Avenue de la Paix, 1211 Geneva 10, Switzerland

+41 22 917 12 34

Rulebooks & documents

Open sample message in validatorLearn in the Academy