What is a good DSO? Benchmarks by industry (directional)

“Good” DSO is relative. A Days Sales Outstanding figure that's perfectly healthy for a construction firm would alarm a SaaS business billing monthly, and a wholesaler's normal would look slow to an agency on Net 14. The honest answer isn't a universal target — it's to compare your DSO to your own payment terms and watch the trend over time.

What is DSO and how is it calculated?

Days Sales Outstanding (DSO) is the average number of days it takes to collect a credit sale. You calculate it as (Accounts Receivable ÷ Credit Sales) × the number of days in the period. Use credit sales rather than total revenue — cash sales collect instantly, so they carry a DSO of zero and would otherwise flatter the number.

A quick worked example: if you invoiced €900,000 on credit over a year and have €120,000 still outstanding, your DSO is (120,000 ÷ 900,000) × 365 ≈ 49 days. Over a quarter you'd use 90 or 91 days in place of 365. You can work yours out in a few seconds with our free DSO calculator— it's the number every section below builds on.

DSO is a measure of collection speed, not profitability. A rising DSO means cash is arriving later, which ties up working capital you could otherwise be using — so it's worth tracking even when the business is healthy on paper.

Is there a universal “good” DSO?

Not really. A widely-cited rule of thumb is that a DSO under about 45 days is considered healthy — but that figure is general and heavily industry-relative, so treat it as a loose orientation rather than a target to chase. What “good” looks like depends far more on your terms and your sector than on any single number.

The two tests that actually matter are simple:

• Your DSO versus your own payment terms.If you invoice on Net 30, a DSO hovering near 30–40 days is doing its job. A DSO of 30 is far less impressive on Net 14 than it is on Net 60 — context is everything.
• The trend over time.A stable or falling DSO is a good sign; a steadily rising one is the real warning, even if the absolute number still looks “fine.” Direction beats the snapshot.

The clearest red flag isn't a high number in the abstract — it's a DSO sitting well above your stated terms. That gap is the part driven by late payment, and it's the part you can actually do something about.

Directional DSO ranges by industry

DSO varies enormously by sector, mostly because payment terms and billing cycles differ. Businesses that sell to consumers for cash collect almost instantly; those that sell to other businesses on credit — especially with long project cycles or large contracts — naturally run higher. The ranges below are a way to sanity-check whether you're in a plausible neighbourhood for your kind of business, nothing more.

Read these as illustrative bands, not scores. Two healthy companies in the same row can sit at opposite ends of the range purely because one invoices on Net 30 and the other on Net 60. That's exactly why comparing your DSO to your own terms tells you more than slotting yourself into an industry average.

Better than a benchmark: your terms and Best Possible DSO

A benchmark tells you where other people roughly are; it doesn't tell you how well you're doing. Two sharper references put your number in context: your own payment terms, and your Best Possible DSO. Together they separate the lateness you can influence from the part that's just the nature of your terms.

Compare to your payment terms first

Start with the terms you actually offer. If your standard is Net 30 and your DSO is 38, you're collecting close to on time — that's a good result regardless of what any industry table says. If the same Net 30 business is running a DSO of 70, the terms aren't the problem; collection is. If you want to revisit the terms themselves, our explainer on Net 30 payment terms covers when they help and when they quietly cost you.

Then measure the gap with Best Possible DSO

Best Possible DSO (BPDSO)is the theoretical floor: the DSO you'd have if every customer who isn't yet overdue paid exactly on terms. It's calculated from your current (not-yet-due) receivables, so it reflects the fastest you could realistically collect given the invoices on your books right now.

The useful part is the gap between your actual DSO and your BPDSO. That difference is the late-payment portion — the days added purely because some customers paid after their due date. Chasing a lower DSO than your BPDSO is impossible; closing the gap toward it is entirely within reach, and it's a far more actionable target than any external average.

DSO also has cousins worth knowing if you're building a fuller picture of collections health — the accounts receivable turnover ratio measures the same thing from the other direction (how many times you collect your receivables in a period).

How do you actually improve your DSO?

Once you know your number and the gap to your BPDSO, improvement is mostly about closing that gap — and the single biggest lever is whether follow-up reliably happens at all. Invoice the moment work is delivered, state terms unambiguously, and send reminders before and after the due date on a predictable cadence. Most late payments are oversights, not refusals, so consistency does more than pressure ever will.

We go through the full playbook — invoicing fast, clear terms, reminder cadence, making payment easy, and tracking promises to pay — in how to reduce DSO. The recurring theme there is that ad-hoc chasing, whenever someone remembers, is exactly what lets DSO drift above your terms.

The bottom line

There's no universal “good” DSO. The ~45-day rule of thumb is a loose orientation, and the per-industry ranges above are directional sanity checks — not benchmarks to be scored against. The two tests that genuinely matter are how your DSO compares to your own payment terms, and whether the trend is rising or falling. Work out your number with the DSO calculator, find the gap to your Best Possible DSO, and then close it with consistent, predictable follow-up. That's what turns DSO from a number you worry about into one you control.