Revenue backlog
DEFINITION
Revenue backlog is the total value of contracted revenue not yet recognized, including both billed-but-unearned amounts and unbilled amounts still owed under signed contracts. It gives finance and leadership visibility into future revenue beyond what deferred revenue alone shows.
TABLE OF CONTENTS
RELATED TERMS
Revenue backlog is the total value of contracted revenue that has not yet been recognized, covering both the amount already billed but not yet earned and the amount that is contractually committed but not yet billed. It represents the full pipeline of future revenue a company has already secured through signed contracts, regardless of whether an invoice has gone out yet.
Revenue backlog is broader than deferred revenue because it includes unbilled amounts under a contract, such as the remaining years of a multi-year agreement that has not yet reached its next invoicing milestone. A subscription platform such as Recurly tracks subscription terms, billing schedules, and contract lengths, which gives finance and RevRec teams the underlying data to build an accurate backlog view rather than relying on a manual roll-up of contracts and invoices.
Why revenue backlog matters for subscription businesses
Revenue backlog gives finance and leadership teams visibility into contracted future revenue that goes beyond what appears on the balance sheet as deferred revenue. Because deferred revenue only reflects amounts that have already been billed, it understates the true value of a company's contracted commitments whenever multi-year or multi-period deals exist that have not yet reached their next billing point. Revenue backlog fills that gap by capturing the full remaining contract value, billed and unbilled alike.
This visibility matters directly for forecasting and investor communication. A company with a large, growing revenue backlog has strong forward revenue visibility even if in-period bookings slow temporarily, since much of next year's revenue is already contractually locked in. Public and late-stage private companies in particular often disclose backlog or remaining performance obligation figures because they give investors a clearer picture of committed future revenue than current period revenue alone.
How revenue backlog works
Revenue backlog is built from the full set of active contracts a company holds, tracked against how much of each contract's value has already been billed and recognized.
A customer signs a contract with a defined term and total contract value, such as a three-year agreement.
As each billing period arrives, the company invoices the customer for that period's portion of the contract, and that billed amount becomes deferred revenue until it is earned.
The portion of the total contract value that has not yet been billed, because its billing period has not yet arrived, remains part of the backlog but is not reflected in deferred revenue.
As time passes and future billing periods are invoiced, that unbilled backlog converts into billed deferred revenue, which is then recognized as revenue as the service is delivered.
This is why revenue backlog is often described as having two components: a billed but unearned portion (which overlaps with deferred revenue) and an unbilled portion (which does not appear on the balance sheet at all until it is invoiced).
How to use revenue backlog
Finance, RevRec, and leadership teams use revenue backlog in a few concrete ways.
Report backlog alongside bookings and recognized revenue to give a fuller picture of contracted future revenue, especially for multi-year contracts.
Track how backlog converts into billed and recognized revenue over time, to validate that revenue forecasts are grounded in actual contractual commitments.
Use backlog trends as an input to headcount and investment planning, since a growing backlog signals future revenue that can support additional spend ahead of when it is recognized.
Disclose backlog or remaining performance obligation figures in investor and board reporting where relevant, since these figures show contracted revenue that has not yet reached the income statement.
Revenue backlog vs deferred revenue
Revenue backlog and deferred revenue are related but not the same, and the difference comes down to what has been billed.
Deferred revenue is strictly the billed, unearned portion of a contract, the cash or receivable already invoiced for service not yet delivered. Revenue backlog is broader: it includes deferred revenue plus any remaining contract value that has not yet been billed at all, such as future years of a multi-year deal. Every dollar of deferred revenue is part of revenue backlog, but not every dollar of revenue backlog is deferred revenue, since the unbilled portion of a contract never touches the balance sheet as a liability until it is actually invoiced.
Benefits and examples
Tracking revenue backlog closely delivers real planning and reporting value:
Forward revenue visibility, since backlog shows contracted revenue that has not yet reached the income statement, giving a clearer view of what is already locked in.
Better multi-year deal tracking, since backlog captures the full value of long-term contracts instead of only the portion that happens to have been billed so far.
Stronger investor and board narratives, since backlog figures demonstrate committed future revenue beyond a single period's bookings or recognized revenue.
More informed resourcing decisions, since a growing backlog supports the case for investment ahead of when that revenue actually shows up as recognized.
As an illustrative example, imagine a customer signs a three-year contract worth $300,000 total, billed annually in $100,000 installments at the start of each contract year. At the moment the contract is signed and the first year is invoiced, deferred revenue is $100,000 (the billed, unearned first-year amount), but revenue backlog is the full $300,000, since two more years of contracted value remain even though they have not yet been billed. As the second year is invoiced a year later, that $100,000 moves from unbilled backlog into billed deferred revenue.
Frequently asked questions
Is revenue backlog the same as remaining performance obligations (RPO)? They are closely related concepts and often used to describe similar things: the total value of a company's contracted commitments not yet recognized as revenue. Some companies use the terms interchangeably, though "remaining performance obligations" is the specific term used under ASC 606 disclosure requirements.
Does revenue backlog appear on the balance sheet? Not entirely. The billed portion of backlog appears as deferred revenue on the balance sheet, but the unbilled portion of backlog is off-balance-sheet information typically disclosed separately, if at all.
Why would a company report revenue backlog if it is not required on the balance sheet? Because it gives investors, boards, and internal leadership a fuller view of contracted future revenue than the balance sheet alone shows, which is especially useful for companies with multi-year contracts.
Can revenue backlog decline even if new sales are still happening? Yes, if the rate at which existing backlog is billed and recognized outpaces the rate of new bookings, total backlog can shrink even during a period of continued new sales activity.
