Skip to content

SaaS and cloud era

Remaining performance obligations (RPO)

Remaining performance obligations are the contracted revenue a company has not yet recognized, whether billed or unbilled.

RPO = transaction price allocated to unsatisfied performance obligations at period end

“the aggregate amount of the transaction price allocated to remaining performance obligations was $409.5 million, which consists of both billed and unbilled consideration that we expect to recognize as subscription revenue.”

Era badge: SaaS and cloud. Reported share first reached 25% in 2018.

Verified

Why it emerged

RPO is the one metric on this list that a rule created. The revenue standard ASC 606 requires companies to disclose the transaction price allocated to performance obligations not yet satisfied, and when they expect to recognize it.

The counts follow the effective date. No US software prospectus in this set used the term through 2016. In 2018, the first full year of the standard for public companies, a third of them did.

The rule behind it

Required by ASC 606, paragraph 606-10-50-13, from ASU 2014-09 (May 2014). ASU 2015-14 (August 2015) deferred the start: public business entities apply it to annual reporting periods beginning after December 15, 2017.

“Public business entities, certain not-for-profit entities, and certain employee benefit plans should apply the guidance in Update 2014-09 to annual reporting periods beginning after December 15, 2017, including interim reporting periods within that reporting period.” FASB, ASU 2015-14, Revenue from Contracts with Customers (Topic 606): Deferral of the Effective Date

See also: rules that changed disclosure.

How common it is in IPO prospectuses

US software IPO prospectuses, by filing year. 147 prospectuses across all tech IPOs in the set match at least one wording.

0%25%50%75%100%040608101214161820222426
Light bars: share of prospectuses that mention the metric. Solid bars: estimated share that report it. Hollow bars: years with fewer than 15 prospectuses.
YearProspectuses (n)Mention itEstimated to report itMost common wording
20049small sample0 (0%)0%
20058small sample0 (0%)0%
20069small sample0 (0%)0%
2007170 (0%)0%
20082small sample0 (0%)0%
20096small sample0 (0%)0%
20108small sample0 (0%)0%
201114small sample0 (0%)0%
2012230 (0%)0%
2013210 (0%)0%
2014270 (0%)0%
2015160 (0%)0%
201610small sample0 (0%)0%
2017171 (6%)4%remaining performance obligations
2018207 (35%)26%remaining performance obligations
20191811 (61%)46%remaining performance obligations
20202416 (67%)57%remaining performance obligations
20216944 (64%)54%remaining performance obligations
20223small sample0 (0%)0%
20234small sample1 (25%)21%remaining performance obligations
20249small sample8 (89%)62%remaining performance obligations
202512small sample9 (75%)53%remaining performance obligations
2026166 (38%)26%remaining performance obligations

Wordings searched: remaining performance obligations; current RPO.

Review: 60 matches opened by hand. 100% were the metric itself, and 77%reported it about the company. The estimate multiplies each year's match share by its era's reported rate.

First companies to report it

The earliest US software IPO prospectuses in the set that report it about the company itself, each opened and checked. Earlier filings in the set only mention it. The first match of any kind is Switch, Inc. (Oct 10, 2017).

  1. Mar 16, 2018Zscaler, Inc.. Transaction price allocated to remaining performance obligations was $273.1 million as of January 31, 2018.
  2. Apr 20, 2018Pivotal Software, Inc.. From the precision review: reports its own RPO.
  3. Apr 27, 2018DocuSign, Inc.. Transaction price allocated to remaining performance obligations was $409.5 million.
  4. Jun 29, 2018Domo, Inc.. From the precision review: reports its own RPO.
  5. Jul 26, 2018Tenable Holdings, Inc.. From the precision review: reports its own RPO.

How it gets bent

RPO counts what is contracted, not what is likely. A long contract signed late in a quarter raises RPO in one step, and companies may leave out contracts of one year or less. Zscaler disclosed $273.1 million of RPO in its 2018 prospectus with 56% expected in the next 12 months; the share recognized in the next year matters as much as the total.

Sources: Zscaler, Inc. prospectus (424B4), March 16, 2018; DocuSign, Inc. prospectus (424B4), April 27, 2018

Categories where it matters

Related metrics: ARR

Sources

  1. FASB, ASU 2015-14, read Nov 17, 2026
  2. FASB, ASU 2014-09, Section A, read Nov 17, 2026
  3. Zscaler, Inc. prospectus (424B4), March 16, 2018, read Nov 17, 2026
  4. DocuSign, Inc. prospectus (424B4), April 27, 2018, read Nov 17, 2026

Cite as: Deepak Gupta, “Remaining performance obligations (RPO)”, Rewired Metrics, guptadeepak.com, counted Nov 18, 2026. https://guptadeepak.com/rewired/metrics/remaining-performance-obligations/