Skip to content
EDI 844 — EDI TransactionPublished Nov 4, 2026

EDI 844 Product Transfer Account Adjustment: Chargeback Guide

EDI 844 explained: how distributors claim contract-price chargebacks from manufacturers, the BAA, CON, SII and PAD segments, a live example, the 849 response and common errors.

The EDI 844 is how a distributor gets paid back for selling at someone else's price. A manufacturer negotiates a contract price with a hospital, a group purchasing organization, a contractor or a restaurant chain. The distributor ships the product from its own stock, bought at its normal cost, and invoices the customer at the lower contract price. The 844 is the claim for the gap, line by line, so the manufacturer can check it against the contract and credit the distributor.

This guide covers the full contract chargeback cycle, the 844's structure and every key segment, a live example that ties to the 845 contract and the 849 response, and the errors that get claims rejected.

What Is an EDI 844?

An EDI 844 is the Product Transfer Account Adjustment transaction set defined by the ASC X12 standards body. X12 describes it as transmitting "a debit, credit, or request for credit relating to pre-authorized product transfer actions." In practice, almost every 844 in production is a distributor's chargeback claim against a manufacturer's contract.

References for 844 work:

Who sends it? The distributor or wholesaler that sold the product.

Who receives it? The manufacturer (or the contract administration team or service that runs chargebacks for it).

When is it sent? After the distributor has invoiced contract sales, usually in batches on a schedule the two parties agree, often daily or weekly.

Why does it matter? For the distributor, unclaimed or rejected chargebacks are margin lost on sales already made at a loss. For the manufacturer, paying a chargeback on an ineligible customer or item gives away contract pricing it never agreed to. The 844 is where both sides' records meet.

Distributor Chargebacks vs Retail Chargebacks

"Chargeback" means two very different things in EDI, and searching for one often turns up the other.

Distributor contract chargebackRetail compliance chargeback
Who claims moneyThe distributor, from the manufacturerThe retailer, from the supplier
WhyThe distributor sold at a contract price below its costThe supplier broke a rule: late ASN, bad label, short shipment
Is it a penalty?No. It is how contract pricing gets fundedYes. It is a fine or deduction
EDI documents845 contract, 844 claim, 849 response, 867 resale reportUsually an 812 Credit/Debit Adjustment or a deduction on the 820 remittance
Typical industriesPharma and medical supply, electronics, electrical, foodservice, industrial distributionRetail and grocery

This guide is about the first kind. If you are dealing with fines from a retailer, see our explainer on retail chargebacks instead.

How the Contract Chargeback Cycle Works

The 844 is one step in a four-document cycle. The same contract number runs through all of it.

  1. The manufacturer negotiates a contract. It agrees a price with an end customer, or with a group purchasing organization (GPO) on behalf of its members, for a list of items and a date range.
  2. The manufacturer tells the distributor (845). The 845 Price Authorization Acknowledgment/Status gives the distributor the contract number, the eligible customers, the covered items, the contract prices and the dates.
  3. The distributor sells at the contract price. The customer orders through its normal channel. The distributor ships from stock it bought at its own acquisition cost (in pharma, usually the wholesale acquisition cost, or WAC) and invoices the customer at the contract price.
  4. The distributor claims the difference (844). For each contract sale, the 844 carries the item, the quantity, the distributor's cost, the contract price and the extended claim: (cost minus contract price) times quantity.
  5. The manufacturer validates and responds (849). It checks every line against its own contract records: is the customer eligible, is the item covered, was the sale inside the contract dates, is the price right, is it a duplicate? The 849 Response to Product Transfer Account Adjustment accepts, adjusts or rejects each line.
  6. Money moves. The manufacturer issues a credit or payment for the allowed amount. Rejected lines are corrected and resubmitted, or written off, depending on the reason.
  7. Sales are reported (867). Separately, many distributors send an 867 Product Transfer and Resale Report with all sales of the manufacturer's products, contract or not. Manufacturers use it to trace product to end customers and to cross-check chargebacks.

