What DSO measures and how to reduce it.

Days sales outstanding, or DSO, estimates how long a business takes to convert invoiced revenue into collected cash. It compresses thousands of payment events into one directional measure. It is also easy to misuse. The headline number tells you that cash is moving faster or slower; it does not tell you why.

Start with the formula, then add context

A common calculation is ending accounts receivable divided by relevant sales for the period, multiplied by the number of days in that period. If receivables are $300,000, sales are $900,000, and the period is 90 days, DSO is 30 days.

Compare that result with the payment expectations built into your invoices and customer agreements. A 30-day DSO may be strong for one portfolio and weak for another. Seasonality, rapid revenue growth, and a large invoice near period end can also move the number without indicating a collections failure.

Find what the average is hiding

Two businesses can report the same DSO and have different problems. One may have a healthy core portfolio plus one large disputed account. Another may have hundreds of small invoices drifting into older aging buckets. Break the number into views that point toward action:

• Aging bucket: current, 1–30, 31–60, 61–90, and 90-plus days.
• Customer segment: size, industry, geography, billing model, or account owner.
• Invoice cohort: invoices issued in the same week or month, followed until payment.
• Reason code: no response, missing documentation, dispute, wrong contact, approval delay, or promise missed.
• Channel history: how many messages and calls occurred before a useful response.

Cohort analysis is particularly helpful in a growing company because it shows whether recent invoices are being collected more reliably even when total receivables are rising.

Reduce preventable delay before collections begins

DSO often starts increasing before an invoice becomes overdue. Late invoice creation, an incorrect billing contact, unclear supporting documents, or a missing purchase order can consume days before follow-up has any chance to work. Start with operational hygiene:

1. Issue the invoice promptly and confirm it reached the correct person.
2. Include the information the customer needs to approve it without another exchange.
3. Record known account requirements before the due date.
4. Give every open invoice an owner, a state, and a next action.

Escalate based on evidence

A fixed cadence creates consistency, but the channel should change when the account stops moving. Early reminders are useful for confirming receipt and making the due date visible. Once the customer is silent, another version of the same email often produces the same result. A call can reveal whether the issue is approval timing, a missing document, a dispute, or simple inattention.

Voice matters because it can create a commitment in real time. The useful output is not “call completed.” It is “controller releases payment Friday,” “statement requested,” “invoice disputed,” or “wrong contact.” Each result should update the queue and determine the next action.

Manage promises as carefully as invoices

A promise to pay is only valuable when it has a date, an owner, and a follow-up rule. Track promises due today, promises kept, promises missed, and accounts that repeatedly move the date. Missed promises are stronger escalation signals than invoice age alone because the customer has acknowledged the balance and failed to complete an agreed action.

Use a small operating scorecard

• Percentage of receivables in older aging buckets.
• Time from overdue status to first meaningful response.
• Commitments captured and commitments kept.
• Value and count of unresolved disputes.
• Invoices with no owner or no scheduled next action.
• Cash collected by invoice cohort and customer segment.

A practical 30-day improvement plan

In week one, establish the baseline and identify the oldest, largest, and most silent accounts. In week two, fix contact data and documentation gaps, then define a clear escalation policy. In week three, work a controlled queue with coordinated reminders and calls. In week four, review which interventions produced commitments and which accounts still need commercial judgment.

The goal is not simply a lower DSO number. The goal is a receivables operation in which fewer invoices drift, useful conversations happen earlier, and finance can explain what will happen next.