X12 transaction guide · Finance
EDI 849 Response to Product Transfer Account Adjustment
The X12 document a manufacturer sends to approve, adjust or reject the lines of a distributor's chargeback or account adjustment request.
- Sent by
- Manufacturer or vendor
- Received by
- Distributor or wholesaler
- Standard
- ANSI ASC X12
What is an EDI 849?
The EDI 849 Response to Product Transfer Account Adjustment is the ANSI X12 transaction set used to send a detailed or summary response to a party that requested an accounting adjustment for a pre-authorized product transfer. In practice it is the manufacturer's answer to a distributor's 844 chargeback claim.
For each claim line the 849 states whether it was accepted, adjusted or rejected, the amount allowed and a reason code for any difference. Distributors use it to apply credits, investigate rejected lines and resubmit corrected claims, so the reason codes must be specific enough to act on.
How to read this diagram: the top row shows who sends the 849, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 849 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.
When it is used
- Approving chargeback lines and confirming credit amounts
- Rejecting chargeback lines with a reason
- Reporting partial approvals after price or eligibility checks
Where it fits in the document flow
Structure
Mandatory segments in the 849 (X12 release 008010)
The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.
- ST
- BRC
- N1
- CON
- PAD
- CTT
- SE
Practical example
The 849 in practice
A manufacturer receives a distributor's 844 with 120 chargeback lines. Its contract system approves 114 lines, adjusts four where the claimed price exceeds the contract and rejects two because the end customer was not eligible on the sale date. The 849 reports each result with a reason code, and the distributor applies the credit and corrects the rejected lines.
Implementation
Implementation considerations for the 849
- Return a reason code for every adjusted or rejected line so the distributor can correct it.
- Reference the original claim and line identifiers exactly.
- Reconcile 849 approvals to the credit memos or payments that follow.
- Monitor rejection rates by reason to fix recurring contract or customer data issues.
How ECOM helps
Automate the 849 with ECOM
Industry
Wholesale Distribution
Customer orders, supplier purchasing, catalogs and drop-ship for distributors.
Industry
Pharmaceuticals
Orders, ship notices, chargebacks and sales data exchange for pharma manufacturers and distributors.
Solution
Financial Document Automation
Automate invoices, remittances, payment files and bank statements from capture to posting.
More general questions about EDI are answered in the EDI FAQ.
Related transactions
Related finance documents
Need help with the EDI 849?
ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.