Short-Pays and Deductions: Recovering the Money B2B Customers Quietly Withhold

There's a category of unpaid receivable that most collection advice ignores entirely, and for many B2B sellers it's larger than genuine delinquency: the customer who paid, just not all of it. A short-payment isn't a late payment — the customer has decided the difference isn't owed and considers the invoice closed. Sending a payment reminder to that customer accomplishes nothing, because they aren't late. A deduction is a dispute wearing a payment's clothing, and it comes with a deadline you probably don't know about. This guide covers how to classify deductions, research them before the window closes, dispute them successfully, and fix the upstream problems generating them.

Why deductions are a different problem

The segmentation framework in our collections approach separates unpaid accounts by reason, and deductions belong squarely in the disputed category — with a complication. In an ordinary dispute, the customer tells you they're disputing. In a deduction, they simply pay less and attach a reason code, and it's on you to notice.

That produces three distinctive properties:

• They're easy to miss. A payment arrives, cash application posts it, and the residual balance sits on the aging report looking like ordinary lateness. Businesses without a deduction process discover the accumulation during a year-end reconciliation, long after anything can be done.
• They're time-limited in a way receivables aren't. Ordinary invoices remain collectible until the statute of limitations. Deductions frequently expire under the customer's own dispute window, which is far shorter.
• Collection pressure is counterproductive. Chasing a customer for money they've decided isn't owed damages the relationship without producing payment, which is why deductions must leave the collections queue and enter a research process — the routing principle in our compliance guide, applied for commercial rather than legal reasons.

And the volume is meaningful. For sellers dealing with large retail or distribution customers, deductions can represent a persistent percentage of gross revenue — money that leaks continuously rather than dramatically, which is precisely why it goes unmanaged.

The deduction taxonomy

Classification determines everything downstream, because each type requires different evidence and has a different validity rate.

Type	What the customer is claiming	Evidence needed
Pricing	Invoiced above the agreed price	Signed pricing agreement, quote, or contract in effect on the order date
Shortage	Received fewer units than invoiced	Proof of delivery with signed quantities, packing list, weight tickets
Damage or quality	Goods arrived unusable	Delivery condition notes, inspection records, photos, carrier claim documentation
Promotional or allowance	An agreed discount, rebate, or co-op allowance	The written agreement authorizing it, and evidence it wasn't already applied
Compliance penalty	You violated their routing, labeling, or delivery window requirements	Their published requirements, your compliance records, delivery timestamps
Returns	Goods returned under an authorization	Return authorization, receipt confirmation, credit already issued or not
Unauthorized or unexplained	Nothing stated, or a code that doesn't apply	The invoice and proof of delivery — and a request for the customer's basis

Two observations from the table. Compliance penalties are the fastest-growing category for suppliers to large retailers, and they're frequently valid — the requirements are published, the supplier didn't meet them, and the penalty is contractual. The response is operational rather than dispute-based. And the unauthorized category is where recovery rates are highest, because a deduction taken without a stated basis usually can't be defended when challenged with documentation.

The clock nobody tells you about

This is the operational fact that turns deduction management from bookkeeping into urgency.

Most large customers impose a window — frequently measured in months from the deduction date — after which a deduction is considered final and will not be reviewed regardless of merit. The window is in the vendor agreement or the vendor manual, documents suppliers sign and rarely read.

The second clock is evidentiary. Proof of delivery from a carrier, signed receipts, and inspection records become progressively harder to retrieve as time passes — carriers purge records, contacts change, and the people who could confirm what happened have moved on. A deduction researched in week two is straightforward; the same deduction in month eight may be unwinnable even though it was always invalid.

Together these produce a rule that inverts normal receivables practice: work deductions newest-first, not oldest-first. A business applying standard aging discipline to deductions will spend its capacity on the ones that have already expired while fresh recoverable claims age past their window — which is the single most common structural error in this area.

Researching efficiently

Research time is the dominant cost, so the process should be built to resolve the easy cases fast and escalate only what needs it.

1. Capture at cash application. Every payment that doesn't match an invoice generates a deduction record with the customer, amount, date, invoice, and reason code, on the day it posts. This single control is what makes everything else possible.
2. Auto-classify by reason code where the customer provides one, routing each type to whoever handles it — pricing to sales, shortage and damage to fulfillment, compliance to operations.
3. Check the obvious first. Was a credit already issued? Was this deduction taken twice? Duplicate and already-credited deductions are common and resolve in minutes.
4. Validate against the agreement for pricing and allowance claims, which frequently resolve one way or the other immediately once the correct document is in hand.
5. Pull the delivery evidence for shortage and damage claims while it's still retrievable.
6. Decide: valid, invalid, or uneconomic. Valid deductions get written off promptly and fed into prevention. Invalid ones get disputed. Uneconomic ones get written off regardless of validity, which is a legitimate decision rather than a failure.

