Bookings vs Revenue: A Guide for Tour Operators

A platform can report $186.1 billion in gross travel bookings and $26.9 billion in revenue in the same year. Booking Holdings did exactly that in 2025, producing a revenue-to-gross-bookings conversion of roughly 14% at platform level, based on its published figures (Booking Holdings factsheet). That gap isn't an accounting curiosity. It shows why tour operators can't treat booking volume as a stand-in for cash, earned income, or profit.

For a multi-day tour operator, the gap is even harder to read. A traveler may sign up months before departure, pay a deposit, complete an installment, cancel under a refund policy, or book through an OTA that keeps a commission. A finance flow has to separate each of those events so the operator can see what customers committed to, what money actually arrived, what remains owed, and what the business has earned.

Understanding Bookings vs Revenue in Tour Operations

Bookings and revenue answer different questions. Bookings measure committed contract value at the point of sale, while revenue measures the amount earned as the operator delivers the trip. Accounting guidance treats revenue as earned over the fulfillment period rather than recognizing the full contract value the moment a customer signs, a distinction laid out in this explainer on bookings versus revenue.

That matters immediately for tours. A seven-day itinerary booked in advance creates demand and a delivery obligation, but the booking doesn't mean the operator has earned the full amount on that day. Departure timing, included services, deposits, cancellations, and the treatment of refunds all shape the path from a reservation to recognized income.

Digital distribution widens the gap in practice. A checkout or an OTA can capture a reservation months before the traveler shows up, so the booking line moves long before any trip is delivered. Revenue still waits on service delivery and the operator's accounting treatment, however fast the reservation was captured.

Bookings are a demand signal

Bookings answer forward-looking questions:

• Capacity: Which departures are filling, and where are spaces still available?
• Staffing: How many guides, drivers, coordinators, or suppliers will the itinerary require?
• Collections: Which travelers owe a balance, and when should payment reminders run?
• Purchasing: Which confirmed trips justify deposits to accommodation and activity suppliers?

A booking report can look strong while the income statement stays modest. That isn't automatically a problem. It usually means the operator has sold future departures that haven't run yet.

Revenue reflects completed performance

Revenue belongs to the period in which the operator earns it. A trip that begins later may create a signed commitment today, but the business still has to provide transportation, accommodation coordination, guiding, activities, and traveler support before the commercial obligation is complete.

Bookings also aren't profit. Revenue still has to absorb payment processing, OTA commissions, refunds, supplier costs, payroll, marketing, and overhead. Anyone building a finance dashboard should keep that gap between revenue and profit visible rather than collapsing it into one number.

Practical rule: Use bookings to plan what the business must deliver. Use recognized revenue to assess what the business has delivered. Use profit to judge whether delivery created value.

How Samba's Finance Flow Affects Your Bottom Line

Payment flow changes what each booking report means. The same traveler and itinerary can produce different cash outcomes depending on whether the customer pays through a direct checkout or an intermediary.

Samba's model is Bring Your Own Stripe. The operator connects its own Stripe account, and payouts land directly in its bank account rather than sitting with Samba. The platform charges 2% per booking, with no setup fees or contracts, and the first $10,000 in bookings is fee-free, according to the publisher's product information. Because the charge is tied to booking value, the ledger should separate gross bookings, Stripe processing costs, Samba's service fee, refunds, and recognized revenue.

A $1,000 booking shows the difference. A 2% Samba fee is $20 once the fee-free allowance is used. An OTA commission at 20% is $200; at 30% it is $300. OTA commissions for tour and activity operators commonly run 15% to 30% of the booking value. Payment processing and marketing costs still need separate treatment, but these deductions change the cash available before any trip-delivery cost is paid.

Direct flow and intermediary flow

Settlement confirms that money moved. It doesn't prove the operator has completed the trip obligation, so a Stripe payout should not automatically become reported revenue.

What works in practice

Track gross booking value, cash collected, platform or channel deductions, refunds, remaining balance, and recognized revenue as separate fields. Samba's finance views bring bookings, collections, upcoming balances, transactions, and Stripe payout tracking into one place, but the accounting system still determines the operator's formal revenue treatment.

Multi-day staging makes timing harder. A traveler may pay a deposit before departure, an installment during the planning period, and the final balance shortly before delivery. Cash can rise well before the related service is recognized, while a refund issued after cancellation can reduce cash in a different period from the original booking.

