Audited ·Last updated 29 Jul 2026·5 citations·Tier 2·0 uses

Bookings to Revenue Calculator — ASC 606 Ratable Recognition

Free bookings to revenue calculator. Turn a signed contract into recognised revenue, deferred revenue and unbilled backlog under ASC 606 ratable recognition.

Bookings to Revenue Calculator

The full value of the contract the customer signed, across its whole term. A booking is a commitment, not revenue and not cash — it is the moment the signature lands.
$
The service period the contract covers. Revenue accrues straight-line across this term, so it is the denominator of every recognition figure on this page.
months
How long the period you are reporting on is — 1 for a month, 3 for a quarter, 12 for a year. The model assumes the contract starts at the beginning of it.
months
What you actually invoiced the customer during the period. For a two-year contract billed annually in advance, this is the first year's invoice, not the whole contract.
$
The deferred revenue balance (contract liability) you carried into the period from earlier contracts. Leave at 0 to see this contract in isolation.
$
Revenue recognised in the period
$30,000.00
The share of the booking that becomes revenue in this period, on a straight-line time-elapsed basis. Assumes an even service pattern, one performance obligation, and a contract starting at the beginning of the period — a contract that fails any of those needs a schedule, not a single division.
Bookings per dollar of revenue
8
Revenue recognised per month
$10,000.00
Closing deferred revenue
$90,000.00
Unbilled bookings (backlog)
$120,000.00
Share of the contract recognised
12.50%

Background.

Bookings, billings and revenue are three different numbers, and a subscription business reports all three about the same contract in the same quarter without any of them agreeing. This calculator shows how they separate. Sign a $240,000 two-year contract, invoice the first year's $120,000 up front, and close a quarter: bookings are $240,000, billings are $120,000, and recognised revenue is $30,000. Deferred revenue closes at $90,000 and unbilled backlog stands at $120,000. Every one of those figures is correct, and each answers a different question.

A booking is a commitment — the moment a customer signs. It appears on no financial statement. A billing is an invoice, which drives cash and creates a receivable. Revenue is what FASB ASC 606 lets you recognise, and for a standard SaaS subscription that is spread across the service term. ASC 606-10-25-27 recognises revenue over time when, among other criteria, "the customer simultaneously receives and consumes the benefits provided by the entity's performance as the entity performs" — which is precisely what a subscription does. This page applies a straight-line, time-elapsed measure of progress: $240,000 over 24 months is $10,000 a month, so three months of service is $30,000 of revenue.

The amount you have invoiced beyond what you have recognised is a contract liability, which almost every company labels deferred revenue. Bill $120,000 and recognise $30,000 and you close the quarter owing $90,000 of service, sitting on the balance sheet as a liability. Bill nothing while delivering three months of service and the balance goes the other way — the calculator will show a negative closing figure, which is not a negative liability but a contract asset. The output description says so beside the number, because a negative deferred-revenue balance is a real position and a confusing one.

One output needs a health warning before you read it. The bookings-to-revenue ratio — $240,000 ÷ $30,000 = 8 here — is arithmetically just the contract term divided by the reporting period. It does not depend on the dollar amount at all: a $240 contract and a $240 million contract on the same 24-month term produce the same ratio of 8. That makes it a useful measure of how far your revenue lags your sales, and a useless one for comparing companies with different contract lengths. A vendor selling three-year deals will always show a higher ratio than one selling annual deals, and neither fact says anything about the quality of either business.

Finally, the model. This page assumes the contract starts at the beginning of the reporting period, that the service pattern is even so revenue accrues straight-line, and that the whole booking is a single performance obligation. Real contracts break all three: a mid-quarter start needs proration, an implementation deliverable is usually a separate performance obligation with its own recognition pattern, and usage-based or milestone-based components are variable consideration that ASC 606 handles differently. Where any of those apply, this calculator gives you the ratable baseline and your revenue team gives you the schedule.

What is bookings to revenue calculator?

