EDI has a reputation for complexity. With over 300 transaction set types in the X12 standard alone, it’s easy to see why.
The EDI software market itself keeps expanding, on pace to grow roughly 12% year-over-year, as more mid-market manufacturers and distributors get pulled into automated trading networks by their retail and enterprise customers.
For most manufacturers and distributors on Acumatica, that number is mostly noise because B2B commerce runs primarily through four core documents. Know these well, and you’ve got 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 Acumatica EDI setup, an inbound 850 flows directly into a sales order without manual entry.
The most common pain point is item number mapping. Often, your trading partner’s SKU or UPC won’t match your internal Acumatica item ID. Making sure that cross reference is accurate and maintained prevents misrouted inventory and delayed fulfillment later.
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 treat it as a contractual step, and a late 855 can trigger a non-compliance fine. In Acumatica, it’s generated from the sales order created by the 850. A native EDI setup can trigger it automatically from within the order workflow instead of a separate manual step.
856: The Advanced Ship Notice (ASN)
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. Large retailers require an 856 within a tight window after shipment, and it must match the physical shipment exactly.
Walmart’s OTIF (On Time In Full) program, for example, applies a penalty of 3% of the cost of goods on shipments that miss its delivery and ASN requirements, which makes the 856 one of the most financially consequential documents in the Core Four.
In Acumatica, confirming a shipment in the Shipments screen can trigger the 856 automatically. The window between shipment confirmation and ASN transmission is where most problems occur, so real-time monitoring matters. Get it right, and the receiving team knows exactly what to expect when the truck arrives with fewer delays, fewer discrepancies, fewer chargebacks.
810: The Invoice
The 810 is your electronic invoice. What sets it apart from a standard AR invoice isn’t the data; it’s the tolerance 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.
The most common cause of rejection is a mismatch between what was ordered (the 850) and what’s being invoiced including quantity, unit-of-measure, or price variances. Across the industry, chargebacks tied to mismatches like these are estimated to cost suppliers between 1% and 5% of gross annual revenue, a meaningful hit for any business running on tight margins. A 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
- 850 arrives → Creates a sales order. Your team picks, packs, and prepares to ship.
- 855 goes out → Confirms the order and flags any changes before fulfillment begins.
- 856 goes out → Notifies the trading partner of shipment details. Their receiving clock starts.
- 810 goes out → Invoices for the goods delivered, tied back to the original PO.
When all four flow cleanly and in sequence, your order-to-cash cycle runs largely on autopilot. When one fails, delays, disputes, and chargebacks follow.
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.
This is also where the broader EDI landscape is shifting. Mid-market manufacturers and distributors are under more pressure than ever to onboard new trading partners quickly, and many EDI and B2B integration providers are moving toward hybrid models that pair traditional EDI documents with modern APIs for faster setup and better real-time visibility.
At UniLink Group, our native EDI integration for Acumatica supports the Core Four and beyond, with a dedicated Acumatica team for document mapping, trading partner onboarding, and real-time monitoring. Our development team serves as both the project manager and your long-term EDI department for ongoing maintenance and support once live.
How confident are you in your data as it flows through your Order to Cash process?
Learn more about UniLink’s EDI integration for Acumatica.
