Customer Deductions and Short Payments in Manufacturing A/R
A short payment is a dispute nobody called about. How manufacturers and distributors code, prove and close customer deductions before they age into write-offs.
Sia Ghazvinian
Co-Founder & CEO
Table of contents
Share
A customer owes you $48,200. The payment lands for $45,950, with no note, no debit memo, and a remittance line that just says "per agreement." Your aging report now carries a $2,250 balance nobody on the team can explain, and it will sit there, getting older, until somebody decides it is worth a phone call.
For manufacturers and distributors this is not an edge case. It happens every week. The paying side of the ledger says the same thing: in a UK government survey of late payment, 31% of businesses said they paid their own suppliers late because of disputed invoices, and 36% blamed administrative errors. Atradius's 2025 North America payment practices survey found 43% of US B2B credit sales were overdue, and in Canada it traced most delays to inefficiencies in customer payment processes. A short payment is very often a dispute that nobody picked up the phone about.
A customer deduction is any amount a customer subtracts from an invoice when paying it, usually for a pricing difference, a shortage, damage, a return, a promotion or a compliance penalty. The fix is operational: capture every short pay the day cash is applied, code it by reason, ask for proof, decide valid or invalid against your own records, and close it with a credit memo or a repayment request before the evidence goes stale.
What Counts as a Customer Deduction?
A deduction is a short payment with a reason behind it, even when the customer never tells you the reason. That is what separates it from a late payment. A late payment is the full amount, later. A deduction is part of the amount now, with the rest in question.
Deductions, Disputes and Unapplied Cash Are Not the Same Thing
Three things look alike on an aging report and need different handling:
A dispute is raised before payment: the customer tells you they will not pay part of the invoice, and why.
A deduction is taken at payment: the customer pays less and explains afterward, or not at all.
Unapplied cash is money that arrived and was never matched to an invoice. Some "deductions" are really a payment that landed on the wrong invoice.
Keep the distinction, because each one belongs to a different person on your team, and mixing them is how a $2,250 question turns into a six-month open item.
Why Do Deductions Hit Manufacturers and Distributors So Hard?
Deductions pile up in manufacturing and distribution because an order passes through more hands between the quote and the payment than in almost any other B2B business. Sales sets the price, the warehouse picks the order, a carrier delivers it, the customer's receiving dock counts it, and an AP clerk pays against a purchase order that may not match any of them.
Every Handoff Is a Chance to Short Pay
The usual triggers are ordinary: a price changed after the PO was cut, a shipment went out partial, a pallet arrived crushed, a return was approved by phone and never credited, a volume rebate was taken early, or a large retail customer applied a penalty for a late or mislabeled delivery. None of these are exotic. All of them produce a payment that does not match the invoice.
Why Small Deductions Quietly Become Big Ones
A $180 shortage claim costs more staff time to chase than it is worth, so it waits. Multiply that by hundreds of small accounts and the waiting becomes a balance. The Credit Research Foundation says practitioners have told it deductions spiked, in many cases by double digits over pre-pandemic levels. Every open deduction also stays in receivables, which is why unresolved short pays push DSO up even when customers pay on time. If you want to see the effect on your own numbers, start with how DSO is calculated.
Which Deduction Types Are Usually Valid?
Most deductions trace back to a real event on your side of the order, such as a wrong price or a short shipment, so the first working assumption should be that the customer may be right. The job is to find out quickly, with evidence, and to route each type to the person who can actually settle it.
Deduction type | What usually happened | What to ask for | Who settles it |
|---|---|---|---|
Pricing difference | The PO price and the invoice price do not match, often after a price change | The PO and the price the buyer expected | Sales or pricing |
Shortage | The customer received fewer units than invoiced | Receiving report and your proof of delivery | Shipping or warehouse |
Damage | Goods arrived damaged or unusable | Photos, the signed delivery receipt, any carrier note | Shipping, then the carrier |
Return or credit | Goods came back, or a credit was promised and never issued | The return authorization or the promise in writing | Customer service |
Promotion or allowance | A rebate, co-op or volume allowance was taken against an invoice | The agreement and the claim calculation | Sales |
Compliance penalty | A fine for late delivery, labeling or paperwork | The customer's scorecard or chargeback notice | Operations |
The table is also a root-cause map. If pricing differences dominate, your price file and your quotes are out of sync. If shortages dominate, the problem is on the dock, not in finance. This is the same discipline that matters when getting paid on big orders with long terms: fix the upstream cause, and the collections work shrinks on its own.
How Do You Build a Deduction Workflow That Closes Them?
A deduction workflow that works has five steps and a clock on each one: capture, code, prove, decide and close. Most teams do the first and the last and skip the middle, which is why the same deductions come back month after month.
Capture Every Short Pay the Day Cash Is Applied
Do not park the difference in unapplied cash or "on account" and move on. Open a deduction record tied to the invoice, the amount, the payment date and the customer's remittance note, even if the note is blank.
Code It by Reason Within Two Business Days
Use the reason codes from the table above. If the remittance gives no reason, finding out the reason is the first question you ask the customer, not the last.
Ask for Proof, Politely and in Writing
A short, specific request works far better than a vague one. A version you can copy:
"Hi [Name], we received your payment of $45,950 against invoice 10482 for $48,200, thank you. We would like to close out the $2,250 difference. Could you send the debit memo or the reason for it, for example a pricing, shortage or return credit? If it relates to a pricing difference, the PO number helps us match it on our side. Thanks, [Your name]"
Decide Valid or Invalid Against Your Own Records
Compare the claim with the purchase order, the price list, the signed proof of delivery, any carrier notes and the promotion or rebate agreement. Decide on evidence, not on the size of the customer.
Close It With a Credit Memo or a Repayment Request
If the deduction is valid, issue the credit memo so the invoice closes, and log the root cause. If it is invalid, send the evidence back with a clear request: repay the difference, or confirm it will be added to the next payment. Then put a follow-up date on it, the same way you would for any overdue balance.
How Fast Should You Resolve a Deduction?
Speed matters more than thoroughness on deductions, because evidence ages faster than the invoice does. A reasonable operating target is to code every short pay within two business days and reach a valid or invalid decision within 30 days. After that, proof of delivery gets harder to find, the buyer who took the deduction may have moved on, and many carrier and customer claim processes have their own windows that close without anyone noticing.
Track Days Deduction Outstanding
The metric most teams use is days deduction outstanding (DDO): the average age of open deductions. It sits next to DSO in a good set of accounts receivable KPIs, and it tells you whether your deduction process is keeping up or quietly falling behind. Report it monthly, by reason code and by customer.
When Should You Write Off a Deduction Instead of Fighting It?
Write off a deduction when proving it would cost more than it is worth, when the evidence is gone, or when the customer relationship clearly outweighs the amount. The discipline is to make that call on a rule, not a mood, and to review what you wrote off.
Set a Written Threshold
Pick a dollar threshold below which deductions with a valid reason code are approved automatically, for example amounts under $50. Anything above it gets reviewed. The same thinking applies to when to escalate an invoice: decide the rule in advance so nobody has to agonize over each one.
Watch for Repeat Patterns
The same customer taking the same deduction every month is not a collections problem. It is a pricing, shipping or labeling problem that finance happens to see first. Send the pattern to the team that owns the cause, with the numbers attached.
Where Does Automation Help With Deductions?
Automation helps with the follow-up, not the judgment. The expensive part of most deductions is not the decision; it is the three emails and two phone calls it takes to get a debit memo out of a busy AP team. That is exactly the kind of work an AI collections agent can take on.
A good setup asks for the reason and the proof on every short pay, logs the customer's answer, keeps following up until the paperwork arrives, and routes the file to the person who decides. If you want the mechanics, here is how an AI agent calls customers about overdue invoices, what it says and when it hands off to a person.
How Abivo Handles Short Payments
Abivo's AI employee works from your aging report or your accounting connection and follows up on open balances by email, text and phone, in your brand voice. When a customer raises a dispute or says a deduction was taken, the account is escalated to your team with the full conversation attached, and invoices under review can be held back from follow-up while you work them. Your team makes the valid or invalid call; the AI handles the chasing.
It is built for the buyers we see most often in manufacturing, packaging and wholesale, where long lists of accounts, net 30, 60 and 90 terms and frequent partial shipments make short pays a daily event.
Practical Takeaways for Manufacturers and Distributors
Treat every short pay as a deduction record on the day cash is applied, never as a leftover.
Code by reason within two business days, using a short, fixed list of reason codes.
Ask for the debit memo or proof in writing, with the invoice number, the amount and the PO.
Decide on your own records: the PO, the price list, the proof of delivery and the agreement.
Set a written write-off threshold, and review write-offs by customer and reason every month.
Track days deduction outstanding next to DSO, and send repeat patterns to the team that owns the cause.
Frequently Asked Questions
What is a short payment in accounts receivable?
A short payment is a payment for less than the invoice amount. The difference is usually a deduction the customer took for a price difference, shortage, damage, return, promotion or penalty, and it stays open on your aging report until it is credited, repaid or written off.
What is the difference between a deduction and a dispute?
A dispute is raised before payment, when the customer tells you they will not pay part of an invoice. A deduction is taken at payment, when the customer simply pays less. Both need the same evidence to resolve, but deductions are harder to track because the reason often arrives late or never.
What is days deduction outstanding?
Days deduction outstanding (DDO) is the average age of your open deductions. It works like DSO for short pays: a rising DDO means deductions are coming in faster than your team is resolving them.
Should deductions stay on the aging report?
Yes, until they are resolved. Moving them to unapplied cash or a suspense account hides them, and hidden deductions are the ones that end up as write-offs a year later.
Can AI collections handle customer deductions?
AI can handle the follow-up: asking for the reason and the proof, logging the answer and chasing until the paperwork arrives. The valid or invalid decision should stay with a person on your team who can see the order history.
Curious what this sounds like in practice? Listen to a 98-second sample call.
Ready to stop chasing short pays by hand? Head to Get Started and we will walk through your aging report with you.
