Managing AR disputes and deductions
A dispute is a customer's reason for not paying an invoice in full, and a deduction is the amount they actually withhold. Here is how to tell them apart, find the root cause, route each case, and recover the money customers take by mistake.
Managing AR disputes and deductions means separating the customer's reason for not paying from the dollars they withhold, finding why each one happened, sending it to the person who can resolve it, and collecting back the money customers deduct without a valid claim. A dispute is the stated reason. A deduction is the amount taken. Treating them as one thing is why so many teams let cash leak: they close the conversation when the customer explains the problem and never recover the dollars.
What is the difference between a dispute and a deduction?
A dispute is a customer's objection to an invoice. The customer says the price is wrong, the order was short, or the goods arrived damaged. A deduction is the money the customer subtracts from their payment, usually because of that objection. The two often travel together, but not always. A customer can dispute an invoice and still pay it in full while you investigate. A customer can also short pay with no explanation, which leaves you holding a deduction and no dispute reason until you chase it. The practical point is that a dispute is a question and a deduction is a debit. You resolve the question, but you have to account for the debit either way, by collecting it or writing it off.
What are the common root causes?
Most deductions fall into four buckets, and naming the bucket is the first step in resolving the case.
- Pricing. The invoice price does not match what the customer expected, often because a contract rate or a quoted discount was not applied.
- Shortage. The customer received fewer units than billed, so they pay for what arrived and deduct the rest.
- Damage. Goods arrived broken, spoiled, or rejected at receiving, and the customer refuses to pay for them.
- Promotional and trade. The customer claims an advertising allowance, a rebate, or a trade-spend deal against the invoice, sometimes correctly and sometimes by claiming the same deal twice.
Assigning a clean reason code at intake is what makes the rest of the process work. A deduction with no code cannot be routed, measured, or trended, and it tends to sit until it ages out.
Who should own each case?
The owner depends on the cause, because the person with the answer is rarely the collector who found the problem. Pricing disputes go to whoever set the price, usually sales or the contracts team, since only they can confirm the agreed rate. Shortage and damage claims go to the warehouse or the carrier, because resolving them requires the proof of delivery, the bill of lading, or the receiving report. Promotional deductions go to sales or trade marketing, who know whether the deal was real. Routing each case to the right owner with the supporting document attached is the difference between a deduction that resolves in days and one that bounces between inboxes for a quarter. This is one place where agentic automation helps: a system can read the short pay, classify the reason code, and route the case with the matching document already pulled, so the owner opens a complete file instead of starting an investigation.
How do you recover invalid deductions?
A deduction is invalid when the customer took money they were not entitled to, such as deducting for a shortage that the proof of delivery shows was fully shipped. Recovery is a documentation exercise. Pull the evidence that the deduction was not owed, then issue a chargeback or rebill that puts the amount back on the customer's account with that proof attached. Speed matters, because the longer an invalid deduction sits, the harder it is to collect and the more likely the customer treats it as settled. Set a resolution date on every open deduction so valid ones are written off promptly and invalid ones are pursued before they age. The discipline that recovers cash is not aggression, it is closing the loop on every case rather than letting the easy ones expire.
Why this matters for cash
Unresolved deductions inflate your aging, distort DSO, and quietly write off margin that you earned. A book full of small open short pays is a book that looks worse than it is and that loses real money on the invalid ones. The teams that hold the line treat every deduction as a case with a cause, an owner, and a deadline, and they recover what was taken in error instead of conceding it by default.
Frequently asked questions
- What is the difference between a dispute and a deduction?
- A dispute is the reason a customer gives for not paying an invoice in full, such as a pricing error or a damaged shipment. A deduction is the dollar amount the customer actually withholds from their payment, usually tied to that reason. A dispute can exist without a deduction when the customer flags a problem but still pays, and a deduction can arrive without a stated reason when the customer short pays and leaves you to find out why.
- How do you recover an invalid deduction?
- Identify the reason code, gather the proof that the deduction was not owed, such as a signed proof of delivery or the correct price list, and issue a chargeback or rebill to the customer with that documentation attached. Track each open deduction to a resolution date so valid ones are written off and invalid ones are collected before they age past the point where the customer disputes them again.
- What are the most common causes of deductions?
- The four most common are pricing errors, shortages where the customer received less than billed, damaged or rejected goods, and promotional or trade allowances the customer claims against an invoice. Pricing and promo deductions usually require sign-off from sales, while shortage and damage deductions require proof from the warehouse or carrier.