Days Sales Outstanding — DSO — is the one AR metric that tells you, in a single number, how long it takes your business to collect cash after a sale closes. If you run a B2B company and you're not tracking this weekly, you're navigating without a speedometer.
I've talked with enough AR managers and CFOs to know the pattern: DSO climbs slowly for months, nobody notices until it's 15 days worse than last quarter, and then the CFO is demanding answers while the AR team is already overwhelmed. The number doesn't lie. The problem is that most teams check it monthly — or only when something goes wrong.
The formula (and why two versions exist)
The standard DSO formula is straightforward:
DSO = (Accounts Receivable Balance ÷ Total Credit Sales) × Number of Days
If your ending AR balance is $2.4M, your credit sales over the past 90 days were $6M, and your period is 90 days:
DSO = ($2.4M ÷ $6M) × 90 = 36 days
That's the countback method — clean, fast, widely used. The problem is it's sensitive to revenue seasonality. If your last month had unusually high sales, the denominator inflates and DSO looks artificially good. If sales dipped, DSO looks worse than it is.
The more accurate version is the rolling average DSO, calculated using 12 months of data to smooth out seasonal swings. For mid-market companies with any revenue cyclicality — manufacturing, distribution, professional services — the rolling average is more reliable for trend-spotting.
Either way, the number only means something if you're comparing it to the same period last year and against your standard payment terms. A DSO of 42 days on net-30 terms is a problem. A DSO of 42 days on net-60 terms means you're collecting early.
What the benchmarks actually say
Industry DSO benchmarks vary significantly by sector, but here are realistic reference points for mid-market B2B:
- Manufacturing and distribution: 45–65 days
- Professional services (B2B): 40–55 days
- Software and SaaS (B2B): 30–45 days
- Staffing and recruiting: 50–70 days
- Construction and contracting: 60–85 days
We're not saying these benchmarks are targets to hit. They're context for understanding whether you have a structural problem or just a bad quarter. A mid-market distributor at 80 days DSO in an industry that runs 60 has a 20-day cash gap that deserves a serious investigation.
The components hiding inside your DSO
One of the most useful things you can do with DSO is decompose it into two parts: Best Possible DSO (BPDSO) and the Delinquent DSO.
Best Possible DSO is what your DSO would be if every customer paid exactly on their due date — it represents your terms, not your collection performance. If your average payment terms are net-45, your BPDSO is roughly 45.
Delinquent DSO is the difference: DSO − BPDSO. This is the number your AR team owns. If your total DSO is 67 and your BPDSO is 45, you have 22 days of delinquent DSO. That's the gap between what customers agreed to and when they're actually paying.
That 22-day number is where collections automation lives. A CFO who sees their DSO at 67 knows they have a problem. An AR manager who knows their delinquent DSO is 22 days — and can see which customer segments are driving it — knows exactly where to focus.
Why weekly tracking catches problems monthly tracking misses
Here's a scenario that plays out at a lot of growing mid-market companies. A regional industrial services firm — let's say they're in the $50M revenue range, selling to contractors and property managers — runs AR with two people. Monthly DSO reports go to the CFO. In Q3, a cluster of their larger accounts starts paying on net-60 when terms are net-30. Nobody catches it for six weeks because the monthly report only shows the aggregate number, and a few late payments don't move the total much yet.
By the time the October report lands on the CFO's desk showing DSO up 18 days from August, those accounts are now 75–90 days past due. The window for a friendly payment reminder has closed. They're in escalation territory — which means tighter credit terms going forward, strained relationships, and some percentage of that cash genuinely at risk.
Weekly DSO tracking would have flagged the drift in September, when those accounts were 3–4 weeks past due instead of 8–10. The remediation conversation is different at that point.
What causes DSO to climb — and what doesn't fix it
DSO rises for a few distinct reasons, and conflating them leads to the wrong remediation:
1. Customer-side cash flow pressure. Your customers are having their own liquidity problems and delaying payables. No AR automation fixes this — but early identification lets you get in queue before other vendors.
2. Billing process failures. Invoices going out late, to the wrong contact, with wrong PO numbers, or missing required documentation. These create "legitimate dispute" delays where the customer won't pay until the error is fixed. This is an internal process problem, not a collections problem.
3. Weak or inconsistent follow-up. This is the most common cause for mid-market companies, and it's the most fixable. When a 3-person AR team is managing 400+ open invoices, the follow-up process is inevitably inconsistent. Some accounts get chased promptly. Many don't get a second email until they're 45+ days past due. Generic reminder templates generate generic response rates.
4. No escalation logic. Related to #3 — even when follow-up is consistent, there's no clear rule for when an account gets escalated from automated outreach to a human call. The result is that some accounts stay in email limbo for weeks before someone realizes they've gone silent.
Most companies trying to improve DSO focus exclusively on sending more reminders. That addresses part of cause #3 but ignores the underlying question: are the right accounts getting the right treatment at the right time?
DSO as a leading indicator, not a lagging one
The CFOs who use DSO most effectively treat it as a predictive signal, not just an accounting output. When DSO starts rising before quarter-end, it often signals that the sales team closed deals with customers who have longer payment cycles — or that a segment of the customer base is under financial stress.
Layering payment probability data on top of your DSO trend — which accounts are statistically likely to extend their terms based on historical behavior — turns a backward-looking metric into a forward-looking one. Instead of reporting "DSO went up 8 days last month," you're saying "We have $340K in invoices from accounts with a 70%+ probability of going 30+ days past due — here's the proactive plan."
That shift — from reporting to predicting — is what separates AR teams that are always reacting to the number from AR teams that manage it proactively. The weekly DSO check is the foundation. The payment behavior analysis is what makes it actionable.
A practical weekly DSO routine
For most mid-market finance teams, a useful weekly DSO review takes about 20 minutes if the data is accessible. The questions worth answering each week:
- What is the current DSO versus same period last week, last month, and last year?
- Which aging bucket grew the most? (30–60 days, 60–90 days, 90+ days)
- Which customers account for the largest dollar value moving into the 30+ day bucket this week?
- How many invoices moved from current to past-due without any follow-up contact?
- What is the collection rate this week — invoices resolved as a percentage of invoices due?
That last metric — collection rate — is the operational complement to DSO. DSO tells you the state of your AR. Collection rate tells you how efficiently your team is working it down. Both numbers, tracked together weekly, give a CFO and AR manager the picture they need to stay ahead of cash flow problems rather than discover them too late.
The companies we see managing DSO tightest aren't the ones with the best customers. They're the ones that made AR visibility a non-negotiable weekly discipline rather than a quarterly accounting exercise.