Bookings vs billings vs revenue vs cash

Bookings, billings, recognised revenue and cash receipts answer four different business questions. Bookings track confirmed sales, billings track invoicing, recognised revenue follows the applicable accounting policy, and cash receipts track money received. A useful business dashboard names and calculates each measure separately before combining data from Tally, a sales system or spreadsheets.

When the founder, sales team and accounts team report different “revenue” figures, check the definition as well as the data. All three reports might be internally accurate while measuring different events. They might also contain genuine errors. A shared definition and reconciliation process help distinguish the two.

What each dashboard metric should tell you

Bookings: what sales activity was confirmed? Define what qualifies as a booking, which confirmation date counts and whether the headline is gross bookings or bookings adjusted for cancellations. A quotation or unconfirmed opportunity should not slip into the total unless the metric explicitly measures pipeline.

Net billings: what did we invoice, after specified adjustments? A common operational definition is invoices dated in the period less credit notes dated in the period, on a consistent tax basis. This measures billing activity. It does not automatically establish when revenue was earned.

Recognised revenue: what belongs in the accounting period? Use the applicable accounting framework and your finance-approved policy. The recognition date may differ from the booking, invoice and payment dates.

Customer cash receipts: what money arrived from customers? Define the receipt date and treatment of refunds, payment fees and allocations. Gross receipts and receipts net of refunds are different measures. A bank account balance also includes other movements and should not be labelled customer cash receipts.

The accounting distinction matters. ICAI's AS 9 addresses service performance and uncertainty; it also specifies commission revenue for an agency relationship. IFRS 15 links revenue to satisfying contractual performance obligations, which may happen over time or at a point in time. The applicable framework and contract determine the treatment, rather than a dashboard setting. ICAI AS 9, IFRS Foundation's IFRS 15 overview.

A worked example: four September numbers

Consider a hypothetical Mumbai travel business using a booking system and Tally. The following example illustrates metric differences, not an accounting policy for travel businesses.

Assume that, for these particular packages, the business acts as principal; all amounts exclude tax; no foreign-exchange differences, payment fees or refunds arise; and all relevant services are fully performed on the stated travel dates. Assume finance has approved recognising the specified cancellation charge in September, with the relevant recognition and collectability conditions satisfied. A business acting as agent may instead recognise its commission; confirm the treatment before applying these figures.

• Booking A: Goa package, ₹1,40,000. Confirmed 28 August, paid in full 1 September, invoiced 2 September, services completed 20 September.
• Booking B: Dubai package, ₹3,20,000. Confirmed and invoiced 15 September, ₹1,60,000 advance received 16 September, services to be provided in November.
• Booking C: Conference booking, ₹2,00,000. Confirmed and invoiced 10 September, cancelled 25 September before any payment. An ₹1,60,000 credit note leaves a ₹40,000 cancellation charge payable.
• Booking D: Kerala package, ₹90,000. Confirmed and services completed in September, invoiced 30 September, paid 6 October.

The September dashboard now shows:

1. Gross bookings confirmed: ₹6,10,000. B + C + D = ₹3,20,000 + ₹2,00,000 + ₹90,000. This explicitly defined gross measure still includes C's original booking value; display cancellations separately if needed.
2. Net billings: ₹5,90,000. All four invoices total ₹7,50,000, less C's ₹1,60,000 credit note.
3. Recognised revenue under the stated assumptions: ₹2,70,000. A + D + C's approved cancellation charge = ₹1,40,000 + ₹90,000 + ₹40,000. B's November services are excluded from this illustrative September revenue total.
4. Customer cash receipts: ₹3,00,000. A's ₹1,40,000 payment plus B's ₹1,60,000 advance. C remains unpaid; D's receipt belongs to October.

The ₹40,000 cancellation charge is included in this example's revenue but has not been collected. That distinction would disappear if the dashboard called both measures “sales”.

Write the metric definition before the calculation

For every headline number, record:

• Name and purpose: the specific question it answers, such as “Net billings excluding tax”.
• Source records: the system, document types and status required for inclusion.
• Date basis: confirmation, invoice, credit-note, recognition or receipt date; define the reporting time zone where relevant.
• Adjustments: cancellations, refunds, credit notes, corrections and the periods they affect.
• Tax and currency basis: included or excluded taxes, reporting currency and any conversion rule approved by finance.
• Entity and scope: which business, branch or product is included and which transactions are excluded.
• Owner and version: who approves the definition and when a change takes effect.
• Reconciliation: the independent record or approved schedule used to check the result.

Keep the definition next to the report, with a visible last-refresh time. Otherwise the finance team may compare a closed month with a dashboard that still lacks the final entries.

Reconcile each metric to the right evidence

Do not force all four measures to equal a single sales ledger total. Use checks suited to each one:

• Bookings: match the dashboard to confirmed booking records and its separate cancellation log.
• Net billings: match invoice and credit-note registers on the same date and tax basis. Check whether the source report already nets credit notes so they are not deducted twice.
• Recognised revenue: match the accounting revenue report and the finance-approved recognition schedules or journals supporting it.
• Cash receipts: match customer receipt records to bank or payment-provider reconciliation, explaining timing, fees and unallocated amounts as applicable.

Run the comparison for a closed month and list differences by document identifier. Classify missing imports, duplicates, date mismatches, mapping errors and approved accounting adjustments. Correct the source or calculation and rerun the check. Avoid an unexplained manual override that makes this month's total agree while hiding the underlying problem.

When a custom Tally dashboard is useful

If a standard accounting report already answers the question, use it. A custom dashboard becomes useful when management needs to compare sales activity, delivery and collections across systems, or when staff repeatedly rebuild the same reconciliation in Excel or Google Sheets.

An implementation scope should identify the source documents, supported connection method, refresh schedule, permission limits and acceptance checks. Ask the provider to trace one headline figure back to the documents behind it and show what happens when a source stops updating.

AI questions can then sit on top of approved definitions. An answer to “What was September revenue?” should identify the recognised-revenue measure, period and source. If the user's meaning is ambiguous, the assistant should clarify or show the separately named measures. Fluent wording does not replace a finance-approved calculation.

Bring one disputed metric into the scope

SolvTree's AI dashboard work includes connecting business reporting to sources such as Tally, Excel and Google Sheets. The useful starting point is one decision the dashboard should support and one metric the team can reconcile.

If conflicting figures keep delaying your reviews, talk to SolvTree about the reports that disagree. Identify what each report currently counts and which source the finance owner approves. That is a concrete basis for deciding whether better definitions, a small integration or a custom dashboard is needed.