← Read

The DSO bridge: 6.1 days explained in three sentences

Part 5 of The DSO Bridge. The full walk from 41.0 to 47.1 days, the answer a CFO actually needs, why the order of the steps matters, and a workbook to run it every month.

The DSO Bridge · Ep 526 Oct 20264 min read

Four parts, one question: why did DSO rise from 41.0 to 47.1 days? Here is the whole bridge, and the answer it gives.

The bridge

Each step changes one cause and holds the rest where they were. Two decimals here, so the running total is exact.

Step DSO after the step Change
August 41.00
Sales timing 43.09 +2.09
Terms and mix 44.52 +1.44
Lateness 44.04 −0.48
Disputes 46.12 +2.07
Unapplied cash 47.07 +0.96
September 47.07 +6.07

Every day is accounted for. There is no “other” line.

The answer, in three sentences

DSO rose 6.1 days, from 41.0 to 47.1. 3.5 days are timing and terms: a strong September and one customer moved to Net 60, neither of them a collections issue. Disputes added 2.1 days and unapplied cash 1.0, while undisputed lateness actually improved by 0.5 days.

That is what the CFO needed on day one. It replaces “customers are paying slower” with a breakdown that names an owner for every day.

Same +6.1 days, five different actions

Cause Days Owner Action
Sales timing +2.1 Nobody Explain it. Report countback DSO alongside standard
Terms and mix +1.4 Sales and credit Review the Net 60 deal against its cost of cash
Lateness −0.5 Collections Recognise the improvement
Disputes +2.1 Disputes, billing, pricing Root-cause the jump in disputed balances
Unapplied cash +1.0 Cash application Fix remittance capture and matching

A DSO number on its own would have produced one action: push collections harder. The bridge produces five, and the one aimed at collections is a thank-you.

Order matters

A bridge is not unique. Because the causes interact with each other through the denominator, the days each one gets depend on the order of the steps.

We used timing, terms, lateness, disputes, unapplied. Run the same book in reverse, starting with unapplied cash and ending with timing, and the steps come out like this:

Cause Our order Reverse order
Sales timing +2.1 +1.9
Terms and mix +1.4 +1.5
Lateness −0.5 −0.5
Disputes +2.1 +2.2
Unapplied cash +1.0 +1.0

A tenth or two moves between causes. The story does not change. That is the normal case: as long as one cause is not enormous, the order shifts the decimals, not the conclusion.

The rule is simple. Pick an order, write it down, and keep it month to month. Changing the order between months to make a number look better is the one way to make a bridge dishonest. We put the business causes first (what was sold, on what terms) because they change the base that every later step is measured on.

Running it every month

The bridge needs five inputs at each month-end:

  1. AR aging, current against past due, by due date
  2. credit sales by month, at least three months back
  3. terms changes by customer, with effective dates
  4. past-due AR under an open dispute
  5. the unapplied cash balance

Build it once, and month-end commentary becomes a table instead of a debate. When a number cannot be measured, estimate it, label it as an estimate, and fix the data behind it before next month.

The workbook

The DSO bridge workbook has this example built in, with every formula visible. Replace the inputs with your own month-end figures and the bridge, the three sentences and the reverse-order check rebuild themselves. Find it on the calculators page.

What the series was really about

“DSO went up” is a result. The bridge is the explanation. Most of the time, the result and the explanation point to different teams, and that is exactly when it matters most to have the second one.

Start with the first cut: the best possible DSO and ADD calculator splits terms from lateness in under a minute.

About the author

Abhishek Sahu

Order to Cash Product Manager

Senior product manager with more than six years in order-to-cash, across HighRadius, Deloitte and EXL. He has built products for collections, cash application, deductions and O2C analytics, and holds three US patents in AI-driven financial automation.