How EDI 856 Works
The process generally begins after a supplier receives and prepares an approved purchase order. Once the goods are picked, packed, and scheduled for shipment, the supplier generates an EDI 856 containing the shipment details agreed with the trading partner.
The buyer receives the ASN before the shipment arrives and uses the information to prepare receiving, warehouse, inventory, and reconciliation activities. When the physical shipment arrives, the buyer can compare the received goods with the electronic shipment information and the original order.
- Order reference: The shipment is associated with the relevant purchase order and other transaction identifiers.
- Shipment details: Carrier, shipment date, destination, tracking information, and related logistics details can be communicated.
- Package information: The ASN can describe containers, cartons, pallets, and their hierarchical relationships.
- Item information: Product identifiers, shipped quantities, units of measure, and other line-level information can be included.
- Receiving: The buyer uses the advance information to prepare receiving and reconcile physical goods against electronic records.
Core Data Elements
An EDI 856 can contain information at shipment, order, packaging, and item levels. Shipment-level information identifies the overall movement, while order-level details connect the shipment to the buyer's purchase order. Packaging information can identify cartons or pallets, and item-level information can specify products and quantities.
For example, a supplier might ship 120 units across four cartons. The ASN can identify the shipment, associate it with the relevant order, identify each package, and specify how many units are contained in each package. When the shipment arrives, the receiving team has structured information to compare with the physical delivery.
The exact data requirements vary by industry and trading-partner agreement. Retail, manufacturing, distribution, and other supply-chain environments may require different package identifiers, product codes, carrier information, or delivery details.
EDI 856 in Receiving and ERP Workflows
The EDI 856 connects logistics information with purchasing and enterprise systems. When integrated with an ERP, the ASN can support advance receiving preparation, inventory updates, order reconciliation, and downstream accounting workflows.
ERP configuration also affects how shipment and receiving information connects with financial structures such as the chart of accounts. Organizations extending finance workflows around an ERP should ensure that operational shipment data remains aligned with the accounting and reporting structures used for financial processing.
The ASN can also support downstream invoice validation because the shipment record provides another source of evidence when comparing what was ordered, shipped, received, and ultimately billed.
Tax and Compliance Considerations
Shipping information can have tax implications because ship-from and ship-to locations may influence applicable jurisdiction rules. Organizations may need to consider sales tax, exemptions, economic nexus, VAT or GST requirements, and audit exposure when shipment data is used for tax determination.
In this context, use tax considerations can depend on applicable jurisdiction rules and the relationship between purchasing, delivery locations, and tax treatment. Maintaining accurate shipment addresses and transaction records helps finance teams support appropriate tax validation.
Tax-related business correspondence can include a Tax Notice, while concepts such as Advance Tax and Demand Notice relate to other areas of tax administration and should be distinguished from the operational shipment information contained in an EDI 856.
EDI 856 and Financial Operations
Although the EDI 856 is primarily a logistics transaction, it can contribute to financial control by providing evidence about goods in transit and shipment status. Accurate shipment information helps organizations understand when inventory is moving, when goods are expected to arrive, and when receiving activity can support subsequent financial processing.
These signals can also improve cash flow visibility because purchasing and finance teams can connect inventory movement with expected receipts, supplier obligations, and working-capital planning. A reliable shipment trail can therefore contribute to more informed liquidity and forecasting decisions.
Best Practices for EDI 856
- Maintain order references: Ensure every ASN clearly connects to the appropriate purchase order and shipment identifiers.
- Standardize product data: Use consistent item numbers, units of measure, package identifiers, and location information.
- Validate shipment quantities: Confirm that quantities and package relationships accurately represent the physical shipment.
- Maintain traceability: Retain shipment records, tracking details, and related transaction references for reconciliation.
- Coordinate trading-partner requirements: Define required fields, transmission timing, packaging hierarchy, and acknowledgment expectations.
Summary
EDI 856 Advance Ship Notice is a structured electronic message that communicates shipment details to a buyer before or when goods are shipped. It connects purchase orders with logistics, receiving, inventory, tax validation, and financial workflows. By providing advance visibility into shipment contents and delivery information, the EDI 856 supports accurate receiving, reconciliation, working-capital visibility, and reliable business records.