If your DSO is above 40, rising, or you do not really track it, the instinct is to stare harder at the aging report. The report is not the problem. DSO is an average of hundreds of small decisions: when the first reminder went out, how long a dispute sat quiet, whether a broken promise got a same-day reply or a three-week one. DSO moves when daily behavior moves.

Controllers who have brought DSO down pull the same six levers. Each one is small on its own. Together they change the slope.

Lever 1: Move the first touch before the due date

Most slow payment is inattention, not resistance. The customer planned to pay, then the invoice slid behind other priorities. A reminder three days before the due date catches that drift when it is cheap to fix, because it reframes your invoice as due soon rather than already late.

Teams that add pre-due reminders usually see their current-bucket payments rise first. That is the DSO win hiding in plain sight: every invoice paid before or on the due date never enters the overdue average at all. The reminder should include the invoice number, the amount, the due date, and a payment link, and it should go out automatically so nobody has to remember it.

Lever 2: Surface disputes in week one, not week six

A quiet dispute is the most expensive kind. The customer found something wrong on the invoice at day 5, said nothing, and your collector kept sending standard follow-ups for a month while the balance aged. By the time anyone asks what is actually wrong, a two-day credit memo fix has become a 60-day collection event.

The lever is a direct question early: "Is there anything about this invoice holding things up?" Ask it at 14 to 21 days overdue, not at 45. And separate dispute handling from payment chasing in your queue. An invoice waiting on a credit memo is not a collections problem; it is an operations problem that needs an owner and a deadline. Controllers who split those two buckets consistently report that their 60-plus bucket shrinks faster than any other segment, because those balances were never going to pay until someone fixed the underlying issue.

Lever 3: Treat a broken promise as the highest-priority event

The customer said Friday. It is now Tuesday, and nothing arrived. This is the highest-leverage moment in collections, because the customer already committed to pay. The follow-up writes itself, and it should go out the same day you notice the miss, not in next week's batch.

Here is why this lever moves DSO: promised dates go stale fast. Every day past a missed promise makes the next touchdown awkward and the customer less certain anyone is watching. Teams that re-touch broken promises within one business day collect on them at far higher rates than teams that roll them into the next weekly review. Log the promise when it is made, flag it the day after it breaks, and make the broken-promise queue the first thing the collector opens each morning.

Lever 4: Work a ranked queue, not the whole aging report

Open the full aging report on a Monday and you will do what every team does: start at the top, work down, and run out of week before you reach the balances that matter. The lever is ranking. Sort the queue by balance times days overdue, keep relationship risk in view, and cap the working list at the accounts that actually move the average.

In practice the top 20 accounts usually hold most of the collectible dollars. Those get personal touches and phone calls. The long tail gets the automated sequence. This is not about ignoring small balances; it is about spending human hours where the math is. A two-person finance team cannot call 300 accounts, but it can call 20. Rank the queue so those 20 are always the right 20.

Lever 5: Remove payment friction a willing customer hits

Some late payments are not decisions at all. They are a missing PO reference, remittance details that changed without notice, a portal login that stopped working, or an invoice that went to someone who left the company six months ago. Every one of these adds a week or more while the customer sorts it out, and every one is your fix, not theirs.

Audit the payment path once a quarter from the customer's side: does every reminder include a working payment link, are remittance details current, and does the AP contact on file still work there? Confirm the recipient before the first touch, not after the second bounce. This lever rarely makes a slide deck, but controllers who pull it often find two or three aging balances that were friction, not reluctance, and those clear almost immediately.

Lever 6: Forecast on promise dates, not due dates

This one closes the loop. A cash forecast built on due dates is fiction; half the inputs are promises the team hopes will land on time. A forecast built on promise dates, weighted by each customer's payment behavior, is an operating tool. And the weekly review of that forecast is itself a DSO lever.

When the controller walks the forecast every week and asks "which of these promises are soft," two things happen. Soft promises get re-touched before they break, which is lever three working upstream. And the team develops a habit of writing down expected dates instead of carrying them in memory, which makes the queue in lever four more accurate. Forecast discipline and collections discipline are the same discipline.

What does not move DSO

Worth naming, because teams spend real time on all of these: redesigning the aging report, making the email language sterner, adding a threat the company will not follow through on, and hiring a second collector to work the same unranked queue. DSO is arithmetic. It moves when invoices get paid sooner, which happens when touches go out earlier, disputes get found faster, and broken promises get chased the same day. Everything else is formatting.

Start this week

You do not need all six at once. Pick one. The usual first move is the ranked Monday queue, because it costs nothing and it makes every hour the team already spends more effective. Add pre-due reminders second, then same-day broken-promise follow-up. Measure DSO monthly, not weekly; the number is noisy at small scale and the trend is the signal. Three months of a falling trend is a collections function that works.

Frequently asked questions

What is a good DSO for a B2B SaaS or services company?

It depends on your payment terms, but most controllers treat anything above 40 days as a warning sign and anything above 55 as an active problem. Compare DSO against your contracted terms first: a DSO of 45 on net-30 terms means you are collecting 15 days late on average. Track the trend alongside the absolute number, because a rising DSO is the earlier and more useful signal.

Which lever lowers DSO the fastest?

Chasing broken promises the same day usually produces the fastest cash movement, because it targets money the customer already committed to pay. Ranked daily queues come next, because they focus your limited hours on the balances that move the average. Earlier first touches and dispute triage pay off over a full quarter.

Can I lower DSO without hiring more collections staff?

Yes. Most lean teams lower DSO by changing when and how work happens rather than adding headcount: pre-due reminders that run automatically, a ranked queue so the hours you already spend go to the highest-impact accounts, and same-day broken-promise follow-up. Headcount helps only after the queue is disciplined.

Turn a reminder into a repeatable workflow.

See overdue invoices and prepare your next follow-up in Nomen.

Get started