Contents
Deferred revenue is contract value you have invoiced but not yet earned, and it sits on the balance sheet as a liability. RPO, remaining performance obligation, is all contracted value you have not yet earned, invoiced or not. It equals deferred revenue plus unbilled backlog, so it is usually the larger number. cRPO is the slice due within 12 months. Updated November 2026: added a cRPO answer, a billing terms example, ASC 606 sources and new FAQs.
Not accounting advice. This page explains how deferred revenue and RPO work, in plain language and with illustrative numbers. What goes into your RPO disclosure is a judgment your auditor will review, so confirm your policy with your controller and your audit firm.What is the difference between deferred revenue and RPO?
Deferred revenue is contracted value you have already invoiced but not yet earned. RPO is all contracted value you have not yet earned, invoiced or not. RPO is usually the bigger number, and the difference between them is your unbilled backlog.The distinction turns on a single question: has the invoice gone out? A customer signs a three year deal at $240,000 per year with annual billing. At signing you invoice $240,000, so $240,000 enters deferred revenue and releases across the next twelve months. The remaining $480,000 is contracted, will be performed, and has not been invoiced. It sits in RPO and nowhere on the balance sheet.
Companies that only track the deferred balance are looking at one third of their backlog in that example and calling it the whole thing.
| Deferred revenue | RPO | cRPO | |
|---|---|---|---|
| What it counts | Invoiced or paid, not yet earned | All contracted, non-cancelable value not yet earned | The part of RPO expected to be earned in the next 12 months |
| Where it lives | Balance sheet liability (often labeled unearned revenue) | Revenue note in the 10-K and 10-Q | Revenue note or earnings release, if the company reports it |
| Rule behind it | GAAP balance sheet; ASC 606 calls it a contract liability | ASC 606 disclosure | Company practice within the ASC 606 timing disclosure |
| What moves it | Billing terms as much as sales | Contract length, new contracts, revenue recognized | Renewals, new bookings, contracts rolling inside the 12 month window |
What is deferred revenue?
Deferred revenue is a balance sheet liability representing cash you have collected or invoiced for services you still owe. It is a GAAP account, audited, and it appears on every SaaS balance sheet. ASC 606 calls the same balance a contract liability, and public companies must disclose its opening and closing balances and the revenue recognized from it during the period (PwC Viewpoint, 33.4).It builds when you invoice ahead of delivery and drains as you deliver. In a growing subscription business with annual prepay, the balance grows steadily, because each quarter you invoice more new contract value than you release from old ones. That growth is a genuine positive signal and is the reason billings can be derived from revenue plus the change in deferred revenue.
The metric has one blind spot worth naming. Deferred revenue reflects your invoicing policy as much as your business. Shift a customer cohort from annual prepay to quarterly billing and the deferred balance falls sharply while the contracts, the revenue, and the customer relationships are unchanged. Any read on the deferred balance needs a note on billing terms.
Deferred revenue also has an opposite. When you deliver before you invoice, the balance is unbilled revenue, an asset, not a liability. Our guide to unbilled revenue vs deferred revenue covers that side, and how to forecast deferred revenue covers the roll-forward that projects the balance.
What is RPO?
RPO, remaining performance obligation, is the total transaction price allocated to obligations you have not yet satisfied. ASC 606-10-50-13 requires a company to disclose that aggregate amount and explain when it expects to recognize it as revenue, either in time bands or in words (PwC Viewpoint, 33.4). Public companies include it in quarterly reports too. Our remaining performance obligation glossary entry covers what counts, the cRPO split and where to find it in a 10-K.RPO is the closest thing SaaS has to a contracted order backlog. It includes the deferred revenue balance plus every dollar of committed contract value that has not been invoiced. Salesforce's 10-K states it directly: RPO "represents all future revenue under contract that has not yet been recognized as revenue and includes unearned revenue and unbilled amounts" (Salesforce FY2025 10-K). It excludes anything the customer can cancel without penalty. PwC's example is a two year software contract the customer can end on one month's notice: in substance it is a one month contract, so only one month goes into RPO. Usage above a committed minimum and renewals not yet signed stay out too, because the customer has not committed to them.
Two elections can make disclosed RPO smaller than you would expect. A company may leave out contracts with an original duration of one year or less, and it may leave out some variable consideration, such as usage fees it recognizes as it gains the right to invoice (PwC). Where the one year election applies, the deferred revenue on those short contracts is on the balance sheet but not in the RPO note. Read the note before you compare RPO with deferred revenue or with another company.
RPO grows when you sign long contracts and shrinks as you deliver against them. A company that shifts from one year to three year terms will see RPO jump without any change in ARR, which is a useful reminder that RPO measures contract duration as much as business size. Some companies call the unbilled part backlog, but backlog has no GAAP definition, so check what each company includes.
What is cRPO in finance, and why does it matter more?
cRPO, current remaining performance obligation, is the portion of RPO expected to be recognized as revenue within the next twelve months. ASC 606 lets companies choose their own time bands, and many SaaS companies that report a split, Salesforce among them, use 12 months. The rest is noncurrent RPO. cRPO is a far better forward indicator than total RPO, because total RPO can be moved dramatically by a small number of long deals.One seven year enterprise agreement can add more to total RPO than a full quarter of standard bookings. Total RPO jumps, the market reads it as momentum, and next year's revenue is barely affected. cRPO does not have that problem, because it only counts what converts to revenue inside a twelve month window.
The formulas for a subscription recognized evenly over its term:
| Measure | Formula |
|---|---|
| RPO | Deferred revenue + contracted amounts not yet invoiced |
| Unbilled RPO | RPO minus deferred revenue |
| cRPO per contract | Monthly fee x the smaller of remaining months and 12 |
| Noncurrent RPO | RPO minus cRPO |
| RPO growth | (RPO now minus RPO a year ago) / RPO a year ago |
For a private company, deriving cRPO from the contract file is a straightforward exercise and it produces a contracted revenue floor for the coming year. Anything above that floor has to come from new bookings, renewals of expiring contracts, and usage above minimums. That is a much more useful starting point for an annual plan than a growth rate applied to last year's revenue.
Why is RPO usually larger than deferred revenue?
Because every dollar of deferred revenue on in-scope contracts is inside RPO, and RPO adds the unbilled portion of multi-year contracts on top. Billing terms decide how big the gap is. RPO does not care how you invoice, only what the customer signed. Illustrative example. One customer signs a three year, non-cancelable subscription worth $720,000 ($240,000 a year, recognized evenly at $20,000 a month). Here is the position on the day the contract starts, after the first invoice and before any revenue is recognized, under five different billing terms.| Billing terms | Invoiced at signing | Deferred revenue | Contracted, not invoiced | RPO | cRPO | ARR |
|---|---|---|---|---|---|---|
| All three years upfront | $720,000 | $720,000 | $0 | $720,000 | $240,000 | $240,000 |
| Annual in advance | $240,000 | $240,000 | $480,000 | $720,000 | $240,000 | $240,000 |
| Quarterly in advance | $60,000 | $60,000 | $660,000 | $720,000 | $240,000 | $240,000 |
| Monthly in advance | $20,000 | $20,000 | $700,000 | $720,000 | $240,000 | $240,000 |
| Monthly, cancelable on one month's notice with no penalty | $20,000 | $20,000 | $0 | $20,000 | $20,000 | $240,000 |
Each line ties out. Deferred revenue plus the amount not yet invoiced equals RPO in every row. cRPO is $20,000 times 12 months, or $240,000, wherever more than 12 months remain, and $20,000 times 1 month where only one month is committed.
The size of the gap is itself informative. A company with RPO roughly equal to deferred revenue sells deals invoiced upfront. A company with RPO at three times deferred revenue at signing likely sells three year contracts billed annually, like the second row. Neither is better, but they are different businesses with different cash profiles and different renewal risk concentration.
Which one should you track?
Track all three, because each answers a question the others cannot. The table maps them.| Question | Metric | Why |
|---|---|---|
| How much have we invoiced but not earned? | Deferred revenue | Balance sheet liability, drives cash timing |
| How much contracted revenue is left in total? | RPO | Full committed backlog including unbilled |
| How much contracted revenue lands next year? | cRPO | Twelve month conversion window |
| How big is the recurring base right now? | ARR | Point-in-time annualized snapshot |
| How much did we invoice this quarter? | Billings | Revenue plus change in deferred revenue |
Where does backlog fit in a revenue forecast?
Contracted backlog is the floor. Everything above it is the forecast. Starting from cRPO rather than from a growth assumption changes what the model is actually estimating.The structure is straightforward. cRPO gives you contracted revenue for the next twelve months, which is close to known. Renewals of contracts expiring in the window are probabilistic and forecast from retention behavior. New bookings from pipeline are the volatile layer, and they carry the widest error bars.
Renewals and new business need different methods. Pete Furseth, ORM's COO, puts it plainly: teams that forecast them the same way are making a mistake. With a renewal you generally know the amount, either the current price or the current price plus a lift, and you know when it should close. ORM models renewal timing as a window of about 30 days either side of the renewal date. New business timing depends on when the deal last changed stage.
Expiring contracts also explain a pattern that worries people for no reason. On a multi-year contract, RPO and then cRPO fall toward zero as the renewal date approaches, because the renewal is not in RPO until the customer signs. A falling cRPO on one account is not a churn signal by itself. ORM starts predicting a renewal as soon as the renewal opportunity is created, typically 12 months out, and sees risk come into focus about six months before the renewal date. Customers on auto-renew are more likely to renew than those who are not.
Separating the layers improves forecast accuracy for a mechanical reason. Blending contracted revenue with pipeline-dependent revenue into one number produces a figure that looks confident and cannot be diagnosed when it misses. Split the layers and a miss points at a specific cause. It also makes the forecast easier to defend. Pete's test for a forecast a board trusts is that it is consistent, traceable and shown as a range: a low case, an on-target case and an upper bound. With cRPO as the floor, the low case starts from revenue already under contract, and the range widens only as you add renewals and pipeline.
The pipeline layer needs its own discipline. Pete's view is that most teams over-trust visible pipeline and under-model the business that will be created and closed inside the period, which is why pipeline coverage should be treated as an input rather than a conclusion. Our guide on how to forecast revenue covers building the model from a contracted floor upward.
Frequently Asked Questions
What is the difference between deferred revenue and RPO?
Deferred revenue is contract value you have already invoiced but not yet earned, and it sits on the balance sheet as a liability. RPO, remaining performance obligation, is the total contracted value you have not yet recognized, whether or not you have invoiced it. RPO includes deferred revenue plus unbilled backlog, so it is usually the larger number. They are equal when nothing committed is left to invoice, as with a contract billed fully upfront.
What is cRPO in finance?
cRPO, current remaining performance obligation, is the part of RPO a company expects to recognize as revenue in the next 12 months. ASC 606 requires public companies to say when they expect to recognize RPO, and many SaaS companies answer with a 12 month split. Investors watch cRPO because it is close to a contracted revenue floor for the coming year, and long multi-year deals cannot inflate it.
Why is RPO larger than deferred revenue?
Because RPO captures contracted value you have not invoiced yet. A three year contract billed annually puts one year into deferred revenue at signing and leaves two years unbilled. Both remaining years are contractual obligations you will perform, so both sit in RPO. The longer your average contract term and the more often you bill in small installments, the wider the gap.
What is RPO growth?
RPO growth is the percentage change in remaining performance obligation over a period, usually year over year: RPO this quarter minus RPO a year earlier, divided by RPO a year earlier. It shows whether contracted backlog is building faster than you deliver it. Read it next to cRPO growth, because longer contract terms or one large multi-year deal can lift total RPO without changing next year's revenue.
Is unearned revenue the same as deferred revenue?
They are two names for the same balance: amounts a customer has paid or been invoiced for goods or services you have not delivered yet. Many SaaS companies label it unearned revenue on the balance sheet, and ASC 606 calls it a contract liability. Whatever the label, it is part of RPO, and it releases into revenue as you deliver the service.
Do private SaaS companies need to report RPO?
Public companies must disclose RPO under ASC 606, in annual and interim reports. For nonpublic companies the RPO disclosures are optional, as PwC's private company guide notes, and many do not calculate it. That is a missed opportunity, because RPO comes straight from the contract file and gives a clean read on contracted future revenue that neither the deferred balance nor ARR provides on its own.
See how ORM turns these insights into action
ORM builds custom revenue forecast models for B2B SaaS companies. Not dashboards. Prescriptive analytics that tell you what to do next.
Schedule a Demo



