The short answer
DSO (days sales outstanding) measures how long revenue takes to turn into cash: (accounts receivable ÷ credit sales) × days in period. To reduce it, fix the causes in order — invoice accurately and immediately, apply cash promptly so your ageing is true, resolve disputes with a named owner and a deadline, and run collections as a scheduled process rather than a month-end scramble. Chasing customers harder is the weakest lever and the one most teams reach for first.
Key takeaways
- DSO = (accounts receivable ÷ credit sales) × number of days in the period.
- Days-to-invoice is pure self-inflicted delay and the cheapest thing to fix.
- Unapplied cash inflates DSO artificially and makes you chase customers who have already paid.
- A disputed invoice is not a late payment. It is a billing error, and chasing will not clear it.
- Consistency beats intensity: a mediocre collections process run every week outperforms an excellent one run occasionally.
How do you calculate DSO?
The standard formula is straightforward:
DSO = (Accounts receivable ÷ credit sales) × number of days in the period
For a month with $900,000 of receivables and $1,000,000 of credit sales across 30 days, DSO is (900,000 ÷ 1,000,000) × 30 = 27 days.
Two cautions. Use credit sales rather than total sales, or cash sales will flatter the result. And a single month's DSO is noisy in a seasonal business — a rolling three-month view usually tells a more honest story than any individual month.
Comparing your DSO to your payment terms is more useful than comparing it to any external benchmark. If your terms are 30 days and your DSO is 27, you are doing well. If your terms are 30 and DSO is 58, you have a 28-day problem to explain.
Why is your DSO high? Diagnose before you chase
Run this before you spend a single hour on collections calls. The order matters, because fixing a later cause without fixing an earlier one gets you nowhere.
| Check | If yes | Lever |
|---|---|---|
| Are invoices going out days after delivery? | You are adding delay before the customer sees anything | Invoice on delivery, daily not monthly |
| Are invoices being disputed or short-paid? | This is a billing accuracy problem | Fix invoice data, PO references and format |
| Is there a large unapplied cash balance? | Your ageing is not true | Cash application discipline |
| Do overdue accounts have no contact history? | Nobody is actually chasing | A scheduled collections process |
| Are the same customers always late? | Terms or credit limits are the issue | Credit management, not collections |
| Are disputes sitting unowned? | They will age into credit notes | Named owner and a deadline per dispute |
The single most common mistake is treating a billing problem as a collections problem. If a customer disputes an invoice, they are not choosing to pay late — they are telling you the invoice is wrong. More calls will not fix an incorrect invoice.
What actually reduces DSO, in order of impact?
- Invoice immediately and accurately. Every day between delivery and invoice is a day of DSO you gave away. Match the customer's PO number, line descriptions and format exactly, and submit into their portal if they use one.
- Apply cash promptly. Chase remittance advice as routine. Unapplied cash both overstates DSO and wastes collections effort on customers who have already paid.
- Own disputes. Every dispute gets a name and a date. Unowned disputes age quietly and are usually written off eventually.
- Run collections on a schedule. Segment by value and risk, define the contact sequence per segment, and work it every week without exception.
- Set credit properly at the start. Limits and terms agreed before the sale prevent the problem rather than managing it.
- Make terms easy to comply with. Clear payment instructions, the right contact, a portal submission where required, and an easy payment method.
What does a good collections process look like?
Predictable, segmented and logged. The aim is that no overdue account goes a week without a defined action, and that nobody has to decide from scratch what to do.
Segment first
Not every account deserves the same attention. Split by balance size and by risk, and give the highest-value or highest-risk accounts a more personal, earlier sequence.
Define the sequence
For each segment, write out what happens and when: a reminder before due date, contact shortly after, escalation to a named person, then a defined commercial escalation. Written down, so it happens whether or not the usual person is at their desk.
Log everything
Every contact recorded against the account, with what was promised and by whom. Without this, each conversation starts from zero and customers learn that promises are not tracked.
Escalate on triggers, not on mood
Agree in advance what causes escalation — days overdue, balance size, a broken payment promise — so escalation is a rule rather than a judgment about how annoyed someone is.
How do you chase without damaging the relationship?
Most relationship damage comes from inconsistency and inaccuracy, not from persistence. Being chased for an invoice already paid, or for a disputed amount that nobody investigated, is what makes customers angry. Being contacted predictably about a genuinely overdue balance rarely does.
- Get the facts right before contact. Confirm the invoice is correct and no payment is sitting unapplied.
- Lead by asking whether there is a problem with the invoice, rather than by asserting lateness.
- Keep the routine contact administrative and the escalation commercial, with commercial conversations handled by someone who owns the relationship.
- Separate roles: the person chasing routinely should not be the person negotiating a settlement.
That last point is why collections outsources well. The scheduled, administrative follow-up is process work that benefits from being done consistently. The commercial conversation is yours and should stay yours.
Which metrics should you watch alongside DSO?
DSO alone will mislead you, because it moves for reasons that have nothing to do with collections performance — a large late-month sale raises it without anything going wrong.
- Days to invoice. Delay entirely within your control.
- Invoice accuracy rate. The leading indicator of future disputes.
- Dispute rate and average dispute age. Where cash silently gets stuck.
- Unapplied cash. Proves whether your ageing can be trusted.
- Collection effectiveness index. Performance against what was actually collectable.
- Ageing bucket movement. Whether balances are moving forward or ageing in place.
Track these together and the story becomes legible: rising DSO with a rising dispute rate is a billing problem, while rising DSO with clean invoices and stale contact history is a collections resourcing problem. They need completely different responses.
Frequently asked questions
What is DSO and how is it calculated?
Days sales outstanding measures the average time to collect payment after a sale. The formula is (accounts receivable ÷ credit sales) × number of days in the period. Use credit sales rather than total sales, and prefer a rolling three-month view in seasonal businesses.
What is a good DSO?
The most useful comparison is against your own payment terms rather than an external benchmark. DSO close to your stated terms means the process is working; DSO substantially above them quantifies the problem. Terms and industry norms vary too widely for a single target to be meaningful.
How can I reduce DSO quickly?
Start with days-to-invoice, because it is entirely within your control and costs nothing to fix. Then clear unapplied cash so your ageing is accurate, and put a named owner and deadline on every open dispute. Those three usually move the number before any additional chasing does.
Does chasing customers harder reduce DSO?
Less than people expect, and it is usually the wrong first move. If invoices are inaccurate or cash is unapplied, chasing does not release the money and damages the relationship. Consistent scheduled follow-up on genuinely overdue, accurate invoices is what works.
Should collections be outsourced?
The routine, scheduled part outsources well because it rewards consistency: reminders, follow-up sequences, logging and dispute administration. Credit decisions, settlement negotiations and relationship-sensitive escalations should stay with your own team.