VDA Message Types – Understanding EDI Equivalents

What are VDA Message Types? 

VDA message types are EDI standards defined by the German Association of the Automotive Industry (Verband der Automobilindustrie e.V.). They were developed to support the digital exchange of supply chain data between OEMs, Tier-1 suppliers, and logistics providers. Common message types include VDA 4905 (Delivery Forecast), VDA 4913 (Delivery Note), VDA 4920 (Invoice), and VDA 4939 (Payment Advice). These messages align closely with ANSI X12 and EDIFACT standards, enabling global interoperability. 
 

How Does PartnerLinQ use VDA Messages? 

PartnerLinQ integrates VDA message types into its unified connectivity layer, harmonizing German automotive EDI with global standards. The platform automates VDA transactions through SAP and non-SAP systems, providing visibility across production schedules, shipments, and billing. 
 

What Responses to VDA Messages are expected/sent? 

VDA messages often generate responses used to acknowledge receipt, confirm business acceptance, or report exceptions for automotive transactions such as orders, delivery schedules, shipments, and invoices. These responses ensure (1) the technical delivery and (2) the business intent are both synchronized between trading partners.   

Unlike EDIFACT or X12 that mostly rely on a universal acknowledgment process, VDA uses different response messages depending on whether the response is technical or business-related, for example, VDA 4905 planning schedules may trigger shipment notifications (VDA 4913) and invoices (VDA 4920). PartnerLinQ ensures these workflows align with ANSI X12 830/856/810 and EDIFACT DELFOR/DESADV/INVOIC equivalents. 
 

Technical (Transmission-Level) Responses 

These confirm that a message was successfully delivered and syntactically received. 

Functional (Business-Level) Responses 

These confirm whether the business content of the message can be processed. 

Exception and Change Responses 

VDA messages may also trigger business exception responses rather than simple acknowledgments. 

What does the VDA message workflow support?  

The VDA workflow covers core business and logistics functions: including ordering (VDA4925), Order Response (VDA 4926), delivery (4913), invoicing (4920), planning (4905), and payment (4939).  PartnerLinQ bridges the VDA workflow with SAP IDocs such as DELFOR, DESADV, INVOIC, and REMADV, ensuring seamless integration with ERP systems. 

Accepting an VDA order (VDA4925) message from your automotive trading partner is typically insufficient for complete EDI compliance. Most automotive trading partners will expect other VDA EDI transactions in response to or following a VDA4925 (Purchase Order) message such as: 

What are the Key Features of the VDA message workflow? 

• Optimized for the automotive sector 
• High data accuracy and minimal redundancy 
• Synchronizes planning, shipment, and billing 
• Compatible with EDIFACT, X12, and SAP IDocs 
 

What is the Purpose of the VDA message workflow? 

The purpose of VDA messages is to create standardized communication for automotive manufacturers and suppliers, reducing administrative overhead and ensuring supply chain continuity. 
 

What Information is included in the VDA message workflow? 

VDA uses multiple specialized messages to seamlessly exchange a coordinated set of commercial, planning, logistics, financial, and control data across the automotive supply-chain in Germany.  Originally defined by the German Association of the Automotive Industry (Verband der Automobilindustrie e.V.), they were developed to support the digital exchange of supply chain data between OEMs, Tier-1 suppliers, and logistics providers.  

Today, VDA messages support order creation, delivery forecasting, just-in-time call-offs, shipment execution, invoicing, and exception handling, each transaction designed to support tightly synchronized automotive supply-chain operations. 
 

End-to-End View (Conceptual) 

Information included in the VDA message workflow includes

• Commercial Information (Ordering) - Exchanged when establishing or modifying supply commitments.
• Planning & Forecast Information (Scheduling) - Exchanged to support medium- and short-term production planning.
• Logistics & Shipment Information - Exchanged to execute and track physical movement of goods.
• Financial & Settlement Information - Exchanged to reconcile physical deliveries with financial obligations.
• Status & Exception Information – Exchanged to manage deviations from the planned process.
• Control & Traceability Information - Present in all workflow messages to ensure integrity and auditability. 
   

What are the Essential Components of the VDA message workflow? 