Bookings-to-revenue is the relationship between contracts signed and revenue recognised — three distinct measures that a subscription business reports simultaneously and that never equal each other for a growing company. Bookings are the total contract value a customer has committed to, recorded at signature and appearing on no financial statement. Billings are amounts invoiced during a period, which drive cash collection and accounts receivable. Revenue is what FASB ASC 606 permits to be recognised as performance obligations are satisfied; for a standard subscription that happens over time, ratably across the service term, because the customer simultaneously receives and consumes the benefit of the service as it is delivered. The gap between billings and revenue is a contract liability — deferred revenue — when invoicing runs ahead of delivery, and a contract asset when delivery runs ahead of invoicing. The gap between bookings and billings is unbilled backlog: contracted revenue that has touched neither the income statement nor the cash account. This calculator computes all four figures from one contract on a straight-line basis, and shows the bookings-to-revenue ratio, which measures how far revenue lags sales rather than how well a business is performing.

How to use this calculator.

  1. Enter the total contract value the customer signed, across the whole term. This is the booking, and it is not revenue and not cash.
  2. Enter the contract term in months. Revenue accrues straight-line over this, so it is the denominator of every recognition figure here.
  3. Enter the reporting period in months — 1 for a month, 3 for a quarter, 12 for a year. The model assumes the contract starts at the beginning of it; if yours starts mid-period, prorate the period length accordingly.
  4. Enter what you invoiced during the period. For a two-year contract billed annually in advance, that is the first year's invoice, not the whole contract value.
  5. Enter any deferred revenue carried in from earlier contracts, or leave it at zero to see this contract on its own.
  6. Read recognised revenue as the headline. Then read closing deferred revenue and unbilled backlog together: the first is money collected or invoiced but not yet earned, the second is money contracted but not yet invoiced.
  7. Treat the bookings-to-revenue ratio as a lag measure only. It is the contract term divided by the reporting period and is dictated by how you sell, not by how well you sell.

The formula.

Rev = TCV × min(p, n) ⁄ n · Deferred = D₀ + B − Rev · Backlog = TCV − B

Straight-line recognition divides the total contract value by the term in months to get a monthly rate, then multiplies by the number of months of service delivered in the reporting period. That month count is capped at the contract term, because a reporting period longer than the contract cannot recognise more than the contract is worth. Closing deferred revenue is the opening balance plus billings minus recognised revenue; it is positive when invoicing runs ahead of delivery and negative when delivery runs ahead of invoicing, and the negative case is a contract asset rather than a negative liability. Unbilled bookings are total contract value minus what has been invoiced, and they too can go negative if invoicing has run ahead of the booking being modelled. The bookings-to-revenue ratio is total contract value divided by revenue recognised in the period, which algebraically reduces to the contract term divided by the capped period length — the dollar amounts cancel entirely. All arithmetic is carried at full decimal precision and rounded only at the return boundary, to two decimal places. The order matters: recognised revenue is computed as TCV × months ÷ term rather than by rounding a monthly rate and multiplying, so a $100,000 seven-month contract recognises exactly $100,000 over seven months instead of 7 × $14,285.71 = $99,999.97.

A worked example.

Example

A SaaS vendor signs a two-year contract worth $240,000 in total on the first day of a quarter, and invoices the first year — $120,000 — up front. The customer pays. The quarter closes. The sales team reports a $240,000 booking. The finance team reports $120,000 of billings. The income statement reports $30,000 of revenue: $240,000 divided by 24 months is $10,000 a month, and three months of service have been delivered, so 12.5% of the contract has been recognised. Three numbers, one contract, one quarter, and every one of them right. The balance sheet holds the difference. Closing deferred revenue is $0 opening + $120,000 invoiced − $30,000 recognised = $90,000 — nine months of service already paid for and not yet delivered. Unbilled bookings are $240,000 − $120,000 = $120,000, the second year of the contract, which will be invoiced next year and does not appear anywhere on this quarter's statements. The bookings-to-revenue ratio is $240,000 ÷ $30,000 = 8. Read it carefully: that 8 is exactly 24 months of term divided by 3 months of reporting period, and it would be 8 for a $240 contract on the same terms. It tells you that revenue lags bookings by a factor of eight in a quarterly view of a two-year deal — useful for understanding why a great sales quarter barely moves the revenue line, and worthless for comparing this vendor to one that sells annual contracts. Change one thing and the picture flips. Bill nothing this quarter and invoice in arrears instead: recognised revenue is still $30,000, but closing deferred revenue becomes −$30,000. That negative figure is a contract asset — service delivered and not yet invoiced — and it belongs on the other side of the balance sheet. A cash-flow forecast built from a deferred-revenue balance that has quietly gone negative will be wrong in the direction that hurts.

