Skip to main content

The order backlog that guarantees future revenue

When Boeing reports earnings, investors hunt for one figure above all others: the backlog of unfilled orders. Boeing's order book often exceeds two years of revenue, representing future deliveries customers have already committed to pay for. That backlog is an immensely valuable asset. It tells investors that even if sales completely stop today, Boeing will be earning revenue for years.

The same logic applies to thousands of companies with contractual obligations to deliver goods or services in future periods. When a manufacturing company signs a multi-year supply contract, when a software company signs a three-year SaaS deal, when a contractor wins a project to be completed over 18 months, these represent revenue that the company has already earned the right to record—it's just waiting for the performance obligation to be satisfied (delivery, completion, or passage of time).

This is called Remaining Performance Obligations (RPO) in GAAP terminology, or backlog in industry jargon. It's one of the most underappreciated metrics in financial statements. RPO lives in the MD&A or footnotes, reported in dollars and sometimes as a multiple of recent quarterly revenue. It's not sexy. But it's predictive of future earnings and provides visibility into the business that income statement alone cannot.

Quick definition: Remaining Performance Obligations (RPO) = the total value of contracts signed with customers for which the company has not yet recognized revenue because the performance obligation has not yet been satisfied. Backlog is the operational term for the same thing.

Key takeaways​

  1. RPO is contracted but not yet earned — The company has signed the deal and has a legal right to revenue, but hasn't yet delivered the goods or services, so it hasn't recognized it on the income statement.

  2. RPO is a balance sheet footnote that predicts future income statements — It's the pipeline, the forward visibility of revenue. Companies with large RPO relative to quarterly revenue have high visibility into future earnings.

  3. RPO / quarterly revenue shows how many quarters of visibility the company has — If quarterly revenue is $1 billion and RPO is $4 billion, the company has roughly 4 quarters (one year) of visibility into future revenue.

  4. Growing RPO is a bullish signal; declining RPO is a warning — If RPO is growing faster than revenue, it suggests the company is signing bigger deals and the growth rate is accelerating. If RPO is declining, it's a sign of slowing deal activity.

  5. RPO composition matters: current vs. non-current — Current RPO is revenue expected within 12 months; non-current is beyond. A company with mostly non-current RPO has longer revenue visibility but less near-term cash certainty.

  6. RPO is distinct from deferred revenue — Deferred revenue (liability) is cash already received for future performance; RPO is performance obligations not yet billed or received.

The difference between RPO, backlog, and deferred revenue​

These terms are related but distinct, and conflating them causes real mistakes in analysis.

Remaining Performance Obligations (RPO): The GAAP term for the total value of all signed contracts for which revenue hasn't yet been recognized. RPO includes:

  • Multi-year contracts with scheduled delivery
  • Service contracts that will be performed over time
  • Contracts with installment payments, where revenue is recognized over time but the entire contract value is RPO until earned

Backlog: The operational equivalent of RPO, used especially in manufacturing and engineering (Boeing, Lockheed, Caterpillar). It's the value of orders for which manufacturing hasn't been completed. Backlog and RPO are functionally the same.

Deferred Revenue (or Deferred Income): Cash the company has already received from customers but hasn't earned yet because the performance obligation hasn't been satisfied. It's a liability on the balance sheet. For a SaaS company that collects annual subscription fees upfront, deferred revenue equals 12 months of revenue for all customers. As the company delivers the service month by month, it recognizes revenue and reduces deferred revenue.

The key difference: RPO includes contracts where the company hasn't been paid yet and might not bill until later (e.g., a construction project where final payment comes at completion). Deferred revenue includes only amounts already received.

Both matter, but for different reasons. Deferred revenue predicts cash received now; RPO predicts revenue to be recognized and cash to be received later.

Where to find RPO and why it's important​

RPO is disclosed in the Revenue Recognition footnote of the 10-K or 10-Q, usually buried in the notes along with contract balances and performance obligation disclosures. Some companies are better about calling it out in MD&A; others require you to dig into footnotes.

Look for a line like "Remaining performance obligations as of [date]: $X billion, expected to be recognized as revenue over the next 1–3 years."

The timing of when RPO is expected to be recognized is critical:

  • Current portion (next 12 months): This revenue is highly likely to be recognized within a year. It's as close to certain as accounting gets (barring customer default or cancellation).
  • Non-current portion (beyond 12 months): This is revenue expected 2–5 years out. It's still contractually obligated, but the longer the time horizon, the higher the execution risk.

For a manufacturing company with a two-year backlog, RPO is valuable because customer commitments are binding and cancellation typically triggers significant penalties. For a SaaS company, RPO from a multi-year contract can be terminated by the customer if they go out of business or change their needs. The stability of RPO depends on the industry and customer nature.

