EDI: Document Types

EDI 810Invoice

The electronic invoice sent from a supplier to a buyer, replacing a paper invoice. The 810 includes line-item detail, quantities, unit prices, terms, and total amounts. Discrepancies between the 810 and the original 850 Purchase Order are a leading cause of payment delays and chargebacks.

Why EDI 810 (Invoice) matters in B2B integration

EDI 810 (Invoice) is part of the edi: document types vocabulary that operators, IT leaders, and integration architects use when scoping ecommerce, ERP, EDI, and fulfillment projects. APIWORX integrates 200+ systems across this landscape — if EDI 810 (Invoice) touches your stack, we can help you connect it without custom code.

Talk to an integration architect

EDI 820Payment Order / Remittance Advice

Sent from buyer to supplier to communicate that a payment has been made or is scheduled, along with the invoices it covers. The 820 enables automated cash application in the supplier's AR module, eliminating manual remittance matching.

EDI 830Planning Schedule with Release Capability

A forecast document sent from a buyer to a supplier outlining anticipated purchase volumes over a planning horizon. The 830 allows suppliers to plan production and inventory ahead of formal purchase orders — common in manufacturing and automotive supply chains.

EDI 832Price/Sales Catalog

Transmits a supplier's product catalog — including item numbers, descriptions, pricing, and availability — to a trading partner. The 832 keeps buyer systems current with supplier catalog changes without manual re-entry, and is common for distributors and wholesalers.

EDI 846Inventory Inquiry/Advice

Communicates current inventory levels from a supplier or warehouse to a trading partner. The 846 enables demand planning, available-to-promise logic, and replenishment triggers — and is used in drop-ship and vendor-managed inventory (VMI) programs.

EDI 850Purchase Order

The foundational EDI transaction: a formal order sent from a buyer to a supplier specifying items, quantities, prices, ship-to addresses, and required delivery dates. Every downstream EDI transaction — the 855 acknowledgment, 856 ASN, 810 invoice — traces back to the originating 850.

EDI 855Purchase Order Acknowledgment

Sent by the supplier in response to an 850 to confirm receipt, acceptance, or rejection of the purchase order. The 855 may confirm as-submitted, flag changes (backorders, substitutions), or reject entirely. Many retail compliance programs require a 855 within hours of PO receipt.