Oracle's US$664 billion in remaining performance obligations, or RPO, describes contracted revenue still to be recognised under its reporting definition. It is not US$664 billion of revenue already earned, cash already collected or profit available to shareholders.
That distinction helps explain how a company can report rapid AI-related growth while spending more cash on infrastructure than its operations generate.
The September results in context
Oracle's 10 September 2026 earnings release reported the following for the first quarter of fiscal 2027:
| Reported measure | Rounded amount in US dollars |
|---|---|
| Revenue | $19.3 billion |
| Cloud infrastructure revenue | $7.4 billion |
| Remaining performance obligations | $664 billion |
| Operating cash flow | $23 billion |
| Free cash flow | Negative $5 billion |
The release reported cloud infrastructure revenue growth of 121% year on year. Its RPO balance rose by US$209 billion from a year earlier.
These measures cover different things. RPO is a balance at a point in time; quarterly revenue and cash flow cover activity during a period. Comparing them requires more than placing the largest number in a headline.
Four terms to keep separate
Bookings describe business signed under a company's stated convention. Definitions can differ between issuers.
RPO describes revenue allocated to remaining contractual performance obligations within the reporting scope. Check the financial-statement notes for exclusions, timing and changes.
Revenue reflects what the company has earned through delivery under the applicable accounting rules.
Cash flow follows cash receipts and payments. Billing and collection can happen before or after revenue recognition.
A company can sign a contract today, receive a deposit next quarter and deliver services over several years. Each event belongs in a different part of the analysis.
A hypothetical five-year contract
Suppose a cloud provider signs a US$100 million service contract, receives US$20 million upfront and delivers one-fifth of the service in the first year. Assume straight-line recognition is appropriate and ignore all other contracts.
| Moment | Cash collected to date | Revenue recognised to date | Remaining contracted service value |
|---|---|---|---|
| After signing and collecting the advance, before service | $20m | $0 | $100m |
| After the first year of service | $20m | $20m | $80m |
This simplified example shows why cash and revenue need not move together. Actual contract terms can produce different recognition and collection patterns.
Now suppose the provider pays US$35 million for equipment upfront. Receiving US$20 million from the customer does not fund the full equipment purchase, let alone wages, power and other obligations.
The contract might still be economically attractive over its life. To assess that, you need its future receipts, costs, funding and risks. Neither the initial cash shortfall nor the headline contract value settles the question.
Read the cash-flow bridge
Start with operating cash flow, then inspect the issuer's free-cash-flow reconciliation and capital-expenditure disclosures. Keep the reporting period consistent.
In a separate hypothetical example:
US$12 billion operating cash flow − US$15 billion capital spending = negative US$3 billion free cash flow.
That does not mean an accounting loss of US$3 billion. Equipment purchases and depreciation affect the statements differently, and companies may define free cash flow with additional adjustments.
Customer advances can also boost a period's operating cash flow while leaving future delivery costs. Look at the balance sheet and notes alongside the cash-flow total.
Oracle's financial filings are the place to examine the detailed disclosures rather than treating the earnings headline as the complete contract analysis.
Questions that test a backlog headline
- When is delivery expected? A long-duration commitment is different from revenue expected next quarter.
- How concentrated are the customers? One large counterparty can dominate the risk.
- What must the supplier build? Check equipment, power, facilities and funding requirements.
- What has the customer already paid? Separate contracted demand from collected cash.
- What could change the contract? Read cancellation, usage and other relevant terms where disclosed.
- How much profit might delivery produce? Revenue growth alone does not establish margins or returns on capital.
- What does the share price already assume? A strong company result can still fall short of market expectations.
Where information is unavailable, write “not disclosed” in your research notes. Replacing a missing assumption with an optimistic guess creates false precision.
Turn research into a testable trade thesis
A journal entry such as “AI demand is huge” gives you little to review. A more useful note identifies the next observable checkpoint: revenue conversion, delivered capacity, margin performance or financing requirements.
For example: “Review the next results for delivery against stated guidance and the relationship between operating cash flow and infrastructure spending.” That is a research task, not a prediction that the stock must rise.
If you plan to hold through the next announcement, use the earnings-season guide to decide the exposure before the release. Check portfolio concentration if several holdings depend on the same AI spending cycle.
Common questions
Is RPO the same as deferred revenue?
No. Deferred revenue generally reflects amounts billed or collected before the related revenue is earned. RPO can also include contracted amounts not yet billed, subject to the issuer's accounting disclosures.
Does negative free cash flow prove the AI investment will fail?
No. It identifies a funding and return-on-investment question. Future utilisation, pricing, costs and financing determine whether the spending creates value.
Can I convert the entire RPO balance into next year's revenue?
No. Read the disclosed timing and scope. A multi-year balance is not a one-year forecast.
Reviewed 27 September 2026. Reported Oracle figures are dated; contract examples are hypothetical. General information only, not a recommendation to buy or sell Oracle.