Definition · SaaS metrics
Remaining Performance Obligations
Remaining performance obligations is the total contracted revenue not yet recognized, disclosed under ASC 606, split into current and long-term, and how it differs from deferred revenue and bookings. For remaining performance obligations, the useful boundary is whether the movement comes from customers, contracts, billing, cash timing, or recognition rules.
Also known as RPO, cRPO, current remaining performance obligations, contracted revenue backlog
Why it matters
Understanding remaining performance obligations matters because revenue and customer metrics can change materially when teams mix contract, billing, cash, recognition, churn, or expansion logic. The definition protects the story from drifting. Pluvo computes remaining performance obligations from contract terms, separating current from long-term backlog.
In practice
Revenue example
Teams use remaining performance obligations when they need to separate customer, contract, billing, recognition, and cash effects. That prevents a revenue movement from being misread as growth, churn, expansion, or timing noise.
Pluvo example
Pluvo computes remaining performance obligations from contract terms, separating current from long-term backlog.
In practice, teams should define remaining performance obligations with a clear source, owner, time period, and decision before they use it in reporting, planning, or operating reviews.
Understanding remaining performance obligations matters because revenue and customer metrics can change materially when teams mix contract, billing, cash, recognition, churn, or expansion logic. The definition protects the story from drifting. Pluvo computes remaining performance obligations from contract terms, separating current from long-term backlog.
A strong workflow for remaining performance obligations separates the definition from the action: first agree what the term means, then decide how it is measured, when it changes, and who is accountable for the next step.
Pluvo computes remaining performance obligations from contract terms, separating current from long-term backlog.
FAQ
What is RPO in SaaS?
Remaining performance obligations is the total contracted revenue not yet recognized, disclosed under ASC 606, split into current and long-term, and how it differs from deferred revenue and bookings. For remaining performance obligations, the useful boundary is whether the movement comes from customers, contracts, billing, cash timing, or recognition rules.
What is the difference between RPO and deferred revenue?
The boundary for remaining performance obligations differs from related terms by scope, source data, time period, and decision use. In this glossary, it covers the total contracted revenue not yet recognized, disclosed under ASC 606, split into current and long-term, and how it differs from deferred revenue and bookings, so teams should compare those boundaries before using it in reporting or planning.
What is cRPO?
Remaining performance obligations is the total contracted revenue not yet recognized, disclosed under ASC 606, split into current and long-term, and how it differs from deferred revenue and bookings. For remaining performance obligations, the useful boundary is whether the movement comes from customers, contracts, billing, cash timing, or recognition rules. For remaining performance obligations, the practical boundary is the total contracted revenue not yet recognized, disclosed under ASC 606, split into current and long-term, and how it differs from deferred revenue and bookings.