CoreWeave reported $2.575 billion of revenue for the quarter ended 30 June 2026 in its 11 August earnings release. Its accompanying second-quarter presentation put revenue backlog at $104.2 billion, including $103.7 billion of remaining performance obligations and $0.5 billion of other estimated future revenue under existing committed customer contracts.
The second-quarter outlook raised full-year 2026 capital-expenditure guidance to $35 billion to $39 billion from the first-quarter range of $31 billion to $35 billion. The current range is guidance, not incurred capex or immediate expense. For a group financial controller, those figures do not form one accounting bridge. Contract status, service availability, billing, asset readiness, depreciation and borrowing costs each need their own cut-off evidence before commitments or constructed capacity reach revenue or expense. CoreWeave has not disclosed the transaction-level evidence or control design behind those six gates, and this analysis does not allege that any recorded balance is misstated.
What changed and what it means
Misaligned status dates can advance or delay revenue, misclassify contract balances and construction in progress, or shift depreciation and interest between assets and expense.
- Decision affected
- Decide whether quarter-end evidence supports the separate cutoff of committed contracts, RPO, contract balances, capacity delivery, assets placed in service, depreciation and capitalized interest.
- Evidence in brief
- CoreWeave’s Q2 records distinguish $104.2bn of backlog from $2.575bn of revenue and disclose RPO, contract balances, construction in progress, depreciation and capitalized interest.
- What remains unresolved
- Public filings do not disclose contract-level acceptance evidence, site-level placed-in-service approvals or the exact control design for these six close gates.
- Next verification
- Reconcile contract status, service availability, billing, commissioning and financing evidence before locking revenue and infrastructure-cost entries.
Key takeaways
- CoreWeave’s $104.2 billion backlog at 30 June 2026 was not recognized revenue; it combined $103.7 billion of RPO with $0.5 billion of other estimated future revenue.
- RPO includes billed and unbilled consideration, while deferred revenue and contract assets reflect different performance and invoicing states.
- Construction in progress was $11.918 billion, so placed-in-service approval controls when asset balances enter the depreciable population.
- Capitalized interest was $79 million for the quarter and net interest expense was $640 million, making the capitalization cut-off a separate close decision.
What CoreWeave’s $104.2bn backlog actually contains
CoreWeave’s backlog rose from $99.4 billion at 31 March, as shown in its first-quarter release, to $104.2 billion at 30 June. The headline measure is broader than RPO. The company’s presentation separates it into $103.7 billion of RPO and $0.5 billion of other amounts it estimates will become revenue under existing committed contracts. Both components remain subject to delivery and service-availability requirements.
The June 2026 Form 10-Q defines RPO as transaction price, net of estimated variable consideration, allocated to obligations that are undelivered or partly undelivered. That estimate considers potential availability credits, delivery delays and capacity that CoreWeave has a right to resell. The filing also says RPO includes billed and unbilled consideration.
That combination is why backlog cannot be read as an invoice balance or a revenue balance. A contract can enter RPO before service is available. Consideration can be billed before performance and sit in deferred revenue. Service can be delivered before an unconditional right to payment exists and create a contract asset. Recognized revenue follows the performance obligation, not the commercial label attached to the order book.
One quarter contains several accounting states
| Reported measure | 30 June 2026 state | Close question |
|---|---|---|
| Quarterly revenue | $2.575 billion | Which services were delivered in the quarter under the approved recognition policy? |
| Revenue backlog | $104.2 billion | Which committed amounts satisfy the company’s backlog definition and remain subject to delivery or availability? |
| Unsatisfied RPO | $103.7 billion | Do contract terms, variable-consideration estimates and billed or unbilled status support the population? |
| Deferred revenue | $9.7 billion | Which invoices or prepayments precede performance, and when should each balance release? |
| Contract assets | $179 million | Which delivered services have earned consideration that remains conditional? |
| Construction in progress | $11.918 billion | Which assets were not yet ready for their intended use at quarter end? |
| PP&E depreciation and amortization | $1.4 billion for Q2 | Did the depreciable population start on supported placed-in-service dates? |
| Capitalized interest | $79 million for Q2 | Were qualifying construction activities still in progress for each capitalized amount? |
Even “capital expenditure” needs a definition check. CoreWeave’s presentation calculates $9.352 billion for Q2 as the increase in gross property and equipment, including assets acquired under finance leases, less the change in construction in progress. The earnings-release cash-flow statement separately reports $6.422 billion of cash purchases of property and equipment. Neither number is a depreciation charge, and the two figures should not be forced into one cash-to-expense bridge.
Build one close bridge, not one metric
1. Confirm contract status before accepting the RPO population
The contract register should identify the executed agreement, enforceable term, committed capacity, pricing, renewal or termination provisions, material rights and approval date. The RPO schedule then needs a contract-level bridge to transaction price, variable consideration and unsatisfied obligations. A signed commitment can support inclusion in the commercial population without proving that service has started or revenue has been earned. The Cerebras finance-systems case adds a mixed hardware-and-cloud example in which commercial model, pass-through, customer-warrant and rented-capacity states change how revenue and margin are read.
2. Prove service availability before starting revenue
CoreWeave’s 2025 Form 10-K accounting policy says committed contracts provide access to cloud capacity over a specified duration and revenue is recognized ratably over the contract period. The close file therefore needs the operational event that establishes delivery and availability, not only a contract effective date. Commissioning records, customer notices, capacity allocation, incident data and service-credit calculations should agree with the revenue start and any constraint on consideration.
3. Reconcile billings to deferred revenue and contract assets
The 10-Q reports $9.7 billion of current and non-current deferred revenue, up from $8.2 billion at 31 December 2025, and $179 million of contract assets. The controller should roll those balances by contract and explain invoices, cash, service delivered, revenue recognized, credits and reclassifications. Because RPO contains both billed and unbilled consideration, billing completeness does not prove RPO completeness, and an invoice does not prove revenue.
4. Separate construction from assets placed in service
Construction in progress increased to $11.918 billion from $9.376 billion at year end. CoreWeave’s policy defines CIP as property and equipment not yet placed into service for its intended use. The fixed-asset register should therefore require a supported readiness date, asset location, component detail, cost accumulation and approval to transfer from CIP. Contracted power, delivered equipment or construction spend alone does not establish that an asset is ready for depreciation.
5. Start depreciation from the approved asset population
PP&E depreciation and amortization was $1.4 billion in Q2 2026, compared with $553 million a year earlier. The close should reconcile opening depreciable assets, transfers from CIP, disposals, useful lives, partial-period conventions and ledger expense. A late commissioning date affects both ending CIP and current-period depreciation, so the two reviews should share the same approved placed-in-service evidence.
6. Stop capitalizing interest at the supported cut-off
CoreWeave capitalized $79 million of interest in Q2 and reported $640 million of net interest expense. Its filing says net interest expense is presented after capitalized interest. The capitalization schedule should identify qualifying assets, eligible debt or weighted-average rates, accumulated expenditures, active preparation periods and suspension or completion dates. The control question is not whether borrowing exists, but whether activities needed to prepare each asset for its intended use remained in progress.
What the control disclosure does and does not establish
CoreWeave disclosed in its controls assessment that previously identified material weaknesses continued at 30 June 2026. The filing describes weaknesses involving IT general controls, segregation of duties and the number of qualified finance, accounting and operations personnel. It also states that the identified deficiencies did not result in a material misstatement.
That disclosure raises the importance of reproducible close evidence, but it does not prove a failure in any of the six controls mapped here. The public filing does not disclose contract-level acceptance files, site-level placed-in-service approvals, depreciation-start testing or the detailed capitalized-interest schedule. Those items remain unknown outside the company and should not be inferred from the existence of broader material weaknesses.
The controller’s quarter-end evidence pack
Before locking the period, the controller should require six reviewed schedules: a contract-to-RPO roll-forward, a service-availability-to-revenue bridge, a billing-to-contract-balance reconciliation, a CIP-to-placed-in-service roll-forward, a depreciation population test and a capitalized-interest calculation. Each should use the same contract, site, asset and date identifiers so exceptions can be traced across commercial, operations, billing, fixed-assets and treasury records.
The $104.2 billion backlog provides visibility into estimated future revenue under committed contracts. It does not replace the evidence that determines when revenue begins, when a billed amount remains deferred, when constructed capacity becomes depreciable or when borrowing cost stops entering the asset. Those are separate close decisions, and the quarter-end file should preserve their boundaries. Where those decisions are automated, revenue recognition software selection determines whether the schedule and its supporting evidence stay reproducible after a contract changes.