A worked example with real numbers: a distributor buys a case of exam gloves at $92.40. The manufacturer's contract with a health system sets the price at $71.25. The distributor sells 40 cases to that health system at $71.25 and then claims 40 x ($92.40 minus $71.25) = $846.00 on an 844. Without that credit, the distributor loses $21.15 on every case.

Where the 844 Is Used

Contract chargebacks exist wherever a manufacturer sets prices for end customers it does not ship to directly.

  • Pharmaceuticals. The largest user. Manufacturers hold contracts with GPOs, hospitals, pharmacies and government programs, and the big wholesalers claim chargebacks on every contract sale. HDA's guidelines and the wholesalers' own specs shape most of what you will see, including pharma identifiers such as DEA numbers, Health Industry Numbers (HINs) and NDCs.
  • Medical and surgical supply. The same model runs through med-surg distributors, with GPO contracts covering gloves, catheters, dressings and devices.
  • Electronic components. Distributors claim "ship and debit" credits when they sell below book price under a manufacturer's special pricing approval. The X12 code lists reflect this with product transfer types such as "Ship and Debit Sale", and ECIA publishes industry guidance for these transactions.
  • Electrical, industrial and building products distribution. Manufacturers grant special pricing agreements for specific contractors or projects, and distributors claim the difference on sales against them.
  • Foodservice. Manufacturers set deviated or contract prices for restaurant chains and operators, and broadline distributors claim the deviation. Some programs run on 844 and 849; many still run on spreadsheets and portals.

The X12 structure is the same across industries. The identifiers, the required segments and the rules for what counts as a valid claim come from the industry guideline and each partner's implementation guide.

Interactive Example: Med-Surg Contract Chargeback (844)

A medical supply distributor, Lakeshore Medical Supply, claims chargebacks from the manufacturer Cedar Ridge Medical on contract CRM-GPO-2026-118, the contract Cedar Ridge published on the 845 example. Three lines were sold to the contracted health system on two invoices:

LineItemQtyDistributor costContract priceClaim
1Nitrile exam gloves40 cases$92.40$71.25$846.00
2Foley catheter kit12 cases$148.00$119.50$342.00
3Foam dressing 4x425 boxes$64.80$52.00$320.00
Total$1,508.00

Line 2 has a problem the distributor has not spotted: the catheter kit is not on the contract. The 849 example shows the manufacturer rejecting it.

Use the Plain English tab for a readable summary, or click any segment to see each element.

Live exampleDistributor to Manufacturer (Med-Surg)EDI 844

Medical Supply 844 Contract Chargeback Claim

The distributor claims the difference between its acquisition cost and the contract price on three lines sold to the contracted health system: SII lines with cost, contract price and extended claim, N9 invoice references and a CC claim total

Document
844 Product Transfer Account Adjustment
From / to
LAKESHOREMED → CEDARRIDGEMED
Segments
21
Party (DS)
LAKESHORE MEDICAL SUPPLY
Supplier
CEDAR RIDGE MEDICAL
Ship To
RIVERBEND COMMUNITY HEALTH
400 HOSPITAL DRIVE, SPRINGFIELD, OH, 45501
Interchange date
Nov 16, 2026

Raw EDI (X12)

