By Vaibhav Rane, Founder, Cresolv One
The most expensive money in your business is the cash you've already earned but haven't collected. It's already yours. Until it lands, you're financing your customers — for free.
That gap has a name: Days Sales Outstanding. And when DSO creeps up, the instinct is to blame customers who pay slowly or a collections team that's stretched too thin. In my experience reviewing finance functions, that's rarely the real story. A high DSO is usually not a customer problem or a headcount problem. It's a process problem — invoices sent late, follow-ups that depend on someone remembering, and disputes no one can see until they're old.
The good news about a process problem is that you can fix it with controls, not hires. Here are the three levers that move DSO the most.
The DSO clock starts the moment you could have invoiced — not the moment you actually do. Every day between "work delivered" and "invoice issued" is a day of collection you gave away before a customer ever saw the bill.
Two things quietly stretch that gap. The first is delay: invoices batched to month-end, waiting on someone to assemble details, or stuck behind an internal approval. The second, and more damaging, is error. An invoice with the wrong PO number, a missing tax detail, or a quantity that doesn't match the delivery doesn't just get paid late — it gets disputed, and a disputed invoice can age for weeks before anyone treats it as a problem.
The control here is to make correct, complete invoicing automatic and immediate: generate the invoice as soon as the trigger event happens, validate it against the order and the delivery before it goes out, and catch the errors that cause disputes before the customer does. Getting the invoice out a week earlier and right the first time is the single biggest lever most teams leave untouched.
Ask a stretched finance team how collections follow-up happens and the honest answer is often "when someone gets to it." Reminders go out when a person remembers, in the order they remember, with the accounts that shout loudest getting attention and the quiet-but-large ones slipping.
Collections that depend on memory don't scale and don't hold up under pressure — which is exactly when DSO climbs. The fix isn't more people; it's a defined cadence that runs whether or not anyone remembers: a polite nudge before due date, a firm reminder on the day, a structured escalation after. Consistent, scheduled, and logged — so every account gets the same disciplined follow-up and your team spends its time on the conversations that actually need a human, not on remembering to send the first three emails.
This is where automation earns its keep on the receivables side: not replacing the relationship, but making sure the routine chase never gets forgotten.
The invoices that wreck DSO aren't usually the ones a customer is refusing to pay. They're the ones stuck in a quiet disagreement no one has flagged — a pricing query, a short delivery, a missing reference — sitting in an inbox while the aging counter ticks.
A dispute you can't see is a dispute you can't resolve. The control is to make disputes a tracked, owned, visible item the moment they arise: logged against the invoice, assigned to someone, with a clock on them — so a query raised on day 3 is resolved in days, not discovered at day 45 during an aging review. When disputes are visible, they get closed. When they're invisible, they become the tail of overdue receivables that drags your average out.
Notice what these levers have in common. None of them is about chasing customers harder, and none requires more headcount. Each one closes a gap where cash leaks out of a process: the gap before the invoice goes out, the gap where follow-up depends on memory, and the gap where a dispute hides. Tighten those three loops and the cash was there all along — you were just financing your customers while it sat in someone else's account.
That's the shift from collections-as-effort to collections-as-control: instead of a team working harder every month-end, a system that bills on time, follows up on schedule, and never lets a dispute disappear.
Cresolv One's AR automation is built around exactly these controls — accurate invoicing, a systematic follow-up cadence, and dispute visibility — integrated with your existing ERP rather than replacing it, and designed by people who've run these functions.
So the question worth sitting with: what's your DSO today versus where it should be — and of those three gaps, which one is quietly costing you the most?
See where your process stands with the readiness assessment: cresolv.com/digital-readiness — or explore AR Automation.