Bookings vs Billings vs Revenue and the Balances That Link Them

Bookings vs billings vs revenue is the difference between a contract signed, an invoice sent and a service delivered. Only revenue has a rulebook, ASC 606, which also defines the two balances linking all three: deferred revenue and remaining performance obligations (RPO). Bookings are best counted as RPO counts them, by the term the customer cannot cancel.

The three can differ by an order of magnitude in a single quarter. In the three months to 31 December 2025, Microsoft’s commercial bookings rose 230%, driven by “the previously announced large Azure commitment from OpenAI that reflects multi-year demand needs”. In the same quarter its commercial RPO rose 110% to $625 billion, its revenue rose 17% to $81.3 billion, and Microsoft Cloud revenue, the closest match to the commercial book, rose 26% (Microsoft, 2026). Even against the cloud figure, bookings grew almost nine times as fast. How much of a booking should a founder, a finance lead or a board believe? ASC 606 gives an answer, although it never uses the word.

Bookings vs billings vs revenue, and the two balances between them

	What it counts	Moves when	Defined by	Reported in
Bookings	Contract value signed in the period	A contract is signed	No standard; each company sets its own	Sales reports, earnings calls
Billings	Amounts invoiced in the period	An invoice is issued	No standard; usually revenue plus the change in deferred revenue	Non-GAAP tables
Revenue	Service transferred to the customer	The service is delivered	ASC 606 (US GAAP); IFRS 15	Income statement
Deferred revenue	Billed or paid, not yet earned	Up with billings, down with revenue	ASC 606, as a contract liability	Balance sheet
RPO	Contracted, not yet earned, within the noncancellable term	Up with binding commitments, down with revenue	ASC 606-10-50-13	Notes to a public company’s accounts

Source: FASB, ASU 2014-09 (ASC 606); EY (2026) on the absence of a common definition of backlog; AppDynamics S-1 (2016) and Electronic Arts 10-K (2026) for the billings formula; CX Cash synthesis.

Does any accounting standard define bookings vs billings vs revenue?

Only revenue. ASC 606, the US revenue standard issued in May 2014, applies to public companies for years beginning after 15 December 2017 (Journal of Accountancy, 2015). It reduces revenue to five steps, and the last is to “Recognize revenue when (or as) the entity satisfies a performance obligation” (FASB, 2014). A subscription is usually satisfied over time, so its revenue arrives a day at a time, whatever the invoice says and whenever the cash lands.

Bookings and billings appear nowhere in the standard, and mean different things in different filings. Electronic Arts reports net bookings, computed “by adding total net revenue to the change in deferred net revenue for online-enabled games”: $8,026 million in the year to March 2026, on $7,531 million of revenue (EA, 2026). A SaaS company would call that formula billings. Uber defines Gross Bookings as “the total dollar value, including any applicable taxes, tolls, and fees” of its rides, deliveries and freight (Uber, 2026). At Uber, bookings include the tolls. Microsoft’s FY2026 10-K never uses the word, although its earnings calls report commercial bookings.

The SEC asks listed companies that publish such metrics for “A clear definition of the metric and how it is calculated”, and an explanation when the method changes (SEC, 2020). A private company’s board pack carries no such duty. Letting the signing date stand in for the revenue date has a price, and MicroStrategy paid it. Between its 1998 IPO and March 2000, the SEC alleged, the company “improperly recognized material amounts of revenue upfront” and recorded revenue from deals whose contracts were not properly executed in the same fiscal period. The restatement removed about $66 million of the $365 million of revenue reported over three years, or 18% (our arithmetic), and the stock fell “from $260 per share to close at $86 per share on March 20, 2000” (SEC, 2000).

How do deferred revenue and RPO connect the three numbers?

The standard defines where bookings and billings leave a mark. Once either party to a contract has performed, a company must show the contract on its balance sheet “as a contract asset or a contract liability, depending on the relationship between the entity’s performance and the customer’s payment” (ASC 606-10-45-1). An invoice issued or a payment received before the service creates a contract liability, which most software companies call deferred or unearned revenue. A signed contract on which neither side has yet performed creates no balance at all. Its only trace is the disclosure of remaining performance obligations: “The aggregate amount of the transaction price allocated to the performance obligations that are unsatisfied (or partially unsatisfied)” at the period end (ASC 606-10-50-13).

