X12 transaction code
X12 865 Purchase Order Change Acknowledgment
The X12 865 Purchase Order Change Acknowledgment is the name one trading partner uses for the X12 865 Purchase Order Change Acknowledgment/Request (Seller Initiated) transaction set, used when a seller acknowledges or proposes an order change. The supplier (seller) sends the 865 to the buyer, typically in response to the buyer's 860 Purchase Order Change Request.
- Standard
- X12
- Code
- 865
- Partner references
- 1
At a glance
X12 865 Purchase Order Change Acknowledgment at a glance
What the 865 carries, who sends it to whom, when it goes out, and the segments trading partners list for it.
This page lists the partner reference that name the 865 this way. The full EDI 865 guide is on the X12 865 Purchase Order Change Acknowledgment/Request (Seller Initiated) page.
| Document | X12 865 Purchase Order Change Acknowledgment |
|---|---|
| Business record | Seller order-change response or request |
| Who sends it to whom | The supplier (seller) sends the 865 to the buyer, typically in response to the buyer's 860 Purchase Order Change Request. |
| When it is sent | 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. |
| Match on | Original purchase order, change reference and affected line |
| Partner references | 1 trading partner in this directory |
| Related documents | X12 850 Purchase Order, X12 860 Purchase Order Change Request (Buyer Initiated), X12 855 Purchase Order Acknowledgment |
Key segments in the X12 865 Purchase Order Change Acknowledgment
The business segments in the one partner document reference listed below. The table leaves out envelope segments (ISA, GS, ST, SE, GE, IEA). Your partner guide sets which segments and elements your account must send.
| Segment | Name | Purpose | Partner references |
|---|---|---|---|
| BCA | Beginning Segment (Order Change Request Acknowledgment) | To indicate the beginning of the purchase order change acknowledgment transaction set and transmit identifying numbers and dates. | 1 of 1 |
| N1 | Name | To identify a party by type of organization, name and code. | 1 of 1 |
| POC | Line Item Change | To specify changes to a line item. | 1 of 1 |
| CTT | Transaction Totals | To transmit a hash total for a specific element in the transaction set. | 1 of 1 |
Stacksync connects EDI documents such as the X12 865 to your ERP, CRM and databases with two-way sync. Read the EDI overview, check pricing and security, or book a demo to walk through your partner guide.
Implementation guide
X12 865 mapping and validation
X12 865 Purchase Order Change Acknowledgment is used when a seller acknowledges or proposes an order change. Preserve original purchase order, change reference and affected line so the seller order-change response or request in your business system stays connected to the original document.
Use the version and implementation guide agreed with your trading partner to confirm required fields and responses.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| Match the business record | seller order-change response or request original purchase order, change reference and affected line |
|
| Update the receiving system | Processing the seller order-change response or request ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the seller order-change response or request Original document reference and matching response |
|
How the related documents differ
Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.
- X12 850 Purchase Order
purchase order or sales order: a buyer places an order.
- X12 860 Purchase Order Change Request (Buyer Initiated)
buyer order-change request: a buyer changes a previously issued order.
- X12 855 Purchase Order Acknowledgment
purchase-order response: a seller responds to an order.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when a seller acknowledges or proposes an order change. Name the operational owner of the seller order-change response or request and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map original purchase order, change reference and affected line. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and partner guide. Preserve the source reference alongside any new destination identifier.
-
Test failures before launch
Run the failure cases in the mapping table against realistic seller order-change response or request data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.
-
Track every document to completion
Record transport delivery and document validation separately from successful seller order-change response or request processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 865 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic seller order-change response or request data.
- Each submitted document can be traced through delivery, validation and processing in the receiving system.
- Your team knows how to investigate and recover a rejected or timed-out seller order-change response or request without processing it twice.
Document structure
X12 865 Purchase Order Change Acknowledgment at the element level
The X12 865 reference contains 21 segment entries and 72 data elements; 40 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- 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
Find your trading partner for X12 865
1 partner, 1 channel. Choose a channel to inspect its listed document reference and implementation context.
Catalog breakdown
Where X12 865 Purchase Order Change Acknowledgment appears in this catalog
The largest groups of classified 865 catalog entries are in automotive.
By industry
- automotive 1 channel
FAQ
X12 865 Purchase Order Change Acknowledgment questions
What is the X12 865 Purchase Order Change Acknowledgment?
The X12 865 Purchase Order Change Acknowledgment is the name one trading partner uses for the X12 865 Purchase Order Change Acknowledgment/Request (Seller Initiated) transaction set. Trading partners use it when a seller acknowledges or proposes an order change. It carries the data for the seller order-change response or request, and your system matches it on original purchase order, change reference and affected line.
Who sends the X12 865 Purchase Order Change Acknowledgment and who receives it?
The supplier (seller) sends the 865 to the buyer, typically in response to the buyer's 860 Purchase Order Change Request. Your trading partner agreement confirms the direction and version for your account.
When is the X12 865 Purchase Order Change Acknowledgment sent?
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. Your partner guide sets any deadline or schedule for the document.
What are the key segments in the X12 865 Purchase Order Change Acknowledgment?
The one partner document reference listed here includes BCA (Beginning Segment (Order Change Request Acknowledgment)), N1 (Name), POC (Line Item Change), CTT (Transaction Totals). Each partner guide sets which segments and elements your account must send.
What is the difference between 865 and 850?
The 850 is the original purchase order. The 865 comes from the supplier: it answers a buyer's 860 change or proposes a change to the order itself.
What should I map for X12 865?
Start with original purchase order, change reference and affected line and the target seller order-change response or request. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.
How should I test 865 error handling?
Distinguish a seller-proposed change from acceptance of a buyer-requested change. Reject an outdated revision that would overwrite a later agreed quantity. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
Which partners list X12 865?
The directory on this page links 1 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires.
Connect EDI to your business systems
See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.
