# Accounts Receivable for SaaS: A Founder's Guide (with AR Aging and DSO)

> Accounts receivable for SaaS - how to think about AR aging, DSO benchmarks, dunning workflows, and how MoR billing changes the AR collection picture entirely.
- **Author**: Ayush Agarwal
- **Published**: 2026-05-28
- **Category**: SaaS Finance, Billing, Accounts Receivable
- **URL**: https://dodopayments.com/blogs/accounts-receivable-saas-guide

---

Accounts receivable (AR) is the money your customers owe you for services or products you have already delivered. In accounting terms, it is an asset on the balance sheet - a future cash inflow that has been earned but not yet collected. For SaaS, AR sits in the gap between invoice issuance and payment receipt, and the size of that gap is one of the most important operational metrics in the business.

A SaaS company with $5M in annual recurring revenue and 30 days of AR has $410,000 sitting in receivables at any given time. The same company with 60 days of AR has $820,000 - cash that could otherwise be invested in product, hiring, or growth. Cutting days sales outstanding (DSO) from 60 to 30 days unlocks $410,000 in working capital without changing revenue, headcount, or pricing.

This guide explains what accounts receivable means for SaaS specifically, how to read an AR aging report, what good DSO looks like by business model, how dunning fits in, and how Merchant of Record (MoR) billing changes the AR picture entirely.

## What Accounts Receivable Means for SaaS

In traditional accounting, AR is created when you issue an invoice and increased revenue and AR both go up by the invoice amount. When the customer pays, AR goes down and cash goes up. The difference between the two events is the AR balance.

For SaaS, this plays out in three distinct billing models:

**Self-serve credit card billing (B2C and small-team B2B)**: Invoices are charged automatically at the start of each billing cycle. Successful charges hit cash immediately. Failed charges enter AR until they resolve. AR balances are typically small (under one month of revenue) and mostly consist of failed payments waiting for dunning to recover them.

**Annual upfront contracts (mid-market and enterprise B2B)**: The customer commits to a year of service and pays upfront, either in full or in quarterly installments. Each installment generates an invoice that sits in AR until paid. AR is bursty - large balances on invoice dates that drain as payments arrive over 15-45 days.

**Net-terms invoicing (enterprise B2B and B2G)**: The customer pays after delivery, typically on Net 30, Net 60, or longer terms. The full quarterly or annual invoice sits in AR for the duration of the payment term. AR can equal a meaningful percentage of annual revenue at any given time.

Most SaaS companies operate a mix - self-serve plans charged to cards, mid-market on annual upfront with multiple installments, and enterprise on net terms. The AR profile of the business is the weighted average of those three flows.

## The AR Aging Report

An AR aging report breaks down outstanding receivables by how long they have been outstanding. It is the single most important AR management tool. A typical aging bucket structure looks like this:

| Aging Bucket | Description | Risk Level |
| --- | --- | --- |
| Current | Within payment terms | Normal |
| 1-30 days past due | Just over terms | Low |
| 31-60 days past due | Persistent late payer | Moderate |
| 61-90 days past due | Recovery effort required | High |
| Over 90 days past due | Likely bad debt | Very high |

The healthier the business, the more concentrated the AR is in the "current" bucket and the less in the 60+ buckets. A typical SaaS aging report should show 80%+ current, 10-15% in the 1-30 bucket, and 5% or less in 30+ buckets combined.

When the 30+ buckets start growing, three things are usually happening: enterprise customers are stretching payment terms, payment failures on self-serve plans are not being recovered through dunning, or the sales team is closing deals with customers who lack the financial discipline to pay on time. Each pattern requires a different response.

Most accounting systems (NetSuite, Sage Intacct, QuickBooks, Xero) generate aging reports automatically. SaaS-specific billing platforms add SaaS-relevant cuts on top - aging by plan tier, by customer segment, by payment method, and by ACV (annual contract value) bucket.