The efficiency principle worth building around: a large share of deductions resolve without investigation once someone looks at them. Duplicates, already-issued credits, and misapplied codes are common, and a process that surfaces them quickly recovers meaningful money for very little effort — which funds the harder research.

What actually wins a dispute

Deduction disputes are decided on documents, not on argument. The evidence that carries weight:

• Proof of delivery with signed quantities — the single most valuable document in shortage disputes, and the one most often unavailable because nobody retrieved it in time.
• The purchase order, establishing what was ordered at what price.
• The signed pricing agreement in effect on the order date, which resolves most pricing deductions definitively in one direction or the other.
• Packing lists and weight tickets, which corroborate what shipped.
• Delivery condition notations, since goods signed for without exception are difficult to claim as damaged afterward.
• Written authorization for any allowance being claimed, including its terms and whether it was already applied.
• Your own compliance records — routing confirmations, label specifications, delivery appointment times — for penalty deductions.

The pattern is the same as in card disputes: the party with better documentation wins, and documentation must be assembled before the deadline rather than in response to it. Which makes the upstream discipline — capturing signed delivery confirmations, keeping pricing agreements accessible, retaining compliance evidence — the real determinant of recovery rates, exactly as our chargeback guide argues for card transactions.

Submitting through the right channel

A well-researched, well-documented dispute submitted through the wrong channel frequently isn't reviewed at all.

Large customers typically maintain vendor portals with defined claim types, required attachments, and submission deadlines. A dispute raised by email to a buyer, or by phone to accounts payable, may never enter the review queue — not out of bad faith, but because the process routes claims from one place and nowhere else.

Practical requirements:

• Know each major customer's process before you need it, including the portal, the claim types, and the deadline.
• Match the claim type to their categories, since a claim filed under the wrong type gets rejected on process grounds without the merits being considered.
• Attach everything required, in the format specified. Incomplete submissions are the most common rejection reason.
• Track submitted claims to resolution. Claims that are submitted and never followed up frequently sit indefinitely — and following up requires knowing what you submitted and when, which requires a log.
• Escalate through the relationship where the process stalls, using the commercial relationship rather than instead of the process.

One relationship note worth stating: deduction disputes are ordinary commercial business, not conflict. Large customers expect vendors to dispute invalid deductions and have built processes for it. A supplier who disputes professionally and accurately is behaving normally; one who never disputes is simply funding the customer's error rate.

The economics of pursuit

Deduction management is capacity-constrained, and treating every deduction identically wastes the capacity on the wrong ones.

The framework is the expected-value calculation from our write-off guide, with deduction-specific inputs:

• Research cost is the dominant variable, and it differs enormously by type. A duplicate deduction takes minutes; a damage claim requiring carrier records takes hours.
• Recovery probability varies by type and by how much time has passed. Unauthorized deductions researched quickly recover well; aged compliance penalties generally don't.
• The window caps everything — an expired deduction has zero recovery probability regardless of merit.

Which produces a workable policy: set a threshold below which deductions are written off automatically, work everything above it newest-first, and separately review the aggregate by reason code monthly regardless of individual size — because a small deduction repeated two hundred times is a large problem that no individual claim analysis will surface.

That last point deserves emphasis. The pattern is worth more than any single claim. A supplier writing off small compliance penalties as uneconomic, individually correctly, may be absorbing a substantial annual cost from a routing problem that could be fixed in an afternoon.

Preventing recurrence

The highest return in deduction management isn't recovery — it's the deductions that never happen.

1. Report by reason code monthly, in aggregate and by customer. This is the diagnostic that locates the upstream problem.
2. Fix pricing at the source. Recurring pricing deductions almost always indicate a pricing file that doesn't match the agreement, or a change that never propagated to invoicing — which is a systems fix, not a dispute.
3. Address fulfillment accuracy where shortage claims recur, including how counts are verified at dispatch.
4. Read the vendor manual for compliance requirements and actually implement them. Routing, labeling, appointment windows, and documentation standards generate penalties that are entirely avoidable and entirely valid.
5. Get delivery documentation right — signed proof of delivery with quantities is the evidence that wins shortage disputes and the thing most often missing.
6. Tighten the agreement where you have leverage: deduction notice requirements, documentation obligations on the customer, and dispute windows that work both ways, per the terms discipline in our credit policy guide.
7. Track deduction rate as a metric alongside days sales outstanding, because it's a component of realized revenue that most sellers never measure — and the trade credit dynamics that make late payment normal make quiet short-payment normal too.

Frequently asked questions

---

This guide is educational and does not constitute legal advice. Deduction rights, dispute windows, and documentation requirements are governed by your contracts and your customers' vendor agreements; review those documents and consult counsel where significant amounts are at stake.