EDI 865 - Purchase Order Change Acknowledgment
The EDI 865 is the supplier's formal response to a buyer's 860 Purchase Order Change Request - confirming which changes are accepted, proposing counter-changes, or documenting rejections. It closes the loop on every order modification.
✦ What It Does
The EDI 865 Purchase Order Change Acknowledgment is the supplier-initiated counterpart to the buyer-initiated 860. Where the 855 acknowledges the original 850 PO, the 865 acknowledges the 860 change request. Together, 850→855→860→865 form a complete, documented order management conversation where both parties have a confirmed, mutually-agreed record of the order's current state at every step.
The 865 structure closely parallels the 855 acknowledgment structure. It opens with a BAK segment referencing both the original PO number and the change request being acknowledged. Line-level PO1 loops echo the changed lines, and ACK segments within those loops communicate the supplier's line-level response: accepted (IA), accepted with modifications (IC), rejected (IB), back-ordered (IP), or a revised ship date proposed (IS). The 865 may also propose counter-changes - for example, accepting a quantity decrease to 8 units when the buyer's 860 requested a decrease to 5, because the supplier has already committed production to 8.
From a compliance standpoint, the 865 is underutilized by many suppliers - they process the 860 and update their systems but never send the 865 acknowledgment. This creates an undocumented state where the buyer's system may still show the 860 as "pending acknowledgment" while the supplier believes the change is accepted. Retailers that mandate 865 responses (Target and several grocery chains) will generate compliance exceptions for missing 865s just as they do for missing 855s. Implementing 865 transmissions closes a common gap in order management audit trails.
⚡ When It's Triggered
- A supplier receives an 860 with a quantity decrease and their order management system auto-generates an 865 confirming acceptance of the reduced quantity before any warehouse activity begins on the order.
- An 860 arrives requesting cancellation of a line, but the supplier has already picked and staged the goods - the 865 is sent with a rejection code and a MSG segment explaining that fulfillment is already in progress.
- A buyer's 860 changes the delivery date to two days earlier than the supplier can accommodate - the 865 proposes an intermediate date that works for both parties, triggering a negotiation before the ship date arrives.
- A price change on an 860 cannot be accepted because it conflicts with the supplier's current cost structure - the 865 rejects the PI change and documents the supplier's position, creating a record for AP dispute prevention.
- A supplier's automated 865 generation is triggered as part of their order management workflow: 860 received → ATP check → inventory update → 865 transmitted, all within minutes of the 860's arrival.
Who Uses EDI 865
Retail Suppliers
Retail suppliers who receive frequent 860s - especially during seasonal ramp-ups and promotional periods - benefit most from automated 865 generation. High-volume suppliers at Walmart or Target may process dozens of 860s daily; without automated 865 responses, their compliance teams face hours of manual acknowledgment work and a growing backlog of unconfirmed changes that can cause fulfillment confusion.
Manufacturing
In industrial manufacturing, the 865 is particularly valuable when a buyer's 860 requests changes after production has started. The 865 documents the supplier's constraints clearly - "we've already run 500 units; we can cancel the remaining 200 but not the first 500" - creating a defensible record if the buyer later takes a deduction for receiving a different quantity than the 860 requested.
Distribution
Distributors who receive 860s from their retail customers and generate their own upstream 860s to manufacturers use 865s to cascade change confirmations back through the supply chain. When a manufacturer responds with a counter-proposal via 865, the distributor can either accept it and transmit their own 865 to the retailer or negotiate further - keeping all parties in sync through documented EDI rather than unstructured email or phone.
Grocery Suppliers
Grocery trading partners with active 860/865 programs maintain cleaner promotional order histories. When a promotional quantity changes three times before the event, a proper 860/865 sequence creates an unambiguous record of the final agreed-upon quantity - which matters when disputes arise about whether an apparent short-ship was actually a supplier failure or a buyer change that wasn't communicated clearly.
Key Segments & Data Elements
BAK: Beginning Acknowledgment
Opens the 865 with dual references. BAK01 = transaction set purpose code (00 = original). BAK02 = acknowledgment type: AC (acknowledged), AD (acknowledged with detail changes), AK (acknowledged with changes), RJ (rejected). BAK03 = original PO number (from the 850's BEG03). BAK05 = date of acknowledgment. BAK06 = change request sequence number (from the 860's BCH06, establishing which version of the 860 this 865 is responding to).
PO1: Line Item
Each changed line from the 860 appears as a PO1 loop in the 865. PO101 = original line number from the 850. PO102 = the supplier's accepted quantity (which may differ from both the 850 original and the 860 change request if the supplier is proposing a counter-quantity). PO104 = accepted price. Product identifiers in PO1 echo those from the original 850 so the buyer's system can unambiguously match the line.
ACK: Line Item Acknowledgment
Carries the per-line status code. ACK01 codes: IA = item accepted as changed, IB = item not accepted (change rejected, original PO terms stand), IC = item accepted with further modifications from supplier, ID = item not available, IP = item back-ordered. ACK02 = acknowledged quantity. ACK05/06 = proposed ship date when the supplier is accepting the change but proposing a different timeline than the 860 requested.
REF: Reference to Change Request
REF segments explicitly tie the 865 to the originating documents. REF-CO = contract reference (original blanket PO). REF-PO = original 850 PO number. An additional REF with qualifier CR = change request number, carrying the BCH06 value from the 860 being acknowledged. This tri-level referencing (850 PO, 860 change, 865 ack) creates the complete change history that audit teams and deduction dispute teams rely on.
DTM: Confirmed Dates
When the supplier is accepting the 860's date change, DTM segments in the 865 confirm the new dates. DTM010 = confirmed ship date. DTM002 = confirmed delivery date. When the supplier is counter-proposing dates, these DTM values will differ from the DTM values in the 860 - the buyer must then either issue a second 860 accepting the counter-proposal or negotiate further.
MSG: Message Text
Free-form explanation segment used when a rejection or modification requires context beyond the code-based ACK status. Common uses: "Production already committed - earliest cancel date is [date]", "Price change requires VP approval, pending review", "Cannot accept DC reassignment - carrier contract specifies original DC". MSG content routes to the buyer's buyer/planner for manual review and action.
Related Transaction Sets
Purchase Order Change Request
The 860 that the 865 responds to. Every 865 must reference the BCH06 change request sequence number from the 860 it is acknowledging. If multiple 860s have been sent against the same PO, the sequence number tells the buyer's system which change version has been acknowledged - preventing confusion when changes arrive in rapid succession.
Purchase Order
The original PO that is the foundation of the entire 850→855→860→865 conversation. The 865's BAK03 carries this PO number, and the buyer's OMS uses it to update the order's current agreed-upon state. After a 865 is processed with AC status, the OMS treats the 860 changes as confirmed and updates the order accordingly.
Purchase Order Acknowledgment
The 855 acknowledged the original 850; the 865 acknowledges changes to that acknowledged order. Taken together, they represent the complete supplier-side acknowledgment record for the order's lifetime. When disputing a deduction, suppliers who can present both 855 and 865 documents have significantly stronger evidence than those with only informal communication records.
Need Help with EDI 865?
Better EDI handles 865 mapping, testing, and trading partner certification so you don't have to.
Talk to an EDI Expert