Quant Memo
Core

Deferred Revenue, Billings and RPO

Deferred revenue is money already collected but not yet earned; RPO is the broader promise of everything still owed, billed or not — together they're the best forward-looking signal a subscription business discloses.

Prerequisites: ASC 606 and the Five-Step Revenue Model

A software company sells a one-year subscription for $12,000, billed and paid entirely on day one. Its bank account jumps by $12,000 immediately, but its income statement can't recognize all of that as revenue — the company still owes eleven more months of service. That gap between "cash we've collected" and "revenue we've earned" is exactly what deferred revenue tracks, and it's one of the few line items that tells you something about the future rather than the past.

Deferred revenue is a liability: cash already received for work not yet done. Remaining performance obligations (RPO) is broader still — it's every dollar of contracted, non-cancelable revenue not yet recognized, whether it's been billed or not. Both shrink as revenue is earned and grow as new contracts are signed, making them a rare income-statement-adjacent metric that looks forward instead of back.

How the balance moves

When the $12,000 subscription is sold, the company debits cash $12,000 and credits deferred revenue $12,000 — no revenue yet. Each month, as one-twelfth of the service is delivered, it debits deferred revenue $1,000 and credits revenue $1,000. After twelve months the liability is fully worked off and the full $12,000 has flowed through the income statement.

RPO extends this idea past what's already been billed. A three-year, $36,000 contract billed annually has, at signing, only $12,000 in deferred revenue (this year's bill) but $36,000 in RPO (the full multi-year commitment) — the other $24,000 hasn't been invoiced yet but the customer is contractually on the hook for it.

a 3-year, \$36,000 contract, billed annually Year 1 billed Year 2 unbilled Year 3 unbilled deferred revenue: \$12,000 RPO covers all three years: \$36,000
Deferred revenue only reflects cash already billed. RPO captures the full contracted commitment, billed or not.

Worked example

A cloud company reports $40 million in deferred revenue at the start of the quarter and $46 million at the end. During the quarter it recognized $25 million of subscription revenue. Billings — the total amount invoiced to customers, whether recognized as revenue yet or not — can be reconstructed:

Billings=Revenue+(Ending deferred revenueBeginning deferred revenue)\text{Billings} = \text{Revenue} + (\text{Ending deferred revenue} - \text{Beginning deferred revenue})

In words: billings equal revenue recognized this quarter, plus however much the deferred revenue balance grew (because that growth represents cash billed but not yet earned).

Billings=25+(4640)=31 million\text{Billings} = 25 + (46 - 40) = 31 \text{ million}

So the company billed $31 million in new invoices this quarter, even though only $25 million showed up as revenue — a healthy sign, since new bookings ($31 million) are outrunning what's being recognized ($25 million), meaning the deferred revenue backlog is building rather than draining.

What this means in practice

Because deferred revenue and RPO reflect contracts already signed, they're a leading indicator that shows up before revenue does — a company can miss its quarterly revenue estimate on timing while its RPO growth signals the underlying business is accelerating. Investors in subscription businesses watch RPO growth relative to revenue growth as a check on whether reported growth is sustainable or borrowed from future quarters.

A shrinking deferred revenue balance doesn't automatically mean trouble — it can simply mean a company shifted from annual to monthly billing, which lowers the balance mechanically without any change in the underlying business. Always check the billing cadence before reading a deferred revenue trend as a signal about demand.

Related concepts

Practice in interviews

Further reading

  • FASB ASC 606-10-50, Disclosure of Remaining Performance Obligations
  • Bessemer Venture Partners, 'State of the Cloud' (billings and RPO metrics)
ShareTwitterLinkedIn