Bookings vs Revenue vs Billings: Definitions, Timing, HubSpot Records and Reconciliation

One signed contract produces three numbers, and each team that mistakes one for another makes a different error. A sales report built on bookings places a year of service in the month of signature, and a cash plan built on them expects at signature the money that invoices collect across the year. HubSpot's Billed vs. actual revenue report compares invoices with payments, so its actual revenue is cash collected rather than revenue earned.

This article defines bookings, billings and revenue and reconciles them in a HubSpot portal. It starts with the event that dates each number, the HubSpot record that holds it and the discrepancies those records produce. A sample contract followed month by month then leads to the reconciliation identities, the costs and returns of reconciling, a monthly procedure that ends on a single contract, and the limits of the method.

A booking is the value of a customer's commitment, recorded when the contract is signed. A billing is an amount invoiced, recorded on the invoice date. Revenue is the amount an entity recognises as it transfers promised goods or services, under IFRS 15 and ASC 606, its FASB counterpart. Deferred revenue, which both standards call a contract liability, is consideration received or due before the work is done. A contract asset is a right to consideration for transferred work that is conditional on something other than the passage of time, such as acceptance; a right awaiting only the passage of time is a receivable, and an unbilled receivable until invoiced.

Three Events and the Dates That Place Them

Only one of the three events is defined by an accounting standard: IFRS 15 recognises revenue "to depict the transfer of promised goods or services to the customer in an amount that reflects the consideration to which the entity expects to be entitled", and allocates a contract's transaction price to its performance obligations by relative standalone selling price.

Bookings and billings have no standard behind them: neither word occurs in Section A of ASU 2014-09, the update that created Topic 606. Each company writes its own bookings definition, so identical contracts can produce different bookings, and a definition becomes a defect only when it is unwritten or changes without notice.

Bookings, Billings and Revenue in HubSpot Records

HubSpot records two of the three numbers: bookings on deals and Revenue Hub contracts, and billings on invoices. None of the HubSpot documentation reviewed here describes recognising, deferring or allocating revenue. The guide to end-to-end revenue describes syncing invoices, credit memos and payments with QuickBooks, Xero or NetSuite, leaving recognised revenue in the ledger.

Report on revenue in HubSpot still assigns booked revenue to a created contract, committed revenue to an active one, billed revenue to a sent invoice and collected revenue to a paid one, and the revenue analytics suite defines Billed vs. actual revenue as "the sum amount billed vs. the sum amount paid". None of these is revenue as the standards define it.

In a portal without contracts, bookings are the Amount of closed-won deals dated by Close date, which HubSpot sets to the current date whenever a deal enters a closed-won stage, including a return from closed lost, unless that automation is off. Default deal amount, under Settings → Data Management → Objects → Deals → Setup, sets Amount to total contract value (TCV), annual contract value (ACV), annual recurring revenue (ARR), monthly recurring revenue (MRR) or manual entry. A change "will not retroactively update existing deals", so a portal that has changed the setting once holds its bookings in two definitions. HubSpot documents no property recording which calculation set an Amount.

The calculated TCV, ARR and MRR properties come from line items and do not take Amount into account, so they do not drift with the setting; ARR and MRR require Sales Hub Professional or Enterprise. A deal whose line items arrived by import or API keeps its old Amount. HubSpot defines ACV only as "the value of the deal over a 12-month period", without saying how it treats one-time charges.

Billings are invoices, whose default properties include Amount billed (pre-tax), Invoice Date, Due date and an Invoice Status whose Draft and Voided values bill nothing. A credit memo reduces the balance due on an open invoice.

Computing recognised revenue in HubSpot workflows would put revenue policy where finance cannot audit it, as the Sage Intacct revenue recognition article sets out. The forecast tool sums deal amounts by close date against forecastable revenue goals, so it forecasts bookings, which a revenue forecasting process must convert into billings and revenue before finance can use them.

Discrepancies and Their Mechanisms

Last quarter's bookings change after the quarter has closed. A closed-won deal moved to closed lost and back takes the current date as its Close date, and a line item edit saved with the amount update restates Amount; export the closed-won report at each month end as the record of the period.

HubSpot bookings disagree with the sum of TCV. Amount follows the Default deal amount setting in force when the line items were last saved, follows nothing under manual entry, and stays unchanged when line items arrive by import or API or are saved without updating the amount; step 2 of the monthly procedure lists every such deal.

A HubSpot revenue figure disagrees with the income statement. The Billed vs. actual revenue report sums amounts billed and amounts paid, both grouped by invoice due date, and the MRR waterfall reports recurring revenue "when it becomes effective", leaving out the one-time line item in HubSpot's example scenario. HubSpot documents no allocation by standalone selling price, so none matches recognised revenue except by coincidence; label each report by what it counts and take revenue from the ledger.

Evergreen subscriptions vanish from booked TCV. A Revenue Hub contract that renews until cancelled has no TCV or ACV, while the same line item on a deal with no term set carries a TCV of one year, so a TCV definition has to name the record that counts.

One Sample Contract, Month by Month

The contract below is sample data and describes no customer. Signed on 20 March 2026, it combines a twelve-month subscription from 1 April at $60,000, invoiced quarterly in advance at $15,000, with a $12,000 implementation; every invoice is due on receipt. The implementation is delivered in equal halves across April and May and invoiced on acceptance on 15 June; until acceptance, its delivered work is a contract asset. The implementation is assumed to be a distinct performance obligation satisfied over time, with line prices as standalone selling prices.

In HubSpot the subscription is a $15,000 line item billed quarterly with a term of four payments, and the implementation is a one-time charge. The documented calculations give a TCV of $72,000, an ARR of $60,000 and an MRR of $5,000, so the same deal books $72,000, $60,000 or $5,000 depending on Default deal amount.

