DSO, and what every day of delay actually costs
DSO is the average number of days it takes to get paid for what is sold. It is calculated from two figures already on hand, and it exists for one concrete purpose: putting the cost of every day of delay into euros. Here is the formula, a worked example, and the part almost nobody calculates.
What it is, and what it is actually for
DSO stands for Days Sales Outstanding. It measures how much time passes, on average, between invoicing and the money arriving.
The interesting part is not the number. It is that it translates into days something that sits on the balance sheet in euros and says nothing on its own: the trade receivables balance. A balance of 900,000 euros means nothing until it is known whether that is 20 days of sales or 90.
The formula
Using the period method, which is the most common and the easiest to defend:
DSO = (trade receivables / sales in the period) × days in the period
Three details that change the result:
- Receivables are the closing balance of the period, including VAT if sales include it too. Mixing a figure with VAT and one without is the most frequent error and it always inflates DSO.
- Sales are those of the same period as the days being used. A quarter with 90 days, a year with 365.
- Discounted bills and non-recourse factoring need an explicit criterion, applied the same way every month. Removing them from the balance one month and not the next makes the series measure nothing.
Worked example
| Figure | Value |
|---|---|
| Trade receivables at 30 September | 900,000 € |
| Sales in the third quarter | 2,700,000 € |
| Days in the period | 90 |
| DSO | (900,000 / 2,700,000) × 90 = 30 days |
Thirty days of DSO against a 30 day agreed term sounds perfect. That is exactly where the number deserves suspicion, and the next section explains why.
What counts as a high DSO, and why the answer is not a number
There is no universal good DSO. It depends on three things, and comparing without them informs nothing.
- The agreed term. A DSO of 45 days against a 30 day term is bad. Against 60 days it is excellent. The benchmark is not the sector, it is the contract.
- Seasonality. Where half the year is sold in two months, the closing DSO of that quarter is distorted by construction. That is why the period method is read as a series, never in isolation.
- Concentration. An average of 40 days can be the whole ledger at 40, or half the ledger at 20 and one large customer at 70. Two different companies with the same indicator.
Which is why DSO is useful for comparing against itself month by month, and a poor instrument for comparing against anyone else.
The complement that fixes most of it: best possible DSO
One variant solves a good part of the problem. Calculate DSO using only the not yet due balance: the result is the DSO that would exist if every customer paid exactly on time.
The gap between actual DSO and that floor is the part that depends on collections work rather than on sales terms. It is the only number in this article a collections team can genuinely be held to.
What a day costs, in euros
This is the part that turns the indicator into a decision, and almost nobody calculates it.
Every day of DSO is one day of sales trapped in the ledger. Using the example above:
- Daily sales: 2,700,000 / 90 = 30,000 € per day
- One extra day of DSO is 30,000 € not in the account
- At 10.40%, the Spanish statutory late payment rate for the second half of 2026: 30,000 × 10.40% / 365 = 8.55 € per day
Eight and a half euros sounds trivial. Five days of excess DSO, over a year, is 150,000 euros tied up and over 15,000 euros of annual financing cost. And unlike a cost cut, recovering it costs nobody their job.
The rate used for valuation depends on how the company funds itself. The statutory one works as a reference because it is public and fixed by law; where the real cost of funding is different, use that one and the reasoning does not change.
Three ways to fool yourself with DSO
- Looking at it only at month end. Collecting on the 30th instead of the 2nd moves the indicator without anything having improved. Measure on the same date every time, and distrust improvements that appear exactly at the cut-off.
- Reading the ledger average. It hides concentration, which is the thing worth looking at. Read it per customer and by ageing.
- Chasing the number instead of the cause. DSO drops spectacularly when credit sales stop. So does the business.
Frequently asked questions
How is DSO calculated?
By dividing trade receivables by sales in the period and multiplying by the days in that period. With 900,000 euros of receivables, 2,700,000 of quarterly sales and 90 days, DSO is 30 days.
What is a good DSO?
One close to the agreed payment term. There is no universal figure: 45 days is bad against a 30 day term and very good against 60. Compare against the same company month by month, not against a sector average.
Do receivables include VAT?
Under the same criterion as the sales in the denominator. The usual choice is both with VAT, because the receivables balance carries it. What does not work is mixing.
How often should it be calculated?
Monthly, always on the same day. The series matters far more than any single month, and moving the cut-off date invents improvements that do not exist.
Does factoring lower DSO?
It lowers the receivables balance, so it lowers the number. It does not improve collections: it changes who funds them and at what price. Where it is used, say so when reading the indicator, or what is being measured is a factoring contract rather than a collections process.
What is the difference between DSO and average collection period?
None of substance: they are the same concept. The differences visible between calculations come from the method, not from the name.
What comes next
DSO says how long it takes. Lowering it has two routes, and both start before the due date: recognising in time a customer about to stop paying and chasing with the right tone and channel. And for anyone invoicing into Spain, the invoice statuses in the new regulation provide dates that do not exist today.
Calculating DSO once is easy. Having it per customer, by ageing and up to date is another matter. Book a demo and see it against a real ledger.