In this guide, you will learn what the EDI 855 contains, how it fits into the procurement workflow, what benefits order acknowledgments deliver and how to avoid common implementation errors.
Work with our experts to generate and transmit purchase order acknowledgments automatically.
What Is EDI 855?
The EDI 855 is an electronic document that a seller, such as a manufacturer, distributor or supplier, sends to a buyer in response to an EDI 850 purchase order. This purchase order acknowledgment replaces manual phone calls, faxes and email confirmations with a standardized, machine-readable response that integrates directly into the buyer’s ERP system.
The 855 transaction set follows the ANSI X12 standard maintained by the Accredited Standards Committee (ASC X12). Outside North America, the EDIFACT equivalent is the ORDRSP (Order Response) message, which serves the same function under international EDI document standards.
Unlike the EDI 997 Functional Acknowledgment, which only confirms that an EDI transmission was received without validating content, the EDI 855 provides a substantive business response. It tells the buyer whether the seller can fulfill the order as requested, what modifications are needed or whether the order must be declined entirely.
EDI 855 Acknowledgment Response Types
The purchase order acknowledgment communicates one of several response types. Each response dictates how the buyer should proceed with the order.
EDI 855 order accepted in full
When the seller can fulfill every line item at the requested quantities, prices and delivery dates, the 855 document confirms full acceptance. The buyer’s system updates the order status automatically, and the supply chain moves forward without manual intervention. This is the most straightforward acknowledgment scenario.
EDI 855 accepted with changes
Sellers often cannot fulfill an order exactly as submitted. Inventory shortages, price discrepancies, discontinued products or revised delivery dates require modifications. The EDI 855 communicates these changes at the header level, the line item level or both. For example, a retailer orders 5,000 units but the supplier has only 2,500 in stock. The 855 transaction reports the reduced quantity so the buyer can adjust inventory plans, source the remaining units elsewhere or modify the open-to-buy budget.
EDI 855 order rejected
In some cases, the seller must reject the purchase order entirely. Product unavailability, credit issues or pricing disputes can trigger a full rejection. The EDI 855 communicates this rejection with reason codes, allowing the buyer to resolve the issue and resubmit a corrected purchase order quickly.
EDI 855 Key Data Components
The purchase order acknowledgment contains several critical data segments drawn from the X12 standard. Understanding each component ensures your EDI integration captures the information your procurement team needs.
EDI 855 Purchase Order References
The BAK segment opens every 855 transaction with the transaction set purpose code, acknowledgment type (accepted, rejected or accepted with changes), the original purchase order number and the PO date. The REF segment carries additional reference identifiers when the purchase order number exceeds 22 characters or when supplementary references are required.
EDI 855 Line Item Acknowledgments
The PO1 segment mirrors the original purchase order line items : line number, quantity, unit of measure, unit price and product identification codes (UPC, vendor part number, buyer item number). The ACK segment then provides the acknowledgment status for each individual line item, indicating whether that specific product was accepted, backordered, rejected or substituted. This line-level detail gives buyers granular visibility into exactly which items will ship.
EDI 855 Shipping Dates and Quantities
The DTM segment communicates estimated ship dates, scheduled delivery dates and promised delivery windows. These dates feed directly into the buyer’s inventory planning and warehouse scheduling systems. When a seller modifies the original delivery timeline, the DTM segment in the 855 document makes the change visible immediately so the buyer can adjust dock assignments and staffing plans.
Common EDI 855 ACK Codes
See how our platform generates and sends purchase order acknowledgments within your required timeframe.
EDI 855 in the Order-to-Cash Workflow
The 855 purchase order acknowledgment operates within a sequence of EDI transaction sets that automate the full order-to-cash cycle.
The process begins when a buyer sends an EDI 850 purchase order. The seller responds with an EDI 997 (Functional Acknowledgment) to confirm the transmission was received, followed by the EDI 855 to provide the substantive business response. If the buyer needs to modify the order based on the 855 response, they send an EDI 860 (Purchase Order Change Request). The seller may then respond with an EDI 865 (Purchase Order Change Acknowledgment) to confirm the revised terms.
Once the order is ready to ship, the seller transmits an EDI 856 (Advance Ship Notice) with shipment contents, packaging and tracking details. After delivery, the seller sends an EDI 810 invoice to request payment. The buyer closes the cycle with an EDI 820 (Payment Order/Remittance Advice).
Throughout this workflow, the EDI 855 serves as the critical validation step. Without it, the buyer has no confirmation that the seller received the order, can fulfill it or plans to ship on time. This gap creates downstream problems : inventory shortages, missed delivery windows and invoice reconciliation failures.
Benefits of EDI 855 for Buyers and Sellers
Implementing the EDI 855 purchase order acknowledgment delivers measurable advantages across the procurement process for both trading partners.
EDI 855 order visibility for buyers
The 855 transaction gives buyers immediate insight into order status. Instead of waiting days for a phone call or email confirmation, the buyer’s system receives a structured acknowledgment within hours of sending the purchase order. Many retailers require the EDI 855 within 24 to 48 hours of PO submission. This visibility enables proactive inventory management : if a supplier can only fulfill 50% of an order, the buyer knows immediately and can source the remaining quantity from another vendor. For drop ship operations, the 855 provides delivery status information that buyers share directly with end customers.
EDI 855 compliance and chargebacks
Many large retailers and distributors mandate the EDI 855 as a compliance requirement. Suppliers that fail to send timely, accurate purchase order acknowledgments risk chargebacks, deductions and damaged trading partner relationships. EDI automation ensures the 855 is generated and transmitted within the required timeframe, protecting the seller’s revenue and strengthening buyer confidence.
For sellers, the 855 also creates an auditable record of order acceptance. When invoice disputes arise months later, the purchase order acknowledgment proves exactly what was confirmed, at what quantities and at what prices.
EDI 855 X12 Format Specification
The EDI 855 follows the X12 standard published by ASC X12 under the EDI document standards framework. The most common version is 4010 VICS, though 5010 is also in active use.
Transaction structure — segment sequence
The transaction structure begins with ISA/GS envelope headers, followed by the ST segment (identifying the 855 transaction set), BAK (acknowledgment type, purchase order number and dates), CUR (currency code when applicable), REF (additional references), DTM (estimated ship and delivery dates), N1 loops (ship-to and bill-to party identification), PO1 loops (line item data with quantities, prices and product codes), ACK (line item acknowledgment status), and CTT (transaction totals). SE/GE/IEA trailers close the envelope.
The ACK segment is unique to the 855 and carries acknowledgment codes such as “IA” (item accepted), “IB” (item backordered), “IC” (item accepted with changes) and “IR” (item rejected). Each ACK segment can include revised quantities, dates and product substitutions at the line level.
Because the X12 855 allows optional segments and conditional data elements, working with an experienced EDI provider ensures correct mapping to each trading partner’s specific requirements and acknowledgment workflows.
Common EDI 855 Implementation Errors
Even established EDI programs encounter problems with the 855 purchase order acknowledgment. Recognizing these issues early prevents compliance failures and order processing delays.
Missing or delayed EDI 855 generation
A frequent challenge is that many ERP systems do not generate the EDI 855 automatically. Unlike the EDI 997, which is typically fully automated, the 855 often requires manual creation or custom workflow configuration. Sellers without a streamlined process for generating acknowledgments risk missing the 24-to-48-hour response window that most buyers require.
Data mismatches with the original EDI 850
Data mismatches between the 855 and the original EDI 850 also cause rejections. If the purchase order number, line item codes or UPC identifiers in the acknowledgment do not match the original order, the buyer’s system flags the 855 as invalid. Implementing validation rules that cross-check 855 data against the 850 before transmission eliminates most rejections.
Incomplete line item acknowledgments
Finally, incomplete line item acknowledgments create downstream confusion. If a seller acknowledges some line items but omits others, the buyer cannot determine whether the missing items were accepted, backordered or rejected. Every line item on the original purchase order should receive an explicit ACK status in the 855 response.
Our team helps you validate, map and automate your 855 implementation correctly from day one.
