> ## Content Index
> Fetch the complete content index at: https://www.sotkn.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# What Is Remaining Performance Obligation? Cloud Backlog That Is Not Cash Yet
- URL: https://www.sotkn.com/explained/remaining-performance-obligation-explained/
- Published: 2026-09-28T01:12:49.000Z
- Updated: 2026-09-28T01:12:49.000Z
- Description: Remaining performance obligation is contracted revenue that a cloud operator has not yet recognised: the customer has promised to buy, the operator has promised to deliver, and the cash line waits until the service is performed.
- Author: Sean
- Tags: #desk-explained, Mechanism

EXPLAINED · Mechanism · Last reviewed: 28 Sep 2026 · Next review: after next hyperscaler earnings that print remaining performance obligations

Remaining performance obligation (RPO) is contracted revenue that a cloud operator has not yet recognised: the customer has promised to buy, the operator has promised to deliver, and the cash line waits until the service is performed.

**In short.** RPO is how the [hyperscalers](https://www.sotkn.com/stack/hyperscalers/) layer shows booked cloud demand that is not yet revenue. The stuck step is delivery — energised halls, installed GPUs, accepted capacity — not the booking print. A larger RPO is a longer clock, not cash in the door.

Who gets paid when AI cloud contracts stack up, and which clock you are watching — the booking, the hall, or the recognised hour. Compare the demand dial in [what a hyperscaler is](https://www.sotkn.com/explained/hyperscaler-explained/) and the billed hour in [GPU as a service](https://www.sotkn.com/explained/gpu-as-a-service-explained/).

## What is remaining performance obligation?

Remaining performance obligation is an accounting disclosure. Under US GAAP (ASC 606), a public company reports the transaction price allocated to performance obligations that are unsatisfied, or only partly satisfied, at period-end — plus an explanation of when it expects to recognise that amount as revenue (PwC on ASC 606-10-50-13). In plain English: contracted work still on the books.

Oracle’s 10-K is the hyperscaler version. Remaining performance obligations “represent contracted revenues that had not yet been recognized,” including deferred revenues, uncollected invoices, and amounts that will be invoiced later (year ended 31 May 2026). Three buckets, one number: cash already in, invoices sent, and amounts not billed yet.

The product underneath is usually a cloud subscription, a committed GPU block, or a multi-year infrastructure deal. RPO is the promise in the middle: hours and regions still to perform.

| Label                            | What it is                                 | Cash clock             |
| -------------------------------- | ------------------------------------------ | ---------------------- |
| Booking / contract               | A signed commitment                        | Not revenue            |
| Deferred revenue                 | Cash (or a due invoice) before performance | Cash in; revenue later |
| Remaining performance obligation | Unsatisfied contracted transaction price   | Revenue when delivered |
| Recognised revenue               | The service was performed                  | The P&L line           |

RPO is not a physical part like [HBM](https://www.sotkn.com/explained/hbm-explained/) or [CoWoS](https://www.sotkn.com/explained/cowos-explained/). It is the commercial layer on top. Silicon still has to ship. [Speed-to-power](https://www.sotkn.com/explained/speed-to-power-explained-for-investors/) still has to light the hall.

## Why is RPO not cash — and not this quarter’s revenue?

Revenue is recognised when (or as) the operator satisfies the performance obligation — when control of the service transfers to the customer (ASC 606). A five-year AI cloud contract that starts next year does not print five years of revenue this quarter. It prints RPO now, and revenue later, as hours or subscription periods are delivered.

Oracle’s year-end clock makes the lag visible. As of 31 May 2026, remaining performance obligations were US$638 billion. The company expected to recognise about 12% as revenue over the next twelve months, 34% over months 13 to 36, 34% over months 37 to 60, and the remainder after that (Oracle 10-K, year ended 31 May 2026). Our arithmetic on those company percentages: 12% of US$638 billion is about US$77 billion in the next year; 34% is about US$217 billion in the following two years. 12% + 34% = 46%, so about 54% — roughly US$345 billion — sat beyond month 36\. Booked is not this year’s cloud line.

The Q1 FY27 print then moved the headline. On 10 September 2026 Oracle said remaining performance obligations rose 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 investor release / PR Newswire, 10 Sep 2026). That US$664 billion is a later snapshot. Do not apply the 31 May conversion bands to it — those percentages were disclosed for the year-end figure.

The other hyperscalers print cousins of the same disclosure — not the same cut. Microsoft’s commercial remaining performance obligation rose 84% to US$678 billion as of 30 June 2026 (FY26 Q4 release, 29 Jul 2026). The call added a 2.3-year weighted duration, roughly 30% recognised in the next 12 months, and +25% excluding OpenAI (29 Jul 2026). 30% of US$678 billion is about US$203 billion — our arithmetic. That book is commercial cloud, not GPU hours alone.

Amazon’s long-term AWS remainder was about US$496 billion as of 30 June 2026 (original contract term over one year; 6.4-year weighted remaining life; usage- and performance-driven) (Form 10-Q). Alphabet’s remaining performance obligations — it also says “revenue backlog” — were US$519.5 billion, of which US$513.9 billion related to Google Cloud, with just over 50% expected over the next 24 months; from Q1 2026 the figure includes contracts of one year or less (Form 10-Q, 30 Jun 2026).

| Operator (dated snapshot)     | Figure                             | Conversion clock                                                     | Cut                                                           |
| ----------------------------- | ---------------------------------- | -------------------------------------------------------------------- | ------------------------------------------------------------- |
| Oracle, 31 May 2026           | US$638B RPO                        | \~12% next 12 months; 34% months 13–36; 34% months 37–60; rest after | Includes deferred; some variable consideration exempt         |
| Oracle, 10 Sep 2026 (Q1 FY27) | US$664B RPO                        | Not restated in the Q1 release                                       | Later snapshot after >US$30B AI cloud bookings                |
| Microsoft, 30 Jun 2026        | US$678B commercial RPO             | \~30% next 12 months; 2.3-year duration (call)                       | Commercial cloud, not GPU hours alone                         |
| Amazon, 30 Jun 2026           | \~US$496B                          | Usage + performance; 6.4-year remaining life                         | Original term > one year; primarily AWS                       |
| Alphabet, 30 Jun 2026         | US$519.5B (US$513.9B Google Cloud) | Just over 50% next 24 months                                         | Includes ≤1-year contracts from Q1 2026; excludes cancellable |

Those five rows are not a league table. Different exemptions, mixes, and clocks. Adding them together does not measure AI demand.

## How does RPO turn into a billable hall?

On the hyperscalers layer, RPO converts when three things line up: the contract is enforceable, the operator can perform, and the customer uses the service — or a committed term still bills.

ASC 606 only counts the non-cancellable term (PwC on ASC 606-10-50-13). Alphabet’s backlog excludes cancellable contracts (10-Q, 30 Jun 2026). Oracle recognises consumption infrastructure on utilisation, and subscription cloud ratably once the service is made available (10-K, year ended 31 May 2026). Amazon’s 10-Q is blunt: amount and timing are driven by customer usage and AWS’s performance. A committed block can still bill while idle; an on-demand remainder does not. [GPU as a service](https://www.sotkn.com/explained/gpu-as-a-service-explained/) is the hour. RPO is the unsatisfied contracted price of hours — and other cloud — still to come.

The physical stack still sits underneath. [CoWoS](https://www.sotkn.com/explained/cowos-explained/) and HBM decide when the next tray can ship. [Speed-to-power](https://www.sotkn.com/explained/speed-to-power-explained-for-investors/) and [behind-the-meter power](https://www.sotkn.com/explained/behind-the-meter-power-ai-halls-explained/) decide when a delivered tray becomes an energised hall. Oracle’s Q1 FY27 print showed the delivery side: 850 MW of additional datacenter capacity and more than 300,000 GPUs since the end of Q4, with 97.9% utilisation (investor release and slides, 10 Sep 2026 — company-reported). Capacity delivered is not RPO. RPO is what is still left to perform.

A useful test: if RPO rises while delivered megawatts and utilisation stall, the book is getting longer than the hall. Wire: [Oracle 850 MW — fleet still 97.9% full](https://www.sotkn.com/wire/oracle-850mw-gpu-fleet-still-full-wire/).

## Who gets paid — and where is the stuck step?

On the hyperscalers layer, who gets paid tracks which step clears first when a large AI contract is signed.

| Step            | Who                                                                                               | Why it matters                                                                  |
| --------------- | ------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------- |
| Booking         | Hyperscaler (sometimes a [neocloud](https://www.sotkn.com/explained/neocloud-explained/) offtake) | RPO goes up. Cash may or may not.                                               |
| Stuck step      | Delivery — energised MW, installed GPUs, accepted capacity                                        | Unsatisfied obligations stay unsatisfied until the hall is live                 |
| Upstream feed   | Packaging, HBM, servers                                                                           | No finished accelerator, no hour to perform                                     |
| Power + cooling | Halls, interconnect, CDUs                                                                         | Watts make the obligation satisfiable                                           |
| Customer        | AI lab or platform                                                                                | Pays as the service is delivered — or under a committed term even if usage lags |

Cash can stick at the operator once the fleet is full — Oracle’s 97.9% utilisation after the 850 MW add is one dated print (company-reported, 10 Sep 2026). Cash can stick at the customer as prepaid deferred revenue before the hall is accepted. Cash can stick upstream when CoWoS or HBM bind. The RPO print does not name which of those three is binding. The conversion clock plus the delivery print do.

The US market door is where most public hyperscaler RPO sits: [US speed-to-power](https://www.sotkn.com/markets/us/us-speed-to-power-september-2026/) when halls wait on watts, and [1.8 GW, $1 credit](https://www.sotkn.com/markets/us/us-ferc-joliet-credit-september-2026/) when interconnect — not the booking desk — is the story. China is the other door when domestic hours cannot use the same stack — [China HBM access](https://www.sotkn.com/markets/china/china-hbm-access-september-2026/).

A concentration test, not a ticker call: if a handful of AI offtakers dominate the RPO add, the conversion clock is their delivery and their usage. Microsoft’s Q4 FY26 call said sequential commercial RPO growth came from customers *outside* frontier model companies, with RPO still up 25% excluding OpenAI (29 Jul 2026). Mix disclosure. Not a ranking.

## Common misconceptions

- **People assume remaining performance obligation is cash.** Actually it is unsatisfied contracted transaction price. Deferred revenue is the slice where cash already arrived.
- **People assume a bigger RPO than a peer means more AI demand.** Actually each operator defines the disclosure differently. Compare clocks, not headline billions.
- **People assume RPO converts on a straight line.** Actually Oracle’s year-end bands put only about 12% in the next twelve months (10-K, 31 May 2026). Amazon’s long-term AWS book has a 6.4-year weighted remaining life (10-Q, 30 Jun 2026).
- **People assume booking a US$30 billion AI cloud contract delivers US$30 billion of hours.** Actually Oracle’s Q1 FY27 release separated the two: more than US$30 billion of additional AI cloud contracts *and* 850 MW / 300,000+ GPUs delivered since Q4 (10 Sep 2026).

Not investment advice. Do your own research.

## FAQ

**What is remaining performance obligation?**  
Remaining performance obligation is contracted revenue a company has not yet recognised — the transaction price allocated to performance obligations that are unsatisfied or only partly satisfied at period-end (ASC 606). In cloud, it is booked demand waiting on delivery.

**Is RPO the same as revenue?**  
No. Revenue is recognised when the operator performs. Oracle’s 10-K (year ended 31 May 2026) expected to recognise about 12% of its US$638 billion RPO over the next twelve months. The rest sat on a longer clock.

**How is RPO different from deferred revenue?**  
Deferred revenue is cash collected (or a due invoice) before the service is performed. RPO includes deferred revenue plus amounts not yet invoiced. Oracle’s 10-K lists all three: deferred, uncollected invoices, and future invoices.

**Why do hyperscaler RPO figures not match each other?**  
They are not the same cut. Microsoft prints commercial RPO (US$678 billion as of 30 June 2026). Amazon prints long-term AWS commitments (\~US$496 billion; original term over one year). Alphabet prints remaining performance obligations it also calls revenue backlog (US$519.5 billion), including shorter contracts from Q1 2026\. Compare the footnote, not the headline.

**When does RPO become cash?**  
When the operator invoices and collects — which may be before, as, or after it recognises revenue, depending on prepayments versus consumption. Conversion to revenue happens when the service is delivered. Amazon’s 10-Q says timing is driven by customer usage and AWS’s performance.

**Who gets paid when RPO binds?**  
Operators get paid as they deliver (and when customers prepaid). Upstream, packaging and HBM get paid when the next tray cannot ship. The stuck step is delivery — energised megawatts and accepted capacity — not the booking print.

**Does a bigger RPO mean the operator is safer?**  
No. A larger remainder can mean more contracted demand, a longer delivery clock, a lumpier customer mix, or all three. Microsoft disclosed a 2.3-year weighted duration and that roughly 30% of commercial RPO would be recognised in the next 12 months (FY26 Q4 call). Duration is the clock. It is not a credit rating.

## Related terms

- [Hyperscaler](https://www.sotkn.com/explained/hyperscaler-explained/) — the CapEx dial whose cloud contracts fill RPO.
- [GPU as a service](https://www.sotkn.com/explained/gpu-as-a-service-explained/) — billed accelerator hours; what RPO is waiting to become.
- [Neocloud](https://www.sotkn.com/explained/neocloud-explained/) — specialist seller of the same hour, often as an offtaker or overflow.
- [Neocloud vs hyperscaler](https://www.sotkn.com/explained/neocloud-vs-hyperscaler/) — same GPUs, different who gets paid.
- [Speed-to-power](https://www.sotkn.com/explained/speed-to-power-explained-for-investors/) — the hall clock that decides when an obligation can be satisfied.

## Markets and stack doors

Layer: [hyperscalers](https://www.sotkn.com/stack/hyperscalers/). Sibling layer: [neoclouds](https://www.sotkn.com/stack/neoclouds/). Markets: [US speed-to-power](https://www.sotkn.com/markets/us/us-speed-to-power-september-2026/) · [US interconnect credit](https://www.sotkn.com/markets/us/us-ferc-joliet-credit-september-2026/) · [China HBM access](https://www.sotkn.com/markets/china/china-hbm-access-september-2026/).

[Get the Wire](https://www.sotkn.com/#/portal/signup) — short notes when cloud backlog or hall clocks move. Wire: [Oracle 850 MW](https://www.sotkn.com/wire/oracle-850mw-gpu-fleet-still-full-wire/) · [Oracle Project Jupiter force majeure](https://www.sotkn.com/wire/oracle-project-jupiter-force-majeure-power-wire/). Analysis: [where the stuck step moves](https://www.sotkn.com/analysis/where-does-the-stuck-step-move/).

**How we check this**

Figures come from company filings and government releases, each dated in the list below. Capacity and timing from press reports are labelled as reported, not guided. Where we work something out ourselves, the arithmetic is shown in full.

**Last reviewed:** 28 Sep 2026 · **Next review:** after next hyperscaler earnings that print remaining performance obligations

Spot an error? [Tell us](mailto:sean@thekopinotes.com) and we will correct it and note the change here.

[Our editorial standards →](https://www.sotkn.com/editorial-standards/)

## Sources

- [PwC Viewpoint — ASC 606-10-50-13 remaining performance obligations disclosure (accessed 28 Sep 2026)](https://viewpoint.pwc.com/dt/us/en/pwc/accounting%5Fguides/financial%5Fstatement%5F/financial%5Fstatement%5F%5F%5F18%5FUS/Chapter-33--Revenue-and-contract-costs/33-4-Revenue-disclosures-ASC-606.html?ref=sotkn.com)
- [Oracle 10-K note — RPO definition; US$638B as of 31 May 2026; \~12% / 34% / 34% conversion bands](https://www.sec.gov/Archives/edgar/data/1341439/000119312526277521/R27.htm?ref=sotkn.com)
- [Oracle investor release — Q1 FY27; RPO US$664B; >US$30B AI cloud contracts; 850 MW; >300,000 GPUs (10 Sep 2026)](https://investor.oracle.com/investor-news/news-details/2026/Oracle-Announces-Q1-Results-Driven-by-Triple-Digit-Growth-in-Cloud-Infrastructure-Revenues/default.aspx?ref=sotkn.com)
- [Oracle / PR Newswire — same Q1 FY27 figures (10 Sep 2026)](https://www.prnewswire.com/news-releases/oracle-announces-q1-results-driven-by-triple-digit-growth-in-cloud-infrastructure-revenues-302875728.html?ref=sotkn.com)
- [Oracle Q1 FY27 slides — 97.9% utilisation; 850 MW incremental DC capacity (10 Sep 2026)](https://static.seekingalpha.com/uploads/sa%5Fpresentations/523/135523/original.pdf?ref=sotkn.com)
- [Microsoft FY26 Q4 earnings release — commercial RPO US$678B, +84% (29 Jul 2026)](https://www.microsoft.com/en-us/Investor/earnings/FY-2026-Q4/press-release-webcast?ref=sotkn.com)
- [Microsoft FY26 Q4 earnings call — 2.3-year duration; \~30% next 12 months; +25% excluding OpenAI (29 Jul 2026)](https://www.microsoft.com/en-us/investor/events/fy-2026/earnings-fy-2026-q4?ref=sotkn.com)
- [Amazon Form 10-Q — \~US$496B long-term AWS performance obligations; 6.4-year weighted remaining life (30 Jun 2026)](https://www.sec.gov/Archives/edgar/data/1018724/000101872426000026/amzn-20260630.htm?ref=sotkn.com)
- [Alphabet Form 10-Q — US$519.5B remaining performance obligations; US$513.9B Google Cloud; just over 50% next 24 months (30 Jun 2026)](https://www.sec.gov/Archives/edgar/data/1652044/000165204426000071/goog-20260630.htm?ref=sotkn.com)

S

[**Sean**](https://www.sotkn.com/author/sean/)

Writes Second Order by TKN — who gets paid, where money sticks, and which step is stuck in the AI stack.

[Author page →](https://www.sotkn.com/author/sean/) · [Editorial standards →](https://www.sotkn.com/editorial-standards/)