Key Takeaways

• One 24-month contract worth $132,000 reports $132,000 in bookings, $72,000 in billings and $17,000 in revenue during its first month. All three are right.

• No accounting standard defines bookings or billings. Both words appear zero times in FASB ASU 2014-09, the update that put Topic 606 into the Codification.

• Revenue is defined. ASC 606-10-05-4 Step 5 recognizes it when the seller satisfies a performance obligation by transferring a good or service, which is when the customer obtains control.

• Cash paid ahead of delivery sits on the balance sheet as a contract liability, not as revenue. ASC 606-10-45-2 defines it as an obligation to transfer goods or services for which consideration has been received.

• The three numbers converge exactly once, in the contract's final month, where cumulative billings and cumulative revenue both reach $132,000.

What's the difference between bookings, billings, and revenue?

The difference is the event each number waits for: a signature, an invoice, or delivery. Bookings and billings measure commercial activity. Revenue measures performance, and it's the only one an auditor can test against a standard.

That second row is the one most explainers skip. IFRS 15 walks a seller through five steps: identify the contract, identify the performance obligations, determine the transaction price, allocate it across those obligations, and recognize revenue as each one is satisfied. Nothing equivalent governs the other two, so a sales team can define a booking as total contract value, first-year value, or annualized value and stay internally consistent either way. Compare annual contract value against total contract value on one deal and that gap is where most bookings arguments start.

How does one contract move through all three?

One contract produces three amounts on three different dates, and here's the arithmetic. Inputs: a 24-month contract signed 1 January 2026, a $5,000 per month subscription invoiced 12 months upfront, and a one-time $12,000 implementation fee invoiced on day one and accepted in January. Total contract value is $132,000. I'm assuming the implementation is a distinct obligation satisfied at a point in time and the subscription is satisfied evenly across 24 months, which are the calls Steps 2 and 5 decide on a real contract.

How each cell falls out:

• Month 1 billings of $72,000 are the $60,000 annual prepay plus the $12,000 implementation fee, both invoiced on 1 January.

• Month 1 revenue of $17,000 is the $12,000 fee, earned on acceptance, plus one month of subscription at $5,000.

• Month 1 contract liability of $55,000 is $72,000 invoiced minus $17,000 earned, so the customer has paid for eleven months nobody has delivered.

• Month 12 liability of zero is an accident of the prepay cycle: cumulative revenue reaches $12,000 + (12 x $5,000) = $72,000, matching everything invoiced, and the year-two invoice reopens the gap in month 13.

• Month 24 revenue of $5,000 closes the contract at $12,000 + (24 x $5,000) = $132,000, matching bookings and billings for the first and only time.

Bookings land once, 23 months before the last dollar of revenue does. That lag is why record bookings sit alongside flat revenue with no error anywhere, and why usage-based revenue recognition gets harder when the consumption driving a fee arrives after the invoice.

Which number should you report, and to whom?

Match the number to the question the audience is actually asking, because each of these four wants a different one.

Mismatching them fails in both directions. Bookings shown to a board as revenue inflate a quarter nobody has delivered. Revenue shown to treasury hides the collection dates, since it says nothing about whether an invoice went out. Raising an invoice against recording the underlying charge sits in billing vs invoicing, and performance that outruns the invoice surfaces as unbilled revenue.

Related terms

These five sit closest to the three-way split.

• Annual contract value normalizes a multi-year booking to one year, where most bookings disputes get settled.

• Contracted ARR counts signed commitments that haven't started billing yet.

• Unbilled revenue mirrors an upfront prepay from the opposite side, where delivery outruns the invoice.

• Billing vs invoicing splits the act of working out a charge from the act of sending the document that asks for payment.

• Usage-based revenue recognition applies once consumption rather than the calendar sets the earned amount.

FAQ

Is deferred revenue the same as billings?

No. Billings is what a seller invoiced in a period; deferred revenue is the part of it still unearned at the reporting date. ASC 606-10-45-2 calls that balance a contract liability, an obligation to transfer goods or services for which consideration has been received or is due. On the traced contract, month 1 billings were $72,000 and the liability $55,000.

Can revenue be higher than billings?

Yes, whenever delivery runs ahead of the invoice. A seller that has performed without an unconditional right to payment presents a contract asset under ASC 606-10-45-3, and ASC 606-10-45-4 reserves the word receivable for an unconditional right to consideration. Monthly-in-arrears and metered contracts sit in this shape most of the year.

Does ASC 606 define bookings?

No, and neither does IFRS 15. A text search of FASB ASU 2014-09 Section A returns zero occurrences of "bookings" and zero of "billings" against 337 of "revenue". Its Glossary defines contract, contract asset, contract liability, customer, performance obligation, revenue, standalone selling price and transaction price, and stops there.

Do usage overages count as bookings?

Usage a customer hasn't committed to isn't a booking, because nothing was committed at signature. A minimum commitment is bookable at its committed amount; consumption above it reaches billings when invoiced and revenue when earned, never passing through bookings. Companies that book forecast overage end up defending a number no contract supports.