Had the accountants judged the implementation a setup activity that transfers no service, paragraph 606-10-25-17 would exclude it from the performance obligations, spreading the $12,000 across the subscription's twelve months and giving April $6,000; no HubSpot value records that judgement.

Reconciliation Identities and Remaining Performance Obligations

Two identities connect the numbers. When bookings are counted at total contract value, bookings less cumulative billings is the unbilled remainder. Billings follow from revenue and three balances:

Billings = Revenue + change in deferred revenue − change in contract assets − change in unbilled receivables

May shows why the contract asset term belongs: the month bills nothing and recognises $11,000, deferred revenue falls by $4,000 and a $7,000 contract asset appears, so 0 = 11,000 − 4,000 − 7,000 − 0. Dropping that term returns $7,000 of billings for May and $5,000 for June, against actual billings of zero and $12,000. The error equals the change in the net contract asset, so it falls in each month that balance changes: May, when the asset appears, and June, when the implementation is invoiced.

Paragraph 606-10-45-1 of ASU 2014-09 presents each contract as one asset or one liability, so April's $6,000 of uninvoiced implementation is netted inside a $10,000 subscription liability. It presents unconditional rights separately as receivables, so revenue awaiting only an invoice and time, as with services billed monthly in arrears, is an unbilled receivable; the sample has none. Paragraph 45-2 records deferred revenue when payment is made or falls due. Example 38 records no gross receivable for an invoice issued before its due date, so on thirty-day terms the balance follows the due date; the sample's invoices are due on receipt.

Bookings meet the financial statements in one disclosure, the remaining performance obligation (RPO) of paragraph 606-10-50-13. For one contract it is the contract value less revenue recognised to date, or $40,000 for the sample at the end of July, being $30,000 unbilled and $10,000 deferred. RPO equals bookings less revenue only while the booking definition matches the transaction price, which paragraph 606-10-25-3 limits to the period of present enforceable rights, excluding years the customer can cancel freely.

Costs and Returns of Reconciling the Three Numbers

The reconciliation buys one account of a contract that sales, finance and a board read the same way: commission paid on a named number, cash planning on billings rather than signatures, and a dashboard revenue figure that traces to a ledger entry.

It costs line-item discipline on every deal, since the calculated properties exist only where line items do and a subscription line item with no term set is valued at one year, plus a monthly ledger extract and a named owner in finance. Contracts and their booked and committed reports need a Revenue Hub subscription and seat outside the beta that opens contracts to other subscriptions; the Revenue Hub article prices them.

The case is strongest for contracts of a year or longer, billed quarterly or annually, with separately priced services, where the three numbers stay far apart for months. It is weakest for monthly subscriptions billed monthly with no services, where each invoice equals that month's revenue and MRR serves as the single number.

Monthly Reconciliation Procedure

1. Write the bookings definition in one sentence naming the value counted (TCV, ACV or ARR), the date (Close date at signature) and whether renewals count. Put it in the bookings report's description, set Default deal amount to match, and note the date of the change.
2. Create a deal calculation property equal to Amount minus the property the definition names, under Settings → Properties → Deal properties → Create property, with Field type Calculation and Calculated property type Custom equation; it needs a Professional or Enterprise subscription. A closed-won deal of the month where that difference is not zero, or that has no line items, carries a typed, superseded or stale Amount and is corrected before reporting.
3. In Revenue → Invoices, use Advanced filters for Invoice Date in the month and Invoice Status of Open or Paid, export the view and sum Amount billed (pre-tax). Subtract credit memos dated in the month, excluding tax, to give billings.
4. Take from the ledger the month's recognised revenue and the opening and closing deferred revenue, contract asset and unbilled receivable balances, for the same customers.
5. Compare billings less revenue with the change in deferred revenue less the changes in contract assets and unbilled receivables. A residual equal to the change in advance invoices neither due nor paid reflects the due-date rule; any other residual is an invoice missing from one system, an unsynced credit memo or revenue posted against the wrong customer.
6. Verify on one contract: recompute bookings from its line items, billings from its invoices and revenue from the ledger schedule. Cumulative billings less cumulative revenue should equal deferred revenue less contract asset and unbilled receivable, and, with bookings at total contract value, bookings less cumulative billings should equal the unbilled remainder. A reconciliation that balances in aggregate and fails on one contract contains offsetting errors.

Boundaries of This Reference

This reference does not determine performance obligations, standalone selling prices or variable consideration for any contract, which are judgements for a firm's accountants; the sample states its assumptions instead. Usage-based billing, multi-currency contracts and forecasting are outside it, and the bridge from a bookings forecast to a revenue forecast is set out in aligning the sales and finance forecasts.

HubSpot behaviour is as documented in October 2026, when directly created contracts, contract billing schedules and revenue reporting from contracts were partly in beta. The identities hold by construction once every balance is included, and they cannot show whether a ledger applies the standard correctly, which is a question for an audit.

In Summary

A signature dates a booking, an invoice dates a billing and delivery dates revenue, so one contract reaches the three figures in different months. Only revenue is governed by a standard, ASC 606 and IFRS 15, and a bookings figure is only as stable as its written definition. HubSpot holds bookings on deals and contracts and billings on invoices, records no recognised revenue, and still calls booked, committed, billed and collected amounts revenue in its reports. Amount follows the Default deal amount setting in force at the last line-item save, and changing the setting restates nothing.

The three reconcile through the balance sheet, where billings equal revenue plus the change in deferred revenue, minus the changes in contract assets and unbilled receivables. Without the contract asset term, the sample's May, which issued no invoice, would report $7,000 of billings. The monthly reconciliation therefore starts from one written sentence, the bookings definition, and ends on one contract recomputed three ways.