The deduction management process: how to code, match and dispute retailer deductions

A deduction is an amount a customer subtracts from a payment instead of paying the invoice in full, with a reason given in the remittance advice, a debit memo or a supplier portal. A chargeback is usually an amount the customer bills you, a fine or a promotion claim, often collected by deduction too: KeHE's policies say "charged back" for promotions and spoils, Shopbop calls its fines chargebacks (KeHE, 7.4, 9.2; Shopbop, 2.2). The family, not the word, decides which document settles the question.

The code gives the family, the family gives the document, the document gives the answer. Trade promotion deductions are often money you agreed to pay: check them against the deal, do not dispute them by default.

When a distributor passes a retailer's deduction through

KeHE passes through to the supplier every expense it incurs from retailers for the supplier's products, "regardless of the timing", acting as a "bank" because the retailer deducts from KeHE first (KeHE, 8). When the error came from the retailer's deduction, KeHE repays the supplier only when the retailer has repaid KeHE (4.4). A pass-through deduction therefore has two counterparties, and the backup you send has to work for the retailer's dispute too.

Deductions arrive as lines on a remittance advice: an EDI 820, which X12 defines as the set used to "make a payment, send a remittance advice, or make a payment and send a remittance advice", or a portal export, a PDF, a paper stub. Debit memos can arrive as an EDI 812, used to "notify a trading partner of an adjustment or billback" (X12 transaction sets). Each line carries a deduction number and an amount, and often the invoice, the PO, a code and a short text.

Codes belong to the customer and mean nothing outside its list. The working tool is a code map per customer: the code, its family, the backup it needs, and who owns it inside the company (logistics for shortages, sales for promotions, the EDI team for ASN fines). A code not on the map stops the line until someone adds it. Deductions with no code or a generic one ("MISC", "other") go to research first: ask for the claim detail at once, because nothing in the agreements read here pauses the window while you wait.

The same map belongs in the ERP. In Dynamics 365 Supply Chain Management every deduction needs a reason with a claim basis, price based (a credit on approval) or quantity based (a return order) (Microsoft Learn, deduction workbench): the split between pricing or promotion and shortage. In SAP S/4HANA, the accounts receivable reason code on a residual item can be linked to a dispute case reason, and SAP suggests "Unknown" as the default where the person posting the payment does not know it (SAP Dispute Management configuration guide, 1.5).

Every customer sets its own clock, starting from its own event. The two published grocery documents read for this guide differ by a factor of six.

Three consequences. First, compute a deadline for each deduction, not for each remittance: one check can carry deductions taken on different dates. Second, work the queue by days left, then by amount. Third, find the clock that comes before the window. Under KeHE's policies the supplier agrees to rely on the case count at KeHE's distribution center and that the Unloading Discrepancy Report "shall govern", with 48 hours to answer it; KeHE does not repay a shortage deduction that such a report supports (KeHE, 6.6 and 6.7). For a shortage, the 48 hours after the report are worth more than the 180 days after the deduction.

Shortages: whose count governs

The bill of lading is signed at origin. The GS1 US standard form records which party loaded the trailer and which party counted the freight, and whether the driver counted pieces or pallets; the carrier's signature says it received the product as listed (GS1 US Bill of Lading Guideline, 9.17 and 9.18). A bill marked shipper load and count, or counted by the pallet, shows what you say you loaded. It does not show what the dock counted.

Customers say which count they pay on. KeHE relies on its distribution center's case count, not on documents its drivers signed at origin, and deducts any shortage at the PO price (KeHE, 6.6 and 6.7). To dispute a deduction, it asks for the KeHE PO number and "the bill of lading or other proof of delivery signed by a KeHE employee" (4.4): the receiver's signature, not yours. Shopbop pays only for units received and accepted, and charges $25 a carton plus a $100 fee when receipt quantities do not match the bill of lading or packing slip (Shopbop, 2.3 and 10).

A shortage is disputable when the receiver signed for the full quantity with no exception and no discrepancy report covers that PO. File the signed delivery copy, the ASN and the pick record together for every shipment, before any deduction; see proof of delivery processing.

Pricing: the PO price, the invoice price, the date