1
ISA*00* *00* *ZZ*LAKESHOREMED *ZZ*CEDARRIDGEMED *261116*0830*U*00401*000008441*0*P*:~
2
GS*CF*LAKESHOREMED*CEDARRIDGEMED*20261116*0830*8441*X*004010~
3
ST*844*0001~
4
BAA*00*RA*20261116*AM*LMS-CB-260115~
5
N1*DS*LAKESHORE MEDICAL SUPPLY*ZZ*LKSMED~
6
N1*SU*CEDAR RIDGE MEDICAL*ZZ*CRMED~
7
CON*VC*CRM-GPO-2026-118*VA~
8
N1*ST*RIVERBEND COMMUNITY HEALTH*ZZ*RCH-0001~
9
N3*400 HOSPITAL DRIVE~
10
N4*SPRINGFIELD*OH*45501~
11
SII*VP*CRM-GLV-N200*40*CA*92.40*71.25*846.00~
12
N9*DI*LMS-INV-7781203**20261103~
13
SII*VP*CRM-FOL-16K*12*CA*148.00*119.50*342.00~
14
N9*DI*LMS-INV-7781203**20261103~
15
SII*VP*CRM-DRS-4X4*25*BX*64.80*52.00*320.00~
16
N9*DI*LMS-INV-7781266**20261109~
17
CTT*1~
18
AMT*CC*1508.00~
19
SE*17*0001~
20
GE*1*8441~
21
IEA*1*000008441~

Human-Readable

Interchange

Sender ID(ZZ)LAKESHOREMED
Receiver ID(ZZ)CEDARRIDGEMED
Date261116
Time0830
Standards IDU
Version00401
Control Number000008441
Acknowledgment RequestedNo
UsageProduction
Included Groups (IEA01)1

Functional Group

Functional IDCFCF
SenderLAKESHOREMED
ReceiverCEDARRIDGEMED
Date20261116
Time0830
Control Number8441
Agency CodeX
Version004010
Transactions1
Reported Transaction Count (GE01)1

Transaction 844

Product Transfer Account Adjustment
Transaction Type844
Control Number0001
Segments, ST to SE17
Count in SE0117 (matches)

Segment Detail

BAABeginning Segment for Product Transfer Account Adjustment
BAA01Transaction Set Purpose Code00
BAA02Transaction Type CodeRA
BAA03Date20261116
BAA04Reference Identification QualifierAM
BAA05Reference IdentificationLMS-CB-260115
N1Party Identification
N101Entity CodeDS
N102NameLAKESHORE MEDICAL SUPPLY
N103ID QualifierZZ
N104ID CodeLKSMED
N1Party Identification
N101Entity CodeSU
N102NameCEDAR RIDGE MEDICAL
N103ID QualifierZZ
N104ID CodeCRMED
CONContract Number Detail
CON01Reference Identification QualifierVC
CON02Contract NumberCRM-GPO-2026-118
CON03Contract Status CodeVA
N1Party Identification
N101Entity CodeST
N102NameRIVERBEND COMMUNITY HEALTH
N103ID QualifierZZ
N104ID CodeRCH-0001
N3Party Location
N301Address400 HOSPITAL DRIVE
N4Geographic Location
N401CitySPRINGFIELD
N402State/ProvinceOH
N403Postal Code45501
SIISales Item Information
SII01Product/Service ID QualifierVP
SII02Product/Service IDCRM-GLV-N200
SII03Quantity40
SII04Unit of MeasureCA
SII05Wholesale Acquisition Price92.40
SII06Contract Price71.25
SII07Extended Rebate Amount846.00
N9Reference Identification
N901Reference Identification QualifierDI
N902Reference IdentificationLMS-INV-7781203
N904Date20261103
SIISales Item Information
SII01Product/Service ID QualifierVP
SII02Product/Service IDCRM-FOL-16K
SII03Quantity12
SII04Unit of MeasureCA
SII05Wholesale Acquisition Price148.00
SII06Contract Price119.50
SII07Extended Rebate Amount342.00
N9Reference Identification
N901Reference Identification QualifierDI
N902Reference IdentificationLMS-INV-7781203
N904Date20261103
SIISales Item Information
SII01Product/Service ID QualifierVP
SII02Product/Service IDCRM-DRS-4X4
SII03Quantity25
SII04Unit of MeasureBX
SII05Wholesale Acquisition Price64.80
SII06Contract Price52.00
SII07Extended Rebate Amount320.00
N9Reference Identification
N901Reference Identification QualifierDI
N902Reference IdentificationLMS-INV-7781266
N904Date20261109
CTTTransaction Totals
CTT01Line Item Count1
AMTMonetary Amount Identification
AMT01Amount QualifierCC
AMT02Amount1508.00
1 functional group1 transactionControl #000008441Valid

