What is a Revenue Backlog?

What is Revenue Backlog?

Revenue backlog is the total value of contracts a company has signed but not yet billed or recognised as revenue. It represents money the business is committed to receiving, assuming it delivers.

Backlog is a forward-looking metric. It doesn’t show what’s in the bank; it shows what’s coming, and how much runway exists before the company needs new deals to maintain growth.

Revenue Backlog vs. Deferred Revenue vs. ARR

Three metrics that measure adjacent things:

A $300,000 three-year contract signed today adds $300,000 to backlog immediately. As the company bills and delivers, backlog converts to deferred revenue (when billed in advance) or directly to recognised revenue (when billed in arrears). ARR reflects the annualised value of that contract once it’s active - $100,000 in the example here.

How do you calculate revenue backlog?

Backlog = total contracted value minus everything already billed.

A worked example. A customer signs a 3-year, $360,000 contract on January 1, billed quarterly in advance at $30,000:

Two things the table shows. Backlog moves on signature and on billing, never on cash. And amendments reprice backlog on the day they're signed, which is why backlog accuracy is really contract-data accuracy. The related metric total contract value is the starting number backlog burns down from.

Backlog and RPO: the ASC 606 connection

Public companies report a close cousin of backlog: remaining performance obligations, or RPO. ASC 606 and IFRS 15 require disclosure of the transaction price allocated to unsatisfied performance obligations, which is roughly backlog plus deferred revenue: everything contracted but not yet recognized, whether billed or not.

RPO is why backlog stopped being an internal-only metric. Analysts read RPO growth as the forward indicator of revenue, and auditors test the contract data behind it. A backlog number assembled from CRM exports doesn't survive that test; one computed from the same ledger that bills the contracts does.

Why backlog matters

Visibility into future revenue

Backlog tells you how much revenue is locked in before the quarter starts. High backlog heading into a period means the team doesn’t need to close deals just to hit the number, it needs to deliver on what’s already committed. That changes how you resource and plan.

Signal to investors

Investors in project-based and SaaS businesses use backlog as a leading indicator. Growing backlog with stable churn suggests the business is building momentum. Shrinking backlog (even with strong current revenue) says the pipeline isn’t replacing what’s delivering fast enough.

Limitations

Backlog isn’t guaranteed revenue. Contracts get cancelled. Customers delay. Project scope shrinks. Backlog as a metric is only as reliable as the contracts it’s built on.

How Billing Infrastructure Affects Backlog Accuracy

Contract data fragmentation

Backlog is only as accurate as the contract data feeding it. When deals live in CRM, amendments in email, and billing terms in spreadsheets, the backlog number is always stale. Companies with a single source of truth for contract terms, one system that captures the committed value, start date, and delivery schedule, maintain backlog accuracy without manual reconciliation.

Mid-contract changes

Upsells, downgrades, and contract extensions all affect backlog. A customer who upgrades from $50,000 to $80,000 annually adds $30,000 to backlog at the point of signature, not at billing. Billing systems that process amendments without updating the committed contract value silently understate backlog.

Revenue recognition schedules

Backlog converts to revenue on a schedule — and that schedule is set at contract time. If billing infrastructure can’t track delivery milestones against committed values, backlog burns down on the wrong timeline.

What do usage-based contracts do to backlog?

Usage-based revenue complicates the definition. A pure consumption contract with no commitment has no backlog: nothing is contracted until it's used. What creates backlog in usage-based businesses is the committed layer of the contract:

The practical consequence: as pricing shifts from subscriptions to hybrid and usage-based models, reported backlog systematically understates the real forward revenue, and companies increasingly present "committed + expected consumption" views internally. Keep the two rigorously separate. Mixing forecast into backlog is how forward-revenue numbers stop being auditable.

Backlog Reporting in Practice

A healthy backlog report shows movement through all four stages. Backlog that sits in “signed, not yet started” for extended periods signals either implementation delays or contracts that aren’t converting to delivery.

FAQ

Is revenue backlog the same as bookings?

No. Bookings measure what was signed in a period (a flow). Backlog measures what remains unbilled or unrecognized at a point in time (a stock). A big bookings quarter raises backlog; delivery burns it down.

Can backlog shrink while revenue grows?

Yes, and it's the classic warning sign: the company is delivering out of previously signed contracts faster than it's signing new ones. Current revenue looks fine. Next year's doesn't exist yet.

Does backlog appear on the balance sheet?

No. Backlog is an operational metric. Once billed, the unearned portion appears as deferred revenue, which is a balance sheet liability. RPO appears in financial statement disclosures, not on the balance sheet itself.

How often should backlog be recomputed?

Continuously, in practice: on every signature, amendment, and invoice. If backlog is a monthly spreadsheet exercise, every mid-month amendment makes the number stale by definition.

Related

• Deferred revenue: what billed backlog becomes

• Revenue recognition: the hub concept

• ASC 606: the standard behind RPO disclosure

• Total contract value: the number backlog burns down from