Key Takeaways

• Snowflake defines RPO as deferred revenue plus non-cancelable contracted amounts to be invoiced, and it reported $9,771.5 million at January 31, 2026: $3,361.4 million of balance-sheet deferred revenue and $6,410.1 million for the rest.

• ASC 606-10-50-13 requires the amount and an explanation of when it converts to revenue, either in time bands or through qualitative information.

• ASC 606 never names a 12-month figure, so any current RPO number is a company's own cut: Salesforce defines its as future revenue under contract expected in the next 12 months, and Snowflake's 46% puts its figure near $4.5 billion.

• RPO counts only the noncancellable term, so a $240,000 two-year SaaS contract with a one-month, no-penalty exit right contributes $10,000.

• Contracts of one year or less, right-to-invoice usage, and consumption above a committed minimum can all fall outside RPO, and Snowflake notes that RPO doesn't account for consumption above contracted capacity.

What does ASC 606 require companies to disclose?

ASC 606-10-50-13 requires two disclosures: the aggregate transaction price allocated to unsatisfied or partially unsatisfied performance obligations at period end, and when the company expects to recognize it as revenue. The rule applies to public business entities, while certain other entities may elect out under 606-10-50-16 (Deloitte).

Here's how each part of the disclosure works:

• Amount: the figure covers only the period with enforceable rights and obligations, the noncancellable term (PwC).

• Timing: a company can use quantitative time bands or a qualitative explanation.

• 12-month cut: the standard doesn't name a 12-month figure, so a company that reports one sets the cut itself.

• Worked case: a two-year noncancelable magazine subscription sold for $24 has delivered 9 months and recognized $9, so $24 x 15/24 leaves $15 of RPO.

How does RPO reconcile to deferred revenue and unbilled revenue?

Snowflake and Salesforce both split RPO into the part already invoiced and the part still waiting on an invoice. The first corresponds to deferred revenue, which Salesforce calls unearned revenue. The second is contracted work not yet invoiced, which differs from unbilled revenue, earned work not yet invoiced.

Snowflake's fiscal 2026 10-K shows the split. Its note defines RPO as deferred revenue plus non-cancelable contracted amounts to be invoiced later, so subtracting the balance sheet deferred revenue isolates the unbilled piece (Snowflake 10-K). Salesforce's fiscal 2026 10-K says its RPO includes unearned revenue and unbilled amounts (Salesforce 10-K).

The 46% is rounded, so the cRPO figure is approximate. The same identity works at contract level: a three-year, $36,000 contract billed $12,000 a year in advance has $30,000 of RPO six months in, $6,000 deferred plus $24,000 unbilled. It also shows why contracted ARR differs, since that metric annualizes recurring revenue instead of totaling the full remaining term.

What does RPO leave out?

RPO counts only what the customer has committed to, and ASC 606 lets companies omit some short and usage-based contracts, so RPO can sit below the revenue a company expects. That gap is where usage-based revenue recognition and RPO disagree most.

These items drop out:

• Contracts of one year or less: 606-10-50-14(a) lets a company skip the disclosure.

• Right-to-invoice revenue: usage recognized in the amount invoiced under 606-10-55-18 can be excluded.

• Consumption above a minimum: in PwC's example, a 1,000,000-unit commitment counts and every unit above it doesn't, even when orders are expected.

• Termination for convenience: one month's notice without penalty turns a $240,000, 24-month SaaS contract into $10,000 of RPO ($240,000 / 24).

• On-demand arrangements: Snowflake excludes them because they carry no minimum purchase commitment.

Fixed consideration can't use the right-to-invoice or variable-consideration exemptions (606-10-50-14B). A company that applies an exemption must say which, and describe the variable consideration it excluded. Deloitte notes that many people call this disclosure the backlog disclosure, and revenue backlog covers where company-defined backlog figures diverge from it.

Related terms

Finance teams reconcile RPO against neighboring measures, and each of these defines one:

• Deferred revenue waterfall schedules when the billed portion converts to revenue.

• Unbilled revenue covers earned work that hasn't reached an invoice yet.

• Contracted ARR annualizes signed recurring contracts, where RPO totals what's left.

• Bookings vs billings vs revenue covers the three figures that surround RPO.

• Annual contract value averages a contract's yearly worth, which RPO doesn't.

• Revenue backlog covers company-defined backlog figures and where they diverge from RPO.

FAQ

Is current RPO a GAAP measure?

No. ASC 606 asks for the amount and its timing, in time bands or through qualitative information, and doesn't name a 12-month figure. A company that reports a current figure sets its own cut, and Snowflake estimates its 46% from historical customer consumption patterns.

Do private companies have to disclose RPO?

No, not if they elect out. Under 606-10-50-16, an entity that isn't a public business entity may elect not to provide the disclosure. Deloitte describes the election as available to certain nonpublic entities.

Where does a 10-K report RPO?

It appears in the notes to the financial statements, where ASC 606-10-50-13 requires it. Snowflake also repeats it in its key business metrics. The 46% recognition estimate appears in both places.

How is RPO different from contracted ARR?

RPO totals the contracted dollars not yet recognized across the remaining term, while contracted ARR annualizes signed recurring revenue. A three-year contract with 30 months left contributes 30 months of fees to RPO but one year to contracted ARR. At $12,000 a year, that's $30,000 of RPO against $12,000 of contracted ARR.