Real-world examples​

Boeing and the defense backlog fortress: Boeing's backlog (mostly defense contracts) has consistently been 2–2.5 years of revenue, amounting to $120 billion or more in recent years. This backlog is government contracts that are largely firm and difficult to cancel. It provides massive visibility: even if Boeing won zero new orders, it would still deliver years of revenue. When Boeing's backlog declines, it's treated as a major warning sign. When it grows, it signals strong government spending and long-term demand.

IBM's RPO surprise: IBM, traditionally a services and hardware company, has been increasing its focus on long-term contracts that create large RPO. In recent years, IBM has highlighted RPO growth as evidence of a shift toward recurring revenue contracts, making earnings more predictable. As IBM's RPO has grown from $50 billion to $65 billion, the company has positioned itself as more subscription-like and less exposed to spot demand.

Azure and Microsoft's opaque RPO: Microsoft bundles its cloud, software licensing, and services into complex multi-year enterprise agreements. Microsoft discloses that it has significant unearned revenue and RPO from these contracts, but the company is deliberately vague about the total, disclosing only current-portion (~$45 billion annually). This opacity makes it harder for investors to calculate exact forward revenue visibility, arguably giving the company flexibility in how it reports growth.

Stripe and private-company RPO patterns: While Stripe doesn't file public financial statements, venture capitalists and Stripe investors have noted that the company builds RPO through long-term commitments from enterprise customers, similar to Salesforce. This RPO is reported privately to investors as evidence of the business's resilience and predictability.

The waterfall: understanding RPO changes quarter to quarter​

RPO changes due to three forces:

  1. New contract signings (positive) → New RPO added
  2. Revenue recognition (negative) → Performance obligations satisfied, RPO decreases
  3. Contract modifications (positive or negative) → Existing contracts expanded or reduced

Example: Acme Systems (a software services company) has:

  • Beginning RPO (current portion): $500 million
  • New contracts signed (Q1): $200 million
  • Revenue recognized (Q1): -$150 million
  • Contract upsells / downgrades: -$10 million
  • Ending RPO (current portion): $540 million

The $40 million net growth in current RPO signals that the company is signing contracts faster than it's recognizing revenue, a bullish indicator of acceleration. If this pattern continues, revenue will accelerate next quarter.

Common mistakes​

1. Assuming all RPO is equally likely to be realized. A government defense contract (Boeing) is far more likely to be completed than a SaaS multi-year contract (which can be terminated by customer choice or bankruptcy). RPO from a customer with strong credit and contractual penalties for cancellation is worth more than RPO from a customer in financial distress. Always assess customer concentration and credit quality when evaluating RPO.

2. Confusing RPO growth with organic revenue growth. A company can have growing RPO but declining revenue if the new RPO is all from large, long-term contracts that haven't started being recognized yet. This creates a timing mismatch: revenue will accelerate later, but earnings are suppressed now. Investors often misinterpret this as weakness when it's actually a setup for future acceleration.

3. Ignoring the current vs. non-current split. A company with $10 billion in RPO sounds bullish until you discover it's all non-current (expected to be earned 3–5 years from now). In the near term, the company's revenue visibility is much lower. Always require the time-period breakdown.

4. Failing to account for customer concentration in RPO. If 50% of RPO comes from a single customer and that customer defaults, the company's future revenue collapses. Companies are required to disclose customer concentration in the revenue footnote, but many investors skip this check. A company with high RPO concentration risk is riskier than the headline numbers suggest.

5. Using RPO to backfill earnings models without adjusting for execution risk. RPO is contracted, but contracts can be modified, customers can fail, and execution can slip. A contractor might have $5 billion in backlog but face schedule slips that push revenue recognition into later years. Mechanical models that assume RPO converts to revenue as initially scheduled overestimate earnings.

Expanding RPO analysis: book-to-bill ratio and backlog conversion​

Sophisticated analysts often use a metric called book-to-bill ratio to assess how fast RPO is converting to revenue:

Book-to-bill = New bookings / Revenue in the period

If a company books $500 million in new contracts and recognizes $400 million in revenue, book-to-bill is 1.25x. This means the company is booking more than it's recognizing, so RPO is growing. A book-to-bill above 1.0 is bullish (growing backlog); below 1.0 suggests the backlog is shrinking.

Backlog conversion rate measures how much of the quarter's revenue came from the backlog versus new bookings:

Backlog conversion = Quarterly revenue / Beginning RPO

If a company starts the quarter with $4 billion in RPO and recognizes $1 billion in revenue, backlog conversion is 25%. This means the company will take 4 quarters (one year) to convert existing backlog to revenue, a measure of revenue visibility.

