--- title: "EDI 849 Response to Product Transfer Adjustment | Stacksync" description: "EDI 849 is the X12 Response to Product Transfer Account Adjustment, used when a product-transfer adjustment is accepted or disputed." canonical: https://www.stacksync.com/edi/x12/849-response-to-product-transfer-account-adjustment last_modified: 2026-09-29 --- X12 transaction code # EDI 849 Response to Product Transfer Account Adjustment (X12 849) > 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 849 is the X12 Response to Product Transfer Account Adjustment transaction set, used when a product-transfer adjustment is accepted or disputed. The manufacturer, or its chargeback processing agent, sends the 849 back to the distributor or wholesaler that submitted the 844 claim. Standard X12 Code 849 Partner references 5 [Book an EDI demo](https://www.stacksync.com/book-a-demo) [← All trading partners](https://www.stacksync.com/edi) At a glance ## EDI 849 at a glance What the 849 carries, who sends it to whom, when it goes out, and the segments trading partners list for it. **X12 849 Response to Product Transfer Account Adjustment summary** | | | | --- | --- | | Document | X12 849 Response to Product Transfer Account Adjustment | | Business record | Adjustment claim response | | Who sends it to whom | The manufacturer, or its chargeback processing agent, sends the 849 back to the distributor or wholesaler that submitted the 844 claim. | | When it is sent | A manufacturer finishes validating a received 844 chargeback claim against its contract, pricing, and customer-eligibility records and issues the disposition. | | Match on | Original claim, response line and authorized amount | | Partner references | 5 trading partners in this directory | | Related documents | [X12 844 Product Transfer Account Adjustment](https://www.stacksync.com/edi/x12/844-product-transfer-account-adjustment), [X12 845 Price Authorization Acknowledgment/Status](https://www.stacksync.com/edi/x12/845-price-authorization-acknowledgment-status) | ### Key segments in an EDI 849 The business segments that appear in at least half of the 5 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 | | --- | --- | --- | --- | | BRC | Beginning Segment for Response to Product Transfer Account Adjustment | To identify the beginning of a Response to Product Transfer Account Adjustment Transaction Set. | 5 of 5 | | N1 | Name | To identify a party by type of organization, name, and code. | 5 of 5 | | CON | Contract Number Detail | To specify contract or reference number and status. | 5 of 5 | | PAD | Product Adjustment Detail | To specify the product transfer type, and/or line item number. | 5 of 5 | | CTT | Transaction Totals | To transmit a hash total for a specific element in the transaction set. | 5 of 5 | | AMT | Monetary Amount | To indicate the total monetary amount. | 5 of 5 | | LIN | Item Identification | To specify basic item identification data. | 5 of 5 | | AAA | Request Validation | To specify the validity of the request and indicate follow-up action authorized. | 5 of 5 | | UIT | Unit Detail | To specify item unit data. | 5 of 5 | | QTY | Quantity | To specify quantity information. | 5 of 5 | Stacksync connects EDI documents such as the X12 849 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 849 mapping and validation X12 849 Response to Product Transfer Account Adjustment is used when a product-transfer adjustment is accepted or disputed. Preserve original claim, response line and authorized amount so the adjustment claim response 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 | **adjustment claim response** original claim, response line and authorized amount | Define which combination of original claim, response line and authorized amount identifies one business record, its lines and any later revision. | | Update the receiving system | **Processing the adjustment claim response** ID assigned by the receiving system and processing result | Match partial approval to the submitted claim lines. Test a repeated response and prevent a second credit from being posted. | | Check the processing result | **Processing status for the adjustment claim response** Original document reference and matching response | Reconcile the adjustment claim response 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 844 Product Transfer Account Adjustment](https://www.stacksync.com/edi/x12/844-product-transfer-account-adjustment) **product-transfer adjustment request:** a distributor or reseller requests an account adjustment. - [X12 845 Price Authorization Acknowledgment/Status](https://www.stacksync.com/edi/x12/845-price-authorization-acknowledgment-status) **price authorization status:** an authorization is issued or its status changes. ### Implementation steps 1. #### Choose the starting event and owner Decide which application acts when a product-transfer adjustment is accepted or disputed. Name the operational owner of the adjustment claim response and the team that resolves rejected or ambiguous messages. 2. #### Keep record IDs connected Map original claim, response line and authorized amount. 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 adjustment claim response 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 adjustment claim response processing. Give unresolved errors an owner and check the receiving system before approving retries. ### Go-live checklist - An approved 849 sample and the agreed version and partner guide are available. - The mapping tests pass with realistic adjustment claim response 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 adjustment claim response without processing it twice. ### Related documents and resources - [X12 844 Product Transfer Account Adjustment](https://www.stacksync.com/edi/x12/844-product-transfer-account-adjustment) - [X12 845 Price Authorization Acknowledgment/Status](https://www.stacksync.com/edi/x12/845-price-authorization-acknowledgment-status) - [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 849 Response to Product Transfer Account Adjustment at the element level The X12 849 reference contains 27 segment entries and 80 data elements; 48 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields. Segments 27 Data elements 80 Mandatory elements 48 **Segments with elements marked mandatory in this reference** | Segment | Elements | Mandatory | | --- | --- | --- | | BRC | 4 | 2 | | REF | 2 | 1 | | N1 | 4 | 1 | | N3 | 2 | 1 | | CON | 3 | 3 | | LIN | 5 | 2 | | AAA | 2 | 1 | | QTY | 2 | 1 | | AMT | 3 | 2 | Key identifiers in 849 - Transaction Set Purpose Code - Date - Reference Identification Qualifier - Entity Identifier Code - Address Information - Reference Identification - Contract Status Code - Product/Service ID Qualifier ## Find your trading partner for X12 849 5 partners, 5 channels. Choose a channel to inspect its listed document reference and implementation context. - [Border States](https://www.stacksync.com/edi/borderstates) [Border States Electric Supply](https://www.stacksync.com/edi/borderstates/border-states-electric-supply/x12-849-response-to-product-transfer-account-adjustment) - [Crescent Electric Supply Company](https://www.stacksync.com/edi/crescent-electric-supply) [Crescent Electric Supply Company (via Epicor Eclipse)](https://www.stacksync.com/edi/crescent-electric-supply/crescent-electric-supply-company-via-epicor-eclipse/x12-849-response-to-product-transfer-account-adjustment) - [Granite City Electric](https://www.stacksync.com/edi/granite-city-el) [Granite City Electric (via Epicor Eclipse)](https://www.stacksync.com/edi/granite-city-el/granite-city-electric-via-epicor-eclipse/x12-849-response-to-product-transfer-account-adjustment) - [J.H. Larson Company](https://www.stacksync.com/edi/jh-larson-electrical) [J.H. Larson Company (via Epicor Eclipse)](https://www.stacksync.com/edi/jh-larson-electrical/j-h-larson-company-via-epicor-eclipse/x12-849-response-to-product-transfer-account-adjustment) - [Master Electronics](https://www.stacksync.com/edi/master-electronics) [Master Electronics](https://www.stacksync.com/edi/master-electronics/master-electronics/x12-849-response-to-product-transfer-account-adjustment) Catalog breakdown ## Where X12 849 Response to Product Transfer Account Adjustment appears in this catalog The largest groups of classified 849 catalog entries are in building & hardware and electronics & technology. ### By industry - building & hardware 4 channels - electronics & technology 1 channel ### By network - Epicor Eclipse 3 channels Partner entries with the most listed channels - [Border States](https://www.stacksync.com/edi/borderstates) - [Crescent Electric Supply Company](https://www.stacksync.com/edi/crescent-electric-supply) - [Granite City Electric](https://www.stacksync.com/edi/granite-city-el) - [J.H. Larson Company](https://www.stacksync.com/edi/jh-larson-electrical) - [Master Electronics](https://www.stacksync.com/edi/master-electronics) FAQ ## EDI 849 questions ### What is an EDI 849? EDI 849 is the X12 Response to Product Transfer Account Adjustment transaction set. Trading partners use it when a product-transfer adjustment is accepted or disputed. It carries the data for the adjustment claim response, and your system matches it on original claim, response line and authorized amount. ### Who sends an EDI 849 and who receives it? The manufacturer, or its chargeback processing agent, sends the 849 back to the distributor or wholesaler that submitted the 844 claim. Your trading partner agreement confirms the direction and version for your account. ### When is an EDI 849 sent? A manufacturer finishes validating a received 844 chargeback claim against its contract, pricing, and customer-eligibility records and issues the disposition. Your partner guide sets any deadline or schedule for the document. ### What are the key segments in an EDI 849? Across 5 partner document references listed here, the business segments that appear most often include BRC (Beginning Segment for Response to Product Transfer Account Adjustment), N1 (Name), CON (Contract Number Detail), PAD (Product Adjustment Detail), CTT (Transaction Totals), AMT (Monetary Amount). Each partner guide sets which segments and elements your account must send. ### What is the difference between EDI 849 and EDI 844? The 849 carries the adjustment claim response and is used when a product-transfer adjustment is accepted or disputed. The 844 carries the product-transfer adjustment request and is used when a distributor or reseller requests an account adjustment. ### What should I map for X12 849? Start with original claim, response line and authorized amount and the target adjustment claim response. 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 849 error handling? Match partial approval to the submitted claim lines. Test a repeated response and prevent a second credit from being posted. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment. ### Which partners list X12 849? The directory on this page links 5 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)