DSO benchmarks every tech CFO should know in 2026

Days sales outstanding is one of those metrics that every CFO knows and almost no one benchmarks correctly. The number matters—but only relative to your billing model, your customer mix, and the payment terms you've actually agreed to. A company with a 52-day DSO that sells exclusively to enterprise on Net 45 terms is performing well. A company with a 48-day DSO that sells to mid-market on Net 30 terms has a collection problem disguised as a respectable number.

Here's what the data actually looks like for software and technology companies in 2026, and what your DSO is telling you beyond the headline.

Baseline benchmarks by segment

Across the software and technology sector, median DSO ranges break down roughly as follows:

• SMB-focused SaaS: 28–38 days. These companies typically run credit card or ACH on shorter terms, with smaller average contract values that make slow-pay less tolerated and auto-dunning more effective.
• Mid-market SaaS: 42–58 days. Net 30–45 terms are standard; larger deal sizes mean more manual AP processing on the customer side and more tolerance for escalation delay on the vendor side.
• Enterprise SaaS: 55–75 days. Net 45–60 terms are the baseline; enterprise AP workflows add process time, and procurement involvement lengthens every step. Companies with heavy enterprise mix routinely see DSO above 60 even with no delinquency.
• Usage-based / consumption billing: 48–70 days. Variable invoice amounts add a reconciliation step that delays payment independent of delinquency. Customers who need to verify usage data before paying add 10–20 days to every cycle.
• AI infrastructure and GPU compute: 55–80 days. Newer category with less mature AP processes on the customer side; invoice disputes are more frequent due to cost unpredictability.

These ranges assume customers paying with intent. Accounts that are genuinely delinquent—customers who have stopped engaging—are not reflected in these benchmarks, because those accounts have exited the DSO calculation and entered the bad debt category (or they should have).

What's moved DSO higher in 2026

Three forces have pushed average DSO upward over the past 18 months:

Enterprise payment term pressure. Large enterprise buyers have systematically pushed vendors toward longer terms. Net 30 contracts that were renegotiated at renewal have become Net 45 or Net 60. For software vendors with growing enterprise mix, this alone adds 10–15 days to portfolio DSO without a single account going delinquent.

AP automation creating bottlenecks. Counterintuitively, the proliferation of AP automation software on the customer side has slowed some payment cycles. Automated invoice matching systems kick invoices to exception queues when amounts vary from PO, when GL codes aren't pre-configured, or when vendor records don't match. Each exception adds days. Software vendors with unusual billing structures—usage overages, true-ups, multi-SKU orders—hit these exception queues more often than vendors with simple fixed invoices.

Economic uncertainty and internal approval bottlenecks. Finance teams under budget pressure have added approval layers to outgoing payments. An invoice that once required one signature now requires two or three. This isn't delinquency—it's process drag. But it shows up in DSO, and it tends to concentrate in the 45–75 day range.

The number your DSO hides

Standard DSO calculations—accounts receivable divided by average daily revenue—mask two things that matter more than the headline number.

Tail risk: DSO averages across all open receivables. A book where 85% of invoices are paid in 35 days and 15% are at 120+ days will show a "normal" DSO of 55 days. That 15% tail is your bad debt risk. It needs to be tracked separately, not averaged away.

Best-possible DSO gap: If your weighted average payment terms are Net 35 and your DSO is 58, you have a 23-day gap between what your contracts say and what's actually happening. That gap is your collection inefficiency. Most companies don't measure it, which means they don't see the problem until the tail becomes write-offs.

What a healthy AR picture looks like

Rather than optimizing for a single DSO number, the finance teams we see managing AR well track three things simultaneously:

1. DSO as a trend, not a point-in-time number. Month-over-month DSO movement is more informative than the current figure. An upward trend in DSO is an early warning. A stable or declining trend confirms the process is working.
2. Accounts over 90 days as a percentage of total AR. Anything above 8–10% of outstanding AR in the 90+ day bucket signals a structural escalation problem, not a normal collection lag.
3. Average account age at placement. If you're placing accounts with a collection agency or escalating internally at an average of 120+ days, your DSO is being held artificially low by accounts that should have been escalated earlier.

Using benchmarks to make a decision

The purpose of benchmarking isn't to feel good about your number or bad about it—it's to identify whether the gap between your DSO and what it should be represents a process problem worth fixing.

For a mid-market SaaS company with a 68-day DSO against a benchmark of 42–58, the question is: where are those extra 10–26 days coming from? If it's enterprise customer mix and negotiated terms, that's a structural reality. If it's chronic slow-pay from accounts that agreed to Net 30, that's a recoverable problem—and the first step toward recovering it is knowing your number is outside normal range.