Bookings to Revenue Calculator — ASC 606 Ratable Recognition

Background.

Sales closes a two-year, $240,000 subscription on the first day of the quarter and rings the bell. Finance invoices the first year, $120,000, and the customer pays. At quarter end the income statement shows $30,000 of revenue. Nobody has made a mistake. Bookings, billings and revenue record three different events: a signature, an invoice and service actually delivered.

Revenue follows delivery because of ASC 606, the US standard for revenue from contracts with customers. A hosted subscription passes its test for recognising revenue over time, since the customer "simultaneously receives and consumes the benefits" of the service while it is being provided. Spread evenly, $240,000 over 24 months earns $10,000 a month, so one quarter earns $30,000. The $90,000 invoiced but not yet earned sits on the balance sheet as deferred revenue, a liability for service still owed. The $120,000 not yet invoiced is unbilled backlog, and it appears on no financial statement at all.

Those gaps explain something every subscription business lives with: a record sales quarter barely nudges reported revenue, and a slump in new sales takes several quarters to show up in it.

The arithmetic covers the plain case: one contract, one evenly delivered service, starting on the first day of the period. Implementation work, usage charges and mid-period starts need a proper schedule built by whoever keeps the books, and nothing here is accounting advice.

What is bookings to revenue calculator?

Bookings are the total contract value a customer commits to at signing; they are a sales measure with no accounting-standard definition, which is why companies define them differently. Billings are the invoices raised in a period. Revenue is the part of the contract earned by delivering service, recognised under ASC 606. When invoicing runs ahead of delivery, the difference is a contract liability, usually called deferred revenue; when delivery runs ahead of invoicing, it is a contract asset. Whatever has been booked but not yet invoiced is unbilled backlog.

How to use this calculator.

1. 01Enter the total contract value across the whole term, every year included. Leave out one-off implementation or onboarding fees unless you are sure they belong in the subscription line.
2. 02Enter the contract term in months: 12 for an annual deal, 36 for a three-year one.
3. 03Enter the reporting period in months: 1, 3 or 12. The contract is assumed to start on the period's first day; if it went live partway through, enter the months of service actually delivered, which cannot be less than one.
4. 04Enter what was invoiced during the period. A two-year deal billed annually in advance has its first-year invoice here, not the full contract value.
5. 05Leave opening deferred revenue at zero to see the contract on its own. Any balance you enter is carried straight into the closing figure, with none of it recognised in the period.
6. 06Read revenue, closing deferred revenue and unbilled backlog together; between them they account for the whole booking.

The formula.

Revenue for the period is TCV × min(p, n) ÷ n, where TCV is the total contract value, n the term in months and p the reporting period in months. This is a straight-line, time-elapsed measure of progress, which fits a service delivered evenly. The min(p, n) cap stops a long period over-recognising a short contract: a 12-month report on a $60,000 six-month deal shows $60,000, not $120,000. The monthly rate is TCV ÷ n and the share recognised is min(p, n) ÷ n. Closing deferred revenue is D₀ + B − revenue, with D₀ the opening balance and B the billings; a negative result is a contract asset, meaning service delivered but not yet invoiced. Unbilled backlog is TCV − B. The bookings-to-revenue ratio, TCV ÷ revenue, simplifies to n ÷ min(p, n), so the dollar amounts cancel and the ratio depends only on how long the contract is relative to the reporting period. Note that the opening balance only rolls forward: none of D₀ is treated as earned during the period, so if it belongs to other contracts that are also earning revenue, deduct their recognition separately.

A worked example.

Frequently asked questions.

References& sources.

1. [1]Financial Accounting Standards Board (May 2014). Accounting Standards Update No. 2014-09, "Revenue from Contracts with Customers (Topic 606)." Source for the over-time recognition criteria at ASC 606-10-25-27, including "the customer simultaneously receives and consumes the benefits provided by the entity's performance as the entity performs", and for the measure-of-progress requirement that underlies straight-line recognition. Authoritative PDF; URL verified live (HTTP 200) 29 July 2026 — the file is a binary PDF, and the paragraph text was cross-checked against Deloitte's DART codification chapters on ASC 606-10 step 5.
2. [2]Jordan, J., Hariharan, A., Chen, F., & Kasireddy, P. (21 August 2015). "16 Startup Metrics." Andreessen Horowitz. Independent authority on the bookings/revenue distinction, and on the error of "counting bookings" as recurring revenue. Retrieved 29 July 2026; quote verified against the live page.
3. [3]Deeter, B. (2 October 2012). "The five accounting metrics for cloud companies." Bessemer Venture Partners Atlas. Independent second authority separating recurring subscription revenue from non-recurring services revenue, which is why an implementation deliverable is treated as its own obligation rather than folded into the subscription line. Retrieved 29 July 2026.
4. [4]U.S. Securities and Exchange Commission (30 January 2020). Release No. 33-10751, "Commission Guidance on Management's Discussion and Analysis of Financial Condition and Results of Operations." Requires a registrant presenting an operating metric such as bookings or backlog to disclose its definition, its method of calculation, why it is useful and how management uses it. sec.gov returns HTTP 403 to automated fetchers; release identifiers verified independently.
5. [5]17 CFR § 229.303 (Regulation S-K Item 303, Management's Discussion and Analysis). Context for how backlog and liquidity are discussed alongside GAAP results. Text verified 29 July 2026 via the Cornell LII mirror of the eCFR.