## Days Sales Outstanding (DSO)

DSO is the average number of days it takes to collect payment after a sale. The formula is:

```
DSO = (Accounts Receivable / Total Credit Sales) x Number of Days
```

For a SaaS business with $5M in trailing-12-month revenue and $410,000 in AR, DSO is `(410,000 / 5,000,000) x 365 = 30 days`.

DSO benchmarks vary by SaaS billing model:

| Billing Model | Typical DSO | Notes |
| --- | --- | --- |
| Self-serve card-only | 0-5 days | Cards settle in 2 business days; the only AR is failed payments |
| Annual upfront, credit card | 5-15 days | Same as above, but with larger ticket sizes that take longer to recover when failed |
| Annual upfront, ACH | 15-30 days | ACH settlement is slower and dunning cycles longer |
| Net 30 invoicing | 35-55 days | Net 30 means 30 days from invoice, but enterprise AP teams often take 5-25 extra days |
| Net 60 invoicing | 65-90 days | Same dynamic at longer terms |
| Mixed (typical mid-market SaaS) | 20-40 days | Weighted average of self-serve and enterprise flows |

DSO trends matter more than absolute numbers. A SaaS DSO that creeps from 30 to 45 days over six months is a leading indicator that either enterprise customers are stretching terms or self-serve dunning has degraded. Both are fixable, but only if you measure DSO regularly.

A related metric - DSO best possible - removes the impact of payment terms by recalculating only the "past due" portion. If your Net 30 customers pay on day 30, your DSO is 30 days but your DSO best possible is 0. The gap between actual DSO and DSO best possible tells you how much room there is to improve collection without changing payment terms.

A pattern we see often at Dodo Payments: founders fixate on revenue growth and overlook working capital. For any SaaS at meaningful scale, multi-day reductions in DSO translate into real operating cash - often enough to fund additional headcount without raising more capital. Working capital discipline is one of the cheapest forms of growth funding available to a subscription business.

## The Order-to-Cash Cycle

AR is one stage in the broader order-to-cash (O2C) cycle. Understanding the whole cycle helps locate where AR slowdowns actually originate:

```mermaid
flowchart LR
    A[Customer signs contract] --> B[Invoice issued]
    B --> C[Invoice sent to AP team]
    C --> D[AP approves invoice]
    D --> E[Payment scheduled]
    E --> F[Payment sent]
    F --> G[Cash received]
    G --> H[Reconciled & closed]
```

A slow AR profile usually traces to one or two stages, not all of them. Common culprits:

- **Slow invoice issuance**: Invoices are not issued the day the contract closes. Each day of delay shifts DSO by a day. Automated billing on contract close fixes this
- **Wrong AP contact**: The invoice goes to the original sales contact instead of the buyer's AP team. AP never sees it until the buyer forwards it, days or weeks later
- **PO mismatches**: The invoice does not match the purchase order number, line items, or amount, so AP rejects it. The merchant has to issue a corrected invoice, restarting the clock
- **Approval workflow delays**: The buyer's AP team requires multiple approvers, each of whom takes days. Some enterprise buyers have AP cycles of 15-25 days even on "Net 30" terms
- **Payment method friction**: The buyer prefers wire but the invoice only offers ACH, or vice versa. AP works around it but loses days in the process

Cleaning up O2C is a finance and operations problem that requires alignment between sales, billing, and AP. The fastest improvements usually come from automating invoice issuance, capturing the correct AP contact at contract signing, and offering multiple payment methods on every invoice.

## Dunning: AR Recovery for Self-Serve and Subscription Billing

For SaaS with significant self-serve volume, AR is largely created by failed automated payments, not by net-terms invoicing. The recovery process is called dunning - the systematic retry and customer outreach sequence after an initial payment failure.

A standard SaaS dunning workflow looks like:

