Deferred Revenue vs RPO: Which One Shows Your Real Backlog

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 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 $200,000 per year with annual billing. At signing you invoice $200,000, so $200,000 enters deferred revenue and releases across the next twelve months. The remaining $400,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.

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.

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.

What is RPO?

RPO, remaining performance obligation, is the total transaction price allocated to obligations you have not yet satisfied. It is defined under ASC 606 and disclosed by public companies in their filings.

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. It excludes anything the customer can cancel without penalty, which is why month-to-month subscriptions typically contribute little to it.

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.

Why is RPO always larger?

Because every dollar of deferred revenue is inside RPO, and RPO adds the unbilled portion of multi-year contracts on top. Work through a single customer. Deferred revenue starts at $200,000 and falls to zero over the first year. RPO starts at $600,000 and steps down as each year is delivered. Both are correct. Only RPO tells you the customer is committed for three years.

The size of the gap is itself informative. A company with RPO roughly equal to deferred revenue sells one year deals invoiced upfront. A company with RPO at three times deferred revenue sells long contracts billed annually. Neither is better, but they are different businesses with different cash profiles and different renewal risk concentration.

What is cRPO and why does it matter more?

cRPO is the portion of RPO expected to be recognized within the next twelve months, and it is a far better forward indicator than total RPO. 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.

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.

Which one should you track?

Track all three, because each answers a question the others cannot. The table maps them. None of these replaces the others. A company can have strong RPO and weak billings if it signed long deals with back-loaded invoicing. A company can have a healthy deferred balance and falling cRPO if its contracted backlog is running out. Reading them together is what makes each one useful.

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.

Separating them this way 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.

The pipeline layer needs its own discipline. 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.