For educational purposes only; not investment advice. Investing may result in loss.
Direct answer
Bookings and backlog are usually company-defined operating metrics, not standardized GAAP line items. Bookings commonly measure orders or contract value added during a period. Backlog commonly measures some portion of awarded or contracted value that the company expects to convert into future revenue. Their contract perimeter, valuation, timing, cancellation treatment, and update rules vary, so the issuer’s current definition and reconciliation control the interpretation.
Neither metric is revenue, an unconditional receivable, cash, profit, nor a guarantee. Under revenue accounting, revenue is recognized when or as performance obligations are satisfied. Billing and collection can occur before or after that point. Remaining performance obligations, or RPO, are an accounting disclosure about transaction price allocated to unsatisfied or partly unsatisfied performance obligations; they can overlap with backlog but should not be assumed identical.
Keep the measures separate
Map each measure to a date, period, and contract population:
- bookings: additions during a period under the company’s definition, perhaps gross or net of cancellations
- backlog: a point-in-time balance of included work not yet converted to revenue
- RPO: transaction price allocated to remaining performance obligations under the applicable revenue guidance and disclosure elections
- billings: invoices issued during a period, often a company-calculated metric rather than an income-statement line
- receivable: an unconditional right to consideration, subject only to the passage of time before payment is due
- contract asset: recognized consideration conditional on something other than time, such as further performance
- contract liability or deferred revenue: consideration received, or due under the issuer’s presentation policy, before the related revenue is recognized
- revenue: consideration recognized when or as the promised goods or services transfer under the accounting policy
The events do not follow one universal sequence. A customer may prepay, pay on milestones, be billed after delivery, or receive vendor financing. Revenue may be recognized at a point in time or over time. A booking may never enter reported backlog, backlog may be revised without revenue, and revenue from short-cycle or variable arrangements may never have appeared in the disclosed backlog or RPO.
For a consistently defined backlog, a useful bridge is:
ending backlog = opening backlog + additions - revenue converted - cancellations ± scope, price, currency, and estimate changes
The labels and signs must follow the issuer’s definition. Acquisitions, disposals, foreign exchange, contract modifications, variable consideration, options, task orders, and reclassifications should be shown separately rather than silently treated as organic demand.
Worked examples
Suppose a software company signs a noncancelable three-year service contract for $300, invoices and collects the full amount at inception, and recognizes service revenue evenly. If its bookings metric uses total contract value, bookings increase by $300. Before service begins, cash and the contract liability each increase by $300; revenue remains $0. After one year of service, cumulative revenue is $100 and, ignoring tax, financing, refunds, and other entries, the remaining contract liability is $200.
first-year revenue = $300 / 3 = $100
This example does not make bookings, cash, the contract liability, and revenue interchangeable. A company using annual contract value could report a different booking amount, and a contract with cancellation, usage, variable consideration, acceptance, or financing terms would require different analysis.
Now suppose opening backlog is $1.00 billion. During the year the company reports $600 million of additions, recognizes $500 million of revenue from included backlog, and removes $50 million for cancellations, with no other changes:
ending backlog = $1.00 billion + $600 million - $500 million - $50 million = $1.05 billion
If the company defines book-to-bill as bookings divided by revenue for the same period and perimeter:
book-to-bill = $600 million / $500 million = 1.20×
A ratio above 1.00× means additions exceeded that denominator in this example, not that future revenue, cash, or profit is assured. If backlog includes $300 million expected beyond five years, $150 million awaiting funding, and $100 million cancellable for convenience, the headline balance must be segmented before it can support a forecast.
Practical checklist
- Locate the metric definition, reporting date, units, currency, consolidation perimeter, contract types, and whether it is audited or otherwise assured.
- Determine whether bookings use total, annualized, minimum committed, estimated, funded, awarded, signed, or activated value and whether renewals, options, usage, change orders, and acquisitions are included.
- Reconcile gross additions to net additions after cancellations, churn, debookings, scope changes, price changes, foreign exchange, acquisitions, disposals, and methodology changes.
- Reconcile opening to closing backlog and compare the amount converted to revenue with reported revenue, explaining revenue that bypasses backlog.
- Compare backlog with RPO rather than equating them; inspect practical expedients, exclusions, variable consideration, contract duration, and expected recognition time bands.
- Separate funded from unfunded, firm from optional, cancellable from noncancelable, and awarded from merely anticipated work.
- Test customer credit, termination rights, refund clauses, acceptance criteria, financing contingencies, appropriations, regulatory approvals, and enforceability.
- Compare the conversion schedule with production capacity, staffing, suppliers, inventory, implementation milestones, customer readiness, and historical slippage.
- Stress inflation, fixed-price exposure, cost escalation, penalties, warranty obligations, rework, loss contracts, and margin mix; revenue backlog is not profit backlog.
- Compare bookings, backlog, billings, receivables, contract assets, contract liabilities, cash collections, operating cash flow, and revenue over several periods.
- Measure customer, program, product, geography, currency, and government concentration, including a single award’s effect on growth and book-to-bill.
- Read subsequent filings for cancellations, restructurings, delivery delays, estimate revisions, definition changes, partial recasts, and discontinued disclosure.
Common misconceptions
“A booking is revenue.” A booking follows a company metric; revenue follows the accounting model and satisfaction of performance obligations. Timing and eligible amounts can differ substantially.
“Backlog equals RPO or deferred revenue.” These balances may overlap, but their governing definitions and populations differ. A contract liability reflects advance consideration relative to performance, while RPO concerns allocated transaction price not yet recognized.
“Backlog is guaranteed future cash and profit.” Funding, cancellation, credit, delivery, pricing, cost, margin, currency, and collection risks remain, and estimates can be revised.
“Rising backlog always signals stronger demand.” Growth can reflect acquisitions, currency, longer contract duration, slower delivery, price inflation, or definition changes; falling backlog can reflect accelerated conversion rather than weak orders.
Related topics
Authoritative sources
- Commission Guidance on Key Performance Indicators and Metrics in MD&A — SEC (2026-08-07)
- Beginners’ Guide to Financial Statements — SEC (2026-08-07)
- Revenue Recognition Implementation Q&A — FASB (2026-08-07)
- Revenue from Contracts with Customers Taxonomy Implementation Guide — FASB (2026-08-07)