Summary

  • Oracle reported remaining performance obligations of $638 billion at 31 May 2026 and $664 billion at 31 August 2026, with the recognition schedule published as approximate shares of the balance in dated bands rather than as a dollar backlog.
  • The same revenue note names an elected exemption that removes a class of variable consideration from the balance, so the figure is a residual shaped partly by what the filer chose to leave out.

Every analyst note that divides a big number by annual revenue to produce a visibility quotient has to start somewhere, and the number they reach for is this one. Remaining performance obligations, $664 billion as of 31 August 2026, appears in headlines as contracted future revenue, as a backlog, as the arithmetic proof that the AI build has customers behind it. The filings do not use any of those words. They use a defined term, and the note that defines its perimeter is short enough to read in a minute.

The annual filing states the position plainly. As of 31 May 2026, "we expect to recognize approximately 12% as revenues over the next twelve months, 34% over the subsequent month 13 to month 36, 34% over the subsequent month 37 to month 60 and the remainder thereafter", against a reported balance of $638 billion (Oracle Form 10-K, fiscal 2026). One sentence, four bands, and a residual that runs past the fifth year. The quarterly filing repeats the structure with later figures: "Remaining performance obligations were $664 billion as of August 31, 2026", with approximately 13% expected in the next twelve months, 37% in months 13 to 36, 34% in months 37 to 60, and the remainder thereafter as reported in the same note (Oracle Form 10-Q, quarter ended 31 August 2026, filed 11 September 2026).

Two dated balances and two schedules make a modest comparison possible, and the comparison is arithmetic on rounded figures rather than a company statement. The balance rose $26 billion across the quarter, about 4.1% of the earlier figure. The published shares add to 80% inside sixty months in the annual filing (12 + 34 + 34) and 84% in the quarterly one (13 + 37 + 34), which leaves 20% and 16% in the band the filing calls the remainder thereafter. Apply each share to its own balance and the near-term band implies roughly $77 billion at May and roughly $86 billion at August.

Neither number is printed anywhere in either document, and the filer's rounding to whole billions and whole percentage points does not support a tighter figure than that.

Now the sentence that most readers skip, and the reason this piece exists. "We have elected the optional exemption to not disclose the variable consideration for contracts in which the variable consideration expected to be received over the duration of the contract is allocated entirely to the wholly unsatisfied performance obligations" (Form 10-K, fiscal 2026). That election is permitted, disclosed, and consequential: where consideration varies and is allocated wholly to work not yet started, it is not in the balance. The $664 billion is therefore not an inventory of everything Oracle has signed. It is the aggregate the standard requires after the exemptions the filer chose.

The annual filing carries a second election of a different kind, and it is easy to read as a statement about size when it is a statement about presentation. "We apply the practical expedient and do not adjust the promised amount of consideration for the effects of a significant financing component when the period between transfer of goods or services and customer payment is one year or less" (Form 10-K, fiscal 2026). Say it in plain terms: for short payment windows, the promised amount is not reworked to strip out an interest element. It tells you how the number is assembled, not how large it is.

The standard itself supplies the frame, and the frame needs to be attributed to the standard rather than to the company. ASC 606-10-50-13 requires disclosure of the aggregate transaction price allocated to performance obligations unsatisfied at the reporting date and an explanation of when the entity expects to recognise it; ASC 606-10-50-14 permits an entity to leave out contracts whose original expected duration is one year or less and variable consideration allocated entirely to a wholly unsatisfied obligation (FASB Accounting Standards Codification). Read those two paragraphs beside the filing and the shape of the disclosure becomes clear: an aggregate and a when are mandatory; a dollar figure per band, a currency basis and a schedule of cancellation rights are not.

That last point is where a reader's inference has to stop. The sentences obtained for this article print no dollar amount for any single band, name no currency of denomination, and set out no termination terms. Those three absences are a limit of this reading, not a claim that the documents never address them elsewhere; the filings are long, and this piece covers the remaining-performance-obligations subsection and the election sentences in the revenue note.

What can be said without qualification is narrower and more useful: no sentence electing the short-duration exclusion permitted by ASC 606-10-50-14 was obtained, so nothing here asserts what Oracle did or did not do with that option.

Put the pieces together and the mechanism is unremarkable and easily missed. A balance defined by elected exclusions can grow for reasons that have nothing to do with near-term revenue — a new long-dated signature, a contract modification, an ordinary quarter arriving. Publish the near-term slice as a share rather than a dollar amount and the growth stays legible while the conversion stays approximate. A borrower, a customer or a shareholder can still work with the figure.

They simply have to work with it as a scheduled residual, whose perimeter the filer has printed, rather than as revenue already earned or as a backlog that divides cleanly into visibility.

Oracle Corporation is catalogued in the BTW directory as Oracle Corporation.