ADD rose, and collections got better: what collections doesn't own
Past-due AR holds three different problems. Part 4 of The DSO Bridge: undisputed lateness fell, while disputes added 2.1 days and unapplied cash 1.0.
In Part 2, ADD rose from 4.3 to 6.7 days, the part of DSO that comes from paying late. The obvious reading is that collections slipped. Open up the past-due balance and it says the opposite.
Inside past due
Past-due AR in this book has three components:
| Component | August ($m) | September ($m) | Change |
|---|---|---|---|
| Undisputed late | 0.75 | 0.60 | −20% |
| Disputed | 0.30 | 0.95 | ×3.2 |
| Unapplied cash | 0.25 | 0.55 | ×2.2 |
| Total past due | 1.30 | 2.10 |
Converted to days with each month’s days per $1m (3.33 in August, 3.19 in September):
| Component | August (days) | September (days) |
|---|---|---|
| Undisputed late | 2.5 | 1.9 |
| Disputed | 1.0 | 3.0 |
| Unapplied cash | 0.8 | 1.8 |
| ADD | 4.3 | 6.7 |
The bridge steps
Measured on September’s sales base, so that timing is not counted twice:
Lateness: (0.60 − 0.75) × 3.19 = −0.5 days
Disputes: (0.95 − 0.30) × 3.19 = +2.1 days
Unapplied: (0.55 − 0.25) × 3.19 = +1.0 day
The 0.2-day timing offset from Part 3 closes the loop: −0.2 − 0.5 + 2.1 + 1.0 = +2.4 days, the full rise in ADD.
Collections cut undisputed past due by a fifth. Two other problems more than made up for it.
Disputes: held, not late
A disputed invoice is not late in the ordinary sense. The customer has decided not to pay until something is fixed: a price that does not match the contract, a short quantity, a missing proof of delivery, a PO number that was never on the invoice.
Another reminder call changes none of that. What changes it:
- Logging the dispute fast, with a reason code, so it leaves the collections worklist and enters a resolution queue.
- Routing it to whoever caused it. Pricing errors go to pricing, delivery gaps to logistics, invoice errors to billing.
- Tracking root cause, not just resolution. A dispute that is resolved but recurs every month is a billing problem wearing a collections label.
The owner is the disputes team, together with the function that created the error. In this example, disputed balances tripled in a month. That is worth a conversation with billing and pricing before anyone talks to collections.
Unapplied cash: paid, but open
Unapplied cash is money that arrived but has not been matched to the invoices it pays. Usually the remittance details are missing, incomplete or arrive separately from the payment. Until someone matches it, the invoices still show as open and overdue.
Two costs follow. The aging overstates past due, and collectors chase customers who have already paid, which is the fastest way to irritate a good customer.
One caveat on measurement. This example uses invoice-level aging that is gross of unapplied cash, which is how most aging reports work. If your DSO uses a balance-sheet AR figure that already nets off unapplied cash, the effect lands on your aging and your worklist rather than on DSO. It is still worth sizing, because it still sends collectors to the wrong accounts.
The owner is cash application, and the fix is usually upstream: better remittance capture, portal or EDI remittances, and matching rules that handle short pays.
How to size them on your own book
- Disputed AR: from the dispute log, the open disputes that sit on past-due invoices at month end.
- Unapplied cash: the unapplied or on-account balance at month end.
- No log, or an unreliable one? Sample 30 past-due invoices, classify each one, and extrapolate. Call it an estimate in the pack, and fix the log.
What collections does own
In this example, the lateness step is −0.5 days: undisputed past due fell from $0.75m to $0.60m. That is the one number that measures collections, and it improved. It deserves to be said out loud in the month-end review, because the headline will not say it.
Next, Part 5: the full bridge. All 6.1 days in three sentences, the order question, and a workbook to run it every month.
- Terms or lateness? The first cut of a DSO change
- When a great month raises your DSO
- ADD rose, and collections got better: what collections doesn't own
- The DSO bridge: 6.1 days explained in three sentences