Deferred revenue rises with billings and falls as revenue is recognised; RPO rises with binding commitments and falls the same way. Either inflow can therefore be worked out from revenue and the change in its balance.

billings = revenue + Δ deferred revenue · bookings = revenue + Δ RPO

The first identity is how AppDynamics defined billings in its 2016 S-1: “our total revenues plus the change in our deferred revenue” (AppDynamics, 2016). The second is our definition of bookings, and it counts only what the customer cannot cancel. Salesforce showed investors the balances for a single deal in 2018: $60 million over three years, invoiced annually and signed on the last day of a half-year (Salesforce, 2018).

One $60M contract, six different numbers, $ millions

	Y1 H1	Y1 H2	Y2 H1	Y2 H2	Y3 H1	Y3 H2	Y4 H1
Bookings	60	0	0	0	0	0	0
Billings	20	0	20	0	20	0	0
Revenue	0	10	10	10	10	10	10
Unearned revenue	20	10	20	10	20	10	0
RPO	60	50	40	30	20	10	0
cRPO (next 12 months)	20	20	20	20	20	10	0

Source: Salesforce Investor Day presentation, Form 8-K Exhibit 99.1 (2018), for the unearned revenue, RPO, cRPO and revenue rows. The bookings row (revenue plus the change in RPO) and the billings row (revenue plus the change in unearned revenue) are our arithmetic.

Every row is correct, and no two agree. Bookings put the deal in one half-year. Billings arrive in annual lumps, so unearned revenue halves and doubles every six months, and a board that read it as demand would see a collapse and a recovery that never happened. Revenue is flat.

Why do billings rise and fall when demand has not changed?

Because invoice terms move them as much as customers do. The billings identity always holds, but its result depends on contract terms. AppDynamics billed $258.5 million in the year to January 2016 against $150.6 million of revenue, 1.72 times as much. In the nine months to October 2016 its revenue grew 54% and its billings 44%, and the S-1 warned of “fluctuations in payment terms affecting the billings recognized in a particular period”. Zscaler’s FY2026 10-K lists “the mix of billings among monthly in advance, quarterly in advance, annually in advance and multi-year in advance” among the factors that can move its quarterly results (Zscaler, 2026).

The identity also has no line for balances that arrive from outside the business. Salesforce’s FY2026 10-K walks unearned revenue from $20,743 million to $24,317 million with a line called “Billings and other” of $45,099 million, against revenue of $41,525 million (Salesforce, 2026). The “other” covers currency, contract assets and $651 million of unearned revenue that arrived with Informatica, invoiced before Salesforce owned the company. A calculated-billings figure counts all of it as if Salesforce had sent the invoices.

Billings can also fall while demand holds. Datadog said in 2022 that “some customers aren’t changing their level of usage growth but are being more conservative in their commitments, which impacts billings and RPO growth but not revenue growth” (quoted by Jamin Ball, 2022). A board that ties bonuses or hiring to billings can end up rewarding a finance team for moving customers to annual invoices paid upfront. That may be a good cash decision, and it says nothing about demand.

How much of a signed contract should count as a booking?

Only the part that binds the customer, if the RPO rules are the guide. ASC 606 answers through the RPO disclosure, which PwC says covers only “the noncancellable contract term”. Its worked example is a two-year SaaS contract for $240,000 that the customer may terminate for convenience on one month’s notice, without penalty. The contract adds $10,000 of RPO, 4.2% of its value (our arithmetic), because “the contract is, in substance, a one-month contract with a right to renew”. The answer holds “even if the customer is not expected to terminate the contract” (PwC Viewpoint, §33.4). Renewals stay out “even if such purchases are expected”, and Deloitte’s roadmap excludes amounts subject to termination without penalty (Deloitte, §15.2).

Applied to bookings, the same rule counts a contract only up to the date on which the customer could leave without a penalty. The table below applies it to one hypothetical quarter.

