Days sales outstanding: the DSO formula and how to reduce it

Days sales outstanding is an accounts receivable metric used to understand how quickly a business converts credit sales into cash.

You will usually see it shortened to DSO.

In practical terms, it answers a question like:

How long is our revenue sitting in accounts receivable before we collect it?

A lower DSO generally means you are turning receivables into cash more quickly.

A rising DSO means more cash is sitting in unpaid invoices.

That matters even when the business looks profitable.

You can make a sale today and record the revenue, but if the customer does not pay for another 60 days, you cannot use that money to pay salaries, suppliers, tax or anything else in the meantime.

In the UK, you may also hear people talk about debtor days. The terms are commonly used for the same basic purpose: understanding how long customer balances remain outstanding.

The standard days sales outstanding formula is:

DSO = (Accounts receivable ÷ Credit sales) × Number of days in the period

For example, say a service business has:

• $150,000 in accounts receivable
• $450,000 in credit sales during a 90-day quarter
• 90 days in the measurement period

The calculation is:

($150,000 ÷ $450,000) × 90 = 30 days

The business has a DSO of 30 days.

The same formula works over a month, quarter or year.

What matters is that you use consistent figures.

Use credit sales where possible.

If a customer pays immediately, that sale never becomes an account receivable.

Including large amounts of cash sales can make your DSO look artificially low.

Imagine two businesses each have $100,000 outstanding from customers.

One makes all of its sales on invoice.

The other takes half of its revenue upfront by card.

Using total sales without considering that difference can make the comparison misleading.

For a B2B service business where nearly everything is invoiced, total sales and credit sales may be very similar. But it is still worth understanding what is going into the calculation.

For a quick calculation, businesses often use the accounts receivable balance at the end of the period.

For a more representative calculation, you can use average accounts receivable:

Average AR = (Opening AR + Closing AR) ÷ 2

Then:

DSO = (Average AR ÷ Credit sales) × Number of days

This can be useful if your receivables balance moves substantially during the period.

For example, a big batch of invoices sent on the final day of the month could inflate your closing AR balance even though nothing meaningful changed in your collections performance.

Let's use a simple quarterly example.

A consultancy has:

• Opening accounts receivable: $180,000
• Closing accounts receivable: $220,000
• Credit sales during the quarter: $600,000
• Period: 90 days

First calculate average receivables:

($180,000 + $220,000) ÷ 2 = $200,000

Then calculate DSO:

($200,000 ÷ $600,000) × 90 = 30 days

The company's DSO is 30 days.

If most customers are on Net 30 terms, that looks very different from a DSO of 30 days where customers are supposed to pay in seven days.

Which brings us to the more useful question.

There is no single DSO number every business should aim for.

Start with your actual payment terms.

If most of your customers are on Net 30 and your DSO is 32 days, collections may be working reasonably well.

If most customers are on Net 30 and DSO is 55 days, your invoices are sitting unpaid well beyond the agreed terms.

But even that needs context.

Your DSO can also be affected by:

• The mix of Net 15, Net 30 and Net 60 customers.
• A few unusually large invoices.
• Seasonal changes in sales.
• New customers receiving different terms.
• A large project being invoiced near period end.
• Disputes that have delayed particular invoices.

So rather than asking:

Is 40 days good?

A better question is:

Why is our DSO 40 days, how does that compare with our terms, and is it getting better or worse?

One DSO calculation is a snapshot.

The trend is more useful.

Calculate it consistently each month or quarter and watch what happens.

For example:

That deserves attention.

It does not automatically mean your collections team is performing badly.

But something has changed.

You can then look at the underlying receivables to find out what.

Maybe three large customers have started paying late.

Maybe invoice disputes are taking longer to resolve.

Maybe invoices are being sent days after work is completed.

Maybe customers are promising payment dates and nobody is following up when those dates pass.

DSO tells you where to look.

It does not tell you the answer by itself.

Reducing DSO means getting invoices from "sent" to "paid" more quickly.

That does not necessarily mean chasing customers more aggressively.

Often the biggest improvements come from removing the things that delay payment.

You cannot collect an invoice that has not been sent.

If work finishes on Monday but the invoice goes out the following Friday, you have already added four days to your cash collection cycle before the customer's payment terms even start.

Invoice as soon as the contractual billing point is reached.

For recurring work, automate invoice creation where appropriate.

An invoice can sit unpaid because:

