What is the formula for DSO?

DSO = (Accounts receivable / Total credit sales) x Number of days in the period. Use credit sales only, not total sales, since cash sales were never outstanding and including them understates the number. Keep the period consistent between calculations, because a DSO measured differently each quarter cannot be managed or compared.

The only meaningful benchmark is your own payment terms. On net 30, a DSO in the mid-30s means customers are paying roughly on time. More than about 15 days above your standard terms usually points to a follow-up problem rather than a customer problem. Cross-industry averages are close to useless because terms vary enormously by sector.

How can I reduce DSO quickly?

Work the entire past-due list on a fixed schedule instead of triaging the biggest accounts, and make the later escalation steps actually send. Add a payment link to every message, and ask what is blocking approval rather than repeating the demand. Most overdue invoices are stuck rather than refused, so unblocking them is faster than pressuring them.

Why is my DSO increasing?

Usually one of four things: follow-up stopped after the second reminder, invoices are going out late or with errors, terms drifted longer than anyone decided, or customers are managing their own cash and paying whoever chases hardest. Check the aging buckets rather than the average, since one large early payment can mask a growing 90-plus column.

Does AR automation actually reduce DSO?

It reduces the portion of DSO caused by inconsistent follow-up, which in most companies is the largest portion. It works by ensuring every overdue account gets worked rather than only the loudest, and that the later escalation steps send on schedule. It will not help if DSO is high because of long terms, incorrect invoices, or genuinely insolvent customers.

What is the difference between DSO and average collection period?

They measure the same thing and the terms are used interchangeably in practice. Both express the average number of days between a credit sale and the cash arriving. Some teams calculate average collection period from average receivables across the period rather than the closing balance, which smooths out a lumpy quarter but tells the same story.

How to Reduce DSO: 9 Changes That Actually Work

To reduce DSO, shorten the gap between the due date and the payment: invoice the day the work is done, make paying take one click, and follow up on every overdue account on a fixed schedule rather than when someone remembers. That last one carries most of the weight. Companies rarely have a high DSO because their terms are wrong. They have a high DSO because the long tail of late invoices never gets worked, and the fourth reminder, the one with an edge in it, never gets sent.

Below is the formula, what a reasonable target looks like, and the nine changes that actually move the number, in rough order of how much they move it.

What is the DSO formula?

Days sales outstanding measures the average number of days between making a sale on credit and collecting the cash.

DSO = (Accounts receivable / Total credit sales) x Number of days in the period

So a company with $300,000 in receivables and $900,000 in credit sales over a 90-day quarter has a DSO of (300,000 / 900,000) x 90 = 33 days. Two details people get wrong: use credit sales only, not total sales, because cash sales were never outstanding and including them flatters the number. And keep the period consistent, because a DSO you calculate differently each quarter is a number you cannot manage.

What is a good DSO?

The only honest benchmark is your own payment terms. On net 30, a DSO in the mid-30s means customers are paying roughly on time and your process is working. A DSO of 55 on net 30 means you are financing your customers for an extra 25 days, whatever your aging report says about intentions.

Comparing your DSO to a cross-industry average is close to meaningless, because terms vary enormously: construction and staffing run long, professional services run short. The comparisons worth making are against your own terms, and against your own DSO last quarter. A rule of thumb worth knowing: a DSO more than about 15 days above your standard terms usually indicates a follow-up problem rather than a customer problem.

Nine changes that reduce DSO

1. Follow up on every overdue account, not just the big ones

This is the highest-leverage change available to most finance teams, and it is not a strategy, it is an admission. Manual collections triages. The largest invoices and the angriest customers get chased. The long tail of smaller accounts ages quietly, and in aggregate the tail is usually where the DSO damage is.

A cadence has no favorites. Every overdue account gets the same ladder whether it is $400 or $40,000, which is exactly the thing a human with nine other jobs cannot do.

2. Escalate, do not repeat

