Revenue Backlog vs RPO: What's the Difference?

EXPLAINED · Versus · Last reviewed: 13 Nov 2026 · Next review: after CoreWeave’s report for the quarter ending 31 Dec 2026, which should reprint revenue backlog and remaining performance obligations

Revenue backlog is a company’s own total of the revenue it expects to recognise later under committed contracts. Remaining performance obligation, or RPO, is the accounting remainder: the price allocated to work that has not been delivered yet.

Why an investor cares: the press release carries the company’s wrapper, and the filing carries the accounting remainder. Our total contract value Explained covers the signed book. Our remaining performance obligation Explained covers RPO as the hyperscalers report it. This page compares the two prints on the neoclouds layer.

What is the difference between revenue backlog and RPO?

Revenue backlog is a label the company writes. RPO is the remainder the accounting rules require for work not yet delivered.

CoreWeave’s results release of 10 November 2026 says revenue backlog includes remaining performance obligations, plus other amounts it estimates it will recognise later under committed customer contracts. Both parts wait on delivery and on the service being available. IREN’s results release of 5 November 2026 uses that shape and adds remaining lease arrangements. RPO itself is measured in the quarterly report.

What does CoreWeave count in each print?

On 30 September 2026 CoreWeave’s revenue backlog was approximately $132.5 billion and its unsatisfied RPO was $132.3 billion. Our arithmetic on those rounded figures puts the prints $0.2 billion apart. The release does not name the “other amounts” in that gap.

The Form 10-Q, filed on 12 November 2026, defines RPO as the transaction price, net of estimated variable consideration, allocated to performance not delivered or only partly delivered. CoreWeave’s variable consideration is its estimate of future service credits, of revenue it may miss because delivery is late, and of committed capacity it has the right to resell. RPO includes billed and unbilled amounts.

The committed contracts are take-or-pay. They accounted for 98% of revenue in the quarter, including capacity delivered before a commitment’s start date. Our RPO vs take-or-pay page separates the accounting remainder from that contract form.

A few deals are leases, with CoreWeave as lessor, under ASC 842. Lease income in the periods shown was not material. The contracted value of those leases was about $0.3 billion. That book sits outside RPO. It is close to the $0.2 billion gap, and the filing does not say the two figures are the same dollars.

Where does deferred revenue sit?

Deferred revenue is cash, or a bill, collected before delivery. It is a balance-sheet liability, and it sits inside RPO, because CoreWeave’s RPO includes billed and unbilled consideration.

On 30 September 2026 deferred revenue was $2,269 million current and $7,733 million non-current. The lines add to $10,002 million, which the note states as $10.0 billion. Our arithmetic: that is 7.6% of the $132.3 billion RPO. Subtracting it from the $132.5 billion backlog would invent a gap of $122.5 billion. The printed gap is about $0.2 billion.

During the quarter, $462 million of revenue was recognised from deferred revenue already on the books at the start. That is 12.6% of the quarter’s $3,661 million of revenue, by our arithmetic. Another $1.9 billion of the opening deferred-revenue balance moved to customer liabilities, inside other current liabilities, because contracts became cancellable. The filing states that move. It does not say whether those dollars also left RPO.

Why is IREN’s backlog larger than its RPO?

Most of IREN’s book is a lease, and a lease is not a remaining performance obligation under ASC 606.

The 5 November 2026 release put revenue backlog at $20.3 billion, up 22% from the prior quarter. The footnote includes remaining performance obligations, remaining lease arrangements, and other amounts the company estimates may be recognised later, each of them subject to delivery and availability.

The Form 10-Q gives the first two pieces. ASC 606 remaining performance obligations were $6,347 million: $1,529 million expected within 12 months, $1,652 million in months 13 to 24, and the rest in months 25 to 60. The rest is $3,166 million, by our arithmetic. The figure includes $50 million for the financing component on upfront prepayments. The remaining contracted value of lease arrangements, including capacity the customer cannot use yet, was about $13,957 million.

$6,347 million plus $13,957 million is $20,304 million, which rounds to the $20.3 billion backlog. Our arithmetic leaves no material third bucket on these prints.

