EDI 865 PO Change Acknowledgment/Request: Seller Guide

The EDI 865 is how a supplier answers a change, or starts one. When a buyer sends an 860 Purchase Order Change, the 865 tells it which changes you accept, which you accept with a difference, and which you cannot meet. When nothing came from the buyer but your plan has changed, the same document carries your proposal. Without it, a change is one-sided, and the shipment drifts away from what the buyer expects to receive.

This guide covers the two jobs the 865 does, its segments, two live examples (a reply to an 860 and a seller-initiated change), how it compares with the 855, 860 and 870, and the errors that leave buyer and supplier with different versions of the same order.

What Is an EDI 865?

An EDI 865 is the Purchase Order Change Acknowledgment/Request (Seller Initiated) transaction set defined by the ASC X12 standards body. A seller uses it to acknowledge a buyer's change to a purchase order, or to request a change of its own, at header or line level. It travels in functional group CA (the value in GS01).

Authoritative references for 865 work:

• The X12 transaction set catalog lists the 865 alongside the 860 it answers
• The published 004010 865 structure shows the BCA header and the POC loop, with an ACK loop inside each line
• The BCA segment definition and the POC02 change code list define the elements and codes in this guide
• GS1 US governs the UPC and GTIN identifiers on each changed line
• Each buyer's 865 guide decides whether it wants an 865 at all, which purpose and acknowledgment codes it accepts, and whether it takes seller-initiated changes

Who sends it? The supplier (seller).

When is it sent? In reply to a buyer's 860, within the deadline in the buyer's guide, or on the supplier's own initiative when an open order has to change after the 855 went out.

Why does it matter? A change is only reliable when both sides agree to it. An 860 you never answered, or a backorder you only mentioned by email, leaves the buyer planning around an order you are not going to ship.

The Two Jobs of the 865

Change acknowledgment. The buyer sent an 860. You reply with an 865 that references the same PO and change sequence, repeats each changed line in a POC, and gives your answer in an ACK under it: accepted as changed, accepted with a different quantity or date, or rejected.

Seller-initiated change request. Nothing came from the buyer, but you need to change the order: a ship date slips, an item is replaced, a quantity is short. You send an 865 with the purpose code for a seller-initiated change and a POC per affected line. The buyer accepts or rejects it, often by sending an 860 that confirms the change, or by the method its guide sets out.

BCA01 tells the buyer which job this 865 is doing.

Interactive Example: Reply to a Buyer's 860

Retailer Harbor Home sent an 860 against purchase order 4500087321, increasing line 2 from 6 rugs to 10 and adding a line 4 of 18 wool throws (the first example in the 860 guide). Supplier Cedarline replies:

• BCA01 = 06 (confirmation) and BCA02 = AC (acknowledged with detail and change), because one line is not accepted exactly as requested. BCA05 repeats the buyer's change sequence 1, and BCA06 the PO date.
• Line 2 echoes the buyer's POC (QI, 6 to 10) and its ACK accepts all 10 (IA) to ship November 3.
• Line 4 echoes the added line (AI, 18 throws) and its ACK accepts only 12 (IQ, quantity changed) to ship November 10.

Interactive Example: Seller-Initiated Change

On purchase order 4500087412, Cedarline needs to change two lines before anything ships. BCA01 is 19 (seller initiated change) and BCA02 is left out, because there is nothing from the buyer to acknowledge.

• Line 1's ship date moves to December 1 (POC02 = RS, reschedule, with DTM*068 current scheduled ship date in the line's loop).
• Line 2 offers a replacement item (RE): the white ceramic vase in place of the one ordered, at the same price, with the reason in PID.

Some buyers require BCA02 on every 865, or a particular purpose code for seller-initiated changes. Check its guide before you send the first one.

865 Structure at a Glance

Key Segments Explained

BCA: Beginning Segment for Purchase Order Change Acknowledgment

BCA*06*AC*4500087321**1*20261020~

POC: Line Item Change

POC*4*AI*0*18*EA*14.50**UP*085519001236*VN*CL-THROW-WOL~

The POC layout is the same as in the 860: POC01 the PO line number, POC02 the change code, POC03 and POC04 the quantities, POC05 the unit, POC06 the price, and product ID pairs from POC08. When answering an 860, echo the buyer's POC for each line; when proposing your own change, use the code that describes it. The codes you will use most:

ACK: Line Item Acknowledgment

ACK*IQ*12*EA*068*20261110~

Inside the POC loop, ACK works exactly as on the 855: ACK01 the line status (IA accepted, IQ quantity changed, IP price changed, DR date rescheduled, IB backordered, IR rejected and others), ACK02 and ACK03 the quantity and unit, ACK04 a date qualifier such as 068 current schedule ship, and ACK05 the date. The loop repeats, so a line can be part accepted and part backordered.

Whether a buyer expects a rejection as POC02 = RC, as ACK01 = IR, or both, is a guide-level choice. Map exactly what it asks for.

EDI 865 vs 855, 860 and 870

The 870 reports; the 865 asks for agreement. If a line is simply running late, the buyer may only want an 870. If you need the buyer to accept a different item, quantity or price, that is an 865.

Where the 865 Sits in the Change Loop

1. 850 Purchase Order: buyer places the order.
2. 855 PO Acknowledgment: supplier confirms what will ship.
3. 860 PO Change: buyer changes the order.
4. 865: supplier accepts or rejects the change, or proposes its own.
5. 856 Ship Notice/ASN: supplier ships against the order as agreed.
6. 810 Invoice: billed at the agreed quantities and prices.

The 855 answers the order once. The 865 answers every change after that.

Common 865 Errors and How to Prevent Them

Paste any 865 into the EDI inspector to see each line's change and answer decoded, or diff it against the 860 with Compare EDI documents.

865 Implementation Checklist

• Ask each buyer whether it requires an 865 after an 860, and by when
• List the BCA01, BCA02, POC02 and ACK01 codes it accepts
• Confirm whether it accepts seller-initiated 865s, and how it answers them
• Confirm whether it wants every line restated or only the changed lines
• Map POC from the 860 as an echo, and generate ACK from your actual decision
• Decide who in your business approves a change you cannot fully meet
• Test acceptance, partial acceptance, rejection and a seller-initiated change

Handling Changes Cleanly With OrderSync

Change handling is where small suppliers lose track: an 860 lands in an EDI mailbox, a revised PDF arrives by email, and someone has to work out which open order each one touches before the warehouse picks it.

OrderSync reads inbound orders in any format, EDI 850s and 875s alongside PDFs, emails and spreadsheets, matches customers, items and units to your catalog, and outputs valid X12 or ERP data. See how it handles B2B order management, paste any 865 or 860 into the free EDI inspector, or book a 15-minute walkthrough to see your own orders processed.

Frequently Asked Questions