# EDI 849 Response to Product Transfer Account Adjustment
> EDI 849 explained: how manufacturers accept, adjust or reject distributor chargebacks, the BRC, CON, PAD, AAA, UIT and AMT segments, reject reason codes and a live example.
The EDI 849 Response to Product Transfer Account Adjustment is the X12 transaction a manufacturer sends a distributor to answer an 844 chargeback claim. For each claimed line it confirms the amount allowed, or rejects or adjusts it with a reason code, and its totals show the submitted, adjusted and allowed amounts the credit is based on.
**The EDI 849 is the manufacturer's verdict on a distributor's chargeback.** The distributor claimed the gap between its cost and a contract price on an [844](/guides/edi/844-product-transfer-account-adjustment). The manufacturer checked every line against its [845 contract](/guides/edi/845-price-authorization-acknowledgment) data. The 849 says what it found: which lines it will pay, which it corrected, which it rejected, and why. For the distributor, it is the document that turns a receivable into cash or into a dispute.
This guide covers what the 849 carries, its segments, the reject reason codes, a live example that answers the 844 example line by line, and how to work the rejections.
## What Is an EDI 849?
**An EDI 849 is the Response to Product Transfer Account Adjustment transaction set defined by the [ASC X12 standards body](https://x12.org/products/transaction-sets), used to send a detailed or summary response to a party requesting an accounting adjustment for a pre-authorized product transfer.** In distribution, that party is a distributor and the adjustment is a contract chargeback.
References for 849 work:
- The [X12 004010 849 structure on Stedi](https://www.stedi.com/edi/x12-004010/849) shows the BRC header, the CON and PAD loops and the AAA validation segment
- The [Healthcare Distribution Alliance (HDA)](https://www.hda.org/publications/edi-849-response-to-product-transfer-account-adjustment-%282020%29/) publishes the industry guideline for the 849 in the pharmaceutical chargeback reconciliation process
- [AmerisourceBergen's disputed chargeback 849 specification](https://amerisourcebergen.com/-/media/assets/amerisourcebergen/i849_disputed-chargebacks---june-2023.pdf) is a public example of a wholesaler's 849 rules, including the industry reject reason codes it uses
**Who sends it?** The manufacturer, or the contract administration service that processes its chargebacks.
**Who receives it?** The distributor that sent the 844.
**When is it sent?** After the manufacturer has validated the claim. The timing is set by the agreement between the two parties.
**Why does it matter?** The 849 decides what the distributor is actually paid. A distributor that cannot read 849s automatically ends up with an aging pile of short-paid chargebacks it cannot explain.
## How the 849 Closes the Chargeback Cycle
1. The manufacturer publishes a contract on an **845**.
2. The distributor sells to an eligible customer at the contract price.
3. The distributor claims the difference on an **844**.
4. The manufacturer validates each line: customer eligibility, item coverage, invoice date against contract dates, prices, quantities, duplicates and the claim's age.
5. **The manufacturer answers with an 849.** It references the original chargeback number, and for each line reports the submitted amount, the adjusted (allowed) amount and, for problems, a reject reason.
6. The manufacturer issues a credit or payment for the allowed total.
7. The distributor posts the allowed amounts, then corrects and resubmits rejected lines where the reason allows it, or writes them off.
Partners differ on how much the 849 should contain. AmerisourceBergen, for example, publishes one 849 guide for chargebacks accepted in full and another for disputed ones, and asks that a disputed response list only the contracts, customers and lines in dispute. Other partners expect every claimed line back. Agree the rules before you go live, so a missing line is never ambiguous: it should mean "accepted", not "not processed yet".
The [867 Product Transfer and Resale Report](/guides/edi/867-product-transfer-and-resale-report) runs alongside this cycle. Manufacturers use it to trace sales and to cross-check that a claimed sale really happened.
## Interactive Example: Chargeback Response (849)
Cedar Ridge Medical answers Lakeshore Medical Supply's chargeback `LMS-CB-260115` from the [844 example](/guides/edi/844-product-transfer-account-adjustment), on contract `CRM-GPO-2026-118`:
| Line | Item | Submitted | Allowed | Result |
|---|---|---|---|---|
| 1 | Nitrile exam gloves, 40 cases | $846.00 | $846.00 | Accepted |
| 2 | Foley catheter kit, 12 cases | $342.00 | $0.00 | Rejected: product not on the price authorization |
| 3 | Foam dressing 4x4, 25 boxes | $320.00 | $320.00 | Accepted |
| | **Total** | **$1,508.00** | **$1,166.00** | Net adjustment $342.00 |
The catheter kit was never on the [845 contract](/guides/edi/845-price-authorization-acknowledgment), so the manufacturer rejects line 2 with X12 reject reason `03` and follow-up code `N` (resubmission not allowed). The credit memo for $1,166.00 is `CRM-CM-55120`. These two partners have agreed that every claimed line comes back, so the accepted lines appear too.
## 849 Structure at a Glance
| Area | Segment | Name | Usage | Notes |
|---|---|---|---|---|
| Header | **ST** | Transaction Set Header | Mandatory | `ST01` = `849` |
| Header | **BRC** | Beginning Segment for Response to Product Transfer Account Adjustment | Mandatory | Purpose, date, the manufacturer's reference |
| Header | **CUR** | Currency | Optional | |
| Header | **AAA** | Request Validation | Optional | Validation of the claim as a whole |
| Header | **NTE**, **REF**, **PER**, **DTM** | Notes, references, contact, dates | Optional | `REF` carries the original chargeback number in many guides |
| Header N1 loop | **N1** (N2 to PER) | Name | Optional, repeats | Distributor and manufacturer |
| Detail CON loop | **CON** | Contract Number Detail | Optional, repeats | One per contract answered |
| CON loop | **AAA**, **REF**, **PER**, **DTM** | Validation, references, contact, dates | Optional | `REF` can carry a corrected contract number |
| CON N1 loop | **N1** to **PER** | End customer | Optional, repeats | The customer the claimed sales went to |
| CON PAD loop | **PAD** | Product Adjustment Detail | Mandatory in loop, repeats | One per claim line answered |
| PAD loop | **LIN** | Item Identification | Optional | The item |
| PAD loop | **AAA** | Request Validation | Optional, up to 10 | Line-level accept or reject, with reason |
| PAD loop | **PID**, **MEA**, **UIT**, **QTY**, **AMT**, **RCD**, **REF**, **DTM**, **CUR**, **SSS** | Item detail, prices, quantities, amounts, invoice | Optional | |
| Summary | **CTT** | Transaction Totals | Mandatory | Number of CON segments |
| Summary | **AMT** | Monetary Amount | Optional, up to 5 | Submitted, net adjustment and allowed totals |
| Summary | **SE** | Transaction Set Trailer | Mandatory | Segment count and control number |
The 849 shares functional group **CF** (`GS01`) with the 844.
## Key Segments Explained
### BRC: Beginning Segment
```
BRC*00*20261201*CM*CRM-CM-55120~
```
| Element | Name | Example | What it means |
|---|---|---|---|
| **BRC01** | Transaction Set Purpose Code | `00` | `00` = original. Some guides use a separate code for a response to a resubmission |
| **BRC02** | Date | `20261201` | The date of the response |
| **BRC03** | Reference Identification Qualifier | `CM` | The type of reference in BRC04. `CM` (credit memo) is a common choice |
| **BRC04** | Reference Identification | `CRM-CM-55120` | The manufacturer's credit memo or response number |
| **BRC05** | Time | | Optional |
### REF: The Original Chargeback
```
REF*AM*LMS-CB-260115~
```
`REF01` = `AM` (adjustment memo, chargeback) with the distributor's chargeback number from `BAA05` of the 844. This is the link that lets the distributor's AR team match the response, and the credit, to the open claim. Without it, the 849 has to be matched by contract and invoice, which is slow and error-prone.
### CON and N1: Contract and Customer
```
CON*VC*CRM-GPO-2026-118*VA~
N1*ST*RIVERBEND COMMUNITY HEALTH*ZZ*RCH-0001~
```
The `CON` loop repeats the contract number from the 844, and `N1*ST` the end customer. If the manufacturer believes the distributor quoted the wrong contract, many guides let it send the corrected number in a `REF` in the `CON` loop (one public guide uses qualifier `C8`, corrected contract number) rather than simply rejecting the line.
### PAD and LIN: The Line Being Answered
```
PAD*2~
LIN**VP*CRM-FOL-16K~
```
`PAD01` numbers the line within the contract, and `LIN` identifies the item in the same form the 844 did. The distributor matches each answered line back to the claimed line using the item, the invoice number and the invoice date in the same loop.
### AAA: Request Validation
```
AAA*N**03*N~
```
| Element | Name | Example | What it means |
|---|---|---|---|
| **AAA01** | Yes/No Condition or Response Code | `N` | `N` = the line is not valid as submitted. `Y` = valid |
| **AAA02** | Agency Qualifier Code | (empty) | Empty means `AAA03` comes from the X12 code list. A value here means an industry list |
| **AAA03** | Reject Reason Code | `03` | Why the line was rejected or adjusted |
| **AAA04** | Follow-up Action Code | `N` | What the distributor should do next |
X12's reject reason list (element 901) includes codes written for chargebacks and price authorizations, for example:
| Code | Meaning |
|---|---|
| `01` | Price authorization invalid |
| `02` | Price authorization expired |
| `03` | Product not on the price authorization |
| `04` | Authorized quantity exceeded |
| `16` | Unit resale higher than authorized |
| `19` | Ship date cannot be prior to price authorization issue date |
| `28` | Duplicate invoice number |
| `29` | Claim submitted past exercise period |
The follow-up codes (element 889) include `C` (please correct and resubmit), `E` (resubmit this item only), `N` (resubmission not allowed) and `R` (resubmission allowed).
**Industry code lists are common.** Pharmaceutical distribution uses a reject reason list maintained through the industry guideline, sent with an agency code in `AAA02`, with two-letter codes for situations such as contract expired, customer not covered, drug not covered or contract price incorrect. AmerisourceBergen's public guide notes that these codes do not match the X12 list and that some translators flag them as compliance errors, so set up your translator for the list your partner actually uses.
### UIT: Prices
```
UIT*CA*71.25*CT~
UIT*CA*71.25*SC~
```
| UIT03 code | Meaning |
|---|---|
| `CT` | Contract price, as the manufacturer has it |
| `SC` | Submitted contract price, as the distributor claimed it |
| `WH` | Wholesale price, as the manufacturer has it |
| `SW` | Submitted wholesale price, as the distributor claimed it |
Pairs of `UIT` segments let the manufacturer show the distributor's figure next to its own. When the contract price on file differs from the one claimed, the distributor sees exactly what was corrected. In the example, the rejected catheter line carries only the submitted contract price, because the manufacturer has no contract price for an item that is not on the contract.
### QTY: Quantities
```
QTY*83*12*CA~
QTY*32*12*CA~
```
`QTY01` = `83` (submitted quantity sold) is what the distributor claimed, and `32` (quantity sold) is what the manufacturer accepts. A difference between them is a quantity adjustment. X12 also defines `84` (submitted quantity returned) and `76` (returns) for return lines.
### AMT: Line and Summary Amounts
```
AMT*S*342.00~
AMT*A*0~
```
At line level, `AMT01` = `S` (submitted chargeback claim amount) is what the distributor claimed and `A` (adjusted chargeback claim amount) is what the manufacturer allows. In the summary:
```
CTT*1~
AMT*S*1508.00~
AMT*NA*342.00~
AMT*A*1166.00~
```
`S` is the total claimed, `NA` (net adjustment) the total reduction, and `A` the total allowed. The arithmetic must hold: `S` minus `NA` equals `A`. The allowed total is the amount the credit memo or payment should carry.
## EDI 849 vs 844, 812, 824 and 997
| Document | Sent by | Purpose |
|---|---|---|
| **[844 Product Transfer Account Adjustment](/guides/edi/844-product-transfer-account-adjustment)** | Distributor | The chargeback claim the 849 answers |
| **849 Response** | Manufacturer | Business verdict on each claimed line |
| **[812 Credit/Debit Adjustment](/guides/edi/812-credit-debit-adjustment)** | Either party | General credit or debit against an invoice; not the chargeback response |
| **[824 Application Advice](/guides/edi/824-application-advice)** | Receiver | Reports that a document failed business or application edits |
| **[997 Functional Acknowledgment](/guides/edi/997-functional-acknowledgment)** | Receiver | Confirms the 844 arrived and parsed; says nothing about the claim's validity |
A 997 accepting the 844 is not acceptance of the chargeback. Only the 849 (or the credit itself) tells you that.
## Working 849 Rejections
Group rejected lines by reason and fix the cause, not just the claim.
| Reason family | Likely cause | Fix |
|---|---|---|
| **Customer not eligible or not covered** | Sale priced at contract for a customer not on the roster, or customer ID mismatch | Check the 845 roster and your customer ID mapping; resubmit only if the customer was eligible on the invoice date |
| **Item not covered** | Contract price applied to an item not on the contract | Fix item eligibility in your pricing; these are usually not resubmittable |
| **Outside contract dates** | Invoice date before the customer or item start date, or after expiration | Load customer and item dates, not just contract dates |
| **Price incorrect or corrected** | Contract price changed and your system missed it | Load 845 changes promptly; post the corrected amount |
| **Duplicate** | Same invoice line claimed twice, often after a resubmission | Track claimed lines by invoice and line; resubmit only rejected lines |
| **Too old** | Claim filed after the agreed window | Claim on a schedule; watch for invoices that miss a run |
Track rejection rates by reason, customer and contract every week. A rising "customer not covered" rate usually means a roster change you have not loaded, and it will keep costing money until you do.
## 849 Implementation Checklist
- Get the manufacturer's 849 guide and confirm whether it sends full responses or exceptions only
- Confirm how the original 844 is referenced (`REF*AM` or another qualifier) and what `BRC04` carries
- Load the reject reason list your partner uses, X12 or industry, and map each code to an internal action
- Match each answered line to the claimed line by contract, customer, item, invoice number and date
- Post allowed amounts to AR and reconcile them to the credit memo or payment
- Route rejected lines to a work queue by reason and follow-up code
- Confirm how resubmissions are referenced, so they are not rejected as duplicates
- Send a 997 for every 849
## Handling the Orders Behind Chargebacks With OrderSync
Rejected chargebacks are expensive, and most start with an order booked under the wrong customer or item. When hospital, clinic and contractor orders arrive as PDFs, emails and spreadsheets, that mistake happens at keying.
OrderSync reads customer orders in any format, from EDI 850s and 875s to emails, PDFs and spreadsheets, matches customers, items and units to your catalog, and sends clean orders to your ERP or outputs valid X12. Paste any 849 into the [free EDI inspector](/edi-inspector) to see it parsed with a plain-English summary, read about [EDI for pharmaceutical distribution](/edi-for/pharmaceutical), or [book a 15-minute walkthrough](/book-call) to see your own orders processed.
## Frequently Asked Questions
### What is an EDI 849 used for?
The EDI 849 is used by a manufacturer to respond to a distributor's 844 chargeback claim. It reports, line by line, which claimed amounts are allowed, which are adjusted, and which are rejected with a reason code, plus the totals the manufacturer's credit is based on.
### What is the difference between EDI 844 and 849?
The 844 is the distributor's chargeback claim. The 849 is the manufacturer's response to it. The 849 quotes the 844's chargeback number, repeats the contract and line detail, and adds the allowed amounts and reject reasons.
### What does the AAA segment mean in an 849?
AAA is the request validation segment. AAA01 says whether the line is valid (Y) or not (N), AAA03 gives the reject reason code, and AAA04 says what to do next, such as correct and resubmit or do not resubmit. AAA02, when present, names an industry code list.
### What are the AMT codes S, A and NA in an EDI 849?
S is the submitted chargeback claim amount, A is the adjusted or allowed chargeback amount, and NA is the net adjustment. In the summary, the submitted total minus the net adjustment equals the allowed total.
### Does a manufacturer have to send an 849 for accepted chargebacks?
It depends on the agreement. Some distributors require an 849 for every 844, even when all lines are accepted. Others want only exceptions, listing just the disputed contracts, customers and lines. The distributor's implementation guide says which.
### Can a rejected chargeback be resubmitted?
Sometimes. The follow-up action code in AAA04, or the industry reason code, says whether the line can be corrected and resubmitted. Lines rejected because the customer or item was never on the contract usually cannot be.
### Is an EDI 849 the same as a 997?
No. A 997 only confirms that the 844 was received and was structurally valid. The 849 is the business decision on the chargeback itself: what will be paid and what will not.