Resources · Automotive EDI
VDA EDI messages and editions
The VDA recommendations are the German automotive industry's way of exchanging call-offs, despatch advices, invoices, payments, stock and transport data. They run from the original flat-file record layouts of the 1980s and 1990s to today's EDIFACT-based recommendations. This page lists every numbered recommendation with its format, edition and what replaced it.
- Published by
- VDA, Arbeitskreis SID (EDI)
- Formats
- Flat file, EDIFACT, XML
- List status
- August 2024
- Entries listed
- 66
Each colored card is one business area. The codes on a card are the VDA recommendation numbers in that area; the tables below the drawing give every message, edition and status.
Overview
What VDA is
VDA recommendations are numbered 4900 to 4999. The early ones define flat files made of fixed record types (the "VDA record types", or Satzarten): 4905 for delivery call-offs, 4913 for delivery notes and transport data, 4906 for invoices and 4907 for payment advices. They are old, but they are still exchanged every day between vehicle makers and suppliers.
Since the late 1990s VDA has replaced most of them with recommendations built on UN/EDIFACT: 4984 (DELFOR) for call-offs, 4985 and 4986 (DELJIT) for just-in-time and just-in-sequence calls, 4987 (DESADV) for despatch advices, 4938 for invoices and 4988 (REMADV) for payment advices. A supplier often has to run both generations at the same time, because each vehicle maker retires its flat-file interfaces on its own schedule.
ECOM's B2B gateway reads and writes both generations, so a supplier can keep a customer's VDA 4905 flat file running while it adopts 4984 for another customer, with the same mapping to the ERP.
Tier-1 and tier-2 suppliers
Receive call-offs and send despatch advices and invoices to German and European vehicle makers.
Vehicle makers and logistics providers
Exchange transport orders, transport status and container (returnable packaging) accounts with carriers and warehouses.
Aftermarket and spare parts
Handle bypass (drop-ship) orders and exception handling in the spare parts supply chain.
Delivery schedules and call-offs
What the customer needs, when: delivery schedules, detailed call-offs, just-in-time and just-in-sequence calls.
| VDA no. | Message | What it is for | Edition and status |
|---|---|---|---|
| 4905 | Delivery call-offs | Data transmission of delivery call-offs (Lieferabrufe) to the supplier. | Edition 3 (Oct 1988); Edition 4 (Apr 1996) · Flat file · Legacy, replaced by 4984 |
| 4915 | Detailed call-offs | Fine call-offs (Feinabrufe) for just-in-time deliveries. | Edition 1 (Nov 1989); version 2 (Apr 1996) · Flat file · Legacy, replaced by 4984 and 4985 |
| 4916 | Production-synchronous call-offs | Call-offs synchronized to the customer's production line (PAB, just-in-sequence). | May 1991 · Flat file · Legacy, replaced by 4986 |
| 4984 | Delivery call-offs (DELFOR) | Global DELFOR: delivery schedules and call-offs in EDIFACT. | Version 3.0 (Mar 2022) · EDIFACT · Current |
| 4985 | Just-in-time call-offs (DELJIT) | JIT call-offs in EDIFACT. | Version 3.1 (Apr 2023) · EDIFACT · Current |
| 4986 | Just-in-sequence call-offs (DELJIT) | Production-synchronous (JIS) call-offs in EDIFACT. | Version 3.0 (Mar 2022) · EDIFACT · Current |
Despatch, receipt and proof of delivery
What was shipped and what arrived: delivery notes, receiving feedback, proof of arrival and forwarder certificates.
| VDA no. | Message | What it is for | Edition and status |
|---|---|---|---|
| 4913 | Delivery note and transport data | Remote transmission of delivery notes and transport data. | Edition 1 (Oct 1994); version 4 (Mar 1996) · Flat file · Legacy, replaced by 4987; still widely used |
| 4987 | Despatch advice (DESADV) | Global DESADV: advance ship notice in EDIFACT. | Version 3.0 (Mar 2022) · EDIFACT · Current |
| 4937 | Automated feedback on EDI messages | Receiving advice and automated replies to EDIFACT messages. | Version 3.0 (Aug 2022) · EDIFACT · Current |
| 4989 | Proof of arrival | Confirmation of arrival (Gelangensbestätigung) for tax-exempt intra-EU deliveries. | Version 2.0 (Mar 2023) · EDIFACT · Current |
| 4991 | Forwarder certificates | Forwarder's certificate (Spediteurbescheinigung) for export evidence. | Version 2.0 (Mar 2023) · EDIFACT · Current |
| 4943 | Despatch preview and delivery advice (containers) | Container management: advance notice and delivery advice for returnable packaging. | Version 3.0 (Mar 2022) · EDIFACT · Current |
Invoicing, credit and payment
Getting paid: invoices, credit advices, payment advices and price data.
| VDA no. | Message | What it is for | Edition and status |
|---|---|---|---|
| 4906 | Invoice data | Remote transmission of invoice data. | Edition 2 (May 1993) · Flat file · Legacy, replaced by 4938; VDA notes it no longer meets legal requirements |
| 4908 | Credit advice | Remote transmission of credit advices. | Edition 3 (May 1996) · Flat file · Legacy, replaced by 4938; VDA notes it no longer meets legal requirements |
| 4907 | Payment advice | Remote transmission of payment advices. | Edition 2 (Aug 1993) · Flat file · Legacy, replaced by 4988; still widely used |
| 4932 | Odette EDIFACT INVOIC | Invoice message from the Odette set. | Version 5.1 (May 1999) · Legacy, replaced by 4938 |
| 4938 | Electronic billing documents | Invoices and credit documents: Part 2 EDIFACT INVOIC, Part 3 XML for small businesses, Part 4 freight invoice. | Version 2.0 / 3.0 (Dec 2018) · EDIFACT and XML · Current |
| 4988 | Payment advice (REMADV) | Remittance advice in EDIFACT. | Version 2.0 (Mar 2022) · EDIFACT · Current |
| 4911 | Price data | Remote transmission of price data. | Jan 1989 · Flat file · Legacy, rarely used |
Inventory, containers and packaging
Stock at external warehouses and returnable packaging accounts, movements and orders.
| VDA no. | Message | What it is for | Edition and status |
|---|---|---|---|
| 4930 | Stock and movement information (external warehouse) | Inventory and movement data when stock is held externally. | Flat file · Legacy, replaced by 4990 |
| 4990 | Stock and movement reports (INVRPT) | Inventory and movement reports in EDIFACT. | Version 2.0 (Mar 2023) · EDIFACT · Current |
| 4927 | Container account statements and movements | Returnable packaging account statements and movements. | Edition 1 (Feb 1993); Jan 1997 edition · Flat file · Legacy |
| 4941 | Container management: account statement | Statement of the container account. | Version 1.0 (Feb 2006) · EDIFACT · Current |
| 4942 | Container management: inventory | Container stocktake. | Version 1.0 (Feb 2006) · EDIFACT · Current |
| 4944 | Container management: transport order | Transport order for containers. | Version 1.0 (Feb 2006) · EDIFACT · Retired, replaced by 4933 parts 2 and 4 |
| 4946 | Container management: order and order confirmation | Orders for containers and their confirmation. | Version 3.0 (Mar 2022) · EDIFACT · Current |
| 4947 | Container management: movement report and receipt confirmation | Movements and receipt of containers. | Version 3.0 (Mar 2022) · EDIFACT · Current |
| 4931 | Packaging data sheet | Description of the packaging for a part. | Apr 1993 · Flat file · Legacy |
Transport, logistics and finished vehicles
Moving the goods: transport orders and status, truck control, import control and finished-vehicle logistics.
| VDA no. | Message | What it is for | Edition and status |
|---|---|---|---|
| 4920 | Forwarding order data | Orders from shipper or supplier to the forwarder. | Version 1 (Apr 1989) · Flat file · Legacy, replaced by 4933 |
| 4921 | Arrival data | Arrival of goods at the customer. | Apr 1989 · Flat file · Legacy, replaced by 4945 |
| 4933 | Standardized transport order | Parts 1 and 3 full-load process, parts 2 and 4 empty-container process. | Parts 1 and 3: 3.0; parts 2 and 4: 2.0 (Jun 2021) · EDIFACT · Current |
| 4945 | Transport status messages (IFTSTA) | Status of a transport, including arrival and delivery messages. | Version 3.0 (Mar 2022) · EDIFACT · Current |
| 4982 | Import control system (ICS) | Data exchange with logistics providers for the EU import control system. | Version 1.0 (Dec 2011) · EDIFACT · Current |
| 4996 | Truck control in the arrival area | Operational control of trucks at the gate. | Version 1.0 (May 2019) · XML · Current |
| 4998 | REST API for transport track and trace | API for shipment status. | Version 1.0 (Jul 2021) · XML, OpenAPI 3, JSON · Current |
| 4999 | Paperless transport processes | Process description for paperless transport. | Version 1.1 (May 2022) · PDF · Current |
| 4918 | Vehicle identification and vehicle transport data | Data for finished-vehicle transport. | Apr 1987 · Flat file · Retired, replaced by FV00 |
| 4919 | Vehicle arrival and departure messages | Gate-in and gate-out of vehicles. | Apr 1987 · Flat file · Retired, replaced by the finished-vehicle messages |
| 4970–4980 | EDIFACT messages for finished-vehicle planning and transport | Earlier EDIFACT set for finished vehicles. | Version 1.0 (Mar 2000) · EDIFACT · Retired, replaced by FV00 |
| FV00 | Finished-vehicle distribution messages | Joint Odette, ECG and VDA EDIFACT and XML message set for finished vehicles. | Version 1.0 (Jun 2020) · EDIFACT and XML · Current |
Quotes, orders and aftermarket
Requests for quotation, orders and confirmations, plus the spare parts supply chain.
| VDA no. | Message | What it is for | Edition and status |
|---|---|---|---|
| 4923 | Inquiries | Requests for quotation. | Jan 1992 · Odette message (older) · Retired |
| 4924 | Quotations | Quotes in reply to an inquiry. | Jan 1992 · Odette message (older) · Retired |
| 4925 | Orders | Purchase orders. | Jan 1992 · Odette message (older) · Retired |
| 4926 | Order confirmations | Confirmation of orders. | Jan 1992 · Odette message (older) · Retired |
| 4948 | Bypass (drop-ship) in the aftermarket | Part 0 process, part 1 order, part 2 order response, part 3 despatch advice. | Version 1.0 (Oct 2006) · EDIFACT · Current |
| 4949 | Exception handling in the aftermarket supply chain | Handling deviations in spare parts delivery. | Version 1.0 (May 2007) · EDIFACT · Current |
Envelope, attachments, portals and platform
The frame around the messages, attachments and signatures, portals, and the transfer protocol.
| VDA no. | Message | What it is for | Edition and status |
|---|---|---|---|
| 4900 | Payload frame for EDIFACT messages | Frame for the syntax version 3 compatible profile of syntax version 4. | Version 3.0 (Apr 2022) · EDIFACT · Current |
| 4983 | Attachments and signatures with EDIFACT | Transmission of attachments and signatures. | Version 1.2 (Sep 2020) · EDIFACT and XML · Current |
| 4914 | File transfer protocol | The 1988 transfer protocol. | Mar 1988 · Retired, replaced by OFTP2 |
| 4981 | Portal agents in the automotive portal | Use of portal agents. | Version 1.0 (Oct 2011) · EDIFACT · Legacy |
| 4993 | Portal manager tasks | Responsibilities of portal managers. | Version 1.0 (Feb 2015) · Paper and EDIFACT · Current |
| 4995 | Control of customer documents in the supply chain | Handling customer documents along the chain. | Version 1.0 (Apr 2018) · Current |
| 4997 | Long-term supplier declaration | Structured transmission of long-term supplier declarations for preferential origin. | Version 1.0 (Jan 2021) · XML · Current |
| 4992 | MAT label and eMAT data transmission | Application recommendation for the MAT label and electronic MAT data. | Version 1.0 (Sep 2015) · Paper and EDIFACT · Current |
Labels, paper forms and process guides
Recommendations that are not data messages. They are listed so the numbering is complete; the gateway handles the data messages above, not paper or labels.
| VDA no. | Message | What it is for | Edition and status |
|---|---|---|---|
| 4901 | Basic terms of supply chain data exchange | Explains the delivery processes and terms. | Version 2.0 (Dec 2019) · Text · Current |
| 4902 | Goods tag | Label for goods. | Version 4 (1996, additions 2012) · Label · Legacy, replaced by 4994 (GTL) |
| 4994 | Global Transport Label (GTL) | Application recommendation for the GTL. | Version 2.0 (Jul 2023) · Paper · Current |
| 4903 | Microfilm | Microfilm recommendation. | Apr 1982 · Retired |
| 4904 | Call-offs by fax or form | Paper call-off form. | May 1983 · Paper · Legacy |
| 4912 | Remote data transfer: goods accompanying note | Early delivery paperwork. | Jan 1991 · Retired, replaced by 4939 |
| 4922 | Consignment form (shipper, forwarder, customer) | Consignment note form. | Version 4.0 (Jun 2010) · Form · Legacy, replaced by 4939 |
| 4939 | Consignment documents | Consignment note. | Version 3.5 (Mar 2023) · PDF · Current |
| 4928 | Checklist for assembly partners | Checklist for system suppliers with synchronized delivery. | Version 1.0 (Aug 1996) · Retired |
| 4929 | Odette AVIEXP | Flat-file despatch advice from the Odette set. | Version 5.1 (Feb 1998) · Flat file · Retired |
| 4936 | Web-EDI | Web-based entry of EDI data. | Version 1 (Dec 2000) · PDF · Legacy |
| 4940 | Checklist for using Odette messages | Checklist. | Aug 1993 · Retired |
Structure
How the two generations differ
A flat-file VDA message is a sequence of fixed-length records. Each record starts with a three-digit record type (Satzart) that tells the reader which fields follow: for example one record type for the message header, others for the part, the quantities and the dates. There is no delimiter and no self-description, so the position of every field matters.
The EDIFACT-based recommendations use the standard UN/EDIFACT segments (UNB, UNH, BGM, NAD, LIN and so on) with the VDA rules for which segments, codes and quantities are used. VDA 4900 defines the frame around them.
Most customers still send or expect the older flat-file message on the left, while newer programs use the EDIFACT recommendation on the right. The gateway handles both, so a supplier can move customers one at a time.
Versions
Editions and versions
Flat-file messages are identified by edition (Ausgabe) and date; EDIFACT recommendations by version number and date. The editions ECOM supplies for the flat-file messages are shown beside VDA's own published versions.
| Item | Detail |
|---|---|
| 4905 call-offs | Edition 3 (October 1988); Edition 4 (April 1996) |
| 4906 invoices | Edition 2 (May 1993) |
| 4907 payment advices | Edition 2 (August 1993) |
| 4908 credit advices | Edition 3 (May 1996) |
| 4913 delivery notes | Edition 1 (October 1994); version 4 (March 1996) |
| 4915 detailed call-offs | Edition 1 (November 1989); version 2 (April 1996) |
| 4927 container accounts | Edition 1 (February 1993); the January 1997 edition |
| EDIFACT recommendations | Versions 1.0 to 3.1 between 2006 and 2023; see the tables for each number |
ECOM B2B Gateway
How ECOM handles VDA
The gateway treats each customer's VDA interface as a map between the VDA layout and your ERP, so adding a customer, or moving one from a flat file to EDIFACT, changes the partner side and leaves the ERP side alone.
- 1
Receive
Take the file over OFTP2, AS2, SFTP or another connection the customer requires.
- 2
Read the layout
Parse the flat-file record types or the EDIFACT segments for the edition in use.
- 3
Validate
Check the content against the VDA recommendation and the customer's own rules.
- 4
Map to the ERP
Create schedules, shipments and invoices in the format your ERP accepts, and send the replies back.
The gateway treats each customer's VDA interface as a map between the VDA layout and your ERP, so adding a customer, or moving one from a flat file to EDIFACT, changes the partner side and leaves the ERP side alone.
Good to know
What this page does and does not cover
- Status words follow VDA's own list of August 2024: "Current" means VDA marks it a current recommendation; "Legacy" and "Retired" mean VDA no longer recommends it, although many legacy messages are still in daily use.
- The tables list every numbered recommendation in that list so the numbering is complete. Paper forms, labels, microfilm and process descriptions are not data messages; the gateway handles the data messages.
- Each vehicle maker adds its own rules on top of the VDA recommendation. ECOM confirms the edition and the customer's rules with you before building a map.
Sources, read November 3, 2026
Frequently asked questions
Which VDA message do I need for delivery call-offs?
It depends on the customer. Older programs use the flat-file VDA 4905 (and 4915 for detailed call-offs); newer programs use EDIFACT VDA 4984 (DELFOR), with 4985 for just-in-time and 4986 for just-in-sequence calls. Ask the customer which one it sends.
Does ECOM support the older flat-file VDA messages as well as EDIFACT?
Yes. ECOM's B2B gateway handles the flat-file messages such as 4905, 4906, 4907, 4908, 4913, 4915 and 4927 through their record-type layouts, and the EDIFACT-based recommendations such as 4984 and 4987.
Is VDA 4913 still in use even though it was replaced?
Yes. VDA lists 4913 as replaced by 4987 (DESADV), but notes that it is still widely used, and that some processes, such as the daily consolidated delivery note in JIS processes, still await a new recommendation.
How do VDA messages travel between companies?
Most automotive partners use OFTP2, the secure Odette file transfer protocol, and many also accept AS2 or SFTP. The gateway supports the connection each partner requires.
Connect a VDA partner
Tell us which VDA messages and versions your partner requires. An ECOM specialist confirms the connection, the map and the test plan.