How to reduce DSO: a step-by-step playbook
Reducing days sales outstanding comes down to a handful of operational levers. This playbook walks the steps that pull DSO down and keep it there.
Days sales outstanding (DSO) is the average number of days it takes to collect cash after a sale. A high DSO ties up working capital, distorts your forecast, and forces the business to fund its own growth. Lowering it does not require a new strategy. It comes down to a handful of operational levers, applied consistently, in the gaps between billing and collection.
The steps below are ordered by speed of payoff. The early ones move the number within a cycle or two. The later ones compound over a quarter.
The playbook
-
Fix invoice accuracy first. A wrong invoice does not get paid, it gets disputed, and a dispute can sit for weeks before anyone resolves it. Check that every invoice carries the right amount, the correct contact, the PO number the customer's portal requires, and the terms you agreed to. Accuracy at the source removes a whole class of delay that no amount of chasing can recover.
-
Bill the moment you can. Every day between delivery and invoice is a day added to DSO before the clock even starts. Tie invoicing to the fulfillment event so the bill goes out the same day the product ships or the service is accepted. The faster the invoice lands, the sooner the due date arrives.
-
Run a real collections cadence. Most teams chase by memory, which means they chase late and unevenly. Define a fixed sequence: a reminder before the due date, a prompt on the day, then escalating follow-ups at set intervals after. Automate the routine touches so the team's time goes to the accounts that actually need a conversation. Consistency matters more than tone.
-
Automate cash application. Payments that sit unmatched in a suspense account inflate DSO even though the money has arrived. Match incoming payments to open invoices automatically, including partial payments and remittances that come in separately from the funds. Clean application also means your aging report reflects reality, so the team chases what is genuinely overdue instead of what already paid.
-
Surface disputes early and route them fast. A dispute discovered on day 45 is a month of DSO you will never get back. Watch the inbox for short pays, deductions, and complaints, flag them the moment they appear, and route each one to the owner who can resolve it. Pause the collections sequence on disputed invoices so you are not chasing money that is legitimately on hold.
-
Set clear credit terms and enforce them. DSO problems often start before the invoice, in terms that were never stated plainly or never checked. Run a credit check at order capture, put terms in writing, and make the due date unmistakable on every invoice. Where it fits, offer a small early-payment discount to pull cash forward, and hold firm on limits for accounts that consistently pay late.
Measure the right way
Track DSO monthly, but read it alongside the inputs that drive it: invoice accuracy, dispute rate, and the share of cash applied automatically. A single DSO number tells you the cycle is slow. The inputs tell you where. If accuracy is high and DSO is still climbing, the problem is cadence. If cash sits unapplied, the problem is reconciliation. Diagnose before you push harder.
Use the count-back method rather than a simple average so the figure reflects current collection behavior instead of smoothing over a slow month. Watch the trend, not any single reading.
Where the leverage compounds
The steps above each help on their own. They compound when they connect. The same system that reads a dispute should pause the dunning sequence and route the case. The same system that applies a payment should update the aging report. When those handoffs stop being manual, the gaps where DSO leaks simply close.
This is where agentic automation earns its place. A platform like Rex carries the cycle from invoice to applied cash, handling the routine work and stopping only when a case needs a human decision. The team moves from sending reminders and matching payments to managing the exceptions and the relationships that actually move the number.
Start with invoice accuracy and a real cadence, because those pay off this quarter. Then connect the steps so the gains hold.
Frequently asked questions
- What is a good DSO?
- A good DSO sits close to your stated payment terms. If you bill net 30 and your DSO is 35, you are collecting efficiently. A DSO well above terms signals friction somewhere between the invoice and the payment, usually in billing accuracy or collections cadence.
- How quickly can you reduce DSO?
- The fastest gains come from invoice accuracy and a consistent collections cadence, which can move DSO within one or two billing cycles. Structural changes, like tightening credit terms or automating cash application, compound over a quarter or two.
- Does reducing DSO hurt customer relationships?
- No, when done well it improves them. Most late payment comes from confusion, not unwillingness: a wrong invoice, an unclear due date, or outreach that arrives too late. Clear invoices and steady, polite reminders remove friction rather than create it.