VDA messages are profile-driven when compared with X12 or generic EDIFACT. In other words, VDA doesn’t just define a message format — it defines a business more like a recipe, a profile for how that message must be used.  A predefined usage rule set layered on top of a base syntax, one that is not open to interpretation. 

What VDA does instead is provide a fixed message layout, a single intended use case per message. Automotive-specific rules for Call-offs, JIT sequencing, cumulative quantities,  

Delivery schedules… and so on. So with VDA – a VDA 4915 always means JIT call-off, a VDA 4925 always means purchase order, and VDA 4906 always means invoice and very little partner-specific creativity. 

Every VDA message is built from three essential component layers: (1) Control & Identification, (2) Business Content, and (3) Structural Rules & Profiles. 
 

Control & Identification Components 

These ensure the message can be uniquely identified, routed, and processed and include: 

• Message Type (e.g., VDA 4925, 4915, 4906)
• Message Version / Release
• Sender ID (customer, OEM, or logistics partner)
• Receiver ID (supplier or carrier)
• Message Reference Number (unique per transmission)
• Creation Date & Time
• Test vs Production Indicator 
   

Business Content Components 

These carry the actual commercial and logistics meaning of the message, in support of ordering, scheduling, shipping, and invoicing processes in an automotive supply chain. Business Content Components typically include: 

• Parties
• Document References (RFF)
• Item Data
• Dates and Times
• Logistics Data
• Financial Data (Where applicable) 
   

Structural Rules & Profiles 

This is what makes VDA distinct from generic EDIFACT for example. 

• Fixed Segment Sequence - Messages must follow a strict segment order
• Predefined Field Lengths - Many data elements have fixed lengths and formats.
• Mandatory vs Optional Fields - Defined by VDA recommendation profiles.
• Code Lists - Packaging codes, Transport modes, Reason codes,
• Automotive-Specific Semantics - Call-off , JIT sequencing, Cumulative Quantity  
   

Summary Table 

What Common Segments are included in VDA messages? 

Unlike traditional EDI messages, where ‘segments’ are assembled and together carry transactional order, delivery, and shipping information, VDA messages are built based on fixed-position data fields grouped into logical record sections. Functionally speaking,  

VDA messages contain recurring ‘data groups’ that play the same role as ‘segments’ or ‘elements’ do in other standards. ‘Data groups’ function like ‘segments’ and appear consistently across transactions (even though field positions differ). 

‘Data groups’ appear consistently across various transactions, thus are considered ‘common.’ 

• VDA 4925 (Purchase Order)
• VDA 4913 (Delivery Forecast)
• VDA 4915 / 4985 (JIT Call-off / DELJIT)
• VDA 4905 / 4987 (Despatch Advice / ASN)
• VDA 4906 / 4932 (Invoice) 
   

What Status Codes are included in VDA messages? 

VDA messages, while very similar to messages defined within other standards, does not leverage a single ‘global status code list.’ While status codes are used to represent transaction status (accepted, rejected, pending) unlike X12 or EDIFACT, each message type defines its own status code values, their meanings and where they appear in the layout of the transaction. VDA messages use profile-specific status codes to indicate the business state of orders, delivery schedules, shipments, and invoices. 
 

Document / Transaction Status Codes 

Document / Transaction Status Codes are used to describe the overall purpose or state of the document and are used in the VDA 4925 (PO), VDA 4913 (Forecast), VDA 4915/4985 (JIT), VDA 4905 (Despatch Advice), VDA 4906/4932 (Invoice), for example: 

Order & Schedule Status Codes 

Order & Schedule Status Codes are used to describe the commercial state of an order or delivery call-off and Used in the VDA 4926 (Order Response), VDA 4913 (Delivery Forecast), VDA 4915 (JIT). 

Delivery & Shipment Status Codes 

Delivery & Shipment Status Codes are used to describe the logistics execution state and can be found in the VDA 4905 (Despatch Advice) and VDA 4987 (ASN). 

Call-off / JIT Sequencing Status Codes 

Call-off / JIT Sequencing Status Codes are used in just-in-time and sequence-based supply chains and it is used in the VDA 4915 and VDA 4985 (DELJIT subset).
 

Invoice & Financial Status Codes 

