How to reduce DSO and free up cash fast

Reducing days sales outstanding frees up cash you have already earned but not yet collected. Every day of DSO equals one day of revenue parked in receivables, so cutting DSO converts that parked revenue into cash you can use, with no new sales and no new financing. The levers are operational and the first ones pay off within a billing cycle.

DSO is the average number of days it takes to collect after a sale. It is the most direct measure of how fast your receivables turn into cash, and the part of the cash conversion cycle you control end to end.

What a high DSO costs your business

Put a number on it. The formula for cash tied up is simple:

Cash in receivables = (Annual revenue / 365) x DSO

A business at $50 million revenue with a DSO of 55 days has about $7.5 million sitting in receivables. Cut DSO to 45 days and you release roughly $1.4 million in cash, permanently. That is cash you stop financing with a credit line and start holding in your account.

The cost is not just the financing. A high DSO distorts your forecast, because cash you booked as a sale has not arrived. It forces the business to fund its own growth out of reserves. And it correlates with risk: the longer invoices age, the less likely they are to ever collect. A high DSO is rarely just slow; it is expensive and risky at the same time.

Read your number against your terms before you read it against anyone else. A DSO of 45 on net 30 terms is a 15-day collection gap, which is healthy. A DSO of 45 on net 60 terms means you are collecting ahead of schedule. The gap between DSO and stated terms, not the raw number, tells you whether you have a problem. It also helps to know where your peers sit; the DSO benchmarks by industry put your figure in context.

Why DSO creeps up

DSO almost never jumps. It drifts, a day or two a month, until the number is suddenly twenty points over terms. The drift comes from gaps in the process, not from customers deciding to pay slower:

• Reminders go out late. Cadence that depends on memory slips, so invoices reach 60 days before anyone chases them.
• Invoices are wrong. A dispute freezes the invoice while the clock keeps running.
• Disputes sit unresolved. A short pay nobody picks up holds the whole invoice hostage.
• Cash lands unapplied. Payments stuck in suspense make paid invoices look overdue, so the team chases the wrong accounts and misses the real ones.

Each gap adds days. The fix is to close the gaps, in order of payoff.

The levers that pull DSO down

These are ordered by speed of return. The early ones move the number this quarter:

1. Fix invoice accuracy first. A wrong invoice is disputed, not paid. Confirm the amount, contact, PO number, and terms on every invoice before it goes out.
2. Bill the moment you can. Every day between delivery and invoice is added to DSO before the clock starts. Tie billing to fulfillment.
3. Run a real collections cadence. A reminder before the due date, a prompt on the day, escalating follow-ups at fixed intervals after. Consistency matters more than tone.
4. Apply cash automatically. Match payments to invoices as they arrive, including partials and separate remittances, so the aging report reflects reality.
5. Surface disputes early. Flag short pays and deductions the moment they appear, route them to an owner, and pause chasing on what is legitimately on hold.
6. Tighten credit terms. Set limits on how customers actually pay, put terms in writing, and make the due date unmistakable.

To see how the freed cash flows into the wider balance sheet, read how to unlock cash trapped in your receivables.

Sequence matters as much as the list. Fix accuracy before you push cadence, because chasing wrong invoices harder just generates disputes. Get cadence steady before you tighten credit, because terms only help when you enforce them on time. And apply cash cleanly throughout, or every other number you read will be wrong. Pull the levers in order and each one makes the next more effective. Pull them out of order and you create work without moving the number.

Consistency is the hidden driver

Here is what most DSO programs miss. The levers above are not hard to understand. They are hard to sustain. The reminder that should go out on day three goes out on day twelve, not because anyone failed, but because consistency across hundreds of accounts, every day, is more than a person can hold while doing everything else.

The teams with low DSO are not working harder. They have removed the dependence on memory. Every account gets the right touch at the right time, every time, with no slow weeks and no forgotten follow-ups. Consistency, not effort, is what pulls DSO down and keeps it there.

You can see this in how DSO behaves over a year. A team that runs hard at quarter-end and coasts in between produces a sawtooth: DSO drops in March, drifts up through April and May, drops again in June. The average is mediocre and the cash is unpredictable. A team that works every account every cycle produces a flat, low line. Same total effort, very different result, because the effort is spread evenly instead of bunched. The quarter-end sprint feels productive and accomplishes less than steady coverage that nobody notices.

This is also why throwing people at DSO has limits. A second collector adds capacity, but capacity used inconsistently still leaks. The constraint is rarely how many accounts you can touch in a good week. It is whether every account gets touched in every week, including the busy ones, the short-staffed ones, and the weeks when something more urgent comes up.

Reducing DSO with an AI AR agent

This is where an agentic AR system changes the math. Rex runs the collections cadence continuously across the entire ledger. It sends the right reminder at the right time to each account, never late, never skipped, because it does not depend on anyone remembering. It reads replies to tell a dispute from a payment promise, pauses outreach where an invoice is on hold, applies cash as it lands so the aging stays accurate, and escalates only the accounts that need a human decision.

The result is the consistency that drives DSO down, sustained across every account at once. Your team stops sending reminders and matching payments and starts working the exceptions and the relationships that actually need judgment. DSO falls because the gaps where it used to creep are simply closed.

What makes the drop durable is that it does not rely on anyone keeping up the pace. A manual program improves DSO for as long as the team has the bandwidth to sustain it, then slips back the first busy month. An automated cadence has no busy month. The day-three reminder still goes out on day three in December and in the middle of close, which is exactly when a stretched team would have let it slide. The cash you free this quarter is still freed next quarter, because the mechanism that freed it never takes a week off.

Track the cash you free up

Measure DSO monthly, but read it alongside its inputs: invoice accuracy, dispute rate, and the share of cash applied automatically. If accuracy is high and DSO still climbs, the problem is cadence. If cash sits unapplied, the problem is reconciliation. Watch the trend, not any single reading, and translate every day of DSO you cut back into the cash it puts on your balance sheet. The working capital metrics that sit alongside DSO tell you whether the freed cash is staying freed.

Use the count-back method rather than a simple average so the figure reflects current collection behavior instead of smoothing over a slow month. And report the result the way the business will feel it: not "DSO fell four days" but "we freed roughly $550,000 in cash." The days are the mechanism; the cash is the point.

See how Rex drives DSO down with collections that never miss a follow-up.