We use cookies to provide visitors with the best possible experience on our website. These include analytics and targeting cookies, which may also be used in our marketing efforts.
This website stores data such as cookies to enable essential site functionality, as well as marketing, personalization and analytics. By remaining on this website, you indicate your consent.

A Guide to DSO in SaaS: What days sales outstanding is, why it's important, and how to calculate it

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Subscribe to our catalog
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

What’s a Rich Text element?

The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.

Static and dynamic content editing

A rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!

How to customize formatting for each rich text

Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added

  • fnjksnweffw
  • nckwkecjwncj
  • cnwk wknw
  • w ww l

-

1. to the rich text element using the "When inside of" nested selector system.

  1. nfvkjvnv
  2. e kjvnvkjv
  3. ckc kvjvk
  4. kvjneknek

Finance leaders use SaaS metrics, including key performance indicators (KPIs) to track cash flow and reduce the level of uncertainty they face. Days sales outstanding (DSO) is one such metric that calculates how long it takes for your invoices to collect payments after a sale. While not all SaaS companies track DSO, they should because it can offer insights that other SaaS metrics can miss or obscure.  

Days sales outstanding (DSO) (aka the “average collection period” or “days sales in receivables” refers to the average number of days it takes for your outstanding invoice to be paid once it has been raised.

In this article, we’ll take a deep dive into DSO as a SaaS metric, explaining how it differs from DSO for other types of businesses, how to calculate it, and the kinds of actionable insights you can gain from tracking it.

Table of Contents
What is Days Sales Outstanding and why is it important for SaaS companies?
How do you calculate DSO? 
What is a good DSO for a SaaS business?
Tracking DSO for better cash flow forecasting
FAQs

What is Days Sales Outstanding and why is it important for SaaS companies?

A lower DSO implies that the company can convert credit sales into cash relatively quickly, and that receivables remain outstanding (on the balance sheet) for a shorter duration of time. That is, it takes the company less time to collect payments, ensuring a healthy cash flow and better working capital management. 

A higher DSO, on the other hand, implies that the company is unable to quickly convert credit sales into cash and that receivables remain outstanding (on the balance sheet) for a longer duration of time. That is, the company takes longer to collect payments and doesn’t have a healthy cash flow for operations. A higher DSO is typically a poor indicator of a company’s financial health because a higher amount of company’s funds are stuck as working capital. 

While DSO is a widely-used metric in business overall, for SaaS businesses its utility is somewhat limited. This is because in contrast to non-SaaS businesses, DSO is usually less than 30 days. In non-saas businesses, the DSO is usually longer because collections are further away from the sale. For example, a factory that sells widgets to Walmart would likely offer the retail chain payment terms of 30, 60, or 90 days, maybe even 120 days. While the accounts receivable process is clearly important for these kinds of businesses (i.e. those that invoice and receive payment potentially months later), it is less important for SaaS businesses.

This is because SaaS companies typically have shorter payment terms. However, in SaaS, DSO is easier to understand within the context of how those payments are made, which for most SaaS companies happens in one of two ways:   

  • Automated payments: This could be business-to-consumer (B2C) SaaS businesses (think Netflix here) or business-to-business (B2B) SaaS companies, such as Salesforce or Quickbooks. For companies that automate payment by billing to a credit card on file, the DSO is effectively zero. This is the same regardless of whether the subscription is monthly or annual because the company invoices and the credit card issues payment almost immediately. 
  • Manual payments: While manual payments are non-existent in B2C SaaS, they’re quite common in B2B SaaS. Some B2B SaaS companies do use automated payment systems. However, for those with high annual contract values (ACV) (e.g. thousands of dollars), paying with a credit card just doesn’t make sense. These companies typically have annual or multiyear contracts with terms that require payment within 15-30 days from the date of the invoice. Thus, for SaaS businesses that manually invoice, the DSO is typically 30 days or less.  

In both cases, subscription renewals follow the same process. If payments are automated (barring any issues with the customer’s credit card on file), the plan will automatically renew when the previous subscription ends. 

Likewise, for a company that invoices and collects payments manually, when a customer’s subscription ends, the company issues a new invoice with payment due date based on the terms of the original agreement. 

It is at this point – subscription renewal – that DSO is most useful for SaaS companies. This is where churn happens, and churn can be devastating to a SaaS business. Here’s why: 

  • For every single customer that churns, you need to attract two new customers to maintain growth (one new customer to replace the one you lost and another new customer to grow). 
  • Churn also has a negative compounding effect, meaning that seemingly incremental changes in churn can have an outsized impact on your revenue over time. 

Suffice it to say, in SaaS, you need to do everything you can to avoid churn. And tracking your DSO might be able to help you do that.  

Here’s the thing…if your company uses an automated payment system, DSO isn’t going to tell you much because your DSO is already zero. In cases where the customer’s credit card is declined, your system may offer some grace period during which the customer receives a reminder or two to fix the situation. But if the payment isn’t made, access to the software is revoked. The churn will have already happened automatically.  

However, if your company invoices manually, looking at DSO both in aggregate and at the individual customer level can give you insights that you can use to be more proactive in preventing churn. This is because manual renewals offer a window of opportunity to intervene if you know that churn is likely, which is something you might be able to see if you’re tracking your DSO.  

If your DSO is increasing. If it is, you’ll want to investigate the issue to determine what’s driving that increase and whether you can do anything to reverse it.  

For example, is the increase in DSO the result of macroeconomic indicators (leading or lagging) that are influencing your customers’ ability to pay on time? If so, you may not be able to do much there. However, if there’s a problem with your invoicing or payment processes, that’s definitely something you can address.  

Perhaps most importantly, you would want to determine if you have a potential problem with customer satisfaction because that could lead to higher churn.

How do you calculate DSO? 

DSO is calculated as the average accounts receivable (AR) for a given period  divided by the total sales (i.e. revenue booked) during the same period, multiplied by the number of days in the period of time. 

The DSO equals the average accounts receivable for the period divided by the total sales for the period multiplied by the total number of days in the period.
The DSO formula.

You can use any period of time to calculate DSO (monthly, annually, quarterly). The key is to ensure that you’re using the same number of days to calculate the average AR and the revenue booked across the same time period. 

Here’s what the formula might look like for a typical B2B SaaS company that invoices manually on an annual basis:

The annual average DSO equals the average accounts receivable for the period divided by the total sales for the period multiplied by the total number of days in the period.
A more useful DSO formula for B2B SaaS.

Calculating DSO on a rolling basis

To gain the most valuable insights DSO has to offer for forecasting your cash flow, you’ll want to track it on a rolling basis.  

Calculating an average DSO, aggregated across all customers, on a 12-month rolling basis  will give you a trend line that will reveal whether it is increasing or decreasing over time. This  gives you a window of opportunity to proactively investigate any increases in your DSO. 

Ultimately, though, the goal of tracking your DSO is to get as granular as possible, ideally down to the customer level. Analyzing DSO at the individual customer level can provide actionable insights into potential issues that can affect the reliability of your cash flow. 

To illustrate this, let’s look at a very simple example where we have a SaaS company with eight customers. Each customer is on an annual contract that requires payment 15 days from the date of invoice. Given this, the company uses an assumed DSO of 15 days in its cash flow forecasting. 

If we were only looking at the rolling DSO in aggregate, this is what we might see for the first month of the quarter:    

Chart showing the change in average DSO aggregated across all customers for January and February for our example company. Results are described in the narrative.
Example of a rolling monthly average DSO for the first two months of Q1, aggregated across all customers.

There is a slight increase in our average DSO, but it’s still lower than our expected DSO of 15 days. So maybe we’re not too worried about that. Then, when we update our DSO with actuals from March, suddenly we find that we may have a bigger problem on our hands.

Example of a rolling monthly average DSO updated with actuals for the third month of Q1, aggregated across all customers.

In order to figure out what’s happening here, we have to drill down to the customer level: 

Chart showing the change in average DSO aggregated across all customers for the full quarter for our example company. Results are described in the narrative.
Example of a rolling monthly average DSO at the customer level over a three-month period.

At the customer level, it’s clear to see that there was actually a problem lurking in that slight increase in February. One of our customers took a lot longer to pay than the others. For Customer 5, the DSO was five days higher than our expected DSO. This may signal that Customer 5 is having trouble paying and may be more likely to churn. In this case, we might  want to have our customer success (CS) team work with Customer 5 to better understand the underlying issue.   

Looking more closely at the increase in March, we are seeing a different story possibly emerging. Our average DSO is clearly increasing faster, and when we look at the individual customer DSOs, we find that they're all paying at the last minute or late. This could represent an increased risk of churn, but it might instead be indicative of larger, macroeconomic conditions that are making it harder in general for customers to pay timely. 

Of course, we can’t fix those kinds of problems. But knowing about them gives us an opportunity to more accurately account for the potential risk to our cash flow in our forecast and proactively adjust our spending if needed. 

Understanding your DSO at the customer level also gives you an opportunity to be proactive in other ways that can help your cash flow. For example, if you do find that there are macroeconomic issues driving your DSO higher, you may want to consider adjusting the payment terms in your contracts to achieve a more predictable cash flow. 

The key takeaway in this simple example: Understanding DSO at the customer level is necessary to really understand what is driving any increases or decreases in average DSO.   

The problem is, if you’re using Excel to track your DSO at the customer level, if you have more than around 1,000 customers, it can become very time consuming and unwieldy. One alternative is to group your customers in some way, ideally by similarities in their payment patterns. 

For example, if you have two main types of customers, say SMBs and enterprise, and they have two different types of payment plans. SMBs pay monthly while enterprises pay annually. Thus, that would be a logical way to group your customers to make tracking DSO on a rolling basis easier. 

If you don’t have such clear segments within your customer base, you can experiment with grouping them in other ways, maybe by region or product. When you start grouping customers in different ways and look at their DSOs, you will likely begin to see payment patterns emerge that can help you group them. 

Once you group your customers into different segments, you can calculate an average DSO for each customer group, aggregated across all the customers in that group. This adds a few steps but will make updating your DSO each month a little more manageable when you’re using Excel and have a lot of customers to track.   

What is a good DSO for a SaaS business?

In contrast to other types of businesses that offer extended payment terms, for  SaaS businesses, DSO doesn’t vary much. 

The SaaS business model relies on subscriptions/licenses that grant access to the product to ensure they are paid on time. Given this, customer payment behavior remains fairly consistent. Customers tend to make timely payments to continue to access the product. (And of course, no one wants the hassle of getting their subscriptions or licenses revoked!)

For SaaS companies that invoice manually, DSO should always be less than 15-30, which reflects the typical terms of annual or multiyear SaaS contracts. Of course, companies that use an automated payment system where the customer’s credit card is billed, will have a DSO of zero.   

When a SaaS company that invoices manually has a higher DSO than 30 days, it is not necessarily a cause for alarm. It might mean that the company and the customer care department directed their energies on maintaining the customer relationship — by understanding the issue and showing leniency around payment cycles — instead of simply revoking access.

Tracking DSO for better cash flow forecasting

If you’re not tracking your DSO, you’re missing out on some pretty useful insights it can provide. 

After all, DSO is closely tied to cash flow, and a lower DSO provides more liquidity in your business. Therefore, tracking it can help you develop better forecasts. 

SaaS companies can have some pretty hefty recurring costs themselves, such as cloud hosting fees and likely many subscriptions to different SaaS tools they need for marketing, to run the business, and maintain their service. 

Thus, tracking your DSO can help you know whether you’ll have the working capital necessary to cover those costs. If your DSO is between 15-30 days (close to the payment terms spelled out in your customers’ contracts) you’ll have a more reliable cash flow to make managing those expenses easier. 

Generally, the lower your DSO, the better. A lower DSO means you’ll have more working capital for other things, too, which gives you more freedom to make decisions based on market dynamics and potential opportunities. 

An alternative to using DSO for cash flow forecasting

Understanding the flow of money into your business can be a bit tricky for SaaS businesses because the business model creates recurring revenue, pricing models vary, and there are different ways they can structure their payment terms. 

DSO offers a relatively simple way to forecast the cash coming in, particularly for businesses that have multiyear contracts that are paid annually. 

However, for SaaS businesses with more traditional pricing models in which customers have an annual subscription but pay monthly, the AR runoff method provides an alternative to using DSO for the purposes of cash flow forecasting. 

For example, with a traditional pricing model, your customer signs a $12K annual contract and pays $1K every month. With the AR run off method, you would calculate your collections forecast as 8.33% of the invoice amount every month, which is simply the percentage of the total contract that the customer pays each month. 

The chief benefit of the AR runoff method is that it provides another, perhaps easier way, to forecast your collections when you have a lot of customers and your business uses a traditional SaaS pricing model. 

It’s important to note, though, that using this method won’t provide the insights into customer payment behavior that DSO does – or the corresponding opportunities those insights would provide to reduce churn or take actions to improve the predictability of cash flow in your business. 

Regardless of the method you choose to support your cash flow forecasting, using spreadsheets becomes exponentially difficult (and arguably impossible) to calculate and track thousands of customers individually, month after month.  

Your business can scale, but your spreadsheets won’t. 

No matter how many customers you have or how complex your business model, Drivetrain makes tracking DSO down to the customer level and on a rolling basis easy. In just a few clicks, you can find new insights that will help you improve your cash flow forecasting and proactively mitigate cash flow issues. Drivetrain can also  make using the AR runoff methods a breeze, too.

FAQs

What is DSO?

DSO is the average number of days it takes for your outstanding invoice to be paid once it has been sent. Knowing what your company’s DSO is at the customer level can make it easier to predict and optimize cash flow for strategic planning and decision-making.

How is DSO calculated?

DSO is calculated as the average accounts receivable (AR) for a given period  divided by the total sales (i.e. revenue booked) during the same period, multiplied by the number of days in the period of time. 

The DSO equals the average accounts receivable for the period divided by the total sales for the period multiplied by the total number of days in the period.
 The DSO formula.
Why should SaaS companies track their DSO?

Tracking DSO gives you a quick way to check to see if your customers are paying on time. Tracking it over time can help you identify emerging issues. 

Since DSO is directly related to cash flow, if your DSO is within 15-30 days, which reflects the typical payment terms for B2B SaaS businesses that invoice manually, your cash flow is reasonably reliable. 

If your DSO is higher than this, it could indicate one or more issues that can affect both your cash flow and overall revenue, including:

  • Macroeconomic conditions are making it harder for customers to pay on time 
  • Friction in your invoicing and/or payment processes
  • Problems with customer satisfaction  

While there is little you can do to alter larger issues impacting your market, tracking DSO gives you an opportunity to identify problems that you can address.  

DSO can be tracked for a given period of time or on a rolling basis. Both methods offer the opportunity to proactively identify and address emerging issues. However, calculating a rolling DSO helps ensure you find those issues before they get out of hand.

What is a good DSO for SaaS companies?

In contrast to other types of businesses that offer extended payment terms, for  SaaS businesses, DSO doesn’t vary much. 

For SaaS companies that invoice manually, DSO should always be less than 15-30, which reflects the typical terms of annual or multiyear SaaS contracts. For  companies that use an automated payment system where the customer’s credit card is billed, will have a DSO of zero.   

The only financial model template you'll ever need—just plug in your actuals to see projections
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.