Skip to content
Calculation

How to calculate DSO — and DPO and DIO with it

DSO is the metric most often quoted and second-most often miscalculated. It answers a single question: how many days pass, on average, between issuing an invoice and the money arriving? That number determines how much capital is permanently tied up in receivables — and it is one of the few levers that releases liquidity without involving a bank.

This guide walks through the calculation, a fully worked example, and the errors that distort the figure in practice. For using the metric as a steering instrument and weighing it against DPO and inventory days, see the guide on managing working capital.

The DSO formula

DSO (Days Sales Outstanding) relates the receivables balance to revenue for the same period:

MetricFormula
DSO(trade receivables ÷ revenue) × days in period
DPO(trade payables ÷ cost of goods sold) × days in period
DIO(inventory ÷ cost of goods sold) × days in period

A full financial year puts 365 days into the formula, a quarter 90 or 91, a month 30. What matters is that numerator and denominator describe the same period: a year-end receivables balance belongs with annual revenue, not with December’s.

A worked example

A manufacturer with €12m annual revenue and €7m cost of goods sold reports, at the balance sheet date: €1,800,000 receivables, €800,000 trade payables, €900,000 inventory.

MetricCalculationResult
DSO(1,800,000 ÷ 12,000,000) × 36555 days
DIO(900,000 ÷ 7,000,000) × 36547 days
DPO(800,000 ÷ 7,000,000) × 36542 days
Cash conversion cycle55 + 47 − 4260 days

Read plainly: an average of 60 days passes between paying for inputs and receiving money from the customer — a gap the company finances out of its own pocket.

The value of a single day follows directly from revenue: €12,000,000 ÷ 365 = roughly €32,900 per day of DSO. Cutting five days off the collection period therefore releases about €164,000 — once, but permanently available as long as the level holds.

Calculating DPO and DIO

For DPO and DIO the denominator is not revenue but cost of goods sold, because both metrics describe the purchasing side rather than the sales side. This is the most common error in home-built reports: calculating DPO against revenue produces a systematically understated figure.

A day of DPO is worth correspondingly less than a day of DSO: €7,000,000 ÷ 365 = roughly €19,200 per day. That is why the DSO lever moves faster for most mid-sized companies — it depends on your own invoicing and dunning process, whereas DPO depends on supplier contracts and DIO on production.

Four pitfalls that distort the figure

Gross against net. Receivables sit on the balance sheet including VAT; revenue sits in the P&L net of it. Comparing the two unadjusted overstates DSO by nearly a fifth at a 19 percent VAT rate — 46 real days become 55 on paper. Either gross up revenue or net down receivables.

A single date instead of an average. One balance sheet date is misleading in a seasonal business. Measuring receivables in December after a strong November produces an inflated DSO. An average of opening and closing balances is more robust; a twelve-month monthly average better still.

Advance and progress payments. Payments received on account reduce the economic receivable but, depending on presentation, may not reduce the receivables balance. In project business with progress billing, the pure balance sheet formula is only a rough approximation.

The average hides the outliers. A DSO of 55 days can mean every customer pays after 55 days — or that 90 percent pay after 30 and one large account pays after 180. Only the second is an acute risk. An ageing profile of open items shows this; the mean does not.

Where revenue fluctuates sharply, the countback method gives more realistic values: the receivables balance is worked backwards against the most recent months’ revenue until it is used up, and the days consumed are the DSO. More effort, but immune to seasonality.

DSO and DPO continuously, not once a year

LiquidityLens calculates both metrics automatically from open receivables and payables — and shows immediately how a change feeds through to the 13-week forecast.

See the Liquidity Control Sprint

Reading your own value

No credible absolute target exists for DSO: customary payment terms vary too widely, and a construction supplier working to 60-day terms is doing well at 65 days where an online retailer with the same figure would have a problem. Two comparisons are meaningful instead.

The first is against your own agreed payment terms. If DSO sits systematically above what your invoices state, customers are paying late on average — and the difference is the amount your dunning process can recover without renegotiating a single contract.

The second is your own trend over time. A DSO climbing over several months is among the most reliable early warnings of a liquidity squeeze: it shows money arriving later than planned long before the bank balance reveals it. That is precisely why the metric belongs in the weekly review rather than the annual accounts — and why DSO is one of the inputs that makes cash flow forecasting realistic rather than nominal.

13-week template with a metrics sheet

The free Excel template includes the weekly plan along with fields for DSO, DPO and the cash conversion cycle — a starting point before the calculation runs automatically.

Download the template

Frequently asked questions

How do you calculate DSO?
DSO = (trade receivables ÷ revenue for the period) × number of days in the period. That is 365 days for a full financial year, 90 or 91 for a quarter. Both figures must share the same tax basis: receivables sit gross on the balance sheet while revenue sits net in the P&L, so compare gross with gross.
What is a good DSO value?
There is no universal target, because customary payment terms differ far too much between industries. The meaningful comparison is against your own agreed payment terms: if DSO sits well above them, customers are paying late on average. The second is your own trend — a DSO rising over several months is an early warning signal regardless of the absolute level.
What is the difference between DSO and DPO?
DSO measures how long your customers take to pay you — capital tied up on the asset side. DPO measures how long you take to pay suppliers — interest-free financing on the liability side. Together with inventory days (DIO) they form the cash conversion cycle: DSO + DIO − DPO.
Why does my calculated DSO not match reality?
Usually for one of three reasons: mixing gross and net figures (a distortion of roughly 19 percent), using a single balance sheet date instead of an average balance in a seasonal business, or advance payments sitting in receivables without a corresponding open customer invoice. Where revenue fluctuates sharply, the countback method gives more realistic values than the averaging formula.