amount Invoiced In Period120,000
contract Term Months24
opening Deferred Revenue0
bookings Tcv240,000
reporting Period Months3

Frequently asked questions.

What is the difference between bookings, billings and revenue?
A booking is the total value a customer has committed to when they sign — it appears on no financial statement and is a sales measure. A billing is an invoice issued during the period; it creates a receivable and drives cash collection. Revenue is what accounting rules permit you to recognise, and under FASB ASC 606 a subscription is a performance obligation satisfied over time, so it is recognised ratably across the service term. A single $240,000 two-year contract billed annually in advance produces $240,000 of bookings, $120,000 of billings and $30,000 of revenue in its first quarter. All three are correct, and a growing subscription business will show bookings above billings above revenue for as long as it keeps growing.
How does ASC 606 apply to a SaaS subscription?
ASC 606-10-25-27 lists the criteria under which an entity satisfies a performance obligation over time rather than at a point in time. The first is that "the customer simultaneously receives and consumes the benefits provided by the entity's performance as the entity performs", which describes a hosted subscription exactly — the customer gets value every day the service runs, not on the day the contract is signed. Where a performance obligation is satisfied over time, the entity selects a measure of progress toward its complete satisfaction; for an even service pattern a time-elapsed output method gives straight-line recognition, which is what this calculator implements. It is the ordinary case and not the only one: a contract with an implementation deliverable, milestone acceptance, or usage-based fees will have obligations that do not follow this pattern.
Why can the closing deferred revenue balance be negative?
Because deferred revenue as presented here is opening balance plus billings minus recognised revenue, and if you deliver service before you invoice it, recognition outruns billing. The negative figure is not a negative liability — it is a contract asset, sitting on the other side of the balance sheet, representing revenue earned and not yet invoiced. This is entirely normal for contracts billed monthly in arrears, for annual contracts invoiced at the end of a service year, and for the first period of any deal where the paperwork lagged the go-live date. It matters practically because cash forecasts built off a deferred-revenue balance implicitly assume that balance is positive; when it is not, the cash has not arrived and the forecast is wrong in the direction that hurts.
Is a high bookings-to-revenue ratio good?
It is neither good nor bad, and treating it as a performance measure is the main way this metric is abused. The ratio is total contract value divided by revenue recognised in the period, which reduces algebraically to the contract term divided by the reporting period — the dollar amounts cancel out entirely. A vendor selling three-year deals reviewed quarterly will show a ratio of 12; one selling annual deals will show 4; a monthly self-serve product reviewed monthly will show 1. None of those facts describes execution quality. What the ratio does tell you is how far revenue lags sales in your business, which is genuinely useful for explaining why a record bookings quarter barely moves the revenue line, and for sizing how much of your future revenue is already contracted.
What does this calculator not handle?
Four things, all common. Mid-period contract starts: the model assumes the contract begins on the first day of the reporting period, so a deal that goes live halfway through needs the period length prorated. Multiple performance obligations: an implementation or onboarding deliverable is usually a separate obligation under ASC 606 with its own recognition pattern, and the transaction price has to be allocated between them at standalone selling price — folding it into the subscription line overstates early revenue. Variable consideration: usage-based fees, overages and milestone payments are not fixed and are estimated and constrained under separate rules. And step-up or ramped pricing: a contract worth $50,000, $60,000 and $70,000 across three years does not recognise evenly. For any of those, use this page for the ratable baseline and build the schedule properly.
Should bookings include renewals and multi-year contracts in full?
Whatever you decide, decide once and disclose it — this is the classic place where two companies' "bookings" numbers stop being comparable. Common conventions include counting the full total contract value of new and renewal contracts, counting only the first year, or counting new business separately from renewals. Each is defensible; mixing them across periods is not. The point matters beyond internal tidiness: bookings is an operating metric with no standard-setter definition, and SEC Release 33-10751 requires a registrant presenting such a metric to disclose its definition, why it is useful, how management uses it, and any change in how it is calculated. This calculator takes whichever total you enter and shows how it converts — it cannot tell you what you should have counted.

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.

Embed

Quanta Pro

Paid features are coming later.

  • All 762 calculators remain free
  • No billing is enabled
Coming soon