EDI has a reputation for complexity. With over 300 transaction set types in the X12 standard alone, it's easy to see why. But for most manufacturers and distributors running on IBMi, that number is mostly noise. B2B commerce runs primarily through four core documents. Know these well and you have the foundation for a well-run EDI program.
850: The Purchase Order
The 850 is where everything starts. When a trading partner is ready to place an order, they send an 850 with the full order details: item numbers, quantities, delivery dates, ship-to address, and pricing. In a well-configured IBMi setup, an inbound 850 flows directly into a sales order in your ERP without manual entry.
The most common pain point is item number mapping. Your trading partner's SKU or UPC often won't match your internal item ID. Keeping that cross-reference accurate and maintained prevents misrouted inventory and delayed fulfillment down the line.
855: The Purchase Order Acknowledgment
The 855 is the document most teams underestimate, until a chargeback shows up because they didn't send one. It's your confirmation that you've received the order and can fulfill it. The 855 can acknowledge full acceptance, partial acceptance, or a change like a substituted item or adjusted quantity.
Many large retailers and distributors treat it as a contractual step. A late or missing 855 can trigger a non-compliance penalty. In a properly configured setup, the 855 is generated directly from the sales order created by the 850, automatically, without a separate manual step.
856: The Advance Ship Notice
The 856 is the most compliance-sensitive of the four. It tells your trading partner what's being shipped, when it left, how it's packed, and who's carrying it. Most large customers require an 856 within a tight window after shipment confirmation, and it must match the physical shipment exactly.
Penalties for late or inaccurate 856 transmission can be significant, often calculated as a percentage of the cost of goods on the affected shipment. The window between shipment confirmation and ASN transmission is where most problems occur, which is why real-time monitoring matters. Get it right and your customer's receiving team knows exactly what to expect when the truck arrives. Fewer delays. Fewer discrepancies. Fewer chargebacks.
810: The Invoice
The 810 is your electronic invoice. What sets it apart from a standard accounts receivable invoice isn't the data; it's the tolerance for error. Most trading partners process invoices automatically, so a missing field or a mismatch with the original purchase order means an automatic rejection and a resubmission cycle.
The most common cause of rejection is a mismatch between what was ordered and what's being invoiced: quantity, unit of measure, or price variances. Across the industry, chargebacks tied to invoice mismatches are estimated to cost suppliers between 1% and 5% of gross annual revenue. An EDI setup that traces all four documents back to the originating sales order makes these easy to catch before the invoice goes out.
How the Four Work Together
The 850 arrives and creates a sales order. Your team picks, packs, and prepares to ship. The 855 goes back out, confirming the order and flagging any changes before fulfillment begins. The 856 follows at shipment, notifying the trading partner of exactly what's on the way. The 810 closes the loop, invoicing for the goods delivered and tied back to the original purchase order.
When all four flow cleanly and in sequence, your order-to-cash cycle runs largely on its own. When one fails, delays, disputes, and chargebacks follow. The four documents are only as strong as the weakest link in the chain.
Moving Beyond the Core Four
Most companies start with these four and add others as their trading partner network grows. Common additions include the 997 Functional Acknowledgment, the 824 Application Advice, and retail-specific inventory or promotional documents.
The broader EDI landscape is also shifting. Manufacturers and distributors are under more pressure than ever to onboard new trading partners quickly, and the move toward hybrid models that pair traditional EDI documents with modern APIs is accelerating. For IBMi shops, the good news is that XA, LX, and System21 are well-positioned for this evolution. The platform supports the connectivity. The question is whether the EDI layer on top of it is current and whether the team maintaining it has the bandwidth to keep it that way.
If you have questions about how the Core Four flow inside your IBMi environment, or if you're working through a trading partner requirement and want a second set of eyes, we would be glad to help. Reach out to Frank at fazzalina@unilinkgroup.com or visit www.unilinkgroup.com.
Truly, The UniLink Group
The Core Four: The EDI Documents That Run Your Business
EDI has a reputation for complexity. With over 300 transaction set types in the X12 standard alone, it's easy to see why. But for most manufacturers and distributors running on IBMi, that number is mostly noise. B2B commerce runs primarily through four core documents. Know these well and you have the foundation for a well-run EDI program.
850: The Purchase Order
The 850 is where everything starts. When a trading partner is ready to place an order, they send an 850 with the full order details: item numbers, quantities, delivery dates, ship-to address, and pricing. In a well-configured IBMi setup, an inbound 850 flows directly into a sales order in your ERP without manual entry.
The most common pain point is item number mapping. Your trading partner's SKU or UPC often won't match your internal item ID. Keeping that cross-reference accurate and maintained prevents misrouted inventory and delayed fulfillment down the line.
855: The Purchase Order Acknowledgment
The 855 is the document most teams underestimate, until a chargeback shows up because they didn't send one. It's your confirmation that you've received the order and can fulfill it. The 855 can acknowledge full acceptance, partial acceptance, or a change like a substituted item or adjusted quantity.
Many large retailers and distributors treat it as a contractual step. A late or missing 855 can trigger a non-compliance penalty. In a properly configured setup, the 855 is generated directly from the sales order created by the 850, automatically, without a separate manual step.
856: The Advance Ship Notice
The 856 is the most compliance-sensitive of the four. It tells your trading partner what's being shipped, when it left, how it's packed, and who's carrying it. Most large customers require an 856 within a tight window after shipment confirmation, and it must match the physical shipment exactly.
Penalties for late or inaccurate 856 transmission can be significant, often calculated as a percentage of the cost of goods on the affected shipment. The window between shipment confirmation and ASN transmission is where most problems occur, which is why real-time monitoring matters. Get it right and your customer's receiving team knows exactly what to expect when the truck arrives. Fewer delays. Fewer discrepancies. Fewer chargebacks.
810: The Invoice
The 810 is your electronic invoice. What sets it apart from a standard accounts receivable invoice isn't the data; it's the tolerance for error. Most trading partners process invoices automatically, so a missing field or a mismatch with the original purchase order means an automatic rejection and a resubmission cycle.
The most common cause of rejection is a mismatch between what was ordered and what's being invoiced: quantity, unit of measure, or price variances. Across the industry, chargebacks tied to invoice mismatches are estimated to cost suppliers between 1% and 5% of gross annual revenue. An EDI setup that traces all four documents back to the originating sales order makes these easy to catch before the invoice goes out.
How the Four Work Together
The 850 arrives and creates a sales order. Your team picks, packs, and prepares to ship. The 855 goes back out, confirming the order and flagging any changes before fulfillment begins. The 856 follows at shipment, notifying the trading partner of exactly what's on the way. The 810 closes the loop, invoicing for the goods delivered and tied back to the original purchase order.
When all four flow cleanly and in sequence, your order-to-cash cycle runs largely on its own. When one fails, delays, disputes, and chargebacks follow. The four documents are only as strong as the weakest link in the chain.
Moving Beyond the Core Four
Most companies start with these four and add others as their trading partner network grows. Common additions include the 997 Functional Acknowledgment, the 824 Application Advice, and retail-specific inventory or promotional documents.
The broader EDI landscape is also shifting. Manufacturers and distributors are under more pressure than ever to onboard new trading partners quickly, and the move toward hybrid models that pair traditional EDI documents with modern APIs is accelerating. For IBMi shops, the good news is that XA, LX, and System21 are well-positioned for this evolution. The platform supports the connectivity. The question is whether the EDI layer on top of it is current and whether the team maintaining it has the bandwidth to keep it that way.
If you have questions about how the Core Four flow inside your IBMi environment, or if you're working through a trading partner requirement and want a second set of eyes, we would be glad to help. Reach out to Frank at fazzalina@unilinkgroup.com or visit www.unilinkgroup.com.
Truly, The UniLink Group
Comments
Share this article
Archives
Associated groups