844 Structure at a Glance

The 844 is built around contracts. Each CON loop is one contract, with the customer and the claimed lines inside it.

AreaSegmentNameUsageNotes
HeaderSTTransaction Set HeaderMandatoryST01 = 844
HeaderBAABeginning Segment for Product Transfer Account AdjustmentMandatoryPurpose, transaction type, date, chargeback (debit memo) number
HeaderCUR, NTE, REF, PER, DTMCurrency, notes, references, contact, datesOptionalUsed where the partner guide asks
Header N1 loopN1 (N2 to PER)NameOptional, repeatsThe distributor and the manufacturer
Detail CON loopCONContract Number DetailMandatory, repeatsOne per contract claimed against
CON loopREF, PER, DTMReferences, contact, datesOptional
CON N1 loopN1, N3, N4, REFCustomer name, address, IDsOptional, repeatsThe end customer the contract sale went to
CON SII loopSIISales Item InformationOptional, repeatsCompact claim line: item, quantity, cost, contract price, extended amount
SII loopN9Reference IdentificationOptionalThe distributor's invoice number and date
CON PAD loopPADProduct Adjustment DetailOptional, repeatsAlternative claim line structure
PAD loopLIN, PID, UIT, QTY, AMT, REF, DTMItem, description, prices, quantities, amount, invoiceOptionalUsed when the line is sent in PAD form
SummaryCTTTransaction TotalsMandatoryNumber of CON segments
SummaryAMTMonetary AmountOptionalTotal claim
SummarySETransaction Set TrailerMandatorySegment count and control number

The 844 sits in functional group CF (GS01), which X12 shares between the 844 and the 849.

SII or PAD?

The 4010 844 offers two ways to send a claim line. The SII loop puts the whole line in one segment, and X12's own notes define its prices for chargebacks: SII05 is the wholesale acquisition price, SII06 the contract price and SII07 the extended rebate amount. Pharmaceutical wholesalers commonly use this form. The PAD loop spreads the same facts over LIN, UIT, QTY and AMT segments, and is the shape the 849 response uses. Your partner's guide picks one. Do not mix them in one claim unless the guide says you can.

Key Segments Explained

BAA: Beginning Segment

BAA*00*RA*20261116*AM*LMS-CB-260115~
ElementNameExampleWhat it means
BAA01Transaction Set Purpose Code0000 = original. Resubmissions use the code the partner guide names
BAA02Transaction Type CodeRARA = request for credit, the usual value for a chargeback claim
BAA03Date20261116The date the claim was generated
BAA04Reference Identification QualifierAMAM = adjustment memo (chargeback)
BAA05Reference IdentificationLMS-CB-260115The distributor's chargeback or debit memo number
BAA06TimeOptional

BAA05 is the number everything else hangs off. The manufacturer quotes it back in the 849, the credit memo references it, and your AR team uses it to clear the receivable. Keep it unique and never reuse it for a resubmission unless the guide tells you to.

N1: Distributor and Manufacturer (Header)

N1*DS*LAKESHORE MEDICAL SUPPLY*ZZ*LKSMED~
N1*SU*CEDAR RIDGE MEDICAL*ZZ*CRMED~

The header names both sides. DS (distributor) or DB (distributor branch) identifies who is claiming, and SU (supplier/manufacturer) who is paying. Pharma guides identify parties by DEA number (N103 = 11) or HIN; other industries use DUNS, GLNs or mutually agreed codes. The branch matters: in pharma the claim is usually tied to the specific distribution center that sold the product.

CON: Contract Number Detail

CON*VC*CRM-GPO-2026-118*VA~
ElementNameExampleWhat it means
CON01Reference Identification QualifierVCVC = vendor contract number
CON02Reference IdentificationCRM-GPO-2026-118The contract number from the manufacturer's 845 or contract notice
CON03Contract Status CodeVAVA = valid open contract

