Summary
- Oracle reported remaining performance obligations of US$664 billion at 31 August 2026 and said it expects to recognise approximately 13 per cent of that total as revenues over the next twelve months; the reviewed passages print the band as a percentage and no dollar slice.
- The same filing discloses US$288 billion of additional lease commitments, substantially all data centre, starting between the second quarter of fiscal 2027 and fiscal 2029, while capital expenditures for the quarter were US$28,499 million against US$8,502 million a year earlier, with US$6,247 million of that spending unpaid.
A single quarter gave Oracle two very different ways of talking about the same future. On 10 September 2026 the company's first-quarter release announced that remaining performance obligations had risen US$209 billion year over year to US$664 billion, after booking more than US$30 billion of additional AI cloud contracts in the quarter (Oracle Q1 FY2027 earnings release). That is a number built for a headline, and it got one.
The quarterly report prints the same total and then attaches a sentence that reads like a timetable until you try to use it as one: remaining performance obligations were US$664 billion as of 31 August 2026, of which Oracle expects to recognise approximately 13 per cent as revenues over the next twelve months, 37 per cent over the subsequent month 13 to month 36, 34 per cent over the subsequent month 37 to month 60, and the remainder thereafter (Oracle Corp Form 10-Q, quarter ended 31 August 2026). Four bands, all percentages, no dollars anywhere in the paragraph.
One word, three accounting addresses
The word doing all the work is defined a year earlier, and the definition is worth quoting because it explains why the total is so large. The fiscal 2026 annual report states that remaining performance obligations represent contracted revenues that had not yet been recognised, and include deferred revenues; invoices that have been issued to customers but were uncollected and have not been recognised as revenues; and amounts that will be invoiced and recognised as revenues in future periods (Oracle Corp Form 10-K, fiscal year ended 31 May 2026, Note 1 policies).
Read that clause by clause and the headline becomes three populations sharing one line item: money already on the balance sheet as deferred revenue, money invoiced and still in receivables, and money not yet invoiced at all. The optional exemption the same note elects — not disclosing variable consideration allocated entirely to wholly unsatisfied performance obligations — sits behind the third population, which is the one that grows fastest when a cloud contract is signed years before it is served.
The prior-year anchor is US$638 billion at 31 May 2026, split approximately 12 per cent within twelve months, 34 per cent over months 13 to 36, 34 per cent over months 37 to 60 and the remainder thereafter (Oracle Corp Form 10-K, Note 1 remaining performance obligations). Nothing in that paragraph prints a dollar amount for the twelve-month portion either.
Two dated totals, no bridge
Between those two dates the obligation moved. US$664 billion less US$638 billion is US$26 billion, which is my subtraction, not a printed figure, and it must be read beside the release's "more than US$30 billion of additional AI cloud contracts" booked in the same quarter. The two cannot be laid end to end. Revenue recognised during the quarter, cancellations, contract modifications, foreign exchange and other bookings all move the balance, and no reviewed page prints a quantitative walk from the opening total to the closing one. A reader holding the 10-K note and the 10-Q note has two photographs and no film.
The delivery side has a window, not a calendar
Turn the page and the capacity that must serve that obligation appears in a completely different grammar. As of 31 August 2026, Oracle had US$288 billion of additional lease commitments, substantially all related to data centre arrangements, generally expected to commence between the second quarter of fiscal 2027 and fiscal 2029, for terms of fifteen to nineteen years, and not reflected on the condensed consolidated balance sheets at that date or in the maturities table (the same Form 10-Q cited above).
That sentence is precise about everything except the thing a reader wants: when. A start window spanning roughly two and a half fiscal years, and a term range of fifteen to nineteen years, is a schedule of sorts — but it is a schedule of commencement, not of rent, capacity or delivery. There is no annual figure, no discount rate, no escalator. And the filing does not describe those commitments as a subset of the obligation, which is exactly why the two must not be added, netted or divided into each other.
The same filing prints a separate category: unconditional purchase and certain other obligations of one year or more totalling US$34,150 million at 31 August 2026, described as primarily long-term supply arrangements for components for cloud infrastructure assets and power supply arrangements for data centres. Separate category, separate perimeter, and no statement anywhere about overlap with the lease commitments.
One more number belongs on the pile precisely because it is not the same instrument. The fourth-quarter release of 10 June 2026 states that the prepaid and customer supplied hardware portions of the company's large AI contracts now total US$75 billion (Oracle Q4 FY2026 earnings release). The release does not call that amount remaining performance obligations, and does not present it as a slice of them. Four quantities now sit in view: an obligation, a lease programme, a purchase-obligation total and a prepayment figure. Only the first is time-phased at all.
The spending is already on the statement
Capital spending does not wait for any of these calendars. In the condensed consolidated statements of cash flows, capital expenditures were US$28,499 million for the three months ended 31 August 2026, against US$8,502 million for the same quarter a year earlier. Under non-cash investing activities, unpaid capital expenditures were US$6,247 million, against US$4,010 million.
Note the label: the line says capital expenditures, not payments for property, equipment and capitalised software. Note also the direction of the two lines: the cash outflow more than tripled while the unpaid balance rose by roughly half, which means the quarter's build was financed partly in cash and partly on supplier terms that had not yet cleared. Neither line is a commitment schedule. There is no printed peak-spending figure, no committed-capital total in the passages read, and no annualisation offered by the document — which is why none appears here.
Multiplying one quarter by four to make an annual rate would invent a seasonality assumption the filing never states.
The arithmetic the documents invite, and refuse
Thirteen per cent of US$664 billion is about US$86 billion; twelve per cent of US$638 billion is about US$77 billion. Both are mine, both are approximate twice over — the totals are printed as round billions and the bands as "approximately" — and neither appears as a number in either filing. They are useful as a sense of scale and worthless as a forecast, because a recognition band is a statement about the accounting calendar after a contract exists, not about whether the contract will be served.
What else gets refused, and why. Dividing capital expenditure by any band would put a period cash outflow over a cumulative contracted stock and call the result a cost per dollar of backlog; the documents never join those perimeters. Dividing US$288 billion by fifteen to nineteen years would produce an annual rent with no commencement date, discount rate or escalator behind it. Adding US$288 billion to US$34,150 million, or netting US$75 billion of prepaid and customer-supplied hardware against either, would merge three categories whose overlap no reviewed page states.
Treating the capital line as the cost of the twelve-month slice ignores that the slice is a percentage and the capital is cash.
Where this reading stops
The 10-Q and the 10-K were not read end to end; the passages above were extracted from the filed pages. The liquidity discussion in MD&A beyond those passages was not obtained. No reviewed page prints a dollar amount for any recognition band, a cloud-only or AI-only obligation subtotal, or a quantitative opening-to-closing movement of the obligation. No reviewed page states whether the additional lease commitments and the unconditional purchase obligations overlap.
Nothing here alleges that any figure is wrong, that any obligation will not be delivered, or that spending is unsustainable — the subject is which page carries which instrument, and what a stranger can compose from the three.
One name boundary. The tracked directory entry is Oracle Corporation, and the filer named on the reviewed pages is Oracle Corp. The card is the entity this piece follows; it is not proof that the card and the filer are one legal person (Oracle Corporation directory entry).
What a reader can actually compose from these documents is narrower and more useful than either headline. The obligation is sold on one page, in percentages. The capacity that must deliver it is leased on another page, in a commencement window. The money is already leaving on a third, in cash. A company that manages all three has a plan; the filings we can read show three plans, each dated, none reconciled to the others. The next quarterly report is the test: it will either print a dollar slice or a movement bridge, or it will print another photograph.
Member Briefing
Read the full trend briefing
Members read the full briefing with the source notes behind every finding.
Strategic Circle
A daily briefing in your language, built from changes we have verified.
Join for USD 20/monthCancel anytime.
Members also get the full research library, a daily briefing on the networks they follow and the private forum.






