ediverse

Type to search across standards, messages, tools and glossary.

ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

— 01

Foundations

— 02

Standards

— 03

Flagship messages

— 04

Tools

X12 860 — Purchase Order Change Request

The 860 modifies an already-issued 850. It is the right vehicle to add, remove, or adjust a line after the order has been recorded.

Purpose

Once an 850 has been issued and acknowledged with an 855, any change (quantity adjustment, delivery date change, ship-to swap, line add or remove) goes through an 860 rather than a fresh 850. The PO number stays the same; the 860 increments a version (often in BCH) that lets the supplier trace the sequence of changes.

On the ERP side, receiving an 860 fires an approval workflow at the supplier: if the change is compatible with the current order status (not yet picked, for example), it is integrated and acknowledged with an 865. Otherwise, the 865 carries a line-level reject code and the original commitment stands.

Envelope structure

The 860 travels in a PC functional group (Purchase Order Change). A didactic 860 modifying two lines:

x12 example-860.x12 
ISA*00*          *00*          *ZZ*ACMERETAIL    *ZZ*ACMEVENDOR    *260516*1100*U*00401*000000701*0*P*>~
GS*PC*ACMERETAIL*ACMEVENDOR*20260516*1100*1*X*004010~
ST*860*0001~
BCH*04*SA*PO78901*001*20260516**20260513~
REF*DP*0042~
DTM*002*20260524~
N1*BY*ACME RETAIL CO*92*0001~
POC*1*QC*1*EA*9.99**UP*012345678905~
POC*2*DI*5*EA*19.50**UP*012345678912~
CTT*2~
SE*10*0001~
GE*1*1~
IEA*1*000000701~

The BCH segment (Beginning Segment for Purchase Order Change) opens the transaction: function code (04 = Change), purchase type (SA = Stand-alone Order), original PO number, change sequence number, change date and original PO date. Each POC (Line Item Change) carries a change-type code (QC = Quantity Change, DI = Delete Item, NI = New Item, PC = Price Change…) and the updated quantity or price.

Common segments

  • Header — ST, BCH (Beginning Segment for PO Change), CUR, REF (references), FOB, DTM (modified dates).
  • Parties — N1 loop for Buyer, Ship To, Bill To if modified.
  • Changed lines — POC (Line Item Change) loop with PID, SAC (allowance/charge), SCH, DTM, TXI, REF.
  • Summary — CTT, AMT, SE.

When you'll see it

  • Retail — modifying a planned order after a forecast revision or store-level stock-out.
  • Manufacturing — late cancellation on an automotive call-off before the JIT window.
  • Distribution — splitting an order into two partial shipments with different dates.

Documentation

The code 860 and the name Purchase Order Change Request are public and listed on x12.org/products/transaction-sets. The complete list of POC01 change codes and their exact semantics live in the proprietary Implementation Guides (TR3); ediverse.io does not redistribute them.