Blog · Finance metrics and formulas · Software
A software company's conventional cash cycle can miss the effect of advance subscription billing. Compare receivable and payable days with billings, collections and deferred revenue before judging the cash position.
The cash conversion cycle for software companies usually compares receivables days with payables days, with no inventory component for a pure subscription business. Annual advance invoices can make that figure a poor summary of subscription cash timing. Reconcile billings, cash collections and deferred revenue alongside it before deciding whether cash is arriving sooner or the obligation to deliver service is growing.
The cash conversion cycle guide owns the general formula. For a software business without inventory, the shortened calculation is:
Cash conversion cycle = Revenue-based receivables days − Cost-based payables days
Receivables days = Average trade receivables / Revenue × Period days
Payables days = Average trade payables / Cost of revenue × Period days
Use a consistent credit-revenue scope; the worked example below assumes all revenue comes from invoiced customer contracts. A company with cash sales, hardware inventory or separate financing operations needs to identify those differences before applying the simplified calculation.
The CFA Institute describes the cash conversion cycle as a liquidity measure and identifies receivables and payable days among operating activity ratios. The calculation translates selected balances into days; it does not schedule every future receipt and payment.
In particular, deferred revenue is not an extra payable-days numerator. It is a customer-contract balance, not a vendor invoice awaiting payment. Keep it in its own reconciliation rather than subtracting it from trade receivables or adding it to trade payables.
An annual invoice and the revenue it supports can fall in different periods. The unearned-revenue note in Microsoft's annual report describes annual invoicing at the beginning of contract periods, with revenue recognized over the coverage period. The same report distinguishes the timing of invoicing from revenue recognition. Covirage is not affiliated with Microsoft.
That creates two questions. How quickly does the company collect invoices? How much service has the company already billed but not yet earned? Revenue-based DSO cannot answer both.
A business that changes from monthly to annual billing may increase invoices and cash receipts without a matching immediate increase in recognized revenue. Depending on when customers pay, receivables may rise or fall. The conventional cycle can therefore move even when customer payment behavior has not changed.
For project-based billing without these subscription balances, use the separate cash conversion cycle for service companies. Keep subscription billing and project milestone delays distinct.
The following figures describe an illustrative US software company for January 1 through March 31, 2026, a 90-day quarter. There is no inventory. Customer balances have no write-offs, refunds, tax or currency changes; supplier balances have no noncash adjustments. All billings in the example initially increase deferred revenue, and all recognized revenue reduces it.
| Balance | Opening (USD) | Closing (USD) | Simple average (USD) |
|---|---|---|---|
| Trade receivables | 300,000 | 150,000 | 225,000 |
| Trade payables | 90,000 | 150,000 | 120,000 |
| Deferred revenue | 450,000 | 900,000 | — |
| Quarter activity | Amount (USD) |
|---|---|
| Customer billings | 1,350,000 |
| Customer cash collections | 1,500,000 |
| Recognized revenue | 900,000 |
| Cost of revenue | 600,000 |
| Supplier purchases passing through trade payables | 360,000 |
| Payments against trade payables | 300,000 |
Supplier purchases are the vendor portion of cost of revenue in this example; the remainder consists of nonvendor service costs. The averages are opening plus closing divided by two. They are a consistent approximation, not a substitute for more frequent snapshots when annual invoices create large swings within the quarter. Displayed days below are rounded to one decimal; calculations retain full precision.
| Measure | Calculation | Days |
|---|---|---|
| Revenue-based receivables days | 225,000 / 900,000 × 90 | 22.5 |
| Cost-based payables days | 120,000 / 600,000 × 90 | 18.0 |
| Conventional cash conversion cycle | 22.5 − 18.0 | 4.5 |
| Billings-based receivables days | 225,000 / 1,350,000 × 90 | 15.0 |
| Supplier-purchase-based payment days | 120,000 / 360,000 × 90 | 30.0 |
The conventional cycle is 4.5 days. It does not say that every dollar of spending is recovered after that interval. Cost of revenue includes costs beyond purchases passing through trade payables, and recognized revenue is not the same flow as new subscription invoices.
The billings-based figure of 15.0 days provides a second view of invoice balances. It is still a balance ratio, rather than a measured average of invoice-to-payment dates. Use the DSO guide for the underlying receivables method and inspect the actual dated invoices when collection performance is the question.
Each closing balance must rebuild from its own opening balance and movements:
| Check | Calculation (USD) | Closing balance (USD) |
|---|---|---|
| Receivables | 300,000 + 1,350,000 − 1,500,000 | 150,000 |
| Deferred revenue | 450,000 + 1,350,000 − 900,000 | 900,000 |
| Trade payables | 90,000 + 360,000 − 300,000 | 150,000 |
The company collected $1,500,000 while earning $900,000 of revenue. The tables show where that difference comes from: receivables fell and deferred revenue increased. Collections include money relating to service that remains to be delivered; they are not a measure of current-period profit.
In a real ledger, add separately identified refunds, credits, write-offs, contract assets and other movements to the relevant reconciliation. Never force a difference into collections. Tie the closing balances to the general ledger and customer cash receipts to the cash ledger using the same cutoff.
Finance owns the definitions, reconciliations and cost classification. Billing operations owns invoice issuance and contract schedules. Collections owns unpaid invoices and disputes. Procurement and accounts payable own supplier terms and payment dates, while operating teams explain the service costs that remain after advance payments arrive.
Use those responsibilities to decide what to change. A billing delay calls for a contract or invoice review. A collection delay calls for customer follow-up. More advance receipts call for a review of future service obligations before the company commits the money elsewhere. Cross-sector comparisons need the consistent scope described in cash conversion cycle by industry.
Bring billing, collection and supplier-payment exports, balance snapshots and a deferred-revenue schedule to Covirage. Its tools compute and check the figures; the external AI model explains the results with every figure traced to its rows. Create a free Covirage account, set up your business and bring a sample of your own data.
See Covirage for SaaS sales teams for the business context.
Yes. Receivables days can be shorter than payable days, particularly where customers pay early. A negative figure does not establish financial health: overdue suppliers, financing transactions and future service costs still need review, and the conventional cycle does not explicitly include deferred revenue.
No. Deferred revenue is an accounting balance for amounts billed or received before the related revenue is earned. An unpaid advance invoice can create both receivables and deferred revenue. Reconcile collections separately before treating the balance as available cash.
Conventional revenue-based DSO uses the declared revenue denominator. A billings-based measure can help assess invoice collection when subscription invoicing and revenue recognition differ. Label the two clearly and keep their inputs consistent rather than presenting them as interchangeable measures.