How to Acknowledge an EDI 860 with an EDI 865

A step-by-step guide to building an EDI 865 purchase order change acknowledgment, validating it against the buyer's 860, and testing the exchange.

Share

What an EDI 865 actually does

An EDI 865 is the seller's answer to a buyer's change request. It tells the buyer, line by line, whether you're accepting the change, rejecting it, accepting it with your own modifications, or proposing a change of your own. If you're on the supplier side and a retailer or OEM just sent you an EDI 860, the 865 purchase order change acknowledgment is how you close the loop.

It sits in a specific spot in the order lifecycle. Buyer sends 850 (Purchase Order), seller returns 997 (Functional Acknowledgment), seller sends 855 (PO Acknowledgment), buyer sends 860 (PO Change Request), seller returns 997 (acknowledging the 860), seller sends 865 (PO Change Acknowledgment). The 860 and 865 can also run the other direction: EDI 860 can also be used as a response to EDI 865, when a seller is requesting a change instead of the buyer, and partners can go back and forth between 860 and 865 documents until an agreement is reached.

One thing that trips up teams building this for the first time: the 865 is not universal. Not all trading partners require the 865. Some spec sheets route the acknowledgment through an EDI 855 PO Acknowledgement, indicating that they have received the request and will process it, and stop there. After receiving an EDI 860 transaction, sellers will occasionally be required to send back an EDI 865 Purchase Order Change Acknowledgement — the word "occasionally" is doing real work in that sentence. Check the partner's implementation guide before you build anything. Building a full 865 map for a partner who only wants a 997 and an 855 is wasted mapping effort.

What you need before you start

Before you touch a mapper, confirm the following:

  • The trading partner's implementation guide, stating explicitly whether 865 is required, optional, or replaced entirely by an 855.
  • The original inbound 850 and the 860 it's responding to, matched by PO number and change sequence.
  • A translator or integration platform capable of building the 865 transaction set — Cleo Integration Cloud, IBM Sterling B2B Integrator, TrueCommerce, SPS Commerce, or Orderful all support it.
  • A sandbox or test connection with the partner over AS2 or VAN, so your first 865 doesn't land in their production order system.
  • Confirmed X12 version alignment between you and the partner. A 4010 envelope hitting a partner expecting 5010 (or vice versa) is one of the most common reasons an 865 bounces on the first attempt.

Step-by-step: building and sending the 865

  1. Acknowledge receipt of the 860 with a 997 first. Don't skip this. Most partners expect it fast: most trading partners expect a 997 Functional Acknowledgment within 24 hours of receiving the 860. The 865 comes after, not instead of, the 997.
  2. Match the 860 to your internal order record. Tie it to PO number, the change order sequence number, and the original 850 date. If you can't match on all three, stop and escalate rather than guessing at which PO revision the buyer means.
  3. Route the proposed changes to the order desk or ERP owner. Someone with authority over price, quantity, and ship date needs to accept, reject, or counter-propose each line before you build the response. This isn't an EDI team decision.
  4. Populate the BCA beginning segment. This is the segment that sets intent for the whole document. Key fields: BCA02 (Acknowledgment Type), BCA03 (Purchase Order Number, which must tie back to the original order), BCA05 (Change Order Sequence Number), BCA09 (your own order number), and the date pair that causes the most confusion: BCA11 is the date of the purchase order change request, and BCA12 is the order change acknowledgment date. Get those two reversed and the buyer's system may file your response against the wrong change cycle.
  5. Pick the right BCA02 acknowledgment type code. This single code tells the buyer how to interpret everything that follows.
CodeMeaningTypical use case
ACAcknowledge – With Detail and ChangeYou're accepting the change but modifying some lines (price, quantity, date)
ADAcknowledge – With Detail, No ChangeFull acceptance, with line detail echoed back exactly as requested
AKAcknowledge – No Detail or ChangeBlanket acceptance, no line-by-line echo required by the partner
RJRejected – No DetailYou're rejecting the entire change request