The contract number in CON02 must be the manufacturer's number exactly as it published it. A contract number the manufacturer cannot find rejects every line underneath it.

N1, N3, N4 and REF: The End Customer

N1*ST*RIVERBEND COMMUNITY HEALTH*ZZ*RCH-0001~
N3*400 HOSPITAL DRIVE~
N4*SPRINGFIELD*OH*45501~

Inside the CON loop, N1*ST names the customer the distributor sold to. This is the party whose eligibility the manufacturer checks, so the identifier must match the one on the manufacturer's contract roster. In pharma that is typically the customer's DEA number or HIN, with REF segments for extra IDs such as a 340B identifier. A customer the manufacturer cannot match is one of the most common rejection reasons.

SII: Sales Item Information

SII*VP*CRM-GLV-N200*40*CA*92.40*71.25*846.00~
ElementNameExampleWhat it means
SII01Product/Service ID QualifierVPType of item ID. Pharma uses NDC qualifiers; others use vendor part numbers, UPCs or GTINs
SII02Product/Service IDCRM-GLV-N200The item, as the manufacturer identifies it on the contract
SII03Quantity40Units sold on this invoice line. Some guides send returns as a negative quantity
SII04Unit of MeasureCAMust match the unit the contract price is quoted in
SII05Unit Price (wholesale acquisition price)92.40The distributor's cost basis per unit
SII06Unit Price (contract price)71.25The contract price per unit
SII07Monetary Amount (extended rebate)846.00(SII05 minus SII06) times SII03

The arithmetic has to hold on every line. A claim where SII07 does not equal the difference times the quantity is rejected or corrected by the manufacturer, and either way you wait longer to be paid.

N9: Invoice Reference

N9*DI*LMS-INV-7781203**20261103~

N901 = DI (distributor invoice number), N902 is the invoice to the end customer and N904 its date. The invoice date is what the manufacturer checks against the contract's start and end dates, and against its claim submission window. Some guides also carry a unique line identifier or lot number in N907.

CTT and AMT: Totals

CTT*1~
AMT*CC*1508.00~

CTT01 is the number of CON segments in the transaction, not the number of claim lines. AMT01 = CC (chargeback claim amount) carries the total of all SII07 values. Some guides make the summary AMT mandatory; the X12 standard leaves it optional.

Where the 844 Sits Among Related Documents

DocumentSent byPurposeRole in chargebacks
845 Price AuthorizationManufacturerPublishes the contract: customers, items, prices, datesThe rulebook every 844 is checked against
844 Product Transfer Account AdjustmentDistributorClaims the difference between cost and contract priceThe claim
849 ResponseManufacturerAccepts, adjusts or rejects each claim lineThe verdict
867 Product Transfer and Resale ReportDistributorReports sales to end customersTracing and cross-checking
812 Credit/Debit AdjustmentEither partyGeneral credit or debit against an invoiceUsed for other adjustments; not the contract chargeback claim
820 Payment Order/RemittancePayerPayment and remittance detailMay carry the settlement of allowed chargebacks
997 Functional AcknowledgmentReceiverConfirms the file arrived and parsedSays nothing about whether the claim is valid

Common 844 Errors and How to Prevent Them

ErrorWhat happensPrevention
Customer not on the contractLine rejectedLoad the 845 eligibility roster and check the ship-to before you price the order
Item not covered by the contractLine rejectedCheck the item against the contract's item list, not just the customer
Invoice date outside contract datesLine rejectedCompare the invoice date (not the claim date) with the contract and customer start and end dates
Contract price mismatchLine adjusted to the manufacturer's pricePrice contract orders from the latest 845, including changes
Unit of measure mismatchClaim off by the pack sizeClaim in the unit the contract price is quoted in
Extended amount does not computeLine adjusted or rejectedCalculate SII07 from the other elements, never key it
Duplicate claimSecond claim rejectedTrack every invoice line claimed; resubmit only rejected lines, with the resubmission reference the guide requires
Claim filed too lateLine rejected as too oldClaim on a regular schedule; the submission window is in your contract with the manufacturer
Wrong or missing party IDsWhole claim or contract loop rejectedUse the exact identifiers (DEA, HIN, GLN, DUNS or agreed codes) from the partner guide