Channel comparisons also fail when their bases differ. An operator who mixes OTA net remittances with direct gross bookings will consistently overstate direct-channel performance on commission-heavy itineraries. A $1,000 direct booking and an OTA booking with a 20% commission are not equivalent reporting inputs: the direct figure is before deductions, while the OTA receipt has already lost $200 to distribution. Reports should present gross demand, deductions, net cash, and recognized revenue on the same basis before management touches pricing, marketing, or sales priorities.

Navigating Deposits, Staged Payments, and Cancellations

A multi-day booking usually passes through several financial states. The reservation is created, a deposit is collected, one or more installments arrive, the final balance comes due, and the trip is eventually delivered or canceled. Each state moves cash and reporting differently.

The cleanest way to manage the sequence is to track the booking lifecycle rather than forcing every event into a single "revenue" column.

The booking lifecycle

1. Reservation created: The operator records the customer's commitment and the total contract value. This is the booking signal, even if the departure is months away.
2. Deposit received: Cash has been collected, but the operator may still owe the future service. Depending on the contract and accounting treatment, the amount may stay unearned until delivery.
3. Installment received: The balance sheet and collection schedule change, but payment arrival doesn't mean the related tour service has been earned.
4. Trip delivered: Revenue recognition follows the service performed and the applicable accounting policy. For a staged itinerary, the operator should document how fulfillment is assessed.
5. Cancellation or refund: The operator reverses, retains, or adjusts amounts according to the contract terms and accounting treatment. The booking report should preserve the original reservation and the cancellation event rather than deleting history.

Samba supports deposit and installment schedules, automated reminders, card retries, invoices, receipts, credit notes, and refunds. Each schedule should line up with the written terms offered to travelers. The deposit schedule guidance helps teams structure those payment milestones without confusing collection timing with earned income.

Deposits create a timing question

A non-refundable deposit can create cash before the trip operates. Some travel-industry treatments take a non-refundable deposit straight to profit and loss at booking; other arrangements require amounts received in advance to stay deferred until the service obligation is fulfilled. The correct treatment depends on the contract, the services promised, and the operator's accounting policy, as set out in this travel-industry revenue recognition overview.

So a finance team shouldn't apply one rule to every booking. A deposit retained after a cancellation may be treated differently from a deposit applied to a trip that later operates. Refunds also need their own audit trail, because the booking value, cash collected, and recognized revenue can each change on a different date.

Cash received is a liquidity event. Revenue recognized is an earning event. The two can happen together, but a multi-day trip often separates them.

Build schedules around the service

For every departure, keep the signed terms, payment schedule, cancellation rule, refund record, and delivery dates. A finance review can then answer three separate questions: what did the traveler promise to pay, what has the traveler paid, and what service has the operator earned?

That separation prevents a common forecasting mistake. A large deposit balance can make the bank account look healthy while supplier commitments and future delivery costs stay outstanding. Cash forecasting has to include both incoming installments and the costs required to fulfill the booked departures.

Common Reporting Pitfalls and Reconciliation Steps

The most persistent errors show up when teams compare records created at different moments. A booking date, payment date, Stripe payout date, refund date, and service-delivery date can all belong to the same reservation, but they don't describe the same financial event.

Three reconciliation traps cause most of the confusion.

Trap one, booking date versus payout date

A reservation can be created on one date, the card charged later, and Stripe can settle the money into the bank after that. Compare daily bookings with daily bank deposits and the reports won't match, even when every transaction is correct.

Fix: Reconcile by transaction identifier and keep separate columns for booking creation, payment capture, payout settlement, processing fee, and net bank receipt. The bank statement validates the payout; it doesn't replace the transaction-level record.

Trap two, gross value versus net proceeds

An OTA may report the traveler's gross booking while remitting a reduced amount after commission. A direct Stripe payment can also settle net of processing costs. Comparing either amount directly with recognized revenue distorts the margin view.

Fix: Start with the traveler's gross contract value, then record each deduction as its own line. OTA commissions, Samba service fees, Stripe costs, refunds, and credit notes should stay visible rather than being buried in a single net figure.

Trap three, refund date versus revenue period

A refunded booking can stay in a historical booking report while the related revenue needs an adjustment. Remove the reservation from the booking table and you lose the original demand record. Leave revenue untouched and the income statement overstates what the operator ultimately earned.

