Backlog and RPO explained without confusing contracts with cash

Sources for these deliberately separate examples are CoreWeave's revenue note and earnings release, Oracle's 10-Q, Microsoft's Note 11 and Nebius's filed agreement. The reporting dates differ. These figures are not summed, ranked as equivalent demand or presented as a synchronized market snapshot.

Start with what the company has promised to deliver

A performance obligation is a promise to transfer goods or services to a customer. RPO tracks the transaction price allocated to the part still undelivered. Recognition then follows the applicable accounting policy: signing a multiyear cloud contract does not mean recognizing its entire value immediately.

CoreWeave's definition is especially useful. Its RPO includes billed and unbilled consideration from committed contracts, net of estimated variable consideration. The filing identifies possible service credits, delivery delays and committed capacity it has the right to resell among the adjustments. The number already involves estimates; it is not an unconditional pile of future invoices.

Its earnings-release definition of revenue backlog is broader: RPO plus other amounts it estimates will become revenue under committed customer contracts, subject to delivery and availability requirements. That explains why the release's approximately $104 billion backlog and the filing's $103.7 billion RPO are not interchangeable. Do not turn a rounded difference into a precisely measured new category.

Keep revenue, billing and cash on different clocks

Revenue records performance. Billing establishes an invoice. Cash records payment. These events can occur in a different order, particularly when a customer prepays for capacity that is still being built.

Microsoft's September filing illustrates the gap. Alongside $683 billion of total RPO, Note 11 reports $69.563 billion of unearned revenue at September 30, 2026. The RPO definition includes unearned revenue and amounts expected to be invoiced and recognized in future periods. Adding unearned revenue to RPO would count an included component twice.

Oracle reports $30.789 billion of total deferred revenue at August 31, 2026 in Note 5, separate from its much larger RPO. It describes advance customer payments whose revenue is generally recognized over the contractual periods or as services are used or performed. Its financing-component note also reports $11.4 billion of customer prepayments with a significant financing component during the quarter. That cash event does not make the corresponding future services current-quarter revenue.

For the wider cash picture, read the cash-flow statement rather than inferring collections from backlog. The free-cash-flow explainer covers the separate question of what remains after a company's defined capital spending.

Duration changes the meaning of a large number

Oracle expects only approximately 13% of its August RPO to become revenue over the following twelve months. Microsoft expects approximately 30% of its September total and commercial RPO over that horizon. CoreWeave gives a 24-month initial window, not a directly comparable twelve-month percentage.

A longer contract can enlarge a contract book without producing an equally large increase in next quarter's sales. Weighted-average duration is useful context, but it is not a payment schedule and does not imply revenue arrives evenly. Microsoft's approximately 2.3-year commercial duration should not be used to divide its RPO into identical annual slices.

Likewise, a company's recognition schedule is an expectation about the disclosed obligations, not full revenue guidance. New orders, consumption outside those obligations and changes to estimates can affect future reported revenue.

Read the delivery conditions in individual deals

Nebius's original September 2025 Microsoft filing is a historical contract example, not a claim about its latest company-wide backlog. The agreement describes deployment in tranches during 2025 and 2026, with value conditional on deployment and availability. Additional services or capacity could increase the stated value; that possible expansion is not the same as the base commitment.

The filing also gives Microsoft termination rights for an affected GPU service after missed delivery dates, a grace period and inability to provide alternative capacity. That makes delivery progress a meaningful reading check. A signed contract does not establish that every data hall is operational or every dollar is certain to be recognized on the original timetable.

The distinction is central to how neocloud businesses work: capacity must be financed, built and delivered before a long contract can become a stream of services.

A short checklist for the next earnings release

Record the measure's exact name, the balance date, its scope, the recognition buckets and the company's definition. Check whether figures include optional expansion, whether they overlap with another disclosed total and whether delivery or service-credit conditions can change them. Never assume a company-wide measure is entirely GPU or AI revenue.

CoreWeave's October 27 IR announcement schedules its third-quarter results conference call for November 10, 2026 at 5 PM Toronto (EST). That is a verified call time, not an inferred release hour. When the next disclosures arrive, compare like-for-like definitions and timing rather than simply celebrating a larger headline.

Our guide to reading a 10-Q explains where to find these notes. A defensible conclusion is limited but useful: what customers committed to, what remains undelivered, and when management expects to recognize it. Backlog alone establishes neither profit nor cash available to fund the build.