Three hypothetical contracts counted to the date the customer could leave, first quarter, $ thousands

Contract	Terms	Bookings at contract value	Bookings to the notice date	Billings	Revenue	Deferred revenue at quarter end	RPO at quarter end
A	2 years, $240k, noncancellable, billed annually in advance	240	240	120	30	90	210
B	2 years, $240k, cancellable on 1 month’s notice, billed monthly	240	40	30	30	0	10
C	1 year, $36k, noncancellable, billed quarterly in advance	36	36	9	9	0	27
Total		516	316	159	69	90	247

Source: our calculation for a hypothetical company, with all three contracts signed and started on the first day of the quarter. Contract B follows PwC’s example: each month it is not cancelled adds one more month (10) to the binding term, so four months bind by quarter end. Check: 316 − 69 = 247 of RPO; 159 − 69 = 90 of deferred revenue.

The same three signatures support four headline numbers, from $516k down to $69k. Counted to the notice date, $200k of the quarter’s bookings, 39% of contract value, could walk away on a month’s notice. Private companies may skip the RPO disclosure altogether, since ASC 606-10-50-16 lets an entity other than a public business entity “elect not to provide the disclosures”, so the discipline has to come from the board. TechCrunch reported in May 2026, on the word of investors it did not name, that some AI start-ups were substituting “contracted ARR” for ARR. One VC had seen “companies where CARR is 70% higher than ARR, even though a significant chunk of that contracted revenue will never actually materialize” (TechCrunch, 2026). Bessemer’s own definition of CARR nets out “forecasted churn or downsell” (Bessemer, 2021).

How long will a backlog take to become revenue?

Size alone does not say: a binding backlog can still take years to become revenue. German industry has a word for the clock: Auftragsreichweite, literally the reach of the order book. It is the backlog at the reporting date divided by annual revenue, times 365, or the number of days of revenue already under contract (our translation; German Wikipedia, Auftragseingang). Applied to RPO, it separates a big backlog from a slow one.

RPO measured in days of revenue, fiscal 2026

Company	Year end	RPO	Revenue	RPO in days of revenue	Share of RPO due within 12 months
Salesforce	31 Jan 2026	$72.4B	$41.5B	636	48%
Microsoft	30 Jun 2026	$684B	$331.8B	752	About 30%
Oracle	31 May 2026	$638B	$67.4B	3,457	About 12%

Source: Salesforce, Microsoft and Oracle 10-Ks for fiscal 2026. Days of revenue (RPO ÷ revenue × 365) and Salesforce’s 12-month share (cRPO of $35.1B ÷ RPO) are our arithmetic.

Oracle’s backlog equals about 9.5 years of revenue (our arithmetic), and the company tells readers that “the timing of booking of large contracts” moves both its revenue and its contracting volumes (Oracle, 2026). Microsoft’s backlog was concentrated as well as long. In January 2026 its CFO said “Approximately 45% of our commercial RPO balance is from OpenAI”, and two quarters later commercial bookings grew 10% with OpenAI’s commitments and 18% without them (Microsoft, 2026b). These are three of the largest backlogs in software, but a plain ratio of RPO to revenue reads the same way on a startup’s book: hiring sized to total RPO commits to salaries years before the revenue arrives.

The 12-month slice became a headline metric only in 2018. As ASC 606 took effect that May, Salesforce first reported “current remaining transaction price”, and in August it adopted the names remaining performance obligation and current RPO (Salesforce, 2018a; Salesforce, 2018b). Among the 2017 and 2018 filings on EDGAR, either phrase appears only in Salesforce’s. Others followed: ServiceNow, for one, reported in June 2026 that 46% of its $29.0 billion of RPO was current (ServiceNow, 2026).

Does RPO mean anything for a usage-priced company?

Less than for a subscription business, as Snowflake’s own filing says. It warns that its RPO “is not necessarily indicative of future product revenue growth because it does not account for the timing of customers’ consumption or their consumption of more than their contracted capacity”. Its RPO excludes on-demand use (Snowflake, 2026). A month-to-month self-serve business has about one month of revenue under contract at any moment, yet it may be growing fast. Andreessen Horowitz argued in 2015 that “Billings is a much better forward-looking indicator of the health of a SaaS company than simply looking at revenue” (a16z, 2015). Bessemer calls CARR potentially “an even better indicator of topline momentum than ARR”.