Fix: Keep the original booking, add the cancellation and refund events, and post the accounting adjustment in the period required by the operator's policy. Teams that need a refresher on accrual entries for finance teams can use that resource to structure the supporting entries.

A practical monthly close ties three records together:

• Operational record: Booking, traveler, departure, status, and cancellation details.
• Payment record: Charge, refund, fee, payout, and settlement information.
• Accounting record: Earned revenue, deferred amounts, receivables, and adjustments.

Samba's payment reconciliation workflow connects booking records with payment activity. The key is ownership. One person should investigate exceptions, another should approve material adjustments, and the final report should preserve the evidence used to clear each mismatch.

Direct Bookings vs Intermediary Revenue Analysis

Average revenue per booking usually differs by channel, and the direction is predictable. A direct booking keeps the full ticket minus payment and marketing costs, while the same trip sold through an intermediary arrives already reduced by commission. Run the earlier $1,000 example across a month of mixed channels and the per-booking gap between direct and OTA sales isn't a rounding error—it's the commission line, compounded. Channel volume alone can't explain financial performance, because two bookings of equal face value can settle at very different net amounts.

Direct bookings usually preserve the customer relationship and avoid marketplace commissions. OTAs and wholesalers can still produce demand that a small operator would struggle to reach on its own. The practical question is which channel converts bookings into the strongest realized revenue and margin after distribution costs, refunds, payment costs, and marketing spend.

Compare economics on a consistent basis

Use the same calculation for every channel:

1. Gross booking value.
2. Amount collected.
3. Channel commission or platform fee.
4. Payment and acquisition costs.
5. Refunds and credits.
6. Recognized revenue.
7. Contribution after trip-specific delivery costs.

OTA commissions commonly fall between 15% and 30% per booking. Direct sales aren't cost-free either: payment processing, marketing, staff time, and customer support all reduce the amount retained. Comparing channels on gross bookings hides those differences, while comparing only payouts can hide refunds or future service obligations.

Multi-day trips make the gap harder to read. A booking may be created and partly paid in one period, receive staged payments later, and become earned revenue only as the trip is delivered under the operator's policy. A high booking total can sit alongside limited current cash or recognized income.

Refund timing adds another distortion. Keep the original demand record, then connect cancellations, refunds, and accounting adjustments to it. Delete the booking and you lose channel history; leave revenue unchanged and you overstate what the operator earned.

Direct performance also depends on customer value. A shorter direct itinerary with fewer extras can produce less realized revenue than a larger intermediary booking. A direct traveler is often easier to upsell, support, and retain, because the operator owns the relationship.

Samba's OTA versus direct booking guide helps teams weigh that trade-off. Intermediaries earn their place when they add reachable demand. The reporting failure happens when volume is accepted without measuring commission, payout timing, refunds, and the margin left after delivery costs.

Best Practices for Accurate Financial Management

A reliable weekly review separates demand, cash, earned income, and margin. Operators don't need a complicated dashboard, but they do need consistent definitions and transaction-level evidence.

• Review new bookings: Check gross contract value by departure and channel. Flag cancellations and changes rather than deleting history.
• Review collections: Match deposits, installments, failed cards, refunds, and upcoming balances against the payment system and bank activity.
• Review earned revenue: Apply the operator's documented recognition policy to trips delivered during the period. Keep future service amounts separate.
• Review channel deductions: Track OTA commissions, Samba fees, Stripe costs, marketing spend, and credits as distinct items.
• Review exceptions: Investigate any booking with a missing payment, unmatched payout, overdue balance, refund, or status conflict.
• Review forecast risk: Compare confirmed departures with the cash required for suppliers, staffing, and delivery.

Samba can centralize online checkout, deposits, installment schedules, traveler data, departures, invoices, refunds, and Stripe-connected finance records. Used alongside an accounting system, it gives operators a practical place to reconcile the operational and payment sides of the bookings-versus-revenue relationship.

The weekly habit matters more than a good-looking report. A clean reconciliation makes cash forecasting more credible, exposes weak collection processes early, and gives management a defensible basis for channel and pricing decisions.

Samba connects direct booking pages and widgets with deposits, installments, traveler records, departures, refunds, and Stripe-linked payment tracking, helping tour operators keep operational and financial records aligned. Visit Samba to see how the platform can support clearer bookings, collections, and revenue workflows.