How to audit retailer deductions and short payments

A short payment has two separate questions: does the remittance reconcile to the invoice, and is the deduction supported by the applicable agreement and evidence? Answering only the first can make an invalid charge look finished.

Most suppliers check the first question because the bank statement forces it. The second question is where money stays behind: a shortage that the receiving record does not support, a promotion charged outside its dates, a fee taken twice. This guide walks through both questions in order, with one worked case from invoice to recovery.

Reconcile the invoice and the remittance

Calculate expected due from invoice lines, allowances, entered tax and credit notes. Compare that with cash received, listed deductions and any unapplied amount. If invoice expected is 1,000, cash is 900 and the remittance identifies a 100 deduction, the payment reconciles. The 100 still needs review.

Written as formulas:

expected due E = Σ (quantity × unit price − allowances + entered tax + entered charges) − credit notes;
accounted A = cash received + listed deductions + unapplied amount;
difference R = E − A.

A difference beyond the customer's tolerance is unresolved. It is not a deduction until the remittance names one. Link a payment to an invoice automatically when the reference matches exactly and uniquely; a near match such as "1002" against "INV-1002" stays unapplied until someone reviews it. Otherwise one wrong link can make two invoices look wrong.

Decode the reason and calculate the rule

Match the reason code to a dated rule. Quantity shortages need ordered, shipped, invoiced and accepted quantities. Promotional allowances need eligible products, dates, units and the agreed rate. A fixed compliance fee needs the event and supporting condition. Do not calculate the rule from the amount the retailer already deducted; that only repeats the claim.

Each customer can have its own rules, and a rule has an effective date. Use the rule in force on the event date (the delivery, the promotion week, the late shipment), not the one in force today. If the rule starts after the event, the honest result is "rule not found", not a guess. Typical methods:

Method	Calculation from entered facts
Quantity shortage	max(0, invoiced quantity − accepted quantity) × unit price
Percentage allowance	eligible base × agreed rate
Fixed fee	number of events × fee per event
Promotion	eligible units × allowance per unit

Check the evidence

Suppose the shortage deduction is 100 but receiving records support only 60. The audit can classify 60 as supported under the entered rule and 40 as a dispute candidate. If the receiving record is missing, it should say “missing evidence,” not automatically call the whole amount valid or invalid.

List the documents each rule needs: purchase order, advance shipping notice, proof of delivery, receiving record, agreement, promotion terms, correspondence. A document you have requested but not yet received is still missing. The supported amount is min(claimed, rule-calculated), and it is shown when every required field and document is present; the difference is a dispute candidate, not money you are sure to recover.

A worked case: 1,000 invoice, 100 deducted, 60 supported

Step	Input	Result
Invoice	100 units × 10.00	expected 1,000.00
Remittance	cash 900.00 + shortage deduction 100.00	accounted 1,000.00, difference 0.00: reconciled
Rule	quantity shortage, in force since 1 January, receiving record required	rule found, record present
Shortage	invoiced 100 − accepted 94 = 6 units × 10.00	rule amount 60.00
Support	min(100.00 claimed, 60.00 calculated)	supported 60.00, dispute candidate 40.00
Deadline	notice 30 September + 30 calendar days	dispute by 30 October
Case	40.00 submitted on 12 October	on time
Recovery	credit 40.00 confirmed on 20 October	recovered 40.00, open 0.00, recovery rate 100.00%

Two lines in this table are easy to get wrong. The remittance "reconciles" although 40 of the deduction is not supported, and the recovery is counted once even after the credit is used.

Protect the deadline

Protect the deadline. Record the notice date, the entered dispute window and whether the rule uses calendar days or another supplied business calendar. Build an evidence checklist linked to the source pages and files. The software can organise a packet; the user remains responsible for submission and any legal position.

Make the date rule explicit. With the notice date as day 0, 30 calendar days from 30 September is 30 October; a dispute recorded on 30 October is on time and one recorded on 31 October is late. With a business-day window, weekends and the holidays you enter are skipped: 5 business days from Friday 30 October, with 3 November entered as a holiday, end on 9 November. Sort the queue by deadline, then amount, then ID, so the case that expires first is on top.

Track credit and cash without inflation

Track recoveries without inflation. A confirmed 40 credit is a recovery event. Applying that same credit to a later invoice is usage, not a second 40 recovery. Cash, credits, offers, write-offs and open amounts deserve separate fields. Recovery rate uses confirmed recovered money or credit, not amounts merely requested.

In the worked case, the 40 credit is later applied against another invoice. The ledger shows credit accepted 40, credit used 40, recovered 40, not 80. If a further 10 of cash were entered for the same case, it would be refused, because 40 + 10 is more than the 40 submitted. A credit of 40 followed by cash of 60 on a claim of 100 recovers 100, not 140. Open claim = disputed − confirmed credits − confirmed cash − written off; with no submitted amount the recovery rate is N/A rather than 0%. A wrong entry is reversed with a reason, which restores the open amount instead of deleting history.

Duplicates and partial payments

The same deduction can appear twice: a retailer error, or the same remittance imported twice. Use a duplicate key (by default customer, invoice, reason, shipment and amount) to flag the second row as a possible duplicate without merging it. For example, two identical 100 deductions show a total claimed of 200, a supported amount of 60 and 100 flagged for review, so nothing is doubled silently. A payment that covers several invoices but names one of them exactly leaves the rest as unapplied cash until you link it.

Checklist for each short payment

Recalculate expected due from the invoice lines, not from the remittance.
Reconcile cash, deductions and unapplied amount against it.
Link payments automatically when the reference is exact and unique; review the rest.
Find the customer's rule in force on the event date.
Calculate the rule from entered facts (accepted quantity, eligible units, events).
Mark missing documents as missing, not as proof either way.
Separate supported, dispute candidate and unresolved amounts.
Record the notice date, window and day convention; work the queue by deadline.
Record credit, credit use, cash and write-off as different events.
Report the recovery rate from confirmed amounts, with N/A at zero.

Limits

This method organises facts you enter or import from CSV; it does not connect to EDI or retailer portals, submit disputes or decide who is legally right. Agreements differ between customers, so the rules are yours to enter and keep current. Attachments stay in your own files; the audit stores their metadata and links. For invoices that are simply paid late rather than short, the Invoice Recovery Desk fits better; to check supplier bills against orders and receipts on the buying side, see Purchase & Invoice Match.

Keep it in one record

Retail Deductions & Short-Pay Audit keeps invoice reconciliation, rule calculation, evidence, deadline and recovery allocation in one record. Open the fictional grocery case to follow the 1,000 invoice from remittance through partial support and confirmed recovery.

Explore the fictional demo · See the full tool