A pricing deduction is usually a difference between the PO and the invoice. KeHE pays the lower of its PO net price and the supplier's invoice amount (KeHE, 5.3), wants cost changes 90 days before its published effective date (4.7), asks for a PO Opportunity Form to correct a PO's price before it is filled (5.2) and charges back price protection on its inventory when your price goes down (4.8). Sprouts pays at the received quantities and the purchase order costs and rejects an invoice whose quantities or costs vary from them (Sprouts, 6.1). Check the price in force on the PO date: if the PO was right, the deduction is valid; if it carried an old price after an accepted change, the dispute needs the notice and its acceptance.

Trade promotions: check against the deal

The deduction has to match the funding method agreed. In KeHE's policies: off-invoice allowances on every PO written during the buy dates, plus a deduction of the extra discount when KeHE sells more during the promotion than it bought (KeHE, 7.3); manufacturer charge backs computed on KeHE's outbound case shipments during the funding period, charged every two weeks, with the backup in the supplier portal (7.4); scans, ads, demos and slotting processed for the retailer and passed through with an administrative fee (7.5); and turnover orders charged back at KeHE's wholesale price unless the supplier provides backup of a different arrangement (7.6). Microsoft's trade allowance management names the same three event types, bill back, lump sum and off-invoice, and settles the customer's short-pay against the approved claim (Microsoft Learn, trade allowance management).

Four checks, in order: an agreement exists for the event; items, dates and rate match; the quantity basis matches (purchases, shipments or scans); and it was not paid another way: taken off-invoice and billed back, deducted on two remittances, or paid by check too.

Compliance fines: the rule, the schedule, your timestamps

Fines come from a routing guide or vendor manual with a fee schedule. Shopbop's published schedule of minimum chargebacks is a clear example: $300 a shipment for a late shipment, $250 a shipment for an ASN not delivered before the shipment reaches the fulfillment center, $2.60 a unit for carton contents that do not match the ASN, and $20 a unit plus a $100 fee for a mis-ship, shortage or overage against the PO (Shopbop, 10). KeHE charges fill rate and on-time fees set in its terms and routing guide (KeHE, 6.5), and leaves lumping and non-compliance fees at its docks to the carrier on supplier-delivered freight, with the supplier responsible for any disputed fee (6.3).

A fine for a rule you broke is valid. Dispute the ones your own timestamps contradict: an 856 sent before arrival, with the 997 functional acknowledgment the customer's system returned for it; an appointment kept; a fee above the schedule. The ASN rules themselves are in the guide to EDI 850, 855, 856 and 810.

Returns, spoils and post-audit claims

Spoils are charged in one of two ways at KeHE: the amount credited to the retailer plus a fee per unit, or a fixed spoils allowance built into the price to the retailer in place of individual charges (KeHE, 9.2). Check that nothing is charged both ways. Post-audit claims can reach back further than the dispute window: KeHE may audit two years of transactions, longer if a retailer requires it, gives 30 days' notice before deducting a claim found by a third-party auditor, and asks suppliers to keep full accounts for at least two years (KeHE, 4.9). Ask for the claim detail, check the period and look for the credit already given.

Before the decision, the work is reading and finding; the decision itself is judgement about the deal and the customer.

Your ERP is where the decision is recorded. Dynamics 365's deduction workbench matches a deduction to an open credit, splits it, denies it or writes it off, and a periodic task settles approved deductions whose Deduction ID and amount match a credit (Microsoft Learn). SAP creates a dispute case for the residual item of an underpayment when the incoming payment is posted, and can write off small or uncollectible disputed amounts automatically (SAP Dispute Management configuration guide, 1.1 and 1.5.2.2). A reading and matching layer feeds those records; the write-off threshold stays a decision someone signs.

Measure the queue, not only the money back.

The cheapest deduction is the one that never happens, and the agreements say where to act: answer every discrepancy report inside its 48 hours, correct a PO before it ships, send cost changes 90 days ahead, submit promotions through the customer's own channel before its deadlines (KeHE, 5.2, 4.7, 6.6 and 7.2), and send invoices within the days the customer allows (Sprouts, 6.1).