Invoice & Financial Status Codes are used to describe billing and settlement state and can be found in the VDA 4906, VDA 4932 (Invoice), and VDA 4908 / 4938 (Credit/Debit) 

Technical / Processing Status Codes 

Technical / Processing Status Codes are used to indicate message handling results and these are most often embedded in response messages or handled via transport acknowledgments (e.g., OFTP/OFTP2) 

What Reason Codes are included in VDA messages? 

Here again, VDA reason codes are profile-specific business explanation codes that explain why an order, call-off, shipment, or invoice was rejected, changed, or adjusted.  Used to qualify rejections, changes, and most importantly, deviations in automotive order, scheduling, shipping, and invoicing processes explanations for rejections and/or changes include qualification include quantity unavailable, capacity constraints, material shortages, scheduling conflicts, packaging rather than using a single universal reason code list. They communicate why a transaction could not be processed as requested.  Where X12 message might indicate simply ‘Rejected’ a VDA response indicates ‘Rejected — due to material shortage’, or ‘Changed — due to capacity constraint’ or ‘Delayed — due to transport issue’ a structure that enables automated exception handling and coordinated supply-chain response – perhaps the first steps in the direction of fully autonomous supply chain. 
 

Common Reason Code Categories in VDA Messages 

Where Reason Codes Are Used 

What Use Cases do VDA messages support? 

VDA messages support high-volume end-to-end automotive supply-chain use cases including purchase order management, delivery forecasting, just-in-time scheduling, shipment notification, invoicing, exception handling, and compliance.  

Together, these use cases enable tightly synchronized, high-volume, and automated collaboration between OEMs and suppliers.

• Delivery scheduling between OEMs and suppliers
• Packaging Instructions
• Forwarding Instructions
• Delivery Notes / Dispatch Advice (ASN - Advance Shipping Notice)
• Receipt Acknowledgment
• Automated invoicing, remittance, and reconciliation
   

What are the Benefits of VDA messages? 

• Improves supply chain synchronization 
• Reduces manual reconciliation 
• Enhances automotive compliance (VDA & AIAG alignment)  
 

How Efficient are VDA messages? 

VDA messages are optimized for high-volume, repetitive automotive transactions such as call-offs, delivery schedules, ASNs, and invoices. They are the backbone that enables the most demanding and efficient manufacturing practices in the world, the automotive sector. Their design prioritizes speed, predictability, and low processing cost over flexibility, in fact, VDA messages are extremely efficient VDA messages are used almost exclusively for Just-in-Time (JIT) and Just-in-Sequence (JIS) in the automobile sector when compared with other manufacturing sectors.   

• Parsing is simple (fixed field positions, no variable-length loops)
• Validation is predictable (rules are embedded in the profile)
• File sizes are small compared to X12 or EDIFACT
• CPU and memory usage is low during processing
• Batch processing is fast, even at very high volumes 
   

Key Efficiency Characteristics 

How Compliant are VDA messages? 

VDA messages are highly compliant by design. Primarily governed by industry rather than government (e.g., regulation) they leverage strict, profile-driven rules that define field usage, code values, and business semantics for specific automotive processes. Compliance is industry-mandated rather than legally mandated, and operationally compulsory for participation in many automotive supply networks and enforced through industry standards and trading partner agreements.  The result is deterministic validation, reduced ambiguity, and reliable automation across OEM and supplier networks. 

• Messages follow the exact structure defined in the VDA recommendation
• Mandatory data elements are always populated
• Codes and qualifiers match allowed values
• Business rules (e.g., cumulative quantity logic) are applied consistently
• Rejected or changed transactions include valid reason codes
• Superseded messages properly reference prior versions 
   

What is the Format of a VDA message? 

VDA messages are structured variable-length text files (Delimited). VDA messages use predefined field lengths. While many data elements have fixed lengths and formats, they can be harmonized with EDI and IDoc mappings in some of the more advanced solutions in the market like the PartnerLinQ platform which consolidates, normalizes and harmonizes data from various sources making critical information accessible for optimizing supply chain operations. 
 

How Accurate are VDA messages? 