Company figures from the releases and the Form 10-Qs. Sums, shares and the $0.2 billion are Second Order arithmetic.

When does the book become revenue?

Revenue starts when the company delivers and the service is available. Until that day both prints are a clock.

CoreWeave expected to recognise 36% of its $132.3 billion RPO over the 24 months to 30 September 2028, 38% in months 25 to 48, and the rest in months 49 to 86. Our arithmetic: about $47.6 billion, about $50.3 billion, and about $34.4 billion. Month 86 is seven years and two months from the balance-sheet date.

On 30 June 2026 unsatisfied RPO was $103.7 billion, with 41% expected over the 24 months to 30 June 2028, about $42.5 billion by our arithmetic. By September the near-term share had moved from 41% to 36%, and the dollars in that window had moved from about $42.5 billion to about $47.6 billion. The far end of the disclosure moved from month 78 to month 86.

RPO rose by $28.6 billion in the quarter, by our arithmetic, against $3,661 million of revenue recognised. The filing does not split that rise into new contracts, revenue recognised, and cancellations.

Who gets paid — and where is the stuck step?

Our read: the build and the lenders are paid while the book is still a book. The neocloud recognises revenue when the cluster is delivered and available.

• Equipment and buildings. Cash spent on property and equipment, including capitalised software, was $23,558 million in the nine months to 30 September 2026. Revenue in those nine months was $8,314 million. The cash out was 2.83 times revenue recognised, by our arithmetic. The filing does not name the suppliers.
• Lenders. Interest expense, net, was $846 million in the quarter. Operating income was $207 million.
• Customers who pay early. Deferred revenue of $10.0 billion is cash already in for work still owed. The 10 November release said CoreWeave expects about $9 billion of further prepayments and deposits in the next three months. That is an expectation, not cash already booked.
• The neocloud. In the quarter, 98% of revenue came from committed contracts, recognised as the capacity is delivered.

The stuck step is delivery. Both definitions hold the dollars until delivery and availability. Our GPU cluster acceptance Explained is the test at the end of that wait. Our contracted power Explained is the megawatt version of a signed claim that is not yet earning. The same release put active power over 1.7 gigawatts, after more than 200 megawatts added, with more than 1.85 gigawatts still expected at year-end.

What would change the view?

• The prints part. If the “other amounts” in backlog move well past RPO, the press-release book and the accounting remainder are no longer one story. On 30 September 2026 they were $0.2 billion apart on the rounded prints.
• More contracts become cancellable. CoreWeave already moved $1.9 billion out of deferred revenue for that reason. Whether RPO moves with a larger reclassification is something the next filing would have to say.
• The lease book grows. Leases were about $0.3 billion, and lease income was not material. If that book became a large share of backlog, as IREN’s $13,957 million of leases already is, the two prints would separate.
• The near-term dollars stall. Dollars expected in the next 24 months rose from about $42.5 billion to about $47.6 billion while their share of the book fell. A flat dollar slice beside a rising headline would mean new signatures are landing further out.

Common misconceptions

• People assume revenue backlog and RPO are different piles of money. Actually, at CoreWeave on 30 September 2026 they were two prints of one book, about $132.5 billion and $132.3 billion.
• People assume deferred revenue is the gap between the prints. Actually it was $10.0 billion and sits inside RPO. The printed gap was about $0.2 billion, by our arithmetic on the rounded figures.
• People assume every neocloud’s backlog equals its RPO. Actually IREN’s backlog was $20.3 billion and its ASC 606 RPO was $6,347 million. The lease book sits outside RPO.
• People assume a bigger backlog is this year’s revenue. Actually 36% of CoreWeave’s RPO, about $47.6 billion, is the 24-month slice to 30 September 2028. The disclosure runs to month 86.

FAQ

Related terms

Related: total contract value; remaining performance obligation; deferred revenue; RPO vs take-or-pay; GPU cluster acceptance; contracted power.

Markets and stack doors

Layer: Neoclouds. Markets: US. Wire: CoreWeave’s $132.5 billion backlog, and the power that is not yet live.

References