Most of what gets recovered is recovered at steps three through six of a sequence, which is precisely where human follow-up stops. The first reminder is easy to send. The fourth requires deciding how firm to be with a customer you would like to keep, so it sits in drafts.

Write the ladder in advance, on a calm afternoon: friendly at day 5, a question at day 15, firm at day 30, final at day 60. The copy for day 60 written three weeks ahead is better than the copy written at 11pm by someone who has had enough.

3. Ask what is blocking payment, not for payment again

Most overdue invoices are stuck, not refused. They are missing a PO number, they went to the person who signed the contract instead of accounts payable, or they are parked in an approval queue. A message that asks "is this waiting on an approval, or is there something I need to fix?" unblocks those accounts weeks faster than a fourth copy of the same demand, because it hands the recipient a task they can actually complete.

4. Invoice immediately and correctly

DSO starts counting at the invoice, not at the work. A week of internal delay before you bill is a week of DSO you created yourself and then blamed on the customer. And an invoice with a wrong PO number, a missing reference, or the wrong entity name does not get queried on day 2. It gets ignored, discovered on day 40, and restarts the clock.

5. Make paying take one click

Every message should carry the invoice number, the amount, and a payment link. The friction you are usually fighting is effort, not refusal. An AP clerk with twelve invoices open pays the one that does not require finding your bank details.

6. Set terms deliberately, then enforce them

If your terms are net 60 because a salesperson agreed to it once in 2019, your DSO cannot go below 60 no matter how well you chase. Look at what your terms actually are across the ledger, and whether anyone ever agreed to them. A late fee clause you never enforce teaches customers your deadlines are decorative, so either apply it consistently or stop pretending it exists.

7. Check credit before you extend it

The cheapest collections problem is the one you decline. A new customer asking for net 60 on a large first order is a credit decision, not a sales formality. This will not fix an existing DSO, but it stops you rebuilding the problem.

8. Stop the chase the moment they pay or dispute

Not a DSO lever exactly, but the reason DSO programs get abandoned. Chasing a customer who paid yesterday is the fastest way to turn an administrative process into an angry phone call, and one of those is usually enough for a team to quietly stop sending reminders altogether. Automate the stop, not just the send.

9. Measure the aging buckets, not just the average

DSO is an average, and averages hide the thing you need to see. One enormous invoice paid early can mask a rotting 90-plus column. Watch the buckets. The past-60 column is where write-offs are born, and it moves before your DSO does, which makes it the better early warning.

What will not reduce DSO

Being honest about the ceiling is worth more than another tactic. No cadence fixes a DSO that is high because your terms are 60 days, your invoices are wrong, or your customers are genuinely insolvent. Automation compresses the gap between the due date and the payment. It does not move the due date, correct a disputed invoice, or create money that is not there.

If your past-due column is small and your DSO is still high, you do not have a collections problem. You have a terms problem, and the fix is commercial rather than operational.

The pattern underneath all nine

A large share of late payment is not dispute and not distress. It is customers managing their own cash, and they pay the vendors who follow up, in roughly the order those vendors follow up. That is uncomfortable but useful, because it means consistency literally moves you up the queue. Not volume. Not aggression. Consistency.

Which is why DSO is so often a process problem wearing a customer problem's clothes. Your team already knows exactly which invoices are late. The aging report has been saying so for weeks. The gap is never information, it is follow-through.

DebtAgent automates the collections half of accounts receivable: you import the aging report your accounting system already produces, set the ladder once, and every overdue account gets worked on schedule in your own name, with contact windows and frequency caps enforced, every touch logged, and the sequence stopping itself the moment someone pays or disputes. Flat monthly fee from $49, no percentage of what comes back. It sits next to your ledger rather than replacing it, because a collections tool that requires migrating your books is a project, not a purchase.

Report the result honestly when you get it. If DSO drops eight days, that is roughly a week of working capital returned to the business, and it is worth showing the board alongside the statements that put it in context rather than as a metric floating on its own.

For the fee comparison against the other common answer to this problem, see how much collection agencies charge.