Where usage is the product, a16z and Snowflake have the better of it: the forward signal lives in usage, retention and cohorts. Snowflake’s compromise is to report RPO and add that it expects about 54% of its $9.0 billion to become revenue within 12 months “based on historical customer consumption patterns”. Counting only the binding term still earns its place there, because a thin binding backlog is a fact about risk, and a growth metric that hides it borrows confidence from commitments the customer has not made.

Which of the three numbers shows how fast the business is growing?

Revenue shows what has been delivered, and it is the only one of the three with a standard behind it. Billings show invoicing, which moves with payment terms as much as with demand: AppDynamics billed 1.72 times its revenue in one year and then grew billings more slowly than revenue. Bookings show commitment, and the part of a contract that binds the customer is the part worth counting. Bookings vs billings vs revenue reconcile through two balances, deferred revenue for billings and RPO for bookings, and both roll-forwards work for a private company even though ASC 606-10-50-16 lets it skip the RPO disclosure. Counted to the notice date, PwC’s two-year $240,000 contract on one month’s notice is a $10,000 booking.

Sources and notes

• Andreessen Horowitz (2015). 16 Startup Metrics (J. Jordan, A. Hariharan, F. Chen and P. Kasireddy).
• AppDynamics, Inc. (2016). Form S-1 registration statement.
• Ball, J. (2022). Clouded Judgement 8.5.22 (quoting Datadog).
• Bessemer Venture Partners (2021). Scaling to $100 million. Atlas.
• Deloitte. Roadmap: Revenue Recognition, §15.2, Contracts with customers.
• Electronic Arts Inc. (2026). Form 10-K for the fiscal year ended 31 March 2026.
• EY (2026). Financial reporting developments: Revenue from contracts with customers (ASC 606).
• FASB (2014). Accounting Standards Update 2014-09, Revenue from Contracts with Customers (Topic 606).
• Journal of Accountancy (2015). FASB formally issues revenue recognition delay.
• Microsoft Corporation (2026). FY26 Q2 and Q4 earnings call transcripts; Form 10-K for the fiscal year ended 30 June 2026.
• Oracle Corporation (2026). Form 10-K for the fiscal year ended 31 May 2026.
• PwC Viewpoint. Financial statement presentation guide, §33.4, Revenue disclosures (ASC 606).
• Salesforce, Inc. (2018). Q1 fiscal 2019 results (8-K Exhibit 99.1); Q2 fiscal 2019 results; Investor Day presentation (8-K Exhibit 99.1). (2026). Form 10-K for the fiscal year ended 31 January 2026.
• SEC (2000). Litigation Release No. 16829, SEC v. Michael Jerry Saylor, Sanjeev Kumar Bansal and Mark Steven Lynch.
• SEC (2020). Release No. 33-10751, Commission Guidance on Management’s Discussion and Analysis of Financial Condition and Results of Operations.
• SEC EDGAR (2017 to 2018). Company filings using “current remaining transaction price” or “current remaining performance obligation”.
• ServiceNow, Inc. (2026). Form 10-Q for the quarter ended 30 June 2026.
• Snowflake Inc. (2026). Form 10-Q for the quarter ended 31 July 2026.
• TechCrunch (2026). How VCs and founders use inflated ARR to kingmake AI startups.
• Uber Technologies, Inc. (2026). Form 10-K for the fiscal year ended 31 December 2025.
• Wikipedia (German). Auftragseingang.
• Zscaler, Inc. (2026). Form 10-K for the fiscal year ended 31 July 2026.

Company figures come from the filings, earnings calls and investor presentations listed, and the accounting rules from ASC 606 and the Deloitte, EY and PwC guides to it. Uncited figures, and those marked “our arithmetic”, are derived from the filings cited, including the bookings and billings rows of the $60M contract table, which come from Salesforce’s published rows. The three contracts in the quarter table are hypothetical, and the German gloss is our translation.