VDA messages are designed to ensure precision with minimal human intervention. Delivered through standardized data exchanges like Just-in-Time (JIT) and Just-in-Sequence (JIS), just two examples just how accurate VDA messages can be.  The automobile sector shines with their approach to coordinated supply-chain response, perhaps leading the first steps in a fully autonomous supply chain now that AI is taking hold. 
 

What are the Limitations of a VDA message? 

VDA’s fixed-length formats in support of the automobile sector requires strict adherence and lack flexibility compared to X12 or EDIFACT, messages that are non-compliant typically result in: 

• Message rejection
• Delivery or payment delays
• Manual intervention
• Potential commercial penalties (e.g., chargebacks) 
   

Are Guidelines & Sample Files for VDA messages available? 

Yes. PartnerLinQ provides sample VDA Transactions and Implementation guides are available through its Support and Guideline Management Team. 

Sample implementation guides illustrate both inbound and outbound flows, segment layouts, and valid data examples and support testing and partner onboarding. Customized specification documents for use in on boarding and technical development are available upon request.  

PartnerLinQ provides: 

• Transaction implementation guide
• Sample payloads
• Qualification and testing maps
• Error handling and best-practice notes 

Contact our experts. 

What are the Basic Questions for Integration of the VDA message workflow? 

1. Which VDA versions are used or required?
2. What is the general direction of the transaction?
3. Are orders inbound or outbound?
4. Are there Samples and Specs available?
5. Are functional acknowledgments needed?
6. Is EDIFACT, X12, or AIAG alignment required?
7. Are PO Changes accommodated?
8. How are changes to orders managed today?
9. Is there automation? (an internal systems triggers) or are PO changes triggered manually
10. How will cancellations and changes be managed?
11. Are there other parties interested in this same transaction?
12. What transactions might these interested parties also be a party to?
13. What type of connection will be used for exchanging the EDI Files?  (OFTP/OFTP2, AS2, VAN…)
14. Is the customer only sending EDI or are there other ways to get the order into the system?
15. Is there customization to accommodate Order to Cash flows?
16. How are Payment Terms, FOB, INCO Terms, and/or Method of Payment terms applied?
17. Are Line Items identified by SKU or UPC?
18. How does pricing work?
19. Is a contract or a Price/Sales Catalog transaction in use?
20. Are we expecting Service, Promotion, Allowance, or Charge Information (SAC) within the PO?
     

What is the basic VDA Business Level Workflow model? 

The VDA workflow model reflects how German and European automotive OEMs and suppliers coordinate planning, shipping, invoicing, and payment using fixed-format VDA messages. It’s built to support Just-in-Time (JIT) and Just-in-Sequence (JIS) manufacturing. 

1. OEM issues planning schedule (VDA 4905)
2. Supplier sends delivery note (VDA 4913)
3. Supplier issues invoice (VDA 4920)
4. OEM confirms payment (VDA 4939)

Planning & Forecasting 

VDA 4905 – Delivery Forecast / Scheduling Agreement 

• Communicates medium- to long-term production requirements.
• Defines expected quantities and delivery dates.
• Drives supplier production planning and material procurement. 
   

Shipping Instruction & Execution 

VDA 4908 – Shipping Schedule (call-off / JIT instruction) 

• Converts forecast into near-term shipping requirements.
• Often used for JIT or sequence-based delivery.
• Supplier prepares goods and ships. 
   

Delivery Notification 

VDA 4913 – Delivery Note / Despatch Data 

• Sent when goods are shipped.
• Contains packaging, handling unit, and transport details.
• Enables dock planning and automated receiving. 
   

Invoicing 

VDA 4920 – Invoice 

• Requests payment for delivered goods.
• References shipment and order data for matching. 
   

Payment & Remittance 

VDA 4939 – Payment Advice / Remittance 

• Confirms payment and identifies which invoices were paid. 
   

Quality & Test Reporting 

VDA 4987 – Quality Data / Test Results 

• Provides inspection or quality assurance results.  
   

What are the Best Practices of the VDA message workflow? 

• Validate message formats before transmission
• Map each VDA file to the corresponding X12/EDIFACT/SAP equivalent
• Use automated acknowledgment and reconciliation
• Maintain strict version control across partners 
   

Appendix: Mapping Table – VDA ↔ X12 ↔ EDIFACT ↔ SAP IDoc