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.
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.
| Year | Prospectuses (n) | Mention it | Estimated to report it | Most common wording |
|---|---|---|---|---|
| 2004 | 9small sample | 0 (0%) | 0% | |
| 2005 | 8small sample | 0 (0%) | 0% | |
| 2006 | 9small sample | 0 (0%) | 0% | |
| 2007 | 17 | 0 (0%) | 0% | |
| 2008 | 2small sample | 0 (0%) | 0% | |
| 2009 | 6small sample | 0 (0%) | 0% | |
| 2010 | 8small sample | 0 (0%) | 0% | |
| 2011 | 14small sample | 0 (0%) | 0% | |
| 2012 | 23 | 0 (0%) | 0% | |
| 2013 | 21 | 0 (0%) | 0% | |
| 2014 | 27 | 0 (0%) | 0% | |
| 2015 | 16 | 0 (0%) | 0% | |
| 2016 | 10small sample | 0 (0%) | 0% | |
| 2017 | 17 | 1 (6%) | 4% | remaining performance obligations |
| 2018 | 20 | 7 (35%) | 26% | remaining performance obligations |
| 2019 | 18 | 11 (61%) | 46% | remaining performance obligations |
| 2020 | 24 | 16 (67%) | 57% | remaining performance obligations |
| 2021 | 69 | 44 (64%) | 54% | remaining performance obligations |
| 2022 | 3small sample | 0 (0%) | 0% | |
| 2023 | 4small sample | 1 (25%) | 21% | remaining performance obligations |
| 2024 | 9small sample | 8 (89%) | 62% | remaining performance obligations |
| 2025 | 12small sample | 9 (75%) | 53% | remaining performance obligations |
| 2026 | 16 | 6 (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).
- Mar 16, 2018Zscaler, Inc.. Transaction price allocated to remaining performance obligations was $273.1 million as of January 31, 2018.
- Apr 20, 2018Pivotal Software, Inc.. From the precision review: reports its own RPO.
- Apr 27, 2018DocuSign, Inc.. Transaction price allocated to remaining performance obligations was $409.5 million.
- Jun 29, 2018Domo, Inc.. From the precision review: reports its own RPO.
- 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
- FASB, ASU 2015-14, read Nov 17, 2026
- FASB, ASU 2014-09, Section A, read Nov 17, 2026
- Zscaler, Inc. prospectus (424B4), March 16, 2018, read Nov 17, 2026
- 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/