Terms or lateness? The first cut of a DSO change
Split DSO into best possible DSO and average days delinquent, and the story changes. Part 2 of The DSO Bridge: 3.7 of the 6.1 extra days were not even due.
In Part 1, DSO rose from 41.0 to 47.1 days and nobody could say why. The first cut is the most useful single step in the whole bridge, and it takes two lines of arithmetic.
Every DSO has two parts
Best possible DSO counts only receivables that are not yet due. It is the DSO you would have if every customer paid exactly on the due date, so it is driven by your terms, your customer mix and the timing of your sales.
Average days delinquent (ADD) is everything above that: the days added because some customers pay late, or are holding invoices back.
Best possible DSO = current AR ÷ credit sales × days
ADD = DSO − best possible DSO
The two always add back to DSO. That is what makes the split useful: every day of DSO lands in exactly one of them.
August, split
| $m or days | |
|---|---|
| Current AR (not yet due) | 11.00 |
| Total AR | 12.30 |
| Credit sales, June to August | 27.0 |
| Best possible DSO | 11.00 ÷ 27.0 × 90 = 36.7 |
| DSO | 12.30 ÷ 27.0 × 90 = 41.0 |
| ADD | 41.0 − 36.7 = 4.3 |
September, split
| $m or days | |
|---|---|
| Current AR (not yet due) | 12.65 |
| Total AR | 14.75 |
| Credit sales, July to September | 28.2 |
| Best possible DSO | 12.65 ÷ 28.2 × 90 = 40.4 |
| DSO | 14.75 ÷ 28.2 × 90 = 47.1 |
| ADD | 47.1 − 40.4 = 6.7 |
Reading the change
| August | September | Change | |
|---|---|---|---|
| Best possible DSO | 36.7 | 40.4 | +3.7 |
| ADD | 4.3 | 6.7 | +2.4 |
| DSO | 41.0 | 47.1 | +6.1 |
3.7 of the 6.1 days, about 60%, sit in invoices that customers are not yet required to pay. No amount of chasing touches those days. If the response to this month’s DSO is “make more collection calls”, most of the problem is out of reach before the first call is made.
This is the cut most teams skip, and it is the one that most often changes the conversation. It moves the discussion from “who is not working hard enough” to “which part of the business changed”.
What moves best possible DSO
Three things, none of them owned by collections:
- Terms. Grant longer terms and invoices stay current for longer.
- Mix. Sell more to customers who already have longer terms, and the same thing happens without any terms changing.
- Sales timing. A strong last month fills AR with invoices that are still current, faster than standard DSO’s three-month denominator catches up.
Part 3 takes these apart, and shows how a record month can push DSO up.
Why ADD is not a collections score
It is tempting to read the +2.4 days of ADD as “collections slipped”. Not yet. Past-due AR holds three different things:
- invoices customers are simply paying late
- invoices held back under a dispute
- invoices that have been paid, but where the cash has not been matched to them
Only the first belongs to collections. Part 4 opens up the past-due balance, and in this example the answer is the opposite of what the headline suggests.
Run the first cut on your own numbers
- Take month-end AR aging and split it into current and past due by due date, not invoice date.
- Use credit sales only. Cash sales never create receivables.
- Compute best possible DSO and ADD for this month and last month, on the same window.
- Compare the two changes before you talk to anyone.
The best possible DSO and ADD calculator does the arithmetic for you.
Next, Part 3: the great-month effect. How sales timing and one terms change add 3.5 of the 6.1 days.
- 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
