Oracle’s $288 billion lease promise is not a $288 billion balance-sheet debt

Oracle · Form 10-Q for 31 August 2026 · all amounts in USD

The $288 billion is disclosed, but the leases have not begun

Oracle’s lease note separates the obligations already measured on its balance sheet from signed commitments for future data-center use. Reading them as the same kind of debt creates a false comparison.

1. $43.806 billion is recordedIt is the present-value liability for operating and finance leases already commenced.
2. $288 billion is still aheadAdditional leases are expected to commence from fiscal Q2 2027 through FY2029 and are outside the existing maturity table.
3. $664 billion is a different promiseCustomer remaining performance obligations are future revenue, not a cash reserve that offsets lease payments.

Oracle reported $288 billion of additional lease commitments in its quarterly filing for 31 August 2026. The number is extraordinary. It is also easy to put in the wrong column. It is not the amount of rent due this year, and it is not the lease liability already recorded on the balance sheet. The filing says these commitments have generally not yet commenced; Oracle generally expects them to start between the second quarter of fiscal 2027 and fiscal 2029 and run for 15 to 19 years.

The distinction is neither a loophole nor a reason to ignore the commitments. It is the difference between a future right to use capacity and a lease already under way. A reader who follows the numbers through Oracle’s lease note can see exactly what has been recognized, what remains outside the maturity table and why the company’s $664 billion customer backlog cannot simply be netted against either amount.

A lease enters the accounts when use begins

US lease accounting recognizes a right-of-use asset and a lease liability at the commencement date. Signing a contract and being able to use the underlying property can happen at different times. For a data-center project, there can be a long construction interval between those events. Oracle explicitly states that its $288 billion of additional commitments was absent from both the 31 August balance sheet and the lease-liability maturity table. It does not hide the amount; it puts the figure immediately after that table in Note 6.

That accounting boundary matters to an investor because the economic promise can already shape decisions. A future lease can commit the company to years of payments even before the capacity is available. But calling all $288 billion “current debt” would make a different mistake: the filing provides neither a present-value liability for those uncommenced arrangements nor a year-by-year payment schedule for them. The standard’s recognition point and the economic risk are two separate observations.

The existing lease book reconciles to $43.806 billion

For leases already commenced, Oracle reports $34.621 billion of operating lease liabilities and $9.185 billion of finance lease liabilities. Together they equal $43.806 billion. The same note gives the future cash-payment schedule for those existing leases: $48.050 billion operating plus $15.195 billion finance, or $63.245 billion in undiscounted payments. Subtract $13.429 billion and $6.010 billion of imputed interest, respectively—$19.439 billion in total—and the result is exactly the recorded $43.806 billion.

This bridge is a useful guardrail. Adding $63.245 billion to $43.806 billion would count the same commenced leases twice—once as cash to be paid over time and again as their discounted liability today. Likewise, the $288 billion should not be treated as if it were already part of the $63.245 billion schedule: Oracle says it is not in that table. The graphic uses a completed and an unfinished wing to show an accounting timing difference; it is an original illustration, not a photograph of an Oracle facility.

The $288 billion line is large but not due at once

The $288 billion covers additional lease commitments, substantially all related to data-center arrangements. Its 15-to-19-year terms are a range of contract lengths, not a disclosed annual rent schedule. Dividing $288 billion by 15 or 19 would ignore different commencement dates, payment shapes and terms. The filing also does not tell readers which individual customer contracts will occupy which leased site. These limits matter more than a neat “annualized obligation” that the note cannot support.

The scale has changed sharply. In the comparable August 2025 quarterly filing, Oracle reported $99.8 billion of additional not-yet-commenced lease commitments, mostly data centers. The August 2026 figure is $188.2 billion higher, or about 2.89 times the year-earlier snapshot. That subtraction is not $188.2 billion of newly signed leases: some earlier commitments may have commenced, expired, changed or been replaced, and the two notes report stocks at dates, not a full gross additions-and-runoff bridge. The disclosed range of lease terms also changed from 10–16 years to 15–19 years, so even average contract duration cannot be assumed constant.

The risk is real without overclaiming the accounting. Oracle spent $28.499 billion on capital expenditures in the quarter and reported $23.103 billion of operating cash flow, including $11.363 billion of customer prepayments with a significant financing component. Those are quarter-specific cash-flow figures, not lease payments scheduled by the $288 billion disclosure. They explain why funding and delivery timing deserve attention, but they do not establish a single debt-like present value for the uncommenced leases. This is akin to the distinction in our Nike inventory analysis: an impressive reported amount can be genuine while failing to answer the operational question investors actually have.

Customer backlog is the other side of the buildout

Oracle reported $664 billion of remaining performance obligations from customer contracts at 31 August. It expects approximately 13% to be recognized as revenue in the next twelve months, 37% in months 13–36, 34% in months 37–60 and the remainder later. RPO is contracted revenue not yet recognized. It is not cash already collected and is not a lease asset the company can apply against a landlord’s claim. No filed table matches individual RPO contracts to the $288 billion of future lease commitments, so subtracting one aggregate from the other would produce a number with no defensible accounting meaning.

That does not make the backlog irrelevant. Customer commitments can support an investment decision, just as rising Data Center sales can support an expansion case in our AMD segment analysis. The question is whether the capacity arrives, is used, produces recognized revenue and yields adequate cash after power, equipment, leases and financing. Oracle’s 10-Q supports that sequence as a set of tests. It does not provide a guaranteed margin on the $664 billion or show that every future lease is covered by an identical customer commitment.

Four checks for the next filing

• Watch the two lease populations separately. Has the $288 billion not-yet-commenced line changed, and how much new right-of-use asset and lease liability appears as facilities actually commence? The same 10-Q reports $4.903 billion of operating and $1.539 billion of finance right-of-use assets obtained in exchange for lease obligations in the quarter; those are period flows, not a complete movement bridge for the $288 billion stock.
• Follow payments, not only the balance. The existing lease maturity table shows dated future payments, while the uncommenced line has no annual schedule. Look for the next note’s timing and cash-paid disclosures before constructing a rent run rate.
• Keep capital spending and customer financing visible. Compare capital expenditures with operating cash flow and identify how much of the latter comes from prepayments. A prepayment helps fund capacity today but relates to service still to be delivered.
• Test conversion instead of netting promises. Track whether Oracle’s customer RPO becomes revenue and cash while cloud infrastructure expenses, leases and depreciation rise. A customer backlog and a supplier lease commitment are different contracts.

The discipline resembles our FedEx period-comparison test: before calculating a dramatic change, check whether both sides measure the same thing over the same period. Here the first hurdle is even earlier. The $43.806 billion liability, $288 billion future commitment and $664 billion RPO do not share a measurement basis or a counterparty. The note is most informative when read as three connected questions, not as one subtraction.

Questions about Oracle’s lease commitments

Primary filings and accounting rule

SEC filings and FASB lease guidance checked 28 September 2026

• Oracle Form 10-Q for 31 August 2026 — Note 6 lease assets, liabilities, maturity schedule, uncommenced commitments and purchase obligations; Note 1 customer RPO; MD&A cash flows.
• Oracle Form 10-Q for 31 August 2025 — year-earlier $99.8 billion additional lease commitment snapshot and earlier term range.
• FASB Accounting Standards Update 2016-02, Leases — paragraph 842-20-25-1 recognizes a right-of-use asset and lease liability at commencement.

All dollar amounts are US billions unless stated otherwise. Reconciliations and ratios are PolymathDesk arithmetic from filed figures; they are not a valuation or a recommendation to buy or sell Oracle shares. No Oracle facility is depicted in the editorial illustration.