X12 transaction code
X12 865 Purchase Order Change Acknowledgment
Stop Mapping. Start Trading.
- Standard
- X12
- Code
- 865
- Trading partners
- 1
Specification summary
X12 865 Purchase Order Change Acknowledgment at the element level
The X12 865 specification defines 21 segments carrying 72 data elements, 40 of which are mandatory.
- Segments
- 21
- Data elements
- 72
- Mandatory elements
- 40
| Segment | Elements | Mandatory |
|---|---|---|
| BCA | 4 | 3 |
| REF | 2 | 1 |
| N9 | 2 | 1 |
| MSG | 1 | 1 |
| POC | 12 | 1 |
| PID | 2 | 1 |
| ACK | 15 | 1 |
| DTM | 3 | 1 |
| CTT | 1 | 1 |
- Transaction Set Purpose Code
- Purchase Order Number
- Date
- Reference Identification Qualifier
- Free-Form Message Text
- Change or Response Type Code
- Item Description Type
- Line Item Status Code
Trading partners that support X12 865
1 partner, 1 channel. Click a channel for the full segment guideline.
Usage breakdown
Who trades X12 865 Purchase Order Change Acknowledgment
865 is used most heavily in automotive.
The 865 closes the loop on purchase order changes. In its acknowledgment role it is the seller's formal response to a buyer's 860 Purchase Order Change Request, stating per line whether each requested change is accepted, rejected, or modified. Trading partners require it so both order books reflect the same revised quantities, prices, and dates before fulfillment continues. The supplier (seller) sends the 865 to the buyer, typically in response to the buyer's 860 Purchase Order Change Request. A buyer submits an 860 change to an open purchase order and the supplier's order management system responds with an 865 stating the disposition of each requested change.
By industry
- automotive 1 channel
FAQ
X12 865 questions
What is X12 865 Purchase Order Change Acknowledgment?
X12 865 (Purchase Order Change Acknowledgment) is an EDI transaction set defined by ANSI ASC X12 for exchanging purchase order change acknowledgment between trading partners. It is one of over 300 X12 transaction sets used across retail, healthcare, manufacturing, and logistics. 1 Stacksync trading partner supports this code across 1 channel.
Which trading partners use X12 865?
1 Stacksync partner accepts X12 865: Ford Motor Company. Each partner has its own implementation guideline that Stacksync pre-validates before sending. Browse the full directory above.
How do I integrate X12 865 with my ERP?
Stacksync handles the full X12 865 integration: partner channel certification (AS2, VAN, FTP), transaction-set mapping per the trading partner's implementation guide, translation to your ERP's native data model, and real-time delivery. Typical time from kickoff to production is 3 to 10 business days for a single partner connection.
Ready to automate your EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