Most of these trace back to the order. A sale priced at the contract price for a customer or item that is not actually covered creates a chargeback that will never be paid, which is a straight loss. Checking eligibility at order entry is far cheaper than disputing it at the 849.

844 Implementation Checklist

  • Get the manufacturer's 844 and 849 implementation guides, and the industry guideline they follow
  • Agree the line format (SII or PAD), the party identifiers and the product ID qualifier
  • Confirm how returns and credit-rebills are sent: negative quantities, separate claims or a transaction type code
  • Load 845 contracts, including customer rosters, item lists, prices and every date range
  • Build the claim from invoiced sales data, with the invoice number and date on every line
  • Calculate every extended amount and total in code
  • Agree the claim schedule and the submission window
  • Set up 849 processing to post allowed amounts and work rejected lines
  • Test with valid lines plus deliberate failures: ineligible customer, uncovered item, wrong price, duplicate
  • Watch 997s for structural rejections in the first weeks

Handling the Orders Behind Chargebacks With OrderSync

Chargeback accuracy starts with the order. If a hospital's order arrives as a PDF, an email or a phone note and is keyed into the ERP under the wrong ship-to or the wrong item, the contract price and the chargeback both go wrong with it.

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 844 into the free EDI inspector to see it parsed segment by segment with a plain-English summary, read about EDI for pharmaceutical distribution and EDI for distributors, or book a 15-minute walkthrough to see your own orders processed.

Frequently Asked Questions

What is an EDI 844 used for?

The EDI 844 is used by a distributor to claim a contract chargeback from a manufacturer. When the distributor sells to a contracted customer at a price below its own cost, the 844 lists each sale with the cost, contract price and quantity, and claims the difference as a credit.

What is an EDI 844 chargeback?

It is a claim for the difference between what a distributor paid for a product and the lower contract price the manufacturer agreed with the end customer. It is not a penalty. It is how manufacturers fund contract pricing that is delivered through distributors.

What is the difference between EDI 844 and EDI 849?

The distributor sends the 844 to claim chargebacks. The manufacturer sends the 849 back to accept, adjust or reject each claimed line, with reason codes and the allowed amounts. Together they form the claim and response pair of the chargeback cycle.

What is the difference between an EDI 844 and an EDI 812?

The 844 is specific to contract chargebacks: it is organized by contract, end customer and claimed sale. The 812 is a general credit or debit adjustment against an invoice, used for things like shortages, pricing errors and retail compliance deductions.

What are the main segments in an EDI 844?

BAA starts the claim and carries the chargeback number. N1 segments name the distributor and manufacturer. Each CON loop names a contract, with N1 for the end customer and SII or PAD loops for each claimed sale. CTT and AMT carry the totals.

How is the chargeback amount calculated in an 844?

For each line, the distributor's cost minus the contract price, times the quantity sold. In the SII segment that is SII05 minus SII06, times SII03, reported in SII07. The total of all lines goes in the summary AMT segment.

Which industries use the EDI 844?

Pharmaceutical and medical supply distribution use it most, followed by electronic components (ship and debit), electrical and industrial distribution, and foodservice. Any industry where manufacturers set end-customer prices that distributors fulfil from their own stock can use it.

Does the 844 have anything to do with retail chargebacks?

No. Retail chargebacks are penalties a retailer takes from a supplier for compliance failures, usually sent as 812 adjustments or deductions on a payment. The 844 is a distributor's claim for contract pricing support, and the two processes do not overlap.

James Darby
Last updated: 11/4/2026

Related Resources