Codes AC, AD and AK come straight from the implementation guide structure for BCA02, AC = Acknowledge – With Detail and Change, AD = Acknowledge – With Detail, No Change, AK = Acknowledge – No Detail or Change, while RJ = Rejected – No Detail appears in partner-specific guides. Confirm which subset your partner actually supports; not every trading partner implements all four.

  1. Build one POC loop per changed line item. The BCA sets the intent for the whole document, and each POC carries one line's change action: accept, reject, change quantity, substitute, or cancel. POC01 carries the line number from the original purchase order, and POC02 is the mandatory change or response type code — values like RZ (replace all values on the line) or AI (add a new item) show up depending on what the buyer requested. Attach a CTP segment wherever price changed, and a DTM segment wherever the ready or ship date moved. Inside each POC loop, add an ACK segment carrying the line-level status, since supporting segments such as CTP, DTM, and ACK allow the seller to detail pricing adjustments, effective dates, and acceptance status, with the seller using an ACK segment within the POC loop to indicate acceptance of the change.
  2. Close with CTT. The number of line items (CTT01) is the accumulation of the POC segments, and the hash total (CTT02) is the sum of the quantities ordered across each POC segment. If these don't reconcile with your POC count, your translator should flag it before transmission, not after.
  3. Validate against the partner's implementation guide. If you're in electronics distribution, the ECIA 865 guideline is the reference most distributors and manufacturers map against. Retail partners will have their own spec, usually heavier on N1 (party identification) and REF segments than the base X12 standard requires.
  4. Transmit and confirm the 997. Send the 865 inside a functional group, which per the X12 standard uses Functional Group CA. Confirm the buyer's system returns a clean 997 with no AK9 rejection codes.

How you know it worked

Three signals tell you the 865 landed correctly. First, the buyer's 997 comes back with no AK5 or AK9 error segments. Second, the buyer's ERP or vendor portal reflects the updated PO status matching the ACK code you sent. Third, you don't get another 860 proposing the exact same change you just addressed. If you do get another 860 repeating the same ask, that's a signal your 865 was read as a rejection or a counter-proposal, which is normal in a longer negotiation. Partners can go back and forth between 860 and 865 documents until an agreement is reached, so a second 860 isn't automatically a failure. It's just the next round.

Failure mode: sequence and date mismatches that cause silent drops

The most common real-world failure isn't a hard EDI syntax error. It's a semantic mismatch the translator doesn't catch: BCA11 or BCA12 populated with a date the buyer's system doesn't expect, or a POC loop missing for a line item that was present in the original 860. Neither of these breaks X12 syntax rules, so your outbound 865 transmits clean and gets a 997 back with no errors. The problem shows up downstream, when the buyer's EDI system auto-rejects the acknowledgment internally or simply never posts the status update to the order desk. Nobody gets an error message. The PO just sits in limbo until someone notices the ship date never updated.

The fix is a pre-transmission validation step, not a post-mortem. Before the 865 leaves your network, run a check that confirms every line present in the inbound 860 has a matching ACK status in the outbound 865. Log and alert on any gap rather than letting the transaction go out incomplete. It's worth remembering, too, that not every partner enforces this kind of strict validation on their end. Plenty of mid-size suppliers and distributors still fall back to phone calls or email when the 860/865 cycle isn't implemented on one side, and that's a maintenance reality you should flag to whoever owns the trading partner relationship, not just the EDI queue.

Where this fits into the bigger integration picture

Once a change is actually accepted, through an AD or AK acknowledgment, the updated ship date or quantity needs to propagate past the EDI layer. If your transport execution depends on that PO data, whether that's a carrier connectivity platform like Cargoson or a full TMS such as MercuryGate, Descartes, or Alpega, a stale ship date means a load tender gets built against numbers that no longer match the purchase order. The 865 is the authoritative record of what actually got agreed. Treat it as the trigger for downstream updates, not just a compliance document you file and forget.

Quick checklist before go-live with a new partner

  • Confirm the 865 is actually required for this partner, versus an 855-only or 997-only arrangement.
  • Confirm X12 version alignment (4010 vs 5010) on both sides before the first production transmission.
  • Test a full 850 → 860 → 865 → 997 cycle in sandbox, with every POC loop and ACK status checked manually.
  • Get written sign-off from the partner's EDI contact on at least one complete test cycle before flipping to production.

Run through one real change cycle end to end with a pilot partner before you roll this out across your supplier or customer base. It's the fastest way to find the gaps your implementation guide didn't mention.