These metrics are especially useful for capital-intensive industries (aerospace, defense, engineering, construction) where large, lumpy projects dominate the business model.

RPO in practice: Lockheed Martin and predictable defense earnings​

Lockheed Martin, a prime defense contractor, discloses its backlog prominently because it's a key measure of future revenue visibility. Lockheed's backlog typically runs 1.5–2.0 years of revenue, amounting to $140–160 billion. This massive RPO comes from long-term government contracts for military hardware, missiles, and support services.

For Lockheed, RPO is exceptionally reliable. Government contracts have spending cycles and budgetary pressures, but cancellation is rare and termination requires political will. As a result, Lockheed's backlog is almost as predictive as revenue already in the door. Investors use backlog growth as a leading indicator of future revenue growth. When Lockheed's backlog grows, earnings will follow 12–24 months later.

FAQ​

How do I calculate the quarters of revenue visibility from RPO?​

Divide current RPO by the most recent quarter's revenue. If RPO is $4 billion and quarterly revenue is $1 billion, visibility is 4 quarters. This assumes revenue recognition accelerates evenly, which it may not, but it's a useful rule of thumb.

Should I care more about RPO or deferred revenue?​

Both matter, but for different reasons. Deferred revenue is cash already collected; it's revenue that's almost guaranteed and won't be reversed except for refunds or contract cancellations. RPO is contracted but not yet billed or received. Deferred revenue is a near-certainty; RPO is high-likelihood but subject to execution and customer risk.

Can RPO be a red flag?​

Yes, if it's declining. Declining RPO (especially current RPO) suggests the company is signing fewer or smaller contracts. For a growth company, this is a major warning sign. It can also be a red flag if RPO is concentrated in one customer or geography, suggesting business risk.

What's the difference between RPO and pipeline?​

Pipeline (sales pipeline) is deals in negotiation, not yet signed. RPO is deals already signed. Pipeline is forward-looking but uncertain; RPO is contractually binding. Companies often quote pipeline in earnings calls (e.g., "we have $20 billion in pipeline") to suggest future growth, but pipeline is not RPO and requires several more months of effort to convert.

How do I find RPO if it's not highlighted in the earnings release?​

Search the 10-K or 10-Q for "remaining performance obligations" or "backlog." It should be in the MD&A or the Revenue Recognition footnote (usually Note 2 or 3). If it's not disclosed and the company has material long-term contracts, consider this a red flag for opaque disclosure.

Can RPO be negative?​

No, RPO is always positive or zero. Negative would mean the customer owes nothing and the company has no obligation, which is the end state when the contract is fully performed. However, a company can have negative contract balances if advances (deferred revenue) exceed RPO—but this is reported as a liability, not RPO.

Is RPO the same for all industries?​

No. RPO is most useful for companies with multi-period contracts (defense, industrial, enterprise software, construction). Retail, fast-moving consumer goods, and transactional businesses have minimal RPO because each sale is independent. For those businesses, RPO analysis is less relevant.

  • Deferred revenue: Cash received upfront for future performance, reported as a current liability on the balance sheet.
  • Contract assets: Amounts the company has earned but not yet billed to the customer, reported on the balance sheet under assets.
  • Contract modifications: Changes to existing contracts (expansion, reduction, scope changes) that affect the total contract value and RPO.
  • Performance obligations: Under ASC 606, the specific deliverables the company must provide to the customer; RPO is the total value of unsatisfied performance obligations.
  • Backlog conversion timing: The expected pace at which RPO will convert to revenue, affected by project schedules, customer cash flow, and execution.

Summary​

Remaining Performance Obligations and backlog are foundational concepts for analyzing companies with multi-period contracts. They reveal the forward visibility of revenue that the income statement alone cannot show. A company with growing RPO and high visibility (RPO / revenue ratio above 2x) has more predictable earnings and less dependence on new deal flow in any given period. A company with declining RPO or low visibility is vulnerable to near-term revenue disappointments.

For investors, RPO analysis is the bridge between the sales department's optimism and the revenue accounting department's conservatism. It shows what's been promised but not yet delivered, what's contracted but not yet billed. Understanding RPO separates companies with sustainable, predictable growth from those hustling quarter to quarter to meet targets.

The best place to start RPO analysis is the revenue footnote in the 10-K. Look for the current and non-current split. Compare RPO to quarterly revenue to calculate visibility. Track RPO growth quarter over quarter to spot acceleration or deceleration. For manufacturing and defense contractors, treat backlog as the most important leading indicator of revenue and earnings growth.

Next​

Guidance, consensus, and beat-vs-miss mechanics

Companies with RPO equivalent to 2+ years of revenue have four times the earnings visibility of companies with 6 months of RPO, making contract length a critical valuation factor in capital-intensive industries.