Bookings answer the question "what did we sell this quarter?" Revenue answers the question "what have we actually earned this quarter?" They live in different systems, serve different audiences, and must reconcile without being confused.
Bookings are the total contract value a customer commits to at signing, counted once on the deal date. Revenue is the portion of that contract an accounting team is allowed to recognize in a given period under ASC 606, usually spread ratably over the service term. Bookings reflect sales activity. Revenue reflects earned, delivered value. The two numbers are almost never equal in the same month, and that is by design.
Five things every operator should be able to say in one sentence before they walk into a board meeting, a diligence call, or a sales-finance alignment session. Bookings and revenue tell different stories, and conflating them is the fastest way to lose credibility.
A booking is the full dollar value of a signed contract, counted once on the day it closes. A three-year deal is one booking at the full three-year value. Bookings measure sales output. They are the number sales leadership rallies around because they capture every commitment the customer just made, regardless of how it will be invoiced or earned over time.
Revenue is the slice of a contract an accounting team is allowed to recognize in a given month, quarter, or year under ASC 606. For a subscription, revenue is almost always recognized ratably over the service term. The signed contract becomes revenue slowly, one accounting period at a time, as the product is actually delivered.
A customer who signs a prepaid two-year deal in January produces a large booking in January but only one-twenty-fourth of that value as recognized revenue that same month. Neither number is wrong. They are the same underlying contract viewed through two different lenses: sales commitment versus accounting delivery.
The CRM is the system of record for the deal and the booking. The billing system and the general ledger are the system of record for recognized revenue. Both numbers must reconcile to the same contract, but each one is produced in the system closest to its source of truth. Mixing systems is where the trouble starts.
The most common and most damaging mistake is quoting bookings as if they were revenue in an investor update or a board deck. The company looks twice as large as its financial statements show, diligence catches it, and credibility collapses. Clean definitions, written down and used the same way every time, prevent the embarrassment.
Every booking becomes revenue eventually. The contract tells both systems how. Term length, billing cadence, start date, and performance obligations control how a booking amortizes into revenue over time. When both numbers reconcile back to the same contract list, the sales and finance stories line up without argument.
The clearest way to understand bookings versus revenue is to walk a single contract through both systems. The booking is a one-time event on the deal date. The revenue is a stream of events, one per accounting period, that keeps going for the entire length of the contract. The six cards below trace that journey end to end.
The order form is signed. The CRM moves the opportunity to closed-won. The total contract value is captured as a booking in the period the contract was signed. Nothing about the booking changes over the life of the deal unless the customer signs an amendment. The booking is a point-in-time event tied to the sales close date.
When the service start date arrives, the finance team sets up a revenue schedule. The total subscription portion of the contract is divided across the service term and recognized evenly, one period at a time. A twelve-month subscription recognizes one-twelfth per month. The schedule runs quietly in the general ledger regardless of when the customer actually pays.
Invoicing is separate from both bookings and revenue. A contract can be billed annually in advance, quarterly, or monthly, and the invoice schedule has no effect on the booking number or the revenue recognition schedule. The invoice generates cash and accounts receivable. It does not advance or retard the revenue stream.
When a customer pays upfront for a service they will consume over the next twelve months, the cash is received immediately but the revenue is not earned yet. The unearned portion sits on the balance sheet as deferred revenue, a liability, until the service is actually delivered. Deferred revenue is the accounting-side evidence that bookings and revenue are out of sync.
At the end of each accounting period, the finance system moves one period of value out of deferred revenue and into recognized revenue on the income statement. The booking total does not move. The revenue total grows by one slice. By the end of the service term, the full booking has become revenue and deferred revenue is zero.
When the customer renews, a new booking is recorded in the renewal period at the renewed contract value. Revenue continues to be recognized ratably with no gap, because the service never stopped. One contract transition produces one new booking and no interruption in the revenue stream, which is why the two numbers can drift so far apart over time.
Operators juggle several contract-value acronyms when talking about bookings. Each one answers a slightly different question, and none of them is revenue. Revenue is the ASC 606 number on the income statement. The six cards below separate the four booking-side acronyms from the single accounting-side number so a sales-finance conversation stops talking past itself.
TCV is the full dollar value of a signed contract across its entire term. A three-year deal has a TCV equal to the sum of all three years, including any committed services, implementation fees, and ramp pricing. TCV is the headline booking number for a multi-year sale. It is also the number most prone to being quoted as if it were revenue when it is not.
ACV is TCV divided by the number of years in the term, giving the average annual value of the contract. For a one-year deal, TCV and ACV are the same. For a three-year deal, ACV is one third of TCV. ACV normalizes contracts of different lengths so a sales team can compare deals and set quota against a consistent unit.
ARR is the subscription-only portion of active contracts, annualized. It differs from ACV because it excludes one-time items like implementation, training, or hardware that happen to be inside the contract. ARR is the metric for recurring revenue health. It is still a booking-side management number, not an accounting-side revenue number.
New ARR is the subset of ARR added in a given period from new logos, expansion, and renewals above the previous level. Sales teams forecast and report new ARR. It is often confused with recognized revenue in investor conversations because it sounds similar, but new ARR is still a booking concept measured on the day a contract is signed.
GAAP revenue is what shows up on the audited financial statements under ASC 606. It is only the portion of signed contracts delivered in the period, net of discounts, after performance obligations have been satisfied. It is the number auditors sign off on and the number public investors see. It almost never matches bookings for the same period.
The one discipline that keeps these numbers honest is that every TCV, ACV, ARR, new ARR, and recognized revenue figure must reconcile to the same contract list. Finance, sales, and leadership all argue less when a question like "what is our new ARR?" can be answered with the exact set of contracts that drove it. The contract list is the shared source of truth.
The bookings-versus-revenue conversation is where sales and finance teams most reliably talk past each other. Each team is reporting the right number from its own perspective, and both can be true at the same time. The six patterns below are the friction points that come up in every growing subscription business, and the discipline that resolves each one.
A sales team posts a record bookings quarter driven by a few large multi-year deals. The CFO quietly notes that recognized revenue barely moved. Both numbers are correct. The multi-year deals produced a big booking and will produce revenue slowly over the next twenty-four or thirty-six months. Nothing is broken. The two numbers are measuring different time horizons.
Sales reps are usually compensated on bookings because bookings measure the thing they can control: closing contracts. Public companies are judged on revenue because that is the number on the income statement. The gap between the two is why some companies cap the amount of multi-year commitment they will accept, or discount it, to keep revenue growing in step with bookings.
A contract with a big one-time implementation fee produces a large booking. Under ASC 606, that implementation revenue is often recognized when the implementation is actually delivered, which can be months later and may require milestones. The booking lands immediately. The revenue trickles in. Teams that forget this surprise themselves every quarter.
A ramp deal has a different price in each year of a multi-year contract, usually starting lower and stepping up. ASC 606 generally requires revenue to be recognized evenly across the service term, not on the ramp schedule, which means early-year revenue can be higher than the invoice and later-year revenue lower. The booking is still TCV. Reconciliation requires both sides to see the same ramp.
A renewal signed early in the quarter inflates bookings for that period. The revenue stream continues uninterrupted because the service never stopped. The booking jump looks like growth. The revenue line stays flat. Boards that only look at bookings get excited about a timing artifact. Boards that only look at revenue miss the real demand signal. The honest view shows both.
Usage above a plan floor is typically not part of the booking at signing because the amount is not committed. The overage shows up as revenue in the period it is consumed, with no corresponding booking. A business with large usage overages will show revenue running ahead of bookings, which is a healthy signal if it is understood and a confusing one if it is not.
The practical fix for bookings-versus-revenue confusion is a shared contract record. The CRM owns the booking and the deal. The billing and general ledger systems own the revenue and the recognition schedule. Both sides read the same contract. The six cards below are the pattern Strkr customers use to keep sales output and accounting output reconcilable without a monthly spreadsheet war.
When a sales rep moves an opportunity to closed-won, the CRM captures the TCV, ACV, ARR, term length, start date, and billing cadence as structured fields on the deal. The booking is the TCV figure for the period the deal closed. Reporting the booking is a one-click filter on closed-won deals, not a spreadsheet exercise.
The contract metadata that drives revenue recognition, including term start, term end, ramp schedule, and performance obligations, is recorded against the deal and the account. Finance reads the same record. The CRM is not the recognition engine, but it holds the facts the recognition engine depends on, so the two systems agree on what was sold.
When the stage flips to closed-won, the deal data is handed to the billing system through an integration or an export, creating the customer, the subscription, and the invoice schedule. Finance then owns the revenue side. The CRM owns the deal and the booking. The handoff is explicit, which prevents the "did it get billed?" conversation that otherwise consumes a Friday afternoon.
Every expiring contract shows up on a renewal pipeline with the renewal date, the renewing amount, the owning customer success manager, and the risk level. The renewal is worked like any other deal. When it closes, a new booking is recorded in the renewal period. The revenue stream continues without interruption on the finance side.
When a customer adds seats, upgrades a tier, or buys an additional module mid-term, the expansion is tracked as its own deal on the existing account. When it closes, the expansion booking is recorded in the period. Finance picks up the amendment and adjusts the recognition schedule. Both numbers reflect the change on the right timeline.
At month end, both the bookings report from the CRM and the revenue report from the general ledger tie back to the same contract list. Any contract that appears in one and not the other is a flag. Any mismatch between TCV in the CRM and total contract value in billing is a flag. Reconciliation becomes a one-page diff instead of a week of forensic spreadsheets.
Strkr is a CRM that captures the booking at closed-won with structured contract fields, hands the data cleanly to the billing system, and reconciles back to the same contract list finance recognizes revenue against. Sales and finance work from the same facts, and the monthly reconciliation stops being a battle.
Bookings are the total value of a signed contract, captured once on the deal date. Revenue is the portion of that contract an accounting team is allowed to recognize in a given accounting period under ASC 606, typically spread evenly over the service term. Bookings measure sales output. Revenue measures earned, delivered value. The same contract produces one large booking at signing and a stream of smaller revenue entries over time.
Because they measure different events. A booking is a one-time event on the signing date equal to the full contract value. Revenue is recognized ratably as the service is delivered, usually over twelve, twenty-four, or thirty-six months. A prepaid multi-year deal signed in one month produces a large booking that month and only a small slice of revenue in the same period. Nothing is wrong. The two numbers describe different time horizons.
A booking is the full value of a signed contract on the day it closes. For a one-year subscription, the booking equals the annual contract value. For a multi-year subscription, the booking equals the total contract value for the full term. Bookings typically include the subscription portion plus any committed one-time items like implementation or training that are part of the signed agreement.
ASC 606 is the US accounting standard that governs when and how a business is allowed to recognize revenue from contracts with customers. It requires revenue to be recognized as performance obligations are satisfied, which for most subscription software means recognizing the subscription portion evenly across the service term. ASC 606 is the reason bookings and revenue almost never match in the same period.
Both, labelled clearly. Bookings or new ARR tells the board what the sales team closed in the period. Recognized revenue tells the board what the business actually earned in the period. Showing one without the other hides half the story. The board asks about both. Investors ask about both. Mature teams report both every month and never let one be mistaken for the other.
The CRM owns bookings because the booking is captured at the moment the deal closes, inside the sales workflow. The billing system owns invoicing and revenue recognition because those are triggered by the service start date and the recognition schedule, which run on an accounting cadence. Both systems must reconcile to the same contract list, but each one is the system of record for its own side of the number.
Yes. A quiet sales quarter with no new contracts but a healthy base of existing subscriptions will produce low bookings and continued revenue from contracts signed in prior periods. Usage overages, which are typically not booked at signing but recognized as revenue when consumed, can also push revenue above bookings in a period. Neither case is unhealthy on its own, but both deserve a note in the report.
Every opportunity carries TCV, ACV, ARR, term length, start date, and billing cadence as structured fields. When the deal moves to closed-won, the booking is captured in the period. The renewal pipeline keeps expiring contracts visible, and expansion deals are tracked as their own records on the existing account. Both sides of the number reconcile back to the same contract list, which keeps the sales and finance reports agreeing.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
