--- title: "EDI 865 PO Change Acknowledgment/Request | X12 | Stacksync" description: "EDI 865 is the PO change acknowledgment, used when a seller acknowledges or proposes an order change. See key segments (BCA, REF, POC) and mapping checks." canonical: https://www.stacksync.com/edi/x12/865-purchase-order-change-acknowledgment-request-seller-initiated last_modified: 2026-09-29 --- X12 transaction code # EDI 865 Purchase Order Change Acknowledgment/Request (Seller Initiated) (X12 865) > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md EDI 865 is the PO change acknowledgment, the X12 Purchase Order Change Acknowledgment/Request (Seller Initiated) transaction set, used when a seller acknowledges or proposes an order change. The supplier sends the 865 to the buyer unprompted, to request or announce changes to a purchase order the buyer placed earlier. Standard X12 Code 865 Partner references 12 [Book an EDI demo](https://www.stacksync.com/book-a-demo) [← All trading partners](https://www.stacksync.com/edi) At a glance ## EDI 865 at a glance What the 865 carries, who sends it to whom, when it goes out, and the segments trading partners list for it. **X12 865 Purchase Order Change Acknowledgment/Request (Seller Initiated) summary** | | | | --- | --- | | Document | X12 865 Purchase Order Change Acknowledgment/Request (Seller Initiated) | | Business record | Seller order-change response or request | | Who sends it to whom | The supplier sends the 865 to the buyer unprompted, to request or announce changes to a purchase order the buyer placed earlier. | | When it is sent | A supplier determines it cannot fulfill an open order as written, for example a stockout, a price update, or a slipped ship date, and issues an 865 proposing the change. | | Match on | Original purchase order, change reference and affected line | | Partner references | 12 trading partners in this directory | | Related documents | [X12 850 Purchase Order](https://www.stacksync.com/edi/x12/850-purchase-order), [X12 860 Purchase Order Change Request (Buyer Initiated)](https://www.stacksync.com/edi/x12/860-purchase-order-change-request-buyer-initiated), [X12 855 Purchase Order Acknowledgment](https://www.stacksync.com/edi/x12/855-purchase-order-acknowledgment) | ### Key segments in an EDI 865 The business segments that appear in at least half of the 12 partner document references listed below, most common first. 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 for Purchase Order Change Acknowledgment | To indicate the beginning of the Purchase Order Change Acknowledgment Transaction Set and transmit identifying numbers and dates. | 12 of 12 | | REF | Reference Identification | To specify identifying information. | 12 of 12 | | POC | Line Item Change | To specify changes to a line item. | 8 of 12 | | CTT | Transaction Totals | To transmit a hash total for a specific element in the transaction set. | 8 of 12 | | N9 | Reference Identification | To transmit identifying information as specified by the Reference Identification Qualifier. | 6 of 12 | | ACK | Line Item Acknowledgment | To acknowledge the ordered quantities and specify the ready date for a specific line item. | 6 of 12 | Stacksync connects EDI documents such as the X12 865 to your ERP, CRM and databases with two-way sync. Read the [EDI overview](https://www.stacksync.com/edi), check [pricing](https://www.stacksync.com/pricing) and [security](https://www.stacksync.com/security), or [book a demo](https://www.stacksync.com/book-a-demo) to walk through your partner guide. Implementation guide ## X12 865 mapping and validation X12 865 Purchase Order Change Acknowledgment/Request (Seller Initiated) 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. **Map records and test the business result** | 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 | Define which combination of original purchase order, change reference and affected line identifies one business record, its lines and any later revision. | | Update the receiving system | **Processing the seller order-change response or request** ID assigned by the receiving system and processing result | Distinguish a seller-proposed change from acceptance of a buyer-requested change. Reject an outdated revision that would overwrite a later agreed quantity. | | Check the processing result | **Processing status for the seller order-change response or request** Original document reference and matching response | Reconcile the seller order-change response or request with the source after a timeout before sending it again. A lost response can occur after the destination has already processed the document. | ### 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](https://www.stacksync.com/edi/x12/850-purchase-order) **purchase order or sales order:** a buyer places an order. - [X12 860 Purchase Order Change Request (Buyer Initiated)](https://www.stacksync.com/edi/x12/860-purchase-order-change-request-buyer-initiated) **buyer order-change request:** a buyer changes a previously issued order. - [X12 855 Purchase Order Acknowledgment](https://www.stacksync.com/edi/x12/855-purchase-order-acknowledgment) **purchase-order response:** a seller responds to an order. ### Implementation steps 1. #### 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. 2. #### 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. 3. #### 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. 4. #### 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. ### Related documents and resources - [X12 850 Purchase Order](https://www.stacksync.com/edi/x12/850-purchase-order) - [X12 860 Purchase Order Change Request (Buyer Initiated)](https://www.stacksync.com/edi/x12/860-purchase-order-change-request-buyer-initiated) - [X12 855 Purchase Order Acknowledgment](https://www.stacksync.com/edi/x12/855-purchase-order-acknowledgment) - [Field mapping workbook](https://www.stacksync.com/blog/two-way-sync-field-mapping-workbook) - [Production readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) **Sources.** Sources reviewed 2026-09-15. - [X12 transaction-set directory](https://x12.org/products/transaction-sets) - [RFC 4130: AS2 and message receipts](https://www.rfc-editor.org/info/rfc4130/) Document structure ## X12 865 Purchase Order Change Acknowledgment/Request (Seller Initiated) 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 **Segments with elements marked mandatory in this reference** | 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 | Key identifiers in 865 - 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 12 partners, 12 channels. Choose a channel to inspect its listed document reference and implementation context. - [ASUSTeK Computer Inc. (dba ASUS)](https://www.stacksync.com/edi/asus) [ASUS](https://www.stacksync.com/edi/asus/asus/x12-865-purchase-order-change-acknowledgment-request-seller-initiated) - [Bealls Inc.](https://www.stacksync.com/edi/bealls-inc) [Bealls Inc (Temporary)](https://www.stacksync.com/edi/bealls-inc/bealls-inc-temporary/x12-865-purchase-order-change-acknowledgment-request-seller-initiated) - [Bluestem Brands](https://www.stacksync.com/edi/bluestem-brands-inc) [Bluestem Brands, Inc. (via SPS Commerce)](https://www.stacksync.com/edi/bluestem-brands-inc/bluestem-brands-inc-via-sps-commerce/x12-865-purchase-order-change-acknowledgment-request-seller-initiated) - [Google](https://www.stacksync.com/edi/google) [Google](https://www.stacksync.com/edi/google/google/x12-865-purchase-order-change-acknowledgment-request-seller-initiated) - [MidwayUSA](https://www.stacksync.com/edi/midwayusa) [MidwayUSA (via SPS Commerce)](https://www.stacksync.com/edi/midwayusa/midwayusa-via-sps-commerce/x12-865-purchase-order-change-acknowledgment-request-seller-initiated) - [MSC Industrial Supply Co.](https://www.stacksync.com/edi/msc-industrial-supply) [MSC Industrial Supply (via SPS Commerce)](https://www.stacksync.com/edi/msc-industrial-supply/msc-industrial-supply-via-sps-commerce/x12-865-purchase-order-change-acknowledgment-request-seller-initiated) - [QVC Group (dba Cornerstone Brands Inc)](https://www.stacksync.com/edi/garnet-hill) [Garnet Hill (via SPS Commerce)](https://www.stacksync.com/edi/garnet-hill/garnet-hill-via-sps-commerce/x12-865-purchase-order-change-acknowledgment-request-seller-initiated) - [Sportsman's Guide](https://www.stacksync.com/edi/sportsmans-guide) [Sportsman's Guide (via SPS Commerce)](https://www.stacksync.com/edi/sportsmans-guide/sportsman-s-guide-via-sps-commerce/x12-865-purchase-order-change-acknowledgment-request-seller-initiated) - [Target](https://www.stacksync.com/edi/target) [Target Direct Vendor Ship](https://www.stacksync.com/edi/target/target-direct-vendor-ship/x12-865-purchase-order-change-acknowledgment-request-seller-initiated) - [UPS](https://www.stacksync.com/edi/ups) [UPS Plus](https://www.stacksync.com/edi/ups/ups-plus/x12-865-purchase-order-change-acknowledgment-request-seller-initiated) - [Wayfair LLC](https://www.stacksync.com/edi/wayfair-llc) [Wayfair](https://www.stacksync.com/edi/wayfair-llc/wayfair/x12-865-purchase-order-change-acknowledgment-request-seller-initiated) - [Williams Sonoma](https://www.stacksync.com/edi/williams-sonoma) [Williams Sonoma via SPS](https://www.stacksync.com/edi/williams-sonoma/williams-sonoma-via-sps/x12-865-purchase-order-change-acknowledgment-request-seller-initiated) Catalog breakdown ## Where X12 865 Purchase Order Change Acknowledgment/Request (Seller Initiated) appears in this catalog The largest groups of classified 865 catalog entries are in retail, electronics & technology and furniture & home. ### By industry - retail 3 channels - electronics & technology 2 channels - furniture & home 2 channels - e-commerce & marketplaces 2 channels - manufacturing & industrial 1 channel - logistics & transport 1 channel ### By network - SPS Commerce 6 channels Partner entries with the most listed channels - [ASUSTeK Computer Inc. (dba ASUS)](https://www.stacksync.com/edi/asus) - [Bealls Inc.](https://www.stacksync.com/edi/bealls-inc) - [Bluestem Brands](https://www.stacksync.com/edi/bluestem-brands-inc) - [Google](https://www.stacksync.com/edi/google) - [MidwayUSA](https://www.stacksync.com/edi/midwayusa) - [MSC Industrial Supply Co.](https://www.stacksync.com/edi/msc-industrial-supply) - [QVC Group (dba Cornerstone Brands Inc)](https://www.stacksync.com/edi/garnet-hill) - [Sportsman's Guide](https://www.stacksync.com/edi/sportsmans-guide) FAQ ## EDI 865 questions ### What is an EDI 865? EDI 865 is the PO change acknowledgment, the X12 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 an EDI 865 and who receives it? The supplier sends the 865 to the buyer unprompted, to request or announce changes to a purchase order the buyer placed earlier. Your trading partner agreement confirms the direction and version for your account. ### When is an EDI 865 sent? A supplier determines it cannot fulfill an open order as written, for example a stockout, a price update, or a slipped ship date, and issues an 865 proposing the change. Your partner guide sets any deadline or schedule for the document. ### What are the key segments in an EDI 865? Across 12 partner document references listed here, the business segments that appear most often include BCA (Beginning Segment for Purchase Order Change Acknowledgment), REF (Reference Identification), POC (Line Item Change), CTT (Transaction Totals), N9 (Reference Identification), ACK (Line Item Acknowledgment). Each partner guide sets which segments and elements your account must send. ### What is the difference between EDI 865 and EDI 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 12 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. [Book an EDI demo](https://www.stacksync.com/book-a-demo) [Explore the EDI platform](https://www.stacksync.com/edi)