How EDI 856 Works
EDI 856 communicates shipment details from a supplier to a buyer before delivery or when the shipment is dispatched. The document can identify the purchase order, shipment, carrier, containers, items, quantities, and expected delivery information. This allows the receiving organization to prepare for incoming goods and reconcile physical receipts against expected quantities.
In a procure-to-pay workflow, the purchase order establishes what the buyer requested, while the EDI 856 communicates what the supplier actually shipped. A purchase requisition may precede the purchase order by initiating the internal request and approval process. Together, these documents create a traceable connection between procurement authorization and shipment execution.
How EDI 857 Works
EDI 857, the Shipment and Billing Notice, communicates shipment information together with billing-related information. It is designed for trading relationships where the recipient needs shipment and financial transaction details in a combined electronic message. The transaction can contain references that connect shipped products with the associated order and billing data.
Using EDI 857 can reduce the separation between fulfillment and billing information. This is particularly relevant when finance teams need shipment evidence to support invoice validation, customer billing, or reconciliation. In sales and procurement environments, understanding PO in Sales: Purchase Orders in the Sales Cycle Guide also helps clarify how order documents connect commercial commitments with downstream transaction processing.
EDI 856 vs EDI 857: Key Differences
The primary difference is the scope of information communicated. EDI 856 focuses on advance shipment details, whereas EDI 857 combines shipment and billing information. The appropriate transaction set depends on the trading partner's requirements, business process, and EDI implementation standards.
- EDI 856: Primarily communicates shipment contents, quantities, packaging, carrier information, and delivery details.
- EDI 857: Communicates shipment information together with billing-related transaction data.
- Receiving: EDI 856 provides advance visibility that helps warehouses prepare for expected receipts.
- Finance: EDI 857 can connect shipment evidence more directly with billing and reconciliation workflows.
- Trading partners: Both transactions depend on agreed implementation guides, data requirements, and business rules.
EDI 856, EDI 857, and Invoice Processing
Shipment data becomes financially important when received quantities must be compared with invoices and purchase orders. invoice processing can use shipment and receiving information as part of extraction, validation, matching, approval, and posting workflows.
An EDI 856 can provide evidence that specific items and quantities were shipped, while receiving records confirm what arrived. An EDI 857 can provide an additional billing context alongside those shipment details. The invoice itself may be represented through an EDI Invoice, creating a broader electronic transaction chain from order through shipment, receipt, invoice, and payment.
Tax and Payment Considerations
EDI shipment and billing information can also support financial controls when transactions affect tax determination, payment authorization, and reconciliation. Shipment records may provide the operational evidence needed to validate the quantities and commercial details used in downstream financial documents.
An EDI Tax Filing represents electronically transmitted tax-related information and should be distinguished from shipment transaction sets such as EDI 856 and EDI 857. Similarly, an EDI Payment File is designed for payment-related data and should not be treated as a substitute for shipment or billing notices. Keeping these transaction purposes distinct helps maintain clear document ownership and audit trails.
Business Use Cases
Retailers, distributors, manufacturers, wholesalers, and logistics-intensive businesses can use EDI 856 and EDI 857 to connect physical movement of goods with commercial and financial workflows. EDI 856 is particularly useful when receiving teams need advance shipment visibility, while EDI 857 is relevant when a trading relationship requires shipment and billing information to travel together.
For finance and procurement teams, the key decision is not simply which transaction is newer or more automated. The important consideration is whether the selected transaction set matches the trading partner's implementation guide and supports the required controls across procurement, fulfillment, receiving, billing, and reconciliation.
Best Practices for EDI 856 and EDI 857
- Map shipment identifiers consistently to purchase orders, orders, containers, and receiving records.
- Validate quantities, units of measure, item identifiers, and dates before downstream processing.
- Maintain clear relationships between shipment information and billing documents.
- Align transaction structures with each trading partner's implementation requirements.
- Use reconciliation controls to compare ordered, shipped, received, billed, and paid quantities.
Clear document mapping also improves spend visibility because procurement teams can connect sourcing and approvals with actual shipment and billing activity. This creates a stronger audit trail across the procure-to-pay cycle.
Summary
EDI 856 is primarily an advance shipment notice that communicates what is being shipped and supports receiving and logistics visibility. EDI 857 combines shipment and billing information for trading relationships that require a broader transaction message. Understanding the distinction helps organizations connect procurement, fulfillment, receiving, invoice validation, tax controls, payments, and financial reporting while maintaining accurate transaction records.