EDI 865 vs EDI 860 and 855: Which Transaction Should Your Supply Chain Use?

The ANSI X12 purchase order change acknowledgment transaction.

EDI 865 The ANSI X12 purchase order change acknowledgment transaction. Understanding how the 865 differs from other PO transactions (notably the 860 and 855) helps trading partners pick the correct message for each step of the order lifecycle and avoid process gaps.

In practical terms the three messages play distinct roles. The buyer or an upstream system initiates change requests with an 860 (or other negotiated channels), the supplier uses an 865 to confirm acceptance or rejection of that change, and the 855 is used earlier in the lifecycle to acknowledge receipt of an original purchase order. Choosing the wrong transaction creates ambiguity: shipping against an unacknowledged change leads to disputes and inventory errors.

High-Level Comparison

• EDI 855: Acknowledges receipt of a new purchase order and optionally flags acceptances or exceptions to the original terms.
• EDI 860: Used by the buyer to request an amendment to an existing PO — quantity changes, date shifts, cancellations, or item substitutions.
• EDI 865: The supplier’s formal acceptance, partial acceptance, or rejection of a change request; it closes the loop after an 860.

Use Cases That Distinguish Them

If a buyer sends a new PO and the supplier needs to confirm lead times or pricing, an 855 is the common reply. If the buyer later needs to alter that PO because of demand changes, they issue an 860. The supplier then evaluates feasibility and replies with an 865 to tell the buyer whether the change will be honored and under what conditions.

Operational Impact Of Using The Correct Transaction

Using the correct message affects automated workflows. An 855 can trigger initial pick-and-pack scheduling. An 860 typically creates change requests in ERP/WMS for review. An 865 should trigger final updates: new allocation, updated ASN timing, and revised appointment windows. Treating the 865 as authoritative avoids processing a change before the supplier has formally agreed.

How To Decide Which To Use

• New Order: Expect an 855 if you require supplier confirmation after issuing a PO.
• Change Initiated By Buyer: Use an 860 to request the amendment; do not assume the supplier accepts the change until you receive an 865.
• Supplier Response Needed: Wait for an 865 when changes affect fulfillment timing, quantities, or routing.

Practical Example Comparing Flows

A national home goods retailer submits a PO for 500 couches. The supplier sends an 855 acknowledging the PO and confirming availability for shipment in two weeks. Two days later the retailer requests an acceleration for 300 units; it issues an 860. The supplier can only accelerate 200 units—so it returns an EDI 865 indicating acceptance of 200 accelerated units, partial acceptance of the balance, and a proposed alternate ship date for the remaining 300. The retailer’s order management system uses the 865 to reallocate stock and schedule two separate inbound appointments.

Mistakes To Avoid

A common error is assuming an 855 covers later changes. It does not. Another mistake is automating shipment upon receipt of an 860 without awaiting the supplier’s 865 — this can result in rejected shipments and chargebacks. Ensure your integration logic distinguishes message types and enforces an approval step when an 865 signals a partial acceptance or rejection.

Recommendations For Trading Partners

• Define SLA: Agree on turnaround times for 855s and 865s so buyers can plan allocation and carriers can book appointments with confidence.
• Standardize Codes: Use mutually agreed status and reason codes for partial acceptance and rejections to avoid manual interpretation.
• Automation Rules: Configure WMS/ERP to block shipment changes until an 865 is received for any active 860 changes.

In short, the EDI 865 is the supplier’s committed response to change requests; while the 855 and 860 serve other points in the order lifecycle, the 865 is the definitive message your supply chain should wait for before executing amended fulfillment plans.