Oracle ended fiscal 2026 with $638 billion of remaining performance obligations, or RPO. That figure is important, but it is not $638 billion of revenue booked for the next year, cash in the bank, or a list of named AI customers.
RPO is the portion of contracted transaction value that Oracle has not yet recognised as revenue. The useful way to read it is with Oracle's disclosed timing bands, annual revenue, cash flow and the conditions that still have to be met before a contract turns into reported sales. Oracle's FY2026 results release and Form 10-K provide those boundaries.
Key takeaways
- Oracle reported $638 billion of RPO at May 31, 2026. It is contracted but unrecognised transaction value, not current-period revenue.
- Oracle expects approximately 12% to be recognised in the following 12 months; most of the disclosed balance is scheduled later than that.
- The $638 billion balance is 9.5 times FY2026 revenue of $67.4 billion, an ATG Press scale calculation rather than a forecast.
- Oracle reported $32.0 billion of FY2026 operating cash flow but negative $23.7 billion of free cash flow while investing in cloud infrastructure. RPO cannot be substituted for either measure.
- Oracle's next official update is FY2027 Q1 results, scheduled for September 10 after the U.S. market close. A new number or timing mix may change this framework.
RPO is a contracted-revenue measure, not a sales total
RPO means the transaction price allocated to performance obligations that have not yet been delivered, or have only partly been delivered. In plain English, it is a backlog of contract value that is still waiting to be recognised under the accounting rules.
That definition makes RPO useful, but it also sets limits on what it proves. A balance can contain contracts with different service periods, hardware arrangements, payment structures and delivery conditions. It does not identify every customer, establish a quarterly revenue run rate, or say what profit margin will be earned when the revenue is recognised.
Oracle's FY2026 release says that much of the recent RPO increase came from large-scale AI contracts. It also says that prepaid and customer-supplied hardware portions of those contracts total $75 billion. That is relevant to funding the buildout, but it is not a disclosure that all remaining RPO has identical economics or that it will convert on a single timetable.
The timing bands matter more than the headline
Oracle's 10-K gives four approximate recognition periods. Keeping the timing beside the total prevents a common error: treating a multi-year contractual balance as next year's sales.
Swipe horizontally to view all columns.
| Oracle RPO timing at May 31, 2026 | Share disclosed by Oracle | Illustrative amount using $638bn | What the row does not mean |
|---|---|---|---|
| Next 12 months | Approximately 12% | About $76.6bn | Not a quarterly target or guaranteed cash receipt. |
| Months 13–36 | Approximately 34% | About $216.9bn | Not FY2027 revenue. It spans two following years. |
| Months 37–60 | Approximately 34% | About $216.9bn | A later recognition band, not a present-period demand measure. |
| Thereafter | Remainder, approximately 20% | About $127.6bn | The residual timing is long-dated and approximate. |
| Total RPO | $638bn reported | $638bn | Contracted but unrecognised value, not revenue or free cash flow. |
On a phone, swipe the table horizontally to view all columns. The dollar illustrations are ATG Press calculations: $638 billion multiplied by Oracle's approximate disclosed percentages, rounded to one decimal place. Because the percentages are approximate, they should be used to understand the shape of the schedule, not as a precise forecast.
A 9.5-times-revenue comparison is useful—but narrow
Oracle reported $67.4 billion of total FY2026 revenue. Dividing $638 billion of RPO by that amount produces 9.5 times. This compares the size of unrecognised contractual obligations at a reporting date with a completed year of revenue.
Swipe horizontally to view all columns.
| FY2026 measure | Company-reported amount | ATG calculation or boundary |
|---|---|---|
| Remaining performance obligations | $638.0bn | Closing contracted-but-unrecognised balance. |
| Total revenue | $67.4bn | Revenue recognised during FY2026. |
| RPO / FY2026 revenue | — | 9.5 times ($638.0bn ÷ $67.4bn). |
| Operating cash flow | $32.0bn | Cash-flow measure; not revenue. |
| Free cash flow | Negative $23.7bn | Cash after capital investment; not an RPO conversion rate. |
On a phone, swipe the table horizontally to view all columns. The first, second, fourth and fifth rows are reported in Oracle's June 10 release; the 9.5-times row is ATG Press arithmetic. It does not say that RPO will become revenue at the same margin, that capital spending will fall, or that an investor should expect a particular stock-price outcome.
For another example of why infrastructure scale and cash deployment should be read together, see ATG Press's Meta capex guide. For a different disclosure boundary in the AI hardware chain, see the Broadcom AI revenue guide.
What to check in the next Oracle release
Oracle has set FY2027 Q1 results for September 10, 2026 after the U.S. market close. Use a short checklist when the company updates its figures:
1. RPO balance and timing: Did the total change, and did Oracle change the share expected in the next 12 months? 2. Recognised cloud revenue: Keep reported cloud and infrastructure revenue separate from the balance of future performance obligations. 3. Capital investment and free cash flow: RPO is a demand-and-contract measure; funding and conversion still show up in cash-flow statements and capital spending. 4. Prepayments and customer-supplied hardware: Check whether Oracle updates the $75 billion context or gives additional economic detail. 5. Definitions and concentration: Treat any change in disclosure wording, contract structure or customer concentration as potentially material to comparisons with earlier quarters.
Use the stock chart as context, not evidence
The chart below identifies Oracle on the New York Stock Exchange. Market data can be delayed and is contextual only; it is not evidence for the RPO, revenue or cash-flow figures in this article.
TradingView's symbol directory identifies NYSE:ORCL as Oracle Corporation. Use the company's releases and filings for the accounting claims.
The practical conclusion
Oracle's $638 billion RPO figure is a meaningful sign of contracted future work, particularly because the company discloses its expected timing bands. The narrow, defensible conclusion is that the reported balance is very large relative to one year of revenue and is predominantly scheduled beyond the next 12 months.
It is not an annual-sales number, a cash balance, a free-cash-flow forecast, a margin figure or an investment recommendation. Reading the balance with its timing, cash-flow and infrastructure-funding context makes the next filing more useful than the headline alone.
Sources
- Oracle — FY2026 fourth-quarter and full-year results (official release, published June 10, 2026; fiscal year ended May 31, 2026; accessed September 9, 2026)
- Oracle — FY2026 Form 10-K (official filing, filed June 20, 2026; accessed September 9, 2026)
- Oracle — FY2027 Q1 results date (official release, published September 2, 2026; accessed September 9, 2026)
- TradingView — NYSE:ORCL (symbol identity only; accessed September 9, 2026)
This article is for informational purposes only and does not constitute investment advice.
