Skip to content



Daimler AG logo


Daimler; Mercedes Benz logo

Electronic data exchange with Daimler

An insight into the EDI requirements of Daimler AG worldwide

Daimler AG suppliers are confronted with a variety of possible EDI requirements. Daimler’s binding specifications for EDI processes and formats are very heterogeneous and are a reflection of the digital transformation that the global automotive industry is currently undergoing.

Daimler still uses the classics of automotive EDI history for connecting its German plant locations according to the old VDA standard:

VDA formats used by Daimler to connect the German plant locations

  • rcv VDA 4905: Delivery schedule from Daimler according to the old VDA standard
  • snd VDA 4913: Delivery notice to Daimler according to the old VDA standard
  • snd VDA 4906: Invoice to Daimler according to the old VDA standard

With these VDA message types of the first hour, mainly the German plants are connected within the Daimler group. Their most important representatives are:

  • Daimler AG Berlin
  • Daimler AG Gaggenau
  • Daimler AG Germersheim
  • Daimler AG Hamburg
  • Daimler AG Mannheim
  • Daimler AG Sindelfingen
  • Daimler AG Stuttgart
  • Daimler AG Wörth (Mercedes Benz Special Trucks)

Use of classic EDIFACT formats at Daimler AG

In addition, classic EDIFACT formats have also been used for some time, but they have never been able to establish themselves across the board:

EDIFACT formats used by Daimler

  • DELFOR: Delivery schedule from Daimler in EDIFACT format
  • DELINS: Just-in-time delivery schedule from Daimler in ODETTE format
  • DESADV: Delivery notice to Daimler in EDIFACT format
  • INVOIC: Invoice to Daimler in EDIFACT format

Stringent requirements for EDI subsystems due to a large number of different formats

In this conglomerate of EDI messages and formats, Daimler uses a variety of different plant identifiers and unloading points. However, most ERP systems do not keep comprehensive records of the necessary combinations of different sender and recipient IDs in the master data.

To quickly and comprehensively implement the EDI message exchange with Daimler AG, the EDI subsystem should therefore be able to convert Daimler-internal identifiers to the internal number ranges of the ERP system so that incoming messages can be correctly assigned when imported via the corresponding ERP interface. For outgoing EDI messages to Daimler, the EDI system then ensures the correct addressing of the EDI messages to be sent and derives the correct recipient identifiers from the ERP-internal assignment. Softzoll’s solutions fully meet these requirements.

Connection of Daimler production facilities in the USA

Another peculiarity must be taken into account by suppliers when integrating U.S. Daimler production facilities with EDI messages. Daimler relies entirely on the American ANSI X12 standard in this area.

ANSI X12 message types used by Daimler:

  • rcv ANSI X12 830: Delivery schedule from Daimler USA in American ANSI X12 format
  • rcv ANSI X12 862: Just-in-time delivery schedule from Daimler USA in American ANSI X12 format
  • snd ANSI X12 856: Delivery notice to Daimler USA in American ANSI X12 format
  • snd ANSI X12 810: Invoice to Daimler USA in American ANSI X12 format

Daimler Supplier Portal


Daimler manuals for remote data transmission

Use of XML formats at Daimler

For supplying C items, Daimler sometimes uses different procurement service providers whose platforms generally work with XML formats in order to spare suppliers the manual entry of documents:

Including XML formats used by Daimler

  • rcv XML ORDERS xCBL3.5: Order from Daimler via CommerceOne in XML format
  • rcv XML ORDERS: Order from Daimler via Covisint in XML format

When sending invoices to Daimler, please note that Daimler responds to the sending of INVOIC messages in some EDI scenarios by sending APERAK messages in EDIFACT format to confirm the successful processing of the received invoices or to acknowledge a rejection.

  • rcv APERAK: Processing status from Daimler in EDIFACT format

Since most ERP systems do not provide interfaces for importing the processing status from the APERAK messages, the upstream EDI system must offer additional functionalities specifically designed for this purpose. Softzoll offers corresponding modules for successful APERAK management, but can also review the incoming APERAK messages from Daimler for error codes by means of additional logics stored in the EDI workflow, send the message IDs of rejected invoices automatically by e-mail, and include the contents of the review report as a CSV attachment in the e-mail message.

OFTP2—tool of choice for EDI communication with Daimler

Daimler relies entirely on the OFTP2 protocol for transporting EDI messages between the Group sites and the supplier industry. As an external service provider for all OFTP2 services, Daimler relies on T-Systems, which is responsible for the complete handling of the initial OFTP2 connection implementation and the management and operation of existing OFTP2 communication links (OFTP2 certificate change etc.) .In some cases, there are also specifications regarding AS2 implementation, but these mainly affect procurement service providers in the context of C items procurement.


Daimler AG / Mercedes Benz Portal,
questions about “Project Future”

What you should know about the "Project Future" at Daimler

In order to better adapt to global changes with a more sustainable and focused business strategy, the Daimler Group launched a new corporate structure on November 1, 2019. This mainly involved spinning off the car, van, truck, and bus businesses to the subsidiaries. As of the end of October 2019, these changes have become effective by virtue of entry in the commercial register.

For suppliers of the previous Daimler AG company, this also had direct effects on the EDI data exchange of existing and future EDI implementations. Daimler is changing the formats of EDI messages away from the old VDA ASCII format definitions to the new global VDA EDIFACT specifications as part of its “Project Future”. In particular, the focus is initially on the following EDI processes:

Project Future—using the following EDI processes

  • rcv VDA 4985 Global DELJIT: Just-in-time delivery schedule from Daimler in VDA EDIFACT format DELJIT
  • snd VDA 4933 Global DESADV: Transport order to Daimler in VDA EDIFACT format DESADV
  • snd VDA 4938 Global INVOIC: Invoice to Daimler in VDA EDIFACT format INVOIC
  • rcv VDA 4938 Global INVOIC: Credit note from Daimler in VDA EDIFACT format INVOIC

There will be no new Odette IDs for logistics processing for the German Daimler AG plants—regardless of whether they belong to Daimler AG, Mercedes-Benz AG, or Daimler Truck AG in the new Group structure; however, new Odette IDs will be required, for example, for transmitting invoices or credit notes (VDA4938). Credit notes will continue to be sent via VDA 4908 or VDA 4938, but the newer VDA 4938 format is now preferred by Daimler.

To accompany Project Future and the resulting changes, Daimler offers a comprehensive portal for suppliers and customers on its corporate website with specifications and additional information on all changes in the course of the EDI-specific changeovers at Daimler. Further important information on the electronic data exchange with Daimler AG can be found here.


Softzoll supports you in all aspects of electronic data exchange with Daimler AG—
both domestically and abroad.

Get in touch with us!


This post is also available in DE.

Questions about EDI?
 +49 (0)30 2100235-30
Leave us a message!
We will get back to you immediately;

 to the contact form
Back To Top