DSO is calculated as accounts receivable divided by total credit sales, multiplied by the number of days in the period measured. The number itself is simple; diagnosing why it's moving is the harder part, since invoicing delays, collections gaps, and payment-matching backlogs all show up as the same upward trend.
What's considered a good DSO?
It depends heavily on industry and payment terms. A company with net-30 terms and a DSO close to 30 to 35 days is collecting close to on schedule; a DSO significantly higher than the stated terms signals a collections or invoicing problem worth investigating.
How does DSO relate to days payable outstanding?
Both are components of the cash conversion cycle. DSO measures collection speed from customers; DPO measures payment speed to suppliers. Together they determine how long cash is tied up between paying for inputs and collecting from sales.
Can AR automation reduce DSO?
Yes. The two biggest levers are faster, more accurate cash application, so payments that already arrived get recognized without delay, and more consistent collections outreach on past-due accounts, so fewer invoices drift into the 60-plus-day range.
Does a rising DSO always mean customers are paying slower?
No. It can also reflect internal issues: invoices going out late, billing errors that trigger disputes, or a cash application backlog where payments have arrived but haven't been matched to the right invoice yet. Breaking DSO down by cause is more useful than tracking the headline number alone.
How often should DSO be measured?
Most finance teams track DSO monthly alongside AR aging reports, watching for trend direction over several periods rather than reacting to a single month's fluctuation, which can be skewed by one large late payment.
How does DSO connect to cash flow forecasting?
DSO shows what portion of booked revenue is sitting in receivables versus already collected, which forecasting models use to project when reported revenue actually converts to usable cash.