Bookings measure an explicitly defined commitment event, revenue follows the applicable recognition policy, and cash collections measure receipts. They can differ in amount and timing. Keep separate formulas, periods and source records, and reconcile differences rather than labelling all three totals sales.
Name the event and the amount being counted
Start with three separate questions. What value of commitments was accepted? What revenue belongs to the period under the organisation's approved policy? What cash was received? Each needs an event date, eligibility rule and amount basis. Specify cancellations, taxes, currency conversion and contract modifications rather than assuming that a signed document, invoice and bank receipt represent interchangeable evidence.
Bookings is a management definition that can vary. State whether it means full contract value, committed minimum value or another measure, and whether renewable options are excluded. Revenue recognition requires the relevant accounting policy and facts about obligations, rather than a shortcut based only on billing. Cash collections need a receipt or settlement definition, including the treatment of fees and money that has not yet cleared.
Keep contract, invoice and receipt relationships
Retain identifiers linking commitments to invoices and receipts. One annual commitment may generate four invoices, and one receipt may settle several invoices. Avoid duplicating the full contract amount on every joined receipt row. Reconcile at the relevant grain before aggregating. Where allocation is necessary, make the rule explicit and retain any unapplied receipt as a separate status rather than guessing the customer or period.
Build timing bridges using opening and closing balances where the data supports them. A receipt this month may settle an earlier invoice; a commitment this month may not begin service until later. The purpose of the bridge is to explain identified differences, not manufacture equality. Keep unknown allocations and disputed contracts visible so they are not quietly absorbed into a convenient reconciling category.
Use each measure for the decision it supports
Bookings may inform future workload, revenue may support period performance reporting, and collections may inform liquidity. A dashboard can present all three if their labels and definitions remain clear. Do not call a collections increase recurring revenue growth without checking what customers paid for and which event periods the receipts represent. Compare the same measure over time using stable definitions and equivalent source maturity.
The IFRS 15 page is further reading for revenue-recognition context. It does not define the fictional bookings metric below, and the arithmetic is deliberately simplified. For actual financial reporting, the approved policy determines treatment of the real contracts. A practical metric card should identify that policy owner and distinguish a management planning view from amounts prepared for formal financial statements.
For cancellations, preserve the original commitment and a separate dated reversal under the bookings rule. Overwriting the original contract value can make an earlier published total impossible to reproduce and hide whether a change reflects new demand or withdrawn commitments.
Fictional annual contract: one commitment, several clocks
A fictional scenario to explain the method, not a customer result or a market benchmark.
A fictional service business signs a 12,000-unit annual contract on 1 January. For its internal bookings metric, it counts the committed 12,000 on the signing date. The scenario assumes service is provided evenly across twelve months and an approved policy yields 1,000 of revenue in January. The customer is invoiced 3,000 for the first quarter but does not pay until February.
January therefore shows 12,000 bookings, 1,000 revenue and zero cash collected for this contract. February includes the 3,000 receipt, while the simplified monthly revenue remains 1,000. Counting the receipt as February bookings would duplicate the commitment, and treating it all as February service would change the question.
The example excludes taxes, modifications and other contracts to isolate timing. It demonstrates why different totals can be legitimate; it does not establish the recognition outcome for a real contract. Source links provide background, while every contract and amount here is fictional.
TAKE THIS INTO YOUR NEXT CONVERSATION
A practical next-step checklist.
- Define commitment, recognition and receipt events.
- Keep amount bases and exclusions explicit.
- Preserve contract-to-invoice-to-receipt links.
- Explain timing differences without forced agreement.
Common questions.
Does invoicing always create revenue?
No. Billing and recognition can follow different timing. Apply the relevant approved policy to the actual obligations and facts.
Can bookings be compared between businesses?
Only after checking definitions such as total contract value, committed minimums, cancellation treatment and included taxes.
Further reading & source context.
These primary references provide background. They are not evidence for the fictional example above and do not endorse Accuralytix.
Found an error or a missing qualification? Send an editorial correction.
Check my data readiness.
Use a practical tool to turn this idea into a clearer starting point.
Check my data readiness