What is days sales outstanding (DSO)?

Days sales outstanding (DSO) measures the average number of days it takes a company to collect payment after a sale. The DSO meaning comes down to how long earned revenue sits in accounts receivable (AR) before it turns into cash.

A longer DSO ties up cash the business has earned but can’t use, and a shorter DSO means billing and collection are converting sales to cash faster. For a growing company, an increasing DSO is one of the first signs that the billing process isn’t scaling with revenue.

Why days sales outstanding matters

Let’s say a company with $3 million in quarterly revenue and a DSO of 45 days has roughly $1.5 million tied up in receivables at any given time. If DSO increases to 60 days, that number rises to $2 million, which leaves $500,000 in cash the business can’t deploy. The company hasn’t lost any revenue or watched a customer default. Collection just got slower, and the slowdown turned into a working capital gap.

Without tracking DSO, that gap grows unnoticed. With it, finance sees the number increasing and can act before it compounds.

How is days sales outstanding calculated?

Days sales outstanding is calculated by dividing accounts receivable by total credit sales and multiplying the result by the number of days in the period. Here’s the DSO formula:

To see how to calculate DSO in practice, let’s say a company has $500,000 in accounts receivable and $1.5 million credit sales for a 90-day quarter. The DSO calculation is as follows: 

Now say receivables grow to $750,000 while quarterly credit sales stay at $1.5 million. The days sales outstanding formula gives us:

Sales didn’t change, but customers now take 15 days longer to pay. Teams calculate DSO monthly, quarterly or annually, using 30, 90 or 365 days. Monthly DSO catches changes quickly but swings with billing timing, while quarterly DSO calculations smooths those swings for trend reporting and annual DSO suits long-term comparisons. What counts as a good DSO depends on payment terms and industry, so teams compare their number against their own terms and prior periods before looking at outside benchmarks.

Why teams struggle with days sales outstanding

A high DSO can come from collection problems or from the billing process itself, and the formula can’t tell the two apart. Here’s why some teams might struggle with it:

• Late invoicing inflates DSO without a collection problem. If invoices go out a week after the service period starts, DSO includes that delay. The customer is paying on time, but the business is billing late.
• Inconsistent payment terms distort the average. Using net 15 for one customer segment and net 60 for another produces a blended DSO that hides what’s happening inside each segment.
• Manual cash application slows the clock. If a payment arrives and sits unallocated for three days while someone matches it to the right invoice, the clock is still running until the payment is applied.
• Contract amendments create billing gaps. When an upgrade goes unbilled for two weeks because the billing system couldn’t modify the active contract, it causes some revenue leakage. DSO increases because there was nothing for the customer to pay yet.
• DSO benchmarks without segment analysis are misleading. A company-wide DSO of 40 days can hide one segment at 15 days and another at 75. Acting on the average means optimizing the wrong group.

How teams improve days sales outstanding

Reducing DSO starts with finding where receivables stall, and accounts receivable aging shows which invoices are running late. Here’s how finance teams reduce DSO and improve it over time:

1. Automate invoice generation: Invoices go out on the billing date, not the day someone remembers, so the DSO clock starts when it should.
2. Standardize payment terms by segment: Setting terms at the contract level means they’re enforced automatically instead of negotiated invoice by invoice, which keeps the blended number meaningful.
3. Automate dunning and payment reminders: Reminders and escalations run on a schedule instead of waiting for the AR clerk to find time, so late payers hear from you early.
4. Automate cash application: Payments match to invoices as they clear instead of in a weekly batch, so DSO stops counting on the day cash arrives.
5. Track DSO by customer segment: Break the company-wide number into groups such as enterprise versus mid-market, domestic versus international or recurring versus project, and target the segment driving the increase.
6. Connect billing to collection: When the billing event triggers the collection workflow automatically, the gap between invoiced and payment follow-up closes.

How ZoneBilling reduces days sales outstanding for NetSuite teams

ZoneBilling automates invoicing inside NetSuite for subscription, usage-based, milestone and hybrid billing on configurable rules. When invoices go out on schedule with the right terms, the DSO clock starts on time instead of lagging behind delivery. ZonePayments connects Stripe for automated AR collection, recording payments and updating the aging report as they clear.

• Invoice on schedule: ZoneBilling generates and sends invoices inside NetSuite on the billing date, which closes the late-invoicing gap that inflates DSO.
• Collect automatically: ZonePayments handles Stripe-based AR collection, matching payments to invoices and recording them in NetSuite without manual cash application.
• Track DSO with trusted data: Billing, invoicing, collection and revenue recognition run inside NetSuite, so DSO reporting draws on one system of record with no reconciliation between platforms.