DSO Calculation: Formula, Benchmark and Worked Example

The DSO calculation divides the outstanding trade receivables balance by revenue for a period and multiplies the result by the number of days in that period. It measures the average number of days between sending an invoice and receiving the cash.

For a controller, days sales outstanding is a working capital figure rather than a collections figure. Every day of DSO represents a day of revenue parked on the balance sheet instead of in the bank account: at € 12 million of annual revenue, each additional day ties up roughly € 33,000. That makes the receivables cycle one of the few levers that releases cash without costing a cent of margin.

What days sales outstanding measures

DSO expresses how many days of revenue are sitting in the receivables balance at any given moment. Three separate things hide inside that single number, and they are not equally controllable:

• The agreed payment term. Whatever the contract or the invoice states. This is the floor you can reach under current agreements.
• Your own invoicing process. The days between delivery and a sent invoice count in full. With project billing or time-and-materials work, two weeks disappear here easily.
• Customer payment behaviour. The overrun beyond the agreed term. Only this part is genuinely a receivables problem.

Alongside DSO sit DIO (inventory days) and DPO (payables days). Together they form the cash conversion cycle; how those three interact is covered in working capital.

The DSO calculation formula

DSO = (outstanding receivables ÷ revenue for the period) × days in the period

1. Take the receivables balance. With stable revenue the closing balance will do; if revenue moves sharply, average the opening and closing balance, otherwise you mostly measure growth.
2. Strip VAT out of that balance. Receivables sit on the balance sheet including VAT, while revenue underneath sits net of VAT.
3. Take revenue over exactly the same period, net of VAT and excluding intercompany sales.
4. Divide the corrected balance by revenue and multiply by the calendar days in the period: 30 or 31 for a month, 90 or 91 for a quarter, 365 for a year.
5. Repeat on the same basis every month. A single reading says little; the twelve-month trend says everything.

So the DSO calculation needs nothing more than one balance sheet item and one profit and loss item. The skill lies in putting both on the same basis, and that is exactly where it usually goes wrong.

Worked example

A wholesaler runs a DSO calculation for the second quarter. Revenue for April, May and June totals € 2,400,000 net of VAT. The receivables balance at 30 June stands at € 1,089,000 including 21% VAT.

Item	Amount
Revenue Q2 (net of VAT)	€ 2,400,000
Receivables 30 June (including VAT)	€ 1,089,000
Receivables net of VAT (÷ 1.21)	€ 900,000
Calendar days in the quarter	91
Outcome	34.1 days

900,000 ÷ 2,400,000 × 91 = 34.1 days. Leaving the gross balance of € 1,089,000 in place would have produced 41.3 days: over seven days too high, purely because of VAT. On a thirty-day payment term, that is the difference between a normal reading and an alarm bell.

The countback method

The standard formula assumes revenue is spread evenly across the period. With growth, seasonal peaks or a large closing invoice that assumption fails, and you end up measuring the revenue pattern instead of payment behaviour.

The countback or exhaustion method solves this by working the receivables balance back against the revenue of the most recent months:

1. Subtract the last month's revenue from the receivables balance. If it fits entirely, count all days of that month.
2. Repeat with the month before, for as long as a balance remains.
3. Once the remainder is smaller than a month's revenue, prorate: remainder divided by that month's revenue, times the days in that month.

In the example above, June revenue is € 850,000, May € 800,000 and April € 750,000. The balance of € 900,000 covers all of June (30 days) and leaves € 50,000, which is 50,000 ÷ 800,000 × 31 = 1.9 days in May. A countback DSO calculation therefore returns 31.9 days against 34.1 under the standard formula. Those 2.2 days are the growth effect, not weaker collections. Use the standard formula for the trend and the countback method to judge a single period.

What is a good DSO?

There is no absolute benchmark. The only meaningful comparison is against your own weighted average payment term, because that determines what is achievable.

• Up to ten days above the agreed term: normal administrative drift. Invoices falling due on a Friday, payment runs executed every other week.
• Ten to twenty days above: a process issue. Usually incorrect invoice details, missing purchase order numbers, or a dunning cycle that only starts after the first reminder.
• More than twenty days above: the agreement is structurally ignored, or the concentration sits with a handful of large customers imposing their own terms.

Sector ranges differ widely: retail and hospitality sit at practically zero days because payment is immediate, wholesale and manufacturing typically land between 30 and 45 days, and professional services and construction closer to 45 to 60. Never benchmark against a general average; benchmark against your own history and your own terms.

Legislation sets the ceiling. Under the EU late payment rules, 30 days applies by default in B2B trade and 60 days is the contractual maximum unless expressly agreed and not grossly unfair to the supplier. In the Netherlands, large companies have been barred since 1 July 2022 from agreeing terms longer than 30 days with SME suppliers. Local rules vary, so check the jurisdiction of the selling entity before treating any figure as a breach.

Pitfalls

• VAT on one side only. Dividing a gross receivables balance by net revenue produces a figure 21% too high at a 21% rate. By far the most common error.
• Annual revenue in a seasonal business. A DSO calculation on twelve months of revenue when half of it lands in the fourth quarter reports a December figure that does not exist. Use a rolling three-month window instead.
• Credit notes and advance payments. These rarely sit where you expect them and can compress or inflate the balance by tens of days. Exclude them explicitly or disclose them.
• Intercompany receivables in a consolidated figure. Current account positions between group entities distort the picture completely, because no real payment term sits behind them. Filter them out before consolidating.
• Treating the metric as the only lever. Factoring, early payment discounts and tight credit limits all lower the number immediately, at the cost of margin or revenue. Always read the drop alongside gross margin.

Frequently asked questions

How do you run a DSO calculation in Excel?

Set up three columns per month: the receivables balance net of VAT, revenue net of VAT, and calendar days. The fourth column is balance divided by revenue times days. Extend the series across twelve months and chart it; the trend line tells you more than any single month.

What is the difference between DSO and the average collection period?

Nothing material. Both express the same thing in days. Watch the context though: sales teams often use "payment term" for what was agreed, while DSO measures what actually happened. That gap is the overrun you steer on.

Should the DSO calculation include VAT?

Net of VAT, on both sides. The receivables balance carries VAT and must be grossed down, or revenue must be grossed up. Either route gives the same answer; only mixing a gross balance with net revenue is wrong.

How often should this metric be measured?

Monthly, as a fixed part of the close. A metric that only surfaces with the annual accounts arrives months too late to support a conversation with a customer.

From metric to steering

Underneath the number sits the aging analysis. It splits open invoices across buckets: current, 1 to 30, 31 to 60, 61 to 90 and more than 90 days overdue, so you can see whether a rising term comes from one large customer or from the whole portfolio. Smartbooks shows that analysis per entity and consolidated, with the option to filter out intercompany relations, and lets you drive planned receivables off a DSO metric so working capital moves with your revenue forecast. The metric then lives in the same reporting set as the result itself.

Running a monthly DSO calculation and placing the outcome next to your 13-week cashflow planning lets you see a rising term coming rather than explaining it afterwards. Start with a twelve-month series on a fixed basis, then add the adjacent metrics: cash flow calculation for the cash itself, or the knowledge center for the rest of the set.