EDI Transaction Sets Every Manufacturer Should Know
EDI transaction sets are numbered document types in the ANSI X12 standard, each representing one business document - 850 is a purchase order, 856 an advance ship notice, 810 an invoice. Manufacturers typically live inside a dozen of the roughly 300 defined sets, and the same business meaning carries different numbers in EDIFACT (ORDERS, DESADV, INVOIC). This reference covers the sets that matter in discrete, aerospace, and automotive supply chains, what data each carries, and which ERP records they create or update in Infor SyteLine, LN, and M3.
Purchase Order Transaction Sets: 850, 860, and 855
The 850 purchase order is the anchor document. Its BEG segment carries the PO number and date, the PO1 loop carries line items with buyer part number, quantity, price, and unit of measure, and the DTM segments carry requested delivery dates. The 860 purchase order change request communicates quantity, date, or cancellation changes against an existing PO and must be applied to the same ERP order, not posted as a new one. The 855 purchase order acknowledgment is your response, using ACK segments to accept, reject, or counter each line with a promised date.
- 850 BEG02 carries the PO type code: SA for standalone, BE for blanket, RL for release against a blanket
- 860 changes are line-level; always match on PO1-01 line number, never on part number alone
- 855 ACK01 codes: IA accepted, IR rejected, IB backordered, IQ accepted with quantity change
- Blanket order releases arrive as 850 with BEG02 of RL, and must post as releases in ERP, not new orders
Shipping Transaction Sets: 856, 861, and 214
The 856 advance ship notice is the highest-risk document in most programs because customer receiving scans it. It uses a hierarchical HL loop structure - shipment, order, tare, pack, item - and the SN1 segments must match the physical pallet and carton build exactly. Serial or lot numbers ride in REF segments at the item level. The 861 receiving advice comes back from the customer confirming quantities received, which is your early warning for discrepancies. The 214 transportation carrier shipment status message flows from the carrier and is what feeds tracking visibility in your ERP shipping records.
- 856 HL structure must match the label hierarchy: pallet SSCC-18 to carton to item
- Mismatched 856 quantities are the leading cause of automotive and aerospace chargebacks
- Send the 856 before the truck arrives; many primes reject ASNs received after physical receipt
- 861 discrepancies should open an ERP shipping variance record, not just an email alert
Financial and Planning Sets: 810, 820, 830, and 862
The 810 invoice mirrors your ERP invoice: IT1 lines carry quantity, unit price, and part number, and TDS carries the total. Customers reconcile the 810 against their 850 and their receipt, so a price or UOM mismatch triggers a deduction rather than a phone call. The 820 payment order and remittance advice tells you what was actually paid and against which invoices, and should drive automated cash application. In automotive, the 830 planning schedule provides forecast horizons - often 12 to 52 weeks - while the 862 shipping schedule provides firm short-horizon releases that drive actual shipments.
Control Documents: 997, 824, and the Envelope Structure
Every X12 file is wrapped in an ISA/IEA interchange envelope containing one or more GS/GE functional groups, each containing ST/SE transaction sets. Control numbers at each level are your tracking keys and must be unique per partner. The 997 functional acknowledgment confirms syntactic receipt: AK9 with an A means accepted, R means rejected, and P means partially accepted. It says nothing about business validity. That is the 824 application advice, which reports that a syntactically valid document failed a business rule - unknown part number, invalid ship-to. Treat a missing 997 within your partner SLA as an operational incident, because silence usually means the file never arrived.
How Netray Maps Transaction Sets to Your ERP
Netray maintains canonical models for each of these sets against Infor SyteLine, LN, and M3 order, shipment, and invoice structures, so a new partner is a configuration exercise rather than a rebuild. Our AI mapping agent ingests a partner implementation guide and produces a segment-level diff against the canonical model, listing every mandatory element your ERP cannot currently supply. A second agent watches inbound 997 and 824 traffic, correlates rejections back to the originating ERP document, and surfaces the exact failing segment and element - which typically cuts EDI exception investigation time from hours to minutes.
Frequently Asked Questions
What is the difference between an EDI 850 and an EDI 830?
An 850 is a discrete purchase order that authorizes a specific quantity for a specific date. An 830 planning schedule is a rolling forecast, common in automotive, that shows demand across a horizon of weeks or months with firm, committed, and forecast buckets. You ship against firm buckets or an accompanying 862 shipping schedule, not against the forecast portion of the 830.
Does a 997 mean my EDI document was accepted?
Only syntactically. A 997 functional acknowledgment with AK9 status A confirms the file parsed against the X12 standard and the partner implementation guide. It does not confirm the partner could process the business content. If the part number is unknown or the ship-to is invalid, you get a separate 824 application advice, or in some programs no notice at all until a chargeback appears.
Which EDI transaction sets are required by automotive customers?
Most automotive OEM and tier-one programs require the 830 planning schedule, 862 shipping schedule, 856 advance ship notice, 810 invoice, and 997 acknowledgment at minimum. Many add the 820 remittance advice and the 824 application advice. The 856 is the highest-stakes document because receiving scans it, and quantity or label hierarchy mismatches generate chargebacks quickly.
Key Takeaways
- 1Purchase Order Transaction Sets: 850, 860, and 855: The 850 purchase order is the anchor document. Its BEG segment carries the PO number and date, the PO1 loop carries line items with buyer part number, quantity, price, and unit of measure, and the DTM segments carry requested delivery dates.
- 2Shipping Transaction Sets: 856, 861, and 214: The 856 advance ship notice is the highest-risk document in most programs because customer receiving scans it. It uses a hierarchical HL loop structure - shipment, order, tare, pack, item - and the SN1 segments must match the physical pallet and carton build exactly.
- 3Financial and Planning Sets: 810, 820, 830, and 862: The 810 invoice mirrors your ERP invoice: IT1 lines carry quantity, unit price, and part number, and TDS carries the total. Customers reconcile the 810 against their 850 and their receipt, so a price or UOM mismatch triggers a deduction rather than a phone call.
Put this into numbers
Free interactive tools for exactly this problem. No signup to use them.
Supply Chain Resilience Checklist
A 30-point audit across sourcing, buffers, demand visibility, ERP data quality, and disruption response, with the highest-risk items flagged as critical.
Free ToolAutomotive Supplier ERP Fit Assessment
Score how well your ERP handles automotive customer requirements including EDI release processing, ASN and AIAG labeling, cumulative quantity reconciliation, PPAP control, and recall traceability.
Free ToolProcure-to-Pay Efficiency Calculator
Quantify the labor cost buried in your purchase order and invoice processing, including exception handling, and benchmark your cost per invoice against automation leaders.
Terms used in this article
Need a mapping specification for a new 850, 856, or 830 partner? Netray can produce the segment-level spec and the ERP posting logic together.
Related Resources
EDI Implementation for Manufacturers
EDI implementation for manufacturers: map 850, 856, and 810 transactions to your ERP, pick a VAN or AS2, and go live with trading partners in 90 days.
ERPE-Commerce to ERP Integration for Manufacturers
E-commerce to ERP integration for manufacturers: sync catalog, pricing, inventory, and orders between Shopify or B2B portals and Infor SyteLine, LN, or M3.
ERPIntegration Error Handling Patterns
Integration error handling patterns for ERP: retries with backoff, idempotency keys, dead-letter queues, poison-message handling, and replay you can trust.