Remaining Performance Obligations (RPO): Formula and Examples

Remaining Performance Obligations (RPO): Formula and Examples

Introduction

Justin (Do San Myung) is Expert Accountant at DualEntry with 20+ years of hands-on experience managing general ledgers, financial close processes, and ERP implementations for mid-market and enterprise companies. As a former Consulting CFO and Controller, he has personally overseen month-end closes, SOX compliance programs, and multi-entity consolidations across technology, manufacturing, and services industries. Justin specializes in transforming manual accounting workflows into automated, AI-driven processes.

What is a remaining performance obligation (RPO)?

A remaining performance obligation is the part of a customer contract a company has committed to deliver but hasn't recognized as revenue yet.
Add all of those up across every signed contract, and the total is the company's RPO: the future revenue it's contractually on the hook to earn. How that revenue is released over time is covered in our guide to SaaS revenue recognition.

RPO came out of ASC 606, the revenue recognition standard, which made it a required disclosure for public companies (ASC 606-10-50-13). In RPO accounting, the underlying question is how much of the transaction price is still allocated to performance obligations the company hasn't satisfied.

How to calculate RPO

For a typical fixed-contract SaaS business, a useful shorthand is:
Under ASC 606, the formal definition is the transaction price allocated to performance obligations that are still unsatisfied or partially unsatisfied.

In practice, those amounts sit at different stages. Deferred revenue (a contract liability, in ASC 606's terms) is money you've already invoiced but haven't earned yet because the service hasn't been delivered.
The rest is contracted revenue that hasn't been invoiced yet, often referred to as backlog. Add the two together and you get the value of signed business still waiting to be recognized.

A worked example

Take a SaaS company that signs a three-year contract with a total contract value (TCV) of $420,000 and an annual contract value (ACV) of $140,000, billed annually upfront. The service is delivered evenly across each year.

Component At signing After 6 months
Deferred revenue (year 1, invoiced) $140,000 $70,000
Backlog (years 2–3, not yet invoiced) $280,000 $280,000
RPO $420,000 $350,000

Splitting current and non-current RPO

Companies also disclose when they expect to recognize their RPO as revenue. For SaaS businesses, the portion expected within the next twelve months is often referred to as current RPO, or cRPO.
Current RPO (cRPO) is the part expected to be recognized in the next twelve months. Non-current RPO is everything beyond that.

RPO vs. backlog vs. ARR vs. deferred revenue

RPO gets mixed up with the other forward-looking numbers a SaaS company tracks, and the differences matter, because they don't measure the same thing. ARR in particular is often confused with MRR.

Metric What it measures GAAP-defined? Contractual or estimated Where it shows up
RPO Signed contract revenue not yet recognized Yes Contractual Public filings
Backlog Unbilled contracted revenue not yet recognized No Contractual Often included in RPO
ARR Annualized run rate of recurring revenue No Company-defined run rate Board decks, investor updates, some filings as a KPI
Deferred revenue Invoiced revenue not yet earned (contract liability) Yes Contractual Balance sheet

How finance teams actually produce RPO each quarter

RPO doesn't sit in one place waiting to be copied out. Finance teams assemble it every quarter from three sources: the contract data, the billing schedules, and the revenue schedules.
Billings show how much has been invoiced during the period, while the revenue schedules show how much of that contracted amount has actually been recognized as revenue.

How to read a public company's RPO disclosure

Most SaaS investors first meet RPO in a 10-K or 10-Q, tucked into the revenue note, or in the earnings release that comes out ahead of it.

Remaining Performance Obligations (RPO) FAQs

How do you calculate remaining performance obligations?

RPO is the sum of deferred revenue (contracted revenue you’ve invoiced but not yet earned) and backlog (contracted revenue you haven’t invoiced yet), which together capture every dollar of signed business a company still has to recognize.

What does performance obligation mean?

A performance obligation is a promise in a contract to transfer a distinct good or service to a customer, and it’s the unit ASC 606 uses to decide when revenue gets recognized, as each obligation is satisfied.

Is remaining performance obligation the same as backlog?

No. Backlog is a company-defined measure of contracted business that hasn’t yet been recognized or billed, while RPO is an ASC 606 disclosure based on the transaction price allocated to unsatisfied or partially unsatisfied performance obligations.

What is RPO in finance?

In finance, RPO is the value of contracted revenue allocated to performance obligations a company hasn’t yet satisfied. It gives finance teams and investors a view of revenue already under contract but not yet recognized.

Is RPO the same as bookings?

No, bookings count the total value of deals signed in a period, while RPO measures contracted revenue not yet recognized across all active contracts.

Why does RPO differ from deferred revenue?

Deferred revenue only counts contracted amounts you’ve already invoiced, while RPO also includes backlog, the future contract years you haven’t billed yet, so RPO captures the full remaining value of multi-year deals.