Ask a finance team why a deduction was taken and you'll usually get a reason code. Ask whether it was right and the room goes quiet. Not because nobody cares, but because the answer is spread across six systems, and no one person can see all of them.
This is how one deduction travels, where its facts end up, and the mismatches that turn a valid shipment into a lost dollar.
The six places one deduction lives
Follow a single promotion deduction, $3,600 taken off a Target remittance in June:
| Where | What it holds | Who usually has it |
|---|---|---|
| The remittance | The amount taken and a reason code | AR, from the bank or lockbox |
| The retailer portal | The claim, the backup and the dispute window | AR, if someone logs in |
| The ERP | The PO, the invoice, the price and the promotion as booked | Finance |
| The warehouse or 3PL | What shipped, when, and the signed proof of delivery | Operations |
| The carrier | Appointment times, delivery records and exceptions | Logistics |
| Sales | The promotion agreed with the buyer, usually in email | The account manager |
To know whether that $3,600 is valid, you need at least four of them. The remittance says a promotion was deducted. Only the sales manager's email says the promotion was agreed for two weeks in May, not June. Only the ERP shows the June shipments were invoiced at full price, as agreed. Put together, the deduction is wrong. Seen from AR alone, it looks like any other promotion deduction.
Where the mismatches come from
Deductions rarely go wrong because someone made a big mistake. They go wrong where two systems describe the same thing differently:
- Dates. The retailer applies a promotion by order date, and your agreement is by ship date. A week of orders lands on the wrong side of the line.
- Units. The retailer counts eaches, and your invoice counts cases. A shortage appears that is really a conversion.
- Split shipments. One PO ships on two trucks. The retailer receives the first, deducts for what's missing, and never matches the second.
- Prices. A price change takes effect in your ERP on the 1st and in the retailer's system on the 15th. Every invoice in between is short-paid.
- Promotions. A deal is agreed by email, never entered anywhere, and deducted twice: once by the retailer and once through a distributor billback.
- Proof. The signed proof of delivery exists, but at the 3PL, under a different reference number.
Each mismatch is small. Each one produces a deduction that a reason code can't explain and a dashboard won't flag.
Why they stay hidden
Reconciling one deduction means opening every system it touches. For a team working hundreds of deductions a month, that isn't possible, so the work gets rationed. Big claims are worked, and small ones are accepted. The ones accepted aren't checked, so nobody learns which mismatches keep causing them. The same June-instead-of-May promotion gets deducted again next year.
What it takes to reconcile them
The fix isn't another report. It's putting each deduction's facts side by side, every time:
- Read the claim the way the retailer wrote it. The code, the backup and the window, straight from the portal.
- Match it to what you booked. The PO, the invoice, the price and the promotion in the ERP.
- Match it to what happened. The shipment, the signed proof of delivery and the carrier record.
- Match it to what was agreed. The program letter or the buyer's email.
- Decide, with the evidence attached. Valid, invalid, or waiting on a document, and why.
Done for every deduction, the patterns show up on their own: the DC whose receiving counts are always short, the promotion calendar that's off by a week, the price change that never reached the retailer. Those are the fixes that stop the next deduction before it's taken.
That's the work Seeft does. It reads every deduction against the records in each of those six places, drafts the dispute for the ones that don't hold up, and posts every outcome back to your ERP.
Questions to ask your team
- For our last ten promotion deductions, how many did anyone compare with the agreed promotion dates?
- Do we invoice in the same unit the retailer receives in?
- When a PO ships on two trucks, how do we match the second delivery to the deduction?
- How long after a price change does the retailer's system catch up?
- Where are our signed proofs of delivery, and could AR find one today?
See it on your own deductions
A free audit puts your recent deductions next to your own records and shows what's recoverable, by retailer and deduction type, within two weeks of receiving your data. For more on where the evidence lives, see our guides to Amazon, Walmart and Target deductions.