The loop in thirty seconds
The buyer's system emits an 850 purchase order. The supplier's system reads it, ships the goods, and sends an 856 advance ship notice describing exactly what is on the truck. After delivery, the supplier sends an 810 invoice referencing both. The buyer's payables matches all three — ordered vs received vs billed — and releases payment. Acknowledgements punctuate every step: 997s confirm transmissions arrived, and the 855 confirms the order itself was accepted. One PO number ties the chain together from order to cash.
Step 1 — the 850 purchase order
The 850 carries the commercial agreement in structured form: line items with buyer SKUs and quantities, unit prices, ship-to and bill-to locations, requested and cancel-by dates, and allowances or charges the buyer expects honored. It is the document everything else is measured against, so reading it precisely matters more than reading it fast. Suppliers typically answer with an 855 acknowledgement — accepting, changing, or rejecting lines — which locks the shared version of the order before anyone picks product. Skim the 850 and the rest of the workflow inherits the error.
Step 2 — the 856 advance ship notice
The 856, universally called the ASN, is a packing list transmitted ahead of the trailer. Its hierarchy runs shipment → order → pack → item: which cartons (each with an SSCC barcode) contain which items in which quantities, plus carrier, tracking, and ship date. The distribution center scans SSCCs at receiving and reconciles against the ASN — accurate ASNs get unloaded fast, inaccurate ones get inspected, relabeled, or penalized. ASN accuracy is the single largest driver of retail chargebacks, which is why our 856 guide treats carton-level discipline as the main event rather than a detail.
Step 3 — the 810 invoice
The 810 requests payment and must mirror reality: shipped quantities (not ordered quantities, when they differ), agreed prices, allowances actually applied, and references back to the PO number and shipment. The buyer's three-way match — 850 vs receiving record vs 810 — clears automatically when the numbers agree and parks the invoice in exception handling when they don't. Most “late payment” stories in EDI are really mismatch stories: a substituted SKU, an allowance missing from the invoice, a quantity invoiced that was never shipped. Invoice accuracy is a downstream consequence of ASN accuracy.
The receipts that hold it together
Two acknowledgement types keep the loop honest. The 997 functional acknowledgement confirms each transmission was syntactically accepted — think certified-mail receipt, not approval. A rejected 997 means fix the structure and resend; an accepted one means the document entered the partner's system, not that the business content was approved. The 855 operates at the business level, confirming the order itself. Track both per document: “sent” is not a status, “accepted” is, and the gap between them is where lost shipments and surprise disputes live.
Where the chain usually breaks
Breakage clusters at the handoffs. Misread 850s produce wrong picks that the ASN then faithfully — and expensively — documents. Late or missing ASNs force manual receiving, which is where chargebacks start. Invoices that don't match the ASN stall in payables while the supplier's cash conversion stretches. The fix is unglamorous: validate each document against the partner's implementation guide before sending, keep PO references intact across all three, and monitor acknowledgements instead of assuming delivery. Run samples through the EDI validator and the 856 validator during onboarding, follow the onboarding guide for certification evidence, and price the ongoing operation against published plans — SignalEDI lists Seasonal $99, Starter $199, Growth $999, and Enterprise $1999 monthly tiers on the pricing page.