Who knows what in deduction handling, and where the gaps cause trouble

Each role holds one piece of a deduction. Sales knows what was promised. Logistics knows what arrived. The deductions analyst knows what the customer took. Accounting knows how it was booked. Trouble starts when someone closes a deduction using only the piece in front of them.

What the deductions analyst sees

The analyst sees the short payment first. Remittance advice, a reason code, perhaps a customer portal screenshot. That is often all there is.

They know which customers deduct aggressively and which reason codes are usually wrong. They know how far back a dispute can go before the customer's own system stops accepting it. This pattern knowledge rarely gets written down.

What they lack is context. A promotional allowance code means nothing without the trade agreement behind it. A shortage claim means nothing without the delivery record. So the analyst spends most of the day asking other people for evidence those people do not consider urgent.

What sales carries in their heads

Account managers know the deals. Not just the signed ones. They know the verbal concession made at a review meeting, the extra display fee agreed on a call, the price that was meant to change but never reached the pricing file.

This is the most dangerous gap in the process. A deduction can look invalid on paper and be entirely fair, because sales agreed to it. The reverse also happens. A sales rep may wave through an unjustified deduction to protect the relationship, without telling finance that a concession has just been granted.

Sales also tends to treat deductions as a finance problem. When asked to confirm a promotion, the request sits behind customer work.

What logistics and customer service hold

The warehouse knows what left the dock. Carriers hold proof of delivery and any signed exceptions. Customer service knows about the damaged pallet the buyer phoned in about, and the order that was changed after it was picked.

None of this sits where the analyst can reach it easily. Proof of delivery may live in a carrier portal. Return authorisations may sit in a separate system with their own reference numbers. Matching a shortage claim to a shipment can take more effort than the claim is worth, so small ones get written off unread.

What accounting knows that nobody upstream does

Accounting knows where the money lands. A deduction approved as a promotional cost hits trade spend. One approved as a pricing error reduces revenue. One left open sits in receivables and ages.

The controller also knows whether accruals for trade promotions already cover the deduction. If the accrual exists and the deduction is coded elsewhere, the business pays twice on paper and revenue looks worse than it is. The analyst approving the deduction usually cannot see the accrual balance.

Accounting also knows what auditors will ask for. A write-off without support is easy to approve today and hard to defend at year end.

Where the gaps turn into losses

The classic failure is the unrecovered invalid deduction. The analyst suspects it is wrong and asks sales to confirm. Sales does not reply. The customer's dispute window closes. The amount is written off, and nobody records why.

A second failure runs the other way. A valid deduction is disputed because the analyst could not see the agreement. The customer gets a chargeback invoice, refuses it, and the buyer complains to sales about being chased for something already agreed. Trust erodes on both sides.

A third sits in the ledger. Approved deductions get posted to a general adjustment account because the correct cost centre was unclear. Margin reporting by customer then quietly understates what each account really costs to serve.

All three come from the same root. The person with the decision does not have the evidence, and the person with the evidence does not own the decision.

Questions to ask the people who run it

What staff actually do often differs from the written procedure. These questions tend to surface the difference.

• When an analyst needs sales to confirm a promotion, how do they ask, and what happens if nobody answers?
• Which reason codes get approved almost automatically, and who decided that?
• Below what size does a deduction get written off without research? Is that threshold written anywhere?
• Where does proof of delivery come from, and how long does it take to find one?
• Who can grant a concession to a customer without telling finance?
• When a chargeback invoice goes out, who tells the account manager first?
• How does the analyst know whether a promotional accrual already covers a deduction?
• Which account do approved deductions get posted to when the right one is unclear?
• Has a customer ever produced an agreement that finance had never seen? What changed afterwards?
• What do the analysts keep in their own spreadsheets that the system does not hold?

The last question usually matters most. Private trackers show exactly which information the formal process fails to carry, and they are the first thing lost when a long-serving analyst leaves.

APQC's Process Classification Framework® (PCF) is an open standard developed by APQC, a nonprofit that promotes benchmarking and best practices worldwide. To download the full PCF or to view definitions and measures, please visit www.apqc.org/pcf.