| Day | Action |
| --- | --- |
| 0 | Initial payment fails. First in-app banner shown. Email #1 sent |
| 1-2 | Automatic retry. If failure was insufficient funds or temporary network issue, this often succeeds |
| 3 | Second retry. Email #2 sent with link to update payment method |
| 5 | Third retry. Email #3 sent. Customer support paged if account value is high |
| 7 | Final retry. Email #4 with explicit cancellation warning |
| 10-14 | Service suspended (read-only mode or full lock) |
| 21-30 | Subscription canceled. AR written off as bad debt |

The single biggest lever in dunning is timing. Retrying on day 0 catches almost nothing (the same problem still exists). Retrying on day 3 catches about 20% of failures (the customer's balance has recovered or the bank-side issue has cleared). Retrying on day 7 catches another 15% on top.

The second biggest lever is communication. Dunning emails with a clear "your subscription will be canceled on [date]" message convert at 2-3x the rate of generic "your payment failed" emails. The threat of service interruption gets attention; vague reminders do not.

For deeper coverage, see our [dunning management guide](https://dodopayments.com/blogs/dunning-management) and the [involuntary churn from failed payments](https://dodopayments.com/blogs/involuntary-churn-failed-payments) playbook.

## Bad Debt and Write-Offs

Not every AR balance becomes cash. Some customers go out of business, dispute the invoice, or simply refuse to pay. Accounting standards require companies to estimate uncollectible AR and book a corresponding bad debt expense.

The standard approach is the allowance method:

- Set up an "allowance for doubtful accounts" contra-asset account
- Each period, estimate what percentage of AR will be uncollectible (often based on aging - higher percentages for older buckets)
- Book the estimate as bad debt expense and increase the allowance
- When a specific receivable becomes confirmed bad debt, write it off against the allowance

For SaaS, healthy bad debt expense is typically 0.5-2% of revenue. Higher than 2% usually indicates either credit underwriting issues (signing customers who cannot pay), invoicing problems (disputes are common), or post-close support failures (customers refuse to pay because they are unhappy with the product).

The ASC 606 revenue recognition rules require SaaS companies to consider collectibility before recognizing revenue. If a contract has substantial collectibility risk at signing, revenue cannot be recognized for that contract until collection becomes reasonably certain. This is most relevant for enterprise SaaS with multi-year contracts to financially weak buyers.

## How Merchant of Record Billing Changes AR

A [Merchant of Record](https://dodopayments.com/blogs/what-is-a-merchant-of-record) is a payment platform that acts as the legal seller of record on every transaction. The MoR handles the entire order-to-cash cycle - invoicing, payment collection, dunning, dispute response, and remittance - and pays the underlying SaaS business a net amount after fees and reserves.

This changes the AR picture in three important ways:

**The MoR holds the customer's AR, not the SaaS business.** From the underlying business's perspective, the "customer" is the MoR. The MoR settles to the business on a regular cadence (weekly or bi-weekly typically), and the AR on the SaaS company's books is just "amount owed by MoR for transactions in the current settlement period." That balance is typically small and very low risk.

**The MoR runs dunning on the SaaS business's behalf.** For self-serve subscriptions, dunning sequences are handled by the MoR's billing infrastructure. Failed payments are retried, customers are emailed, and recoveries are deposited as part of the regular settlement. The SaaS business does not run its own dunning workflow.

**Bad debt is mostly the MoR's problem.** Customers who never pay after multiple dunning attempts are eventually written off by the MoR. The SaaS business does not see those customers as bad debt because the MoR's settlement only includes recovered amounts.

For SaaS companies that want to spend less time on AR mechanics and more time on the product, an MoR effectively outsources the entire AR function. Dodo Payments operates as an MoR and handles invoice issuance, dunning, dispute response, and remittance through one integration. See the [subscription docs](https://docs.dodopayments.com/features/subscription) and the [disputes feature](https://docs.dodopayments.com/features/transactions/disputes) for technical details.

## AR Metrics to Track Monthly

A SaaS finance team should track these metrics monthly at minimum:

- **DSO**: Days sales outstanding overall and by segment (self-serve, mid-market, enterprise)
- **AR aging**: Distribution across current, 30, 60, 90+ buckets
- **Collection effectiveness index (CEI)**: Percentage of available AR (beginning AR + new invoices) that was actually collected during the period
- **Bad debt as % of revenue**: Confirmed write-offs divided by revenue
- **Dunning recovery rate**: Percentage of failed payments that are eventually recovered through the dunning workflow
- **Average days to first invoice**: Time from contract close to invoice issuance

Tracking these monthly catches problems while they are still small. AR aging that drifts from 80% current to 70% current is a 5x increase in the 30+ buckets, but it happens slowly enough that businesses without monthly tracking often miss it until a quarterly cash flow miss surfaces the problem.

## FAQ

### What does accounts receivable mean for a SaaS business?

Accounts receivable is the money owed to a SaaS business by customers who have been invoiced but have not yet paid. It is an asset on the balance sheet. For SaaS, AR is created by self-serve payment failures, by annual contracts where the customer pays in installments, and by enterprise customers on net-terms invoicing.

### What is a good DSO for a SaaS company?

It depends on the billing mix. Self-serve card-only SaaS should have DSO under 10 days. Mid-market SaaS with annual upfront contracts should be 15-30 days. Enterprise SaaS with Net 30 or Net 60 terms typically runs 35-90 days. The right benchmark is your own DSO trend over time - DSO that is steady or improving is healthy; DSO that is creeping up is a signal of degrading collections or stretching customer payment behavior.

### How is accounts receivable different from revenue?

Revenue is the value of services delivered to customers in a period, regardless of when paid. Accounts receivable is the portion of that revenue that has not yet been collected as cash. A SaaS business with $1M in monthly revenue and $400K in AR has earned $1M but is still waiting to collect $400K of it. Revenue is recognized when earned; cash arrives later.

### What is the difference between accounts receivable and deferred revenue?

Accounts receivable is for revenue that has been earned but not yet paid. Deferred revenue is for cash that has been paid but service has not yet been delivered (typically the customer paid annually upfront and the SaaS company is recognizing revenue monthly). Both are balance sheet accounts but they represent opposite sides of the timing mismatch between revenue recognition and cash collection.

### How can a SaaS company reduce DSO?

Issue invoices on the same day the contract closes (not days later). Capture the customer's AP contact at signing so invoices go directly to the team that pays. Offer multiple payment methods (card, ACH, wire) on every invoice. Run automated dunning on failed self-serve payments. Tighten payment terms on new contracts where possible (Net 15 instead of Net 30, monthly billing instead of quarterly). For aggressive DSO improvement, consider working with a Merchant of Record that handles invoicing and collection on your behalf.

## Conclusion

Accounts receivable is one of the most consequential and least glamorous numbers in a SaaS business. It is the gap between revenue and cash, and the size of that gap directly affects working capital, growth investment capacity, and bad debt exposure. SaaS businesses that ignore AR mechanics end up with cash flow problems that look like growth problems. SaaS businesses that manage AR rigorously unlock meaningful working capital improvement without changing revenue or pricing.

The biggest leverage points are invoicing automation, multi-method payment acceptance, disciplined dunning, and good AR aging visibility. For SaaS companies that want to outsource the operational work entirely, [Dodo Payments](https://dodopayments.com) operates as a Merchant of Record and handles invoicing, collection, dunning, and dispute response through one integration.

Read the [dunning management guide](https://dodopayments.com/blogs/dunning-management) for a deeper look at failed-payment recovery, or review [Dodo Payments pricing](https://dodopayments.com/pricing) to compare the MoR cost structure against managing AR independently.
---
- [More SaaS Finance articles](https://dodopayments.com/blogs/category/saas-finance)
- [All articles](https://dodopayments.com/blogs)