Deferred revenue is the line that makes subscription software accounting work, and it answers a simple question: when a customer pays up front for a year of service, where does that money go before the service is delivered? It does not become revenue immediately. Instead it lands on the balance sheet as deferred revenue — a liability — and is released into the income statement as revenue over the period the company actually performs. For a SaaS or security platform billed annually in advance, that means a single payment in January is recognized as revenue across the following twelve months, not all at once. The deferred-revenue balance is, in effect, the pool of customer prepayments still waiting to be earned.

This treatment is dictated by the revenue-recognition standard, ASC 606, which requires a company to recognize revenue as it satisfies its performance obligations rather than when it collects cash. A company's 10-Q states the mechanics directly. CrowdStrike's quarterly report for the period ended April 30, 2026 describes its contract liabilities this way:

"Contract liabilities consist of deferred revenue and include payments received in advance of performance under the contract. Such amounts are recognized as revenue over the contractual period. The Company recognized revenue of $1.2 billion and $950.9 million for the three months ended April 30, 2026 and April 30, 2025, respectively, which was included in the corresponding contract liability balance at the beginning [of the period]."— CrowdStrike Holdings, Inc., Form 10-Q (quarter ended April 30, 2026), source

Two ideas in that passage are worth isolating. First, "deferred revenue" and "contract liability" are the same thing — payments received before performance. Second, the company explicitly quantifies how much of the prior period's deferred-revenue balance turned into recognized revenue this quarter ($1.2 billion). That conversion is the engine of subscription accounting: the balance is continuously refilled by new billings and continuously drained as service is delivered and revenue is recognized.

Why billings is not the same as revenue

Because revenue is recognized over time while cash is often collected up front, the income statement's revenue line can lag what the company actually sold in the period. That gap is why investors watch a derived metric called billings. Billings is not a GAAP line item; it is typically calculated as revenue recognized in the period plus the change in the deferred-revenue balance over that period. The logic: revenue captures what was earned, and the increase in deferred revenue captures new prepayments that have not yet been earned, so adding them approximates what was invoiced during the quarter. Billings is therefore used as a rough proxy for new bookings and demand, especially for businesses billed annually in advance.

On the balance sheet, deferred revenue itself is split into current and noncurrent portions, and that split carries information. The current portion is the prepaid service the company expects to recognize within twelve months; the noncurrent portion is prepaid service for periods beyond a year, which arises when customers pay up front for multi-year terms. A company whose noncurrent deferred revenue is growing is collecting more cash for longer-dated commitments, which strengthens cash visibility but also means more of the recognized-revenue conversion is pushed further out. Reading the two lines together — rather than a single combined figure — tells you not just how large the prepaid book is but how its timing is shaped, the same way the RPO recognition schedule does for the full contracted backlog.

The proxy has real limitations, which is why it is a non-GAAP estimate rather than a reported number. Changes in billing terms distort it: if customers shift from annual to multi-year up-front billing, billings can spike without any change in underlying demand, and if they shift from up-front to monthly or quarterly billing, billings can look soft even as bookings grow. Deferred revenue captures only the billed portion of contracts, so a company that invoices multi-year deals annually will show only the current year's billing flowing through deferred revenue and billings — the later years sit unbilled and appear instead in remaining performance obligations. For that reason, deferred revenue and billings are best read alongside RPO, which captures the full contracted backlog including unbilled future years.

How to read the three numbers together

The disciplined frame is to keep three concepts distinct. Revenue is what the company earned by performing in the period — the audited (or reviewed) GAAP top line. Deferred revenue is what customers have paid for but the company has not yet earned — a balance-sheet liability that the filing reconciles for you. Billings is an analyst's estimate of what was invoiced — useful as a demand signal but sensitive to billing-term changes and not a substitute for either GAAP figure. A current-quarter revenue beat paired with a soft deferred-revenue balance can mean billing timing shifted, not that demand fell; the only way to tell is to read the contract-liability footnote and the company's stated billing practices.

The grounded approach when a company touts a "billings beat" is to go to the 10-Q, find the deferred-revenue (contract-liability) disclosure, and check the change in the balance against the revenue recognized — the components billings is built from. Confirm whether the company defines billings the same way you are computing it, because there is no single mandated formula. And read it against RPO to separate the billed book from the unbilled backlog. Deferred revenue is the one number of the three that is a real, reported, footnoted balance-sheet figure governed by the revenue standard; billings is derived from it. Anchoring on the deferred-revenue line, and on the ASC 606 mechanics that govern it, is what keeps the analysis honest.