Introduction to Automobile EDI X12 Transactions List
The automotive industry has achieved nearly 100% EDI adoption, making it one of the most digitally connected sectors globally.
For over four decades, EDI has been the backbone of automotive supply chains, enabling manufacturers and suppliers to exchange critical business information efficiently.
Understanding the right EDI X12 transactions, segments, and elements is essential for success in this fast-paced industry.
In fact, the automotive sector relies on specific EDI X12 transaction sets to manage everything from purchase orders to vehicle shipping.
We’ve compiled this complete EDI codes list covering 27 essential EDI transaction types used throughout the automotive industry, specifically designed to help you navigate modern supply chain operations.
Here is the full list,
- EDI 120 – Vehicle Shipping Order
- EDI 121 – Vehicle Service
- EDI 124 – Vehicle Damage
- EDI 125 -Multilevel Railcar Load Details
- EDI 126 – Multilevel Railcar Load Details (Variant A)
- EDI 126 – Vehicle Application Advice (Variant B)
- EDI 127 – Vehicle Baying Order
- EDI 128 – Dealer Information
- EDI 129 – Vehicle Carrier Rate Update
- EDI 160 – Transportation Automatic Equipment Identification
- EDI 169 – Transportation Appointment Schedule Information
- EDI 753/754 – Request for Routing Instructions and Routing Instructions
- EDI 846 – Inventory Inquiry/Advice (INVRPT)
- EDI 850 – Purchase Order (ORDERS)
- EDI 855 – Purchase Order Acknowledgment (ORDRSP)
- EDI 860 – Purchase Order Change Request
- EDI 810 – Invoice (INVOIC)
- EDI 820 – Payment Order/Remittance Advice (REMADV)
- EDI 870 – Order Status Report
- EDI 856 – Advance Ship Notice (DESADV)
- EDI 861 – Receiving Advice/Acceptance Certificate
- EDI 997 – Functional Acknowledgment (CONTRL)
- EDI 940 – Warehouse Shipping Order
- EDI 214 – Transportation Carrier Shipment Status Message
- EDI 204 – Motor Carrier Load Tender
- EDI 862 – Shipping Schedule (DELJIT)
- EDI 830 – Planning Schedule with Release Capability (DELFOR)
Key Takeaways
- Master the core transaction flow: EDI 850 (Purchase Order) → EDI 855 (Acknowledgment) → EDI 856 (Ship Notice) → EDI 810 (Invoice) → EDI 820 (Payment) forms the foundation of automotive EDI operations.
- Implement just-in-time coordination: EDI 830 (Planning Schedule) and EDI 862 (Shipping Schedule) work together to support precise delivery timing, with 862 providing hourly-level precision for JIT manufacturing.
- Ensure compliance for supplier ratings: Non-compliance with EDI requirements can result in penalties up to $500 per occurrence and directly impact supplier ratings and partnership opportunities.
- Automate transportation visibility: EDI 204 (Load Tender) and EDI 214 (Shipment Status) eliminate manual tracking calls while providing real-time freight visibility throughout the delivery lifecycle.
- Leverage specialized automotive transactions: Beyond standard EDI, automotive-specific codes like EDI 120 (Vehicle Shipping) and EDI 753/754 (Routing Instructions) optimize vehicle logistics and transportation planning.
1. EDI 120 - Vehicle Shipping Order
The EDI 120 is the foundational transaction that kicks off the vehicle transportation process. Issued by an automobile manufacturer or fleet operator, it serves as the official authorization for a carrier to pick up one or more vehicles and deliver them to a specified destination, typically a dealership or distribution center.
Think of it as the vehicle-level equivalent of a purchase order, but for transportation services. It contains everything a carrier needs to execute the move: vehicle identification, origin and destination addresses, required delivery windows, and any special handling instructions. The EDI 120 is typically sent before vehicles physically arrive at the staging lot, allowing carriers to plan equipment and routing.
KEY DATA ELEMENTS
- Vehicle Identification Number (VIN)
- Origin/destination locations
- Required delivery date
- Vehicle make, model, color
- Carrier and equipment type
- Special handling codes
- Bill of lading reference
- Dealer and zone codes
REAL-WORLD USE CASE
A Michigan auto plant issues EDI 120s to its approved car haulers every evening for vehicles completing assembly that day, allowing carriers to pre-assign trucks and confirm load schedules before sunrise.
2. EDI 121 - Vehicle Service
The EDI 121 captures service, repair, or inspection work performed on a vehicle as it moves through the supply chain. This transaction is used when a vehicle requires work before delivery, whether at a processing center, a railyard, or a port facility, and is critical for maintaining a full service history that follows the vehicle to its destination.
This transaction allows processing centers to communicate completed work back to the manufacturer or fleet manager in a structured format, eliminating paper-based repair orders and enabling automated cost reconciliation. Data from EDI 121 feeds into warranty tracking systems and dealer prep records, ensuring that every touch point on a vehicle’s journey is documented.
KEY DATA ELEMENTS
- VIN and vehicle description
- Service facility identifier
- Work performed codes
- Labor hours and rates
- Parts used and costs
- Service date and technician ID
- Authorization reference
- Payment terms
REAL-WORLD USE CASE
An auto processor at a Gulf Coast port uses EDI 121 to report undercoating, window tinting, and accessory installation work to the OEM, triggering automatic billing reconciliation without manual invoice submission.
3. EDI 124 - Vehicle Damage
Automotive transportation inevitably involves some level of vehicle damage, even minor scratches and dents must be meticulously documented. The EDI 124 provides a standardized electronic method for reporting vehicle damage discovered at any point in the transportation chain, from the originating plant to the dealer’s lot.
Before EDI 124, damage claims were handled through paper forms, photos sent by mail, and lengthy phone negotiations between carriers and OEMs. This transaction digitizes the entire process, allowing carriers to submit damage reports electronically the moment they’re identified, attach location codes indicating where damage occurred, and reference the responsible party. This dramatically speeds up claims processing and helps identify systemic problems, like a particular loading dock with a recurring damage pattern.
KEY DATA ELEMENTS
- VIN and vehicle identification
- Damage location codes
- Damage type and severity
- Discovery location and date
- Responsible party code
- Estimated repair cost
- Claims reference number
- Inspector identification
REAL-WORLD USE CASE
A car hauler driver discovers a door ding at an intermediate delivery point. Using a mobile EDI app, the carrier submits an EDI 124 on the spot, capturing GPS-stamped location data and triggering an immediate claim with the prior carrier that made the last custody transfer.
4. EDI 125 - Multilevel Railcar Load Details
Multilevel railcars, the iconic “auto-rack” cars you see on freight trains, carry anywhere from 8 to 18 vehicles stacked across multiple decks. The EDI 125 communicates the physical load plan for these railcars, specifying exactly which vehicle goes in which position on which deck. This is not merely administrative: incorrect loading can cause damage from vehicle movement, create imbalanced loads, and complicate unloading sequencing at destination yards.
The EDI 125 is sent by the loading facility to the railroad and receiving facility before the train departs. It enables destination rail yards to prepare unloading equipment, plan labor, and pre-stage delivery trucks in the right sequence, so that vehicles destined for the same region are unloaded as a group rather than scattered across multiple trains.
KEY DATA ELEMENTS
- Railcar identification number
- Deck level and position codes
- VIN for each vehicle slot
- Vehicle dimensions and weight
- Load date and origin yard
- Destination yard code
- Train symbol and route
- Loading restrictions or notes
REAL-WORLD USE CASE
An auto-rack loading facility in Kentucky transmits EDI 125s for every car loaded onto a 150-car train, allowing the Kansas City receiving yard to build an unload manifest and stage car haulers for the morning shift before the train arrives overnight.
5. EDI 126 - Multilevel Railcar Load Details (Variant A)
EDI 126, in its railcar load variant, functions as a companion or extended-use version of EDI 125. While the ANSI X12 standard assigns the same transaction set number to two distinct purposes (railcar load details and vehicle application advice, discussed separately below), in the railcar context, EDI 126 may include additional load plan detail, amendment information, or updated sequencing data when the original EDI 125 load plan changes.
In practice, some rail carriers and OEMs use EDI 125 and EDI 126 in tandem: EDI 125 for the initial load plan and EDI 126 for amendments when vehicle swaps or last-minute load changes occur at the staging yard. This dual-number approach accommodates the realities of production scheduling where the final manifest may differ from the original plan.
KEY DATA ELEMENTS
- Amendment reference to original EDI 125
- Changed vehicle positions
- Replacement VINs
- Reason code for changes
- Revised load sequencing
- Updated departure time
REAL-WORLD USE CASE
A vehicle pulled from a railcar due to a last-minute quality hold triggers an EDI 126 amendment, swapping in a replacement VIN so receiving yards update their manifests before the train departs, avoiding a discrepancy at unload.
6. EDI 126 - Vehicle Application Advice (Variant B)
In its second definition under the X12 standard, EDI 126 serves as a Vehicle Application Advice, a transaction used to communicate how a specific built vehicle (identified by VIN) is being matched to or applied against an open dealer or fleet order. This is a critical link between vehicle production, order fulfillment, and distribution systems.
When an OEM builds a vehicle, it must be matched (“applied”) to an existing order. The EDI 126 application advice transaction notifies the dealer, fleet customer, or regional distribution system of this assignment. It effectively closes the loop between the dealer’s order and the physical vehicle that will fulfill it, triggering downstream processes like vehicle tracking activation, dealer invoice preparation, and floorplan financing notifications.
KEY DATA ELEMENTS
•    Dealer/fleet order number
•    VIN assigned to order
•    Build date confirmation
•    Vehicle configuration codes
•    Estimated delivery date
•    Application status code
•    Invoice price references
•    Regional zone codes
REAL-WORLD USE CASE
A dealer in Texas who ordered a specific truck configuration receives an EDI 126 Vehicle Application Advice when the OEM’s system matches a freshly built VIN to that order. Trigger the dealer’s DMS to activate the vehicle record and notify the customer that their truck has been built.
7. EDI 127 - Vehicle Baying Order
“Baying” refers to the systematic assignment of vehicles to specific physical locations called bays, within a storage or processing yard. Large automotive distribution yards can hold tens of thousands of vehicles simultaneously, and without precise baying instructions, locating a specific VIN among thousands of similar-looking vehicles becomes an operational nightmare.
The EDI 127 Vehicle Baying Order provides carriers and yard operators with precise placement instructions: which bay zone, row, and slot each vehicle should occupy upon arrival. This enables efficient retrieval when the vehicle needs to be loaded for the next leg of its journey and supports yard management systems in optimizing vehicle placement to reduce excessive movement and damage risk. It’s the automotive equivalent of a warehouse slotting instruction.
KEY DATA ELEMENTS
•    VIN and vehicle description
•    Yard facility identifier
•    Bay zone and row assignment
•    Slot or position number
•    Priority or hold status
•    Expected dwell time
•    Processing instructions
•    Next destination reference
REAL-WORLD USE CASE
A rail distribution yard in Chicago receives EDI 127 baying orders for 400 incoming vehicles, pre-assigning each to a specific row and slot based on dealer region, grouping vehicles so car haulers for the same region can be loaded contiguously without reshuffling.
8. EDI 128 - Dealer Information
The EDI 128 is a master data transaction that communicates dealer profile information from manufacturers or national distribution systems to carriers, rail operators, and processing centers. Rather than requiring each logistics partner to independently maintain dealer address books (which change frequently due to dealership openings, closings, relocations, and acquisitions), the EDI 128 provides a single authoritative source of dealer data.
This transaction is particularly important for ensuring that final-mile delivery addresses are accurate. A carrier operating from an EDI 128 that hasn’t been updated may deliver vehicles to a former dealership address, causing expensive delays and redelivery charges. Manufacturers typically transmit EDI 128 updates whenever dealer network changes occur, and at regular intervals as a data refresh.
KEY DATA ELEMENTS
- Dealer code and franchise ID
- Physical delivery address
- Receiving hours and contacts
- Vehicle acceptance capacity
- Geographic zone codes
- Special delivery instructions
- Dealer status (active/closed)
- Effective and expiration dates
REAL-WORLD USE CASE
When a dealership group acquires three new locations, the OEM transmits EDI 128 updates to all authorized carriers within 24 hours, ensuring trucks don’t arrive at the wrong addresses when the first vehicle deliveries to those new stores are scheduled.
9. EDI 129 - Vehicle Carrier Rate Update
Freight rates in automotive transportation are not static, they are adjusted based on fuel costs, seasonal demand, lane volume changes, and contract renegotiations. The EDI 129 provides a standardized mechanism for OEMs or freight payers to communicate updated carrier rate schedules to their transportation partners without requiring manual rate table updates on both sides.
Without EDI 129, rate updates typically required bilateral spreadsheet exchanges, phone calls to confirm receipt, and manual entry into multiple systems, a process prone to errors and delays. The transaction ensures that carriers and shippers are working from the same rate tables at any given time, reducing billing disputes and enabling automated freight accrual in financial systems. It’s especially critical during quarterly contract renewals when dozens of lane rates may change simultaneously.
KEY DATA ELEMENTS
- Carrier SCAC code
- Origin-destination lane pair
- New rate and rate basis
- Fuel surcharge schedule
- Effective date of new rate
- Vehicle type/class applicability
- Accessorial charges
- Contract reference number
REAL-WORLD USE CASE
Following quarterly contract negotiations, a major OEM sends EDI 129 rate updates to 12 authorized carriers in a single batch, updating hundreds of lane rates simultaneously and triggering automatic freight audit system recalibrations on both sides.
10. EDI 160 - Transportation Automatic Equipment Identification
The EDI 160 supports automatic equipment identification (AEI) systems, the RFID and transponder technologies used to track railcars, trailers, and containers as they move through rail networks and intermodal facilities. When a railcar equipped with an AEI tag passes a reader, the EDI 160 is generated to report that read event, creating a real-time electronic trail of equipment movement.
For automotive logistics, this is especially valuable in rail operations where thousands of auto-rack cars circulate continuously. EDI 160 data feeds into asset tracking dashboards that allow OEMs and rail operators to monitor where every railcar is at any given moment, knowing whether a car carrying 15 vehicles is in Kansas City, sitting on a siding in Albuquerque, or just arrived at the Los Angeles distribution yard. This visibility directly supports transit time management and customer delivery promise accuracy.
KEY DATA ELEMENTS
- Equipment ID and type code
- AEI transponder number
- Read location identifier
- Date and time of the read event
- Direction of travel
- Train/convoy identifier
- Reader facility code
- Equipment condition flag
REAL-WORLD USE CASE
An OEM’s transportation visibility platform ingests EDI 160 reads from 200+ wayside readers across the rail network, providing real-time ETA calculations for auto-rack cars and triggering alerts when railcars deviate from expected transit paths.
11. EDI 169 - Transportation Appointment Schedule Information
Appointment scheduling is the final coordination layer that ensures the right vehicles, the right equipment, and the right labor resources are available at the same place at the same time. The EDI 169 is the electronic mechanism for communicating transportation appointment schedules between shippers, carriers, and facilities, replacing phone-based scheduling systems that were historically prone to miscommunication and double-booking.
In the automotive context, EDI 169 is used to book pickup windows at assembly plants (where car haulers queue to receive vehicles), arrival appointments at distribution yards, and delivery appointments at dealerships that control their receiving lot. A dealership that is unprepared for a delivery, with its lot full or its receiving staff unavailable, can refuse delivery, creating costly driver detention and redelivery expenses. EDI 169 prevents this by establishing confirmed appointments that all parties can plan around.
KEY DATA ELEMENTS
- Appointment date and time
- Appointment window duration
- Facility location code
- Carrier and driver identifier
- Shipment/load reference
- Vehicle count expected
- Appointment confirmation ID
- Status code (request/confirm/cancel)
REAL-WORLD USE CASE
A car hauler dispatching system transmits EDI 169 appointment requests to five dealerships for the following day’s deliveries. Confirmed responses trigger driver route assignments and load manifests, eliminating the traditional dispatcher call-sheet and reducing appointment conflicts by 60%.
12. EDI 753/754 - Request for Routing Instructions and Routing Instructions
Suppliers initiate EDI 753 transactions to request routing instructions from buyers while communicating that merchandise is ready to ship. This transaction provides general information about shipment details including ship-from and ship-to addresses, requested dates, weights, and purchase order references. Buyers respond with EDI 754 Routing Instructions that authorize shipment by naming the specific carrier through SCAC code, confirming pickup windows, and detailing special handling requirements. In essence, the 753 asks “how should I ship this?” while the 754 answers with authoritative routing direction.
How They Work Together
The workflow begins when suppliers receive EDI 850 purchase orders without finalized routing instructions. Suppliers then transmit 753 messages, which auto-generate valid order releases in the buyer’s transportation management system when purchase order numbers and ship-from location IDs validate correctly. Following TMS processing, buyers send 754 responses back to suppliers. Suppliers acknowledge with EDI 997 functional acknowledgments before using the instructions to build shipments and generate EDI 856 advance ship notices.
Use Cases in Automotive Shipping
Many large retailers, including Amazon, Kohl’s, and Dick’s, use the 753/754 pattern to maintain control of inbound transportation. This process generally requires a response within limited time windows as short as 24 hours before shipment. Beyond the 753/754 pair, automotive manufacturers employ specialized EDI transaction sets including 120 (Vehicle Shipping Order), 121 (Vehicle Service), 124 (Vehicle Damage), 125 (Multilevel Railcar Load Details), 126 (Vehicle Application Advice), 127 (Vehicle Baying Order), 128 (Dealer Information), 129 (Vehicle Carrier Rate Update), 160 (Transportation Automatic Equipment Identification), and 169 (Transportation Appointment Schedule Information) alongside EDI 204 and 214 for comprehensive logistics coordination.
Benefits for Transportation Planning
Automated 753/754 exchanges improve operational efficiency by eliminating manual processes and facilitating routing automation. Buyers control inventory levels and decrease transportation costs through centralized routing authority. Incorrectly bypassing validated 754 instructions can result in routing violations and rejected shipments.
13. EDI 846 - Inventory Inquiry/Advice (INVRPT)
Unlike other EDI transaction sets that flow in one direction, the 846 Inventory Inquiry/Advice (EDIFACT INVRPT) operates between trading partners bi-directionally. Manufacturers, suppliers, and resellers use this EDI document type to share inventory information across various holding locations, including warehouses, distribution centers, outlets, and stores. Sellers transmit 846 messages to provide stock data to potential customers with no purchase obligation, while buyers send inquiries to request availability information. Representatives within a seller’s organization exchange 846 transactions between locations to coordinate internal inventory movements.
Real-Time Inventory Data
The transaction contains inventory location identification, item descriptions, and quantities presented in multiple formats. Quantity data includes on-hand stock, committed quantities, on-order amounts, returns, backorder levels, in-transit inventory, and float quantities. Product identifiers such as SKUs, UPCs, and GTINs appear alongside unit-of-measure specifications. Suppliers include forecasted restock dates, inventory levels by warehouse location, and notices regarding discontinued or backordered items.
How It Supports Supply Chain
Retailers managing drop-ship operations send 846 requests multiple times daily to maintain accurate eCommerce listings and prevent overselling. When automatic replenishment agreements exist between partners, quantity information in the 846 can trigger shipment of materials without additional purchase orders.
Benefits for Planning
Automated 846 exchanges eliminate manual inventory counts and phone calls, reducing errors while supporting vendor-managed inventory programs.
14. EDI 850 - Purchase Order (ORDERS)
Automotive manufacturers send the EDI 850 (EDIFACT ORDERS) to suppliers when requesting parts or materials. This EDI transaction set serves as an electronic purchase order that replaces paper or PDF documents with a structured message both partners’ systems can read automatically. Once received, the EDI 850 flows directly into the supplier’s ERP system, triggering acknowledgments, picking, packing, and shipping processes. The transaction can communicate a single purchase, establish recurring orders, or modify and cancel existing orders based on manufacturer specifications.
Key Data Elements
The EDI 850 follows the X12 envelope structure with an interchange header (ISA), functional group (GS), and transaction set (ST/SE). Inside the transaction, key segments include:
- BEG – Beginning segment with PO number and date
- REF – Reference identifiers such as contract codes
- DTM – Date and time references for delivery dates
- N1, N3, N4 – Name and address loops for ship-to, bill-to, and remit-to parties
- PO1 – Line item details including quantity, unit of measure, price, and product identifier
- CTT – Total number of line items
Each segment captures order number, dates, buyer and seller identifiers, ship-to and bill-to addresses, quantities, prices, payment terms, and delivery instructions.
How Manufacturers Use It
In essence, manufacturers create the 850 in their ERP system, convert it into the ANSI X12 format, and transmit it to suppliers. The structured data eliminates manual entry and enables automated order validation. Suppliers validate the document against X12 specifications and send a functional acknowledgment (EDI 997) to confirm receipt, followed by an order acknowledgment (EDI 855) confirming they can meet requirements.
Benefits for Suppliers
Suppliers process orders in minutes instead of days, reducing data-entry errors and lowering cost per order. The automation provides full audit trails and the ability to scale operations across thousands of partners. Accordingly, faster order processing leads to better supplier ratings due to fewer chargebacks and more efficient sales processing.
15. EDI 855 - Purchase Order Acknowledgment (ORDRSP)
Suppliers send the EDI 855 (EDIFACT ORDRSP) in response to received EDI 850 purchase orders or EDI 860 purchase order changes. This EDI transaction type confirms the supplier received and understood the order while indicating whether they accepted, rejected, or require modifications to fulfill requirements within 24 to 48 hours. Generated through the supplier’s ERP system, the 855 exports are in an ERP-specific format, such as an SAP IDoc, before being converted into the buyer’s required structure. Retailers and manufacturers often require suppliers to transmit the 855Â after receiving the original purchase order.
Purpose in Order Management
This EDI transaction set provides instant feedback on order status, creating a communication loop that keeps both parties aligned. The 855 may confirm full acceptance with no amendments, propose quantity or delivery date changes for specific line items, or highlight items that cannot be supplied with explanations. The message function code indicates acceptance, partial acceptance, or rejection.
How Suppliers Respond
Key segments include purchase order numbers, planned delivery dates, details on items requiring amendments, reasons for rejection, and transport information. Suppliers can report back on changes made to ensure the bulk of orders proceed successfully and to flag problematic items.
Benefits for Communication
Automated order confirmation eliminates phone calls, emails, and faxes, reducing manual entry and saving time. Better supplier ratings result from fewer errors, while buyers gain transparency for accurate open-to-buy calculations and inventory planning.
16. EDI 860 - Purchase Order Change Request
Buyers initiate the EDI 860 (EDIFACT ORDCHG) when modifications to previously transmitted EDI 850 purchase orders become necessary. This EDI transaction type enables quantity adjustments, pricing corrections, delivery date shifts, ship-to location updates, line item additions, or complete cancelations without generating entirely new orders. The 860 references the original purchase order number through the BCH segment, which contains the beginning segment for purchase order change along with change dates. Supported purchase order types include standard POs, planned POs, planned releases, blanket purchase agreements, and blanket releases.
How Changes Are Communicated
The BCH segment carries change indicators: 01 cancels the entire PO, 04 changes based on line items, 05 replaces the original with new line items, and 06 acknowledges a seller-initiated change. The POC segment specifies line item modifications using change type codes: AI (add item), CA (change), DI (delete item), PC (price change), PQ (unit price/quantity change), QD (quantity decrease), QI (quantity increase), and RS (reschedule). When canceling at the header level, every associated line cancels automatically. New lines are appended to the end without reusing old line numbers.
Use Cases in Automotive
For instance, manufacturers send 860 transactions when inventory projections shift, customer demand fluctuates unexpectedly, or production schedules require adjustment. Retailers correct ordering mistakes immediately rather than waiting for fulfillment. The transaction can modify partial shipments already in transit while adjusting remaining quantities.
Benefits for Flexibility
Suppliers receive clear modification instructions, update their systems automatically, and respond with EDI 855 acknowledgments or EDI 997 functional acknowledgments. The 860 creates audit trails documenting every change, prevents invoicing discrepancies, and eliminates manual phone calls or emails.
17. EDI 810 - Invoice (INVOIC)
Suppliers transmit the 810 invoice (EDIFACT INVOIC, VDA 4938) to manufacturers after fulfilling orders, requesting payment based on agreed terms. This EDI document type replaces paper, email, or PDF invoices with structured billing information that flows directly into the buyer’s accounts payable system. Once received, the 810 must pass against the original purchase order (EDI 850) and advance ship notice (EDI 856) three-way matching. Mismatches in quantity, price, or item data trigger rejection and payment delays.
Key Invoice Data Elements
The transaction follows X12 structure with critical segments including BIG (beginning segment with invoice date, number, and PO reference), IT1 (line item data with quantities and prices), TDS (total dollar summary), and CTT (transaction totals counting IT1 segments). The BIG04 field must contain the exact purchase order number to link the invoice properly. Additional segments provide party identification (N1), currency codes (CUR), pricing information (CTP), product descriptions (PID), and carrier details (CAD).
Commport EDI Solutions for Automotive Industry Trusted by Top Automakers and Suppliers Worldwide, Support All Major Automotive EDI Standards. Get Started Today!
How It Streamlines Payment
Buyers automatically match 810 data against purchase orders and shipping notices in their ERP systems. This accelerates payment cycles and improves accuracy, reducing disputes over pricing or quantity. After successful validation, buyers respond with an EDI 997 functional acknowledgment confirming receipt. Payment processing follows with an EDI 820 remittance advice containing payment details.
Benefits for Both Parties
Automated invoice processing reduces employee workload tremendously, eliminating manual data entry. Suppliers experience shorter days sales outstanding while buyers streamline accounts payable processes. Both parties benefit from reduced invoice processing time, fewer errors, and cleaner audit outcomes.
18. EDI 820 - Payment Order/Remittance Advice (REMADV)
Manufacturers initiate the EDI 820 (EDIFACT REMADV) to inform suppliers that they will transfer for received goods or that the transfer has occurred, and how much payment. This payment order enables businesses to automate sending payment instructions to banks, eliminating manual data entry and reducing processing times. The 820 follows the ANSI X12 standard, while EDIFACT uses REMADV to specify the same function. Suppliers receive this EDI transaction set after customers process EDI 810 invoices through their systems. Particularly useful when multiple invoices settle in a single payment, the 820 allows suppliers to relate several invoices to one transfer.
Payment Information Included
The transaction contains buyer and seller information, previous invoice details like invoice number and amount, surcharge or reduction reasons with applied discounts, and partial payments already transferred or still due. Banking information includes details about payer and payee bank accounts, while monetary amounts show total payment and calculation breakdowns. Payment tracking information, date/time references, and any adjustments to invoice amounts complete the data package.
How It Works in Automotive
Within automotive workflows, the 820 appears at the end of the exchange sequence. Once customers receive EDI 810 messages, their EDI systems validate the contents against available data. After syntactic validation, ERP systems update stored details with new information. Payment orders follow, particularly when suppliers issue invoices covering around ten days of delivery notes across various locations, settling them together.
Benefits for Financial Management
Automotive companies can automate financial forecasts, reducing employee workload. Both parties plan cash flows more precisely since ERP systems already contain invoice settlement information before it reaches accounts. Suppliers detect payment errors early and automatically, stabilizing cash flow. Direct transmission of payment details accelerates accounting processes. Furthermore, batch-driven payment runs become efficient for relationships involving large delivery volumes.
19. EDI 870 - Order Status Report
Suppliers transmit the 870 Order Status Report as a mid-cycle communication that bridges the gap between order acknowledgment and shipment notification. Unlike the 855 which responds immediately to new purchase orders or the 856 which fires at shipment, the 870 communicates what’s happening with orders already acknowledged but not yet shipped. This EDI transaction set can be triggered in response to an EDI 869 Order Status Inquiry or sent automatically on scheduled intervals.
Status Information Provided
The 870 opens with a BSR segment establishing the report date, referenced purchase order, and status type. The body uses PO1 loops for individual line items, each with status codes indicating disposition: OS (open, awaiting shipment), BO (back-ordered), PS (partially shipped), CA (canceled), or SH (shipped, not yet received). For back-ordered lines, DTM segments within the PO1 loop carry estimated availability or expected ship dates.
How It Maintains Transparency
Automated 870 reports replace dozens of daily order status inquiries. Suppliers proactively push status information to buyers’ order management systems rather than requiring manual lookup. Retail buyers managing hundreds of open purchase orders rely on 870s to identify at-risk orders before delivery windows close.
Benefits for Order Management
When integrated into OMS platforms, 870 status codes trigger exception workflows. Drop-ship programs depend on these updates for customer experience management, while distributors use 870s to update downstream customer commitments before escalations occur.
20. EDI 856 - Advance Ship Notice (DESADV)
Suppliers generate the 856 transaction (EDIFACT DESADV) immediately after releasing a shipment to the carrier, transmitting detailed shipment information before goods physically arrive at the manufacturer’s facility. This EDI document type serves as an electronic advance ship notice, replacing paper packing slips with structured data that receiving systems can process automatically. The timing proves critical: suppliers must transmit the ASNÂ (transit under 2 hours) and within 30 minutes for all other suppliers within 15 minutes for short lead-time shipments. Manufacturers process inbound 856 files every 10 minutes and send 997 functional acknowledgments immediately upon receipt. If material arrives prior to ASN processing, the transaction errors out since the shipment closes in the receiving system.
Critical Information Included
The 856 uses a hierarchical SOPI structure (Shipment, Order, Pack, Item) to describe packaging relationships in detail. Each transmission contains shipment identification numbers, item quantities with material descriptions, shipment and arrival dates, ship-to addresses including plant and dock locations, carrier data with tracking numbers, and package identification with serial numbers. The ASN number must match the supplier packing slip number exactly, with only one ASN transmitted per packing slip.
How It Improves Visibility
Since the 856 arrives before physical goods, warehouse teams validate expected shipments against actual deliveries, prepare dock space, and allocate resources in advance. Receiving personnel scan GS1-128 barcodes on cartons, accessing the previously received ASN to determine contents without opening packages. This process accelerates goods receipt while reducing human errors tremendously.
Benefits for Manufacturers
Manufacturers running JIT or JIS assembly lines depend on ASNs to confirm supplies arrive on time. The automated data integration eliminates manual entry, prevents inventory planning errors, and enables faster payment processing. Non-compliance with ASN requirements can result in penalties up to $500 per occurrence.
21. EDI 861 - Receiving Advice/Acceptance Certificate
Receiving parties transmit the EDI 861 to formally acknowledge receipt of goods and provide detailed information about quantities and conditions of items received. This EDI transaction set confirms whether shipments arrived complete, partial, damaged, or with discrepancies between what was ordered and what physically arrived. In essence, the 861 serves as an electronic acceptance certificate that buyers send after inspecting delivered materials.
Receipt Information Included
The transaction reports discrepancies such as incorrect quantities, damaged items, or wrong products delivered. FCA US transmits 861 transactions every twenty minutes to provide suppliers with timely discrepancy information. Receipt information includes overage or shortage to the ASN quantity, material received without a corresponding advance ship notice, items returned due to defects or over shipments, and notifications for year-to-date cumulative shipment adjustments. Receiving condition codes specify the exact nature of problems: code 02 indicates shortages, code 03 signals overages, code 11 requires cumulative adjustments, code 13 flags missing ASNs, and code 14 documents scrapped material.
How It Closes the Loop
The 861 integrates directly into order management and inventory systems, updating records to reflect received goods and triggering subsequent actions like payments or inventory replenishment. Accordingly, buyers match 861 data against EDI 850 purchase orders and EDI 856 advance ship notices to validate transaction completeness.
Benefits for Verification
Automating receipt processes reduces manual data entry errors. The transaction standardizes communication between trading partners, facilitates quicker dispute resolution by clearly documenting issues, and serves as essential compliance and auditing documentation. Furthermore, accurate data collection improves inventory management practices, optimizes stock levels, and enhances demand forecasting.
22. EDI 997 - Functional Acknowledgment (CONTRL)
The EDI 997 (EDIFACT CONTRL) operates as both for any ANSI X12 EDI message exchanged between suppliers and manufacturers technical and functional acknowledgment. Specifically, it confirms receipt and acceptance of transactions while stating approval or rejection with detailed error lists. Although not always mandatory, 997 messages prove vital for electronic purchasing processes in manufacturing. Suppliers and manufacturers most commonly use this acknowledgment in response to EDI 850 Purchase Orders or EDI 810 Invoices.
How It Validates Transactions
Technical acknowledgments include segments AK1 (Functional Group Response Header), AK2 (Transaction Set Response Header), and AK5 (Transaction Set Response Trailer), referencing the original transaction and control number. Functional acknowledgments add AK3 (Data Segment Note) and AK4 (Data Element Note) segments, detailing errors within data segments and failure reasons. Status codes indicate A (Accepted), E (Accepted with Errors), R (Rejected), or P (Partially Accepted).
Commport EDI Solutions for Automotive Industry Trusted by Top Automakers and Suppliers Worldwide, Support All Major Automotive EDI Standards. Get Started Today!
Use Cases in Automotive EDI
When manufacturers send 850 purchase orders or suppliers transmit 810 invoices, receivers generate 997 acknowledgments to confirm syntactical accuracy. Typical rejection reasons include character length violations, incomplete mandatory segments, or invalid data.
Benefits for Data Integrity
The 997 creates automatic audit trails confirming message acceptance. Supply chain and financial transactions gain protection through error detection, while troubleshooting becomes easier when rejection reasons appear. Accepted information processes even when partial rejections occur.
23. EDI 940 - Warehouse Shipping Order
Manufacturers and wholesalers use the EDI 940 to instruct third-party logistics providers or remote warehouses to ship goods to buyers. This standardized X12 transaction enables depositors to authorize shipments, confirm orders, or modify and cancel previously transmitted shipping orders. Suppliers commonly rely on 3PLs to maintain inventory and process shipments on their behalf, making the 940 one of two primary EDI transaction sets designed specifically for warehouse communications. The document provides comprehensive shipping instructions including what items to ship, quantities, destinations, and timing.
Warehouse Instructions Included
Core segments include REF (purchase order number), N1 (ship-to address), W01 (warehouse order details with quantities and product IDs), PER (receiver contact information), NTE (shipping instructions), and W66 (special equipment requirements). The W66 segment specifies transportation payment terms, shipment methods, pallet exchange instructions, loading requirements, routing details, and FOB points. Furthermore, the transaction may include temperature control requirements, hazardous material handling, and packaging specifications.
How It Coordinates Distribution
Once received, warehouse management systems automatically process the 940, directing staff to pick items, pack according to instructions, and prepare shipments. The warehouse responds with an EDI 945 Warehouse Shipping Advice confirming dispatch and providing tracking information. This replaces manual methods like emails, faxes, and spreadsheets that create delays and data-entry errors.
Benefits for Logistics Providers
Automated processing reduces administrative overhead while minimizing human errors through structured data formats. Real-time integration with warehouse systems accelerates order fulfillment and strengthens collaboration between depositors and logistics partners.
24. EDI 214 - Transportation Carrier Shipment Status Message
Transportation carriers transmit the EDI 214 exclusively to provide shippers, consignees, and their agents with shipment status throughout the delivery lifecycle. This EDI transaction set tracks physical cargo location at any given time and can report on more than twenty different event types. The document includes shipment identification numbers, status codes with descriptions, date and time stamps, city and state locations, shipment packaging details, weight and quantity specifications, and handling requirements.
Shipment Status Updates
Carriers send multiple 214 transmissions as freight moves through the network, triggered by arrival and departure events plus delivery completion. The AT7 segment carries standardized event codes: AF (departed customer), X4 (arrived at terminal), AR (arrival at destination), I1 (in-gate for intermodal), and D1 (completed unloading). Besides these core events, carriers can include updated estimated time of arrival with each status through a second AT7 line using X2 for intermodal shipments or AG for carload freight.
How It Works in Real-Time
Shippers expect carriers to send 214 messages immediately as events occur. The transaction integrates directly into transportation management systems, warehouse management systems, and ERP platforms. Receivers send an EDI 997 functional acknowledgment confirming receipt.
Benefits for Visibility
Real-time 214 data eliminates manual status calls and portal updates, enabling proactive dock scheduling adjustments and staffing reallocation when delays surface.
25. EDI 204 - Motor Carrier Load Tender
Shippers transmit the EDI 204 Motor Carrier Load Tender to carriers when offering truckload or less-than-truckload freight for transport. This transaction provides detailed shipment information including origin, destination, weight, equipment type, scheduling windows, and accessorial requirements. The 204 serves as an electronic freight tender between shippers and carriers, functioning as an advanced pick-up notification. Carriers receive the standardized load offer and respond with an EDI 990 (Response to Load Tender) accepting or rejecting the shipment.
Purpose in Transportation
The 204 contains key segments: B2 (beginning segment), B2A (set purpose), L11 (reference numbers), G62 (date/time), N1 (party identification), and S5 (stop-off details). This transaction works alongside EDI 214 (Shipment Status) and EDI 210 (Freight Invoice) to create a complete logistics communication loop. Beyond the 204, the automotive sector relies on specialized transportation EDI codes, including 120 (Vehicle Shipping Order), 169 (Transportation Appointment Schedule), and 214 (Carrier Shipment Status).
How Carriers Receive Instructions
Carriers must respond within specified timeframes, often within 30 minutes of receipt. The transaction includes identification information for shipper and receiver, shipping instructions with pickup and delivery timeframes, equipment specifications, and load details covering quantities, dimensions, and weight.
Benefits for Logistics
The 204 reduces data entry errors while improving shipment planning for both parties. Speed increases through standardized offers, accuracy improves via predefined data segments, and scalability enables processing hundreds of daily loads.
26. EDI 862 - Shipping Schedule (DELJIT)
The 862 shipping schedule (DELJIT in EDIFACT) supplements existing EDI 830 planning schedules with precise, time-specific delivery requirements. Manufacturers send this EDI transaction set to communicate exact shipping times and quantities, often on a daily or even hourly basis. The 862 supersedes certain shipping and delivery information from previous planning schedules but never replaces the 830 entirely. This EDI document type cannot authorize labor, materials, or other resources. Instead, it provides the detailed execution layer for commitments already established through the planning schedule.
Key segments within the 862 include BSS (beginning segment), DTM (date/time reference), N1 (name), LIN (item identification), SCH (line item schedule), TD5 (carrier details), and REF (reference information). Each transmission contains buyer and vendor identification, ship-to addresses, product descriptions with SKUs, shipping instructions, packing specifications, and sequencing details.
How It Works with EDI 830
The 830 defines long-term delivery planning, typically covering weeks or months. The 862 extends this planning with precise time information for near-future shipments. For instance, manufacturers issue 830 transactions weekly while sending 862 messages daily to refine requirements. When inventory needs shift rapidly in just-in-time environments, buyers send 862 documents to update the existing 830 instructions. The most recently transmitted 862 overrides the previous 862 messages for a given shipment.
Use Cases in Automotive Industry
Automotive manufacturers rely on 862 transactions to coordinate component delivery to assembly lines, ensuring production runs smoothly without overstocking parts. The transaction provides time-slot-level precision during specific days, reducing stock levels through exact delivery information.
Benefits for Suppliers
Suppliers integrate 862 data directly into production planning systems, aligning manufacturing output with customer demand. Automation reduces manual workload tremendously, as data flows automatically without human intervention. Meeting 862 standards is a prerequisite for supplier ratings and partner nominations in JIT processes.
27. EDI 830 - Planning Schedule with Release Capability (DELFOR)
The EDI 830 transaction set transmits forecasted demand and delivery schedules from manufacturers to suppliers in the automotive supply chain. Known as DELFOR (DELivery FORecast) in EDIFACT messaging, this planning schedule serves three distinct functions: a simple forecast, a forecast with buyer authorization for suppliers to commit resources like labor or material, or one that eliminates the need for discrete purchase orders as an order release mechanism. Manufacturers prepare these forecasts in their ERP systems through planning routines and export them into an ERP-specific format before converting them into ANSI X12 EDI 830 messages.
Purpose in Automotive Supply Chain
This EDI transaction type allows buyers to communicate production schedules with both short-term and long-term demand projections. The planning schedule may include projected quantities, release dates specifying when goods are expected, and time periods that can be stated in daily, weekly, monthly, quarterly intervals. Furthermore, each new EDI 830 message replaces the former planning schedule completely. The document may include release capabilities that authorize shipment and production releases based on forecasted demand.
How It Supports Just-in-Time Manufacturing
By combining forecast data with firm release dates, the 830 supports just-in-time manufacturing and reduces excess inventory. Complex workflows can be triggered in the supplier’s ERP or MRP system for creating production orders, depending on whether the supplier operates as a make-to-stock or make-to-order manufacturer. Suppliers receive the message, validate it against ANSI X12 specifications, and send back a functional acknowledgment (EDI 997) confirming receipt.
Benefits for Production Planning
Suppliers use information from the EDI 830 to plan production schedules, manage raw material procurement, and prepare for upcoming shipments. This automation reduces employee workload since data doesn’t require manual typing, prevents errors through automatic system generation, and enables paperless data exchange. Delivery planning becomes quicker and less prone to errors, while automatic integration of delivery schedules saves time and reduces costs.
Conclusion
Understanding these 27 EDI transaction sets proves essential for automotive manufacturers and suppliers managing modern supply chains.
Given these points, mastering transactions ranging from basic purchase orders (EDI 850) to specialized vehicle logistics (EDI 120-169) and transportation coordination (EDI 204, 214) eliminates manual processes and reduces costly errors.
Most importantly, the automotive industry’s near-complete adoption of EDI means that compliance directly impacts your supplier ratings and partnership opportunities.
Commport EDI Solutions for Automotive Industry Trusted by Top Automakers and Suppliers Worldwide, Support All Major
Automotive EDI Standards. Get Started Today! Without doubt, implementing the right EDI transactions transforms your operations from reactive to proactive, positioning your organization for sustainable growth in this digitally connected sector.
Commport EDI Solutions - #1 EDI Solutions Provider in North America
Need Help? Download: Commport's EDI Buyers Guide
Unlock the full potential of your supply chain with our comprehensive EDI Buyer's Guide — your first step towards seamless, efficient, and error-free transactions
Frequently Asked Questions
Electronic Data Interchange (EDI) in the automotive industry is a standardized system that enables automated communication between manufacturers, suppliers, and logistics partners. It allows these parties to exchange critical business documents like purchase orders, invoices, and shipping notices electronically, eliminating manual processes and improving supply chain efficiency.
The most frequently used EDI transactions in automotive include the EDI 850 (Purchase Order), EDI 856 (Advance Ship Notice), EDI 810 (Invoice), EDI 830 (Planning Schedule), and EDI 862 (Shipping Schedule). These transactions form the foundation of order management, inventory planning, and payment processing between manufacturers and suppliers.
Tier 1 suppliers deliver major systems and assemblies directly to vehicle manufacturers (OEMs). Tier 2 suppliers provide components, software, and parts to Tier 1 suppliers. Tier 3 suppliers furnish raw materials and basic parts to Tier 2 companies. This hierarchical structure ensures efficient production flow from raw materials to finished vehicles.
EDI 830 (Planning Schedule) provides long-term forecasted demand and delivery schedules, typically covering weeks or months. EDI 862 (Shipping Schedule) supplements the 830 with precise, time-specific delivery requirements on a daily or hourly basis. While the 830 establishes planning commitments, the 862 provides exact execution details for near-future shipments.
The EDI 856 is transmitted before goods physically arrive, allowing receiving teams to validate expected shipments, prepare dock space, and allocate resources in advance. Warehouse personnel can scan barcodes and access the previously received ASN to determine package contents without opening them, which accelerates goods receipt and reduces errors in just-in-time manufacturing environments.
