Days Sales Outstanding (DSO) Formula: How to Calculate It and Avoid Common Mistakes

Days sales outstanding, or DSO, measures how long on average it takes a company to collect payment after a sale on credit. The formula itself is simple: DSO = (Accounts Receivable ÷ Net Credit Sales) × Number of Days in the period. The hard part isn't the math — it's avoiding two common mistakes that make the resulting number misleading if you don't know to watch for them.

This guide walks through the formula, a worked example, what counts as a reasonable DSO, and the two mistakes — treating one period's number as the whole picture, and confusing DSO with a related but distinct metric — that most often trip people up.

DSO matters because it's one of the more direct links between your income statement and your actual cash position. A business can be profitable on paper and still run into a cash crunch if the money from those sales is sitting in unpaid invoices rather than in the bank — DSO is the metric that quantifies exactly how much of a lag that is, in days, rather than leaving it as a vague sense that "collections feel slow."

The DSO Formula

DSO = (Accounts Receivable ÷ Net Credit Sales) × Number of Days

Each term matters:

• Accounts Receivable is the total amount currently owed to you by customers who've been invoiced but haven't paid yet.
• Net Credit Sales is your sales made on credit (not cash) during the measurement period, net of any returns or allowances.
• Number of Days is the length of the period you're measuring — commonly 30 for a month, 90 for a quarter, or 365 for a year.

The one detail that trips people up: the "Number of Days" term has to match the same period as the credit-sales figure you're using. If your credit sales figure covers a quarter, use 90 days, not 30 — mismatching the two produces a DSO figure that doesn't actually mean what it looks like it means.

A Worked Example

Say a company has $450,000 in accounts receivable at the end of a month, and recorded $900,000 in net credit sales during that same 30-day month.

DSO = (450,000 ÷ 900,000) × 30 = 0.5 × 30 = 15 days

That means, on average, it takes this company about 15 days to collect payment after a credit sale. Note that only credit sales go into the denominator — cash sales are excluded entirely, because a cash sale is collected immediately, so by definition it contributes zero days to the "outstanding" side of the calculation. Including cash sales would understate how long credit sales actually take to collect.

What Counts as a "Good" DSO

There's no single number that applies across every business. One commonly cited reference point treats a DSO below 45 as generally low — but that framing comes with an explicit caveat even from the source that states it: the right number depends heavily on your industry, your typical payment terms, and your customer base. A company that invoices on net-15 terms and a company that invoices on net-90 terms are going to have structurally different "good" DSO numbers, and neither is wrong for comparing against a different standard than the one that actually applies to its own terms.

The more useful comparison is almost always against your own payment terms and your own trend over time, not a number pulled from an unrelated industry or company.

What Drives DSO Up or Down

A handful of factors commonly push DSO higher:

• Weak customer creditworthiness, where customers who are slower payers make up a larger share of your credit sales.
• Lenient payment terms extended to win sales (net-60 or net-90 instead of net-30, for example).
• Generous credit policies more broadly, approving credit for customers who present more collection risk.
• An ineffective or inconsistent collections process that lets overdue invoices sit without follow-up.

On the other side, DSO tends to fall with early-payment discounts and with a stricter credit policy. It's worth noting that a stricter credit policy is a trade-off, not a pure win: tightening who qualifies for credit terms can reduce DSO while also limiting the pool of customers willing or able to buy from you on credit, so lowering DSO this way can come at the cost of sales volume.

That trade-off is worth sitting with before treating "lower DSO" as an unqualified goal. A company that tightens credit terms hard enough to reject any customer who might pay even a few days late could post an excellent DSO number while also turning away revenue it could have collected successfully with a slightly more lenient policy and a reasonable follow-up process. The useful question isn't "how do we get DSO as low as possible," it's "where is our current DSO coming from, and which of those causes are actually worth fixing."

Two Mistakes That Distort the Number

Mistake 1: Treating a Single Period's DSO as the Whole Picture

DSO is a snapshot calculation, and snapshots can mislead when sales aren't evenly distributed across time. Imagine a company that closes an unusually large deal in the final week of a month. Accounts receivable spikes because that invoice hasn't been paid yet, while the "Net Credit Sales" figure for that same month also includes that large deal — so depending on exactly where in the month it closed and how AR is measured at period-end versus sales recognized across the whole period, a single lumpy month can push DSO up or down in a way that has nothing to do with whether your collections process actually got faster or slower. The number moved, but the underlying collection behavior didn't change at all.

The fix isn't a different formula — it's reading DSO as a trend over several periods, or as a rolling average, rather than reacting to any single month's figure in isolation. A DSO that jumps for one month and then returns to its prior level is far less concerning than one that's been climbing steadily over six consecutive periods. Any business with seasonal demand — a heavier sales quarter around a holiday, an annual renewal cycle concentrated in one month — should expect its single-period DSO to swing somewhat for entirely normal reasons, and should weight the rolling trend more heavily than any individual month precisely because of that.

Mistake 2: Confusing DSO with the AR Turnover Ratio

DSO and the accounts receivable turnover ratio are related, but they answer different questions. DSO measures collection speed — how many days, on average, it takes to collect. The AR turnover ratio measures frequency instead — how many times your receivables are collected ("turned over") within a given period. A company can report both metrics for the exact same underlying collections performance, because they're just two different lenses on the same data: one in days, one in a count. Tracking both gives a more complete picture than relying on either alone, though a full breakdown of the turnover ratio calculation is its own topic worth treating separately.

How to Use DSO in Practice

The practical takeaway from both mistakes above is the same: look at DSO as a trend, not a single data point, and don't treat it as the only metric that matters. Track it monthly or quarterly over time, watch the direction it's moving rather than fixating on any one period's exact value, and pair it with the AR turnover ratio so a sales-timing quirk in one metric doesn't get mistaken for an actual change in collection performance.

Calculating DSO the Right Way

The formula itself takes thirty seconds to apply. Getting value out of it takes a bit more care: make sure your days figure matches your sales period, read the result as part of a trend rather than a single snapshot, and keep the AR turnover ratio alongside it so you're not drawing conclusions from one metric in isolation. Handled that way, days sales outstanding becomes a genuinely useful early signal of collection health rather than a number that can mislead you the one month your sales happen to be lumpy.