• The PO is missing.
• The legal entity is wrong.
• The amount does not match the agreement.
• It was sent to the wrong person.
• The customer's supplier requirements were not followed.

These are not really collections problems.

They are invoice process problems that eventually show up in your DSO.

For important customers, understand their payment process before the first invoice is sent.

Agree payment terms before doing the work.

Then show the due date clearly on the invoice.

"Net 30" is useful internally.

"Payment due October 15" is harder to misunderstand.

If different customers have different terms, make sure your accounting system reflects the actual agreement.

You do not need to wait until an invoice is 30 days late before paying attention to it.

A simple reminder around the due date can uncover problems early.

Maybe the invoice never reached accounts payable.

Maybe they need a PO.

Maybe the person who normally approves it is away.

Our payment reminder email templates cover what to send before, on and just after the due date.

This is one of the biggest differences between sending reminders and actually managing collections.

If a customer replies:

We need PO 5821.

the next action is to find the PO.

If they say:

The hours on this invoice aren't correct.

the next action is to resolve the dispute.

If they say:

Sarah needs to approve it.

you now know where the invoice is stuck.

A generic "Your invoice remains overdue" email does not fix any of those problems.

Suppose a customer replies:

We'll pay next Friday.

Good.

Now record Friday.

If the payment arrives, close the invoice.

If it does not, follow up on the missed promise.

Do not let the commitment disappear inside an email thread.

This is particularly important when you have dozens or hundreds of outstanding invoices.

Slow collections often happen because follow-up depends on someone remembering.

The owner chases when cash feels tight.

The finance manager works through the aged receivables spreadsheet when they get a spare hour.

A customer promises to pay, but the message is forgotten.

Create a process where every overdue invoice has:

• A current status.
• A last action.
• A next action.
• A next action date.
• A known blocker, if there is one.
• A payment promise, if one has been made.

Our collections email sequence shows what that process can look like from first reminder through to the different replies customers send.

Not every overdue invoice needs the same amount of attention.

A $25,000 invoice that is 45 days late may deserve attention before a $200 invoice that became overdue yesterday.

Look at:

• Amount.
• Days overdue.
• Customer history.
• Whether the customer has replied.
• Whether a promise has been missed.
• Whether a dispute is open.
• Whether the invoice is genuinely collectible.

An accounts receivable aging report can help you see where the largest and oldest balances sit.

A disputed invoice can sit in receivables for weeks while finance waits for someone else in the company to answer a question.

Give invoice disputes an owner.

If operations, sales or the project team needs to confirm something, make it clear who is responsible and what information is needed.

Normal chasing should pause while a genuine dispute is being resolved.

Once resolved, confirm the amount due and the new payment expectation.

If a customer agrees to Net 30 and consistently pays in 75 days, reminders alone may not solve the problem.

You may need to review:

• Their credit terms.
• Whether future work should require a deposit.
• Whether limits should be placed on further credit.
• Whether payment milestones would be better.
• Whether the commercial relationship still makes sense on its current terms.

Reducing DSO is not only a finance task.

Sometimes it requires a commercial decision.

You can estimate the amount of receivables associated with each day of DSO.

First calculate average daily credit sales:

Credit sales ÷ Number of days

Say your business has $3.65 million of annual credit sales.

Average daily credit sales are:

$3,650,000 ÷ 365 = $10,000

If DSO falls from 50 days to 40 days, that is approximately 10 fewer days of sales tied up in receivables:

10 × $10,000 = $100,000

That does not mean you generated an extra $100,000 of revenue.

You collected cash sooner that would otherwise have remained in receivables.

That distinction matters.

Potentially.

The goal is not always to force DSO as close to zero as possible.

Payment terms are part of a commercial relationship.

A valuable customer may reasonably require Net 60 terms. Tightening everybody to Net 7 just to improve a metric could make you less competitive.

Look for the unnecessary gap between the terms you agreed and what is actually happening.

If you agreed to 60 days and reliably collect in 58, that may be perfectly healthy.

If you agreed to 30 and routinely collect in 65, there is more to investigate.

DSO gives you one number.

An aging report shows you the invoices behind it.

Both are useful.

Your DSO might be 42 days, but that does not tell you whether:

• Nearly everything is being paid around day 42.
• Most customers pay on day 30 but one huge invoice is 120 days overdue.
• A group of invoices is stuck in dispute.
• One customer represents most of your late receivables.

Use DSO to understand the overall trend.

Use your aging report to work out what is causing it.