A clean bank balance doesn't mean your books are right. Here's how to run a monthly close that proves what the cash relates to, what's still owed, and what doesn't tie back.
At the end of the month, the bank balance can look reassuring while the books are wrong. A tour operator might have a strong cash month because guests paid deposits for departures that won't run for weeks or months, while card payouts arrived in neat batches and channel remittances landed net of commissions and processing. None of that means the month was profitable, settled, or even fully understood.
That's why learning how to audit financial records matters more in a multi-day tour business than in a simpler retail model. The point of a monthly close isn't to admire the cash position. It's to prove what the cash relates to, what still needs to be delivered, what's been refunded, and what doesn't tie back cleanly to a booking.
A standard month-end glance at sales and bank activity misses the two places owner-operators usually get trapped.
The first is batched payouts. Stripe or another processor sends a settlement that combines multiple bookings, less fees, less refunds, sometimes less disputes. That payout will never equal one booking value, so anyone trying to match it one by one usually gives up halfway through.
The second is money collected before travel happens. If a guest pays today for a departure months away, that cash is in the account, but the trip hasn't been delivered. Treating that money as current revenue can make the month look healthier than it really is. What sits in the account may still represent an obligation to carry guests later or refund them under the booking terms.
Modern audit practice runs on evidence, not on management's word for it. The principle hardened after fraud scandals like McKesson & Robbins, and later standards settled the point: an auditor needs enough evidence, of high enough quality, rather than an assertion, as these audit evidence standards lay out.
For a tour operator, that principle is practical, not academic. If the booking record says one thing, the payout report says another, and the bank statement says something else again, the close isn't finished.
Practical rule: A clean close proves each material movement can be traced from booking, to payment, to payout, to bank, and back again.
The Jumpstart Partners audit guide covers the general method, but tour businesses have to adapt it to deposits, installments, refunds, and departures that sit in the future.
For this kind of business, a real close answers seven plain questions:
That's the version of an audit that helps an owner sleep. Not because every line is perfect, but because the records can stand up to a challenge.
A monthly close works best when it happens on a fixed date and follows the same order every time. If it slips until “when things calm down,” it usually becomes a memory exercise, and memory is weak audit evidence.
For most operators, monthly is the right cadence. Then, at season end, it's worth doing a harder pass through liabilities, supplier costs, old credits, and any departure that changed dates or headcount during the year.
Before testing anything, define exactly what set of records the close covers. Independent sampling guidance says the objective, population, sampling unit, tolerable error, expected error, confidence level, and population variability should be set before testing begins, and it recommends a minimum statistical sample size of 30 items for each population or sub-population when a conclusion is needed, as described in the EEA sampling guidance.
That matters even for a small operator. If the goal is to test refunds, then the population is all refunds in the month, not a few memorable ones. If the goal is to check deposit tax treatment, then the population is bookings with staged payments, not whichever files are easiest to open.
The close runs faster when the source material is consistent.
Operators dealing with card and settlement complexity usually find it helps to keep a process note beside the reports. Samba's explanation of payment reconciliation for tour operators is useful because it reflects the issue: settlements arrive aggregated, on different dates, and net of costs.
One of the harder parts of how to audit financial records is that every system tells time differently. The booking might be created on one date, the charge captured on another, the payout sent later, and the bank credit posted later again.
Independent audit guidance on documentation gaps points to recurring problems such as missing invoices, partial records, vague narration fields, and unreconciled balances between books and external statements in multi-system setups, as noted in this review of common audit documentation gaps.
Keep one rule for timing. Close by transaction date inside each source system, then document any cutoff items that crossed into the bank after month end.
A season-end pass should go further than the monthly routine. That's when to revisit old open credits, re-check departures pushed into a new season, and challenge any supplier cost that was accrued loosely during busy months.
The hardest step usually comes first. That's a good reason to keep it first.
Put the payout report and booking ledger side by side. Don't try to match one payout to one booking, because it won't.
A single payout often includes multiple captured payments, less processor fees, less refunded amounts, and sometimes less dispute adjustments. The right method is to filter the booking ledger to all transactions included in that payout period, total the gross customer payments, then subtract the listed fees and any refund components until the payout figure ties.
What works is matching by batch contents. What doesn't work is scanning the bank statement and trying to guess which booking “looks close.”
This is one place a booking platform earns its keep. A per-booking ledger of payments, installments, refunds, and disputes, with transaction and payout tracking through Stripe, turns the step into a comparison between records rather than a rebuild from inbox receipts. Samba is built this way.
Channel money should be checked against bookings confirmed through that channel, not against direct sales totals.
The remittance usually arrives net of commission and net of the channel's own payment handling. So the test is simple in principle: confirm the guest and departure existed, confirm the seat count and gross booking amount, then confirm the deductions shown in the remittance statement explain the net amount received.
A useful working layout is:
Mixed direct and OTA trade usually causes confusion. When both sit in one booking record with payment status attached, the operator is comparing reports instead of rebuilding the month from email confirmations.
This is the step that changes how an operator reads the month.
Money taken for a trip that hasn't happened yet is a liability, not revenue. If those deposits are counted as current earned income, the books can show a strong month that is really a stack of future obligations.
The practical check is to pull all departures not yet run, list the cash collected against each, and separate that balance from revenue earned on trips already delivered. If the departure moves, cancels, or partially refunds later, that distinction matters immediately.
A profitable-looking month can be mostly prepayments for work still owed to guests.
Generic finance advice often misses this because it assumes delivery and payment happen close together. Multi-day tours don't work that way.
Every refund should have a trail. Every credit note should point back to the original invoice. Any orphan should be investigated.
This check is less about suspicion than about completeness. Refunds can be issued in one system while the credit note sits elsewhere, or a booking might be adjusted without the paperwork catching up. Standardizing how refunds get processed and recorded closes most of that gap before it opens.
If a refund exists with no related invoice history, or a credit note exists with no real underlying reduction, stop there and resolve it before closing the month.
Forcing every adjustment back to its original sale is one of the fastest ways to clear up a confusing month, and this external audit primer makes the same case.
This error hides in plain sight. A booking can apply one tax treatment to the deposit, then a different one across the installment schedule that follows.
The only reliable way to catch it is to read the booking end to end. Start with the first customer-facing amount, then review each later payment document and make sure the treatment stayed consistent across the same booking logic.
This article avoids jurisdiction-specific advice for a reason. The test here isn't “what rate should apply?” The test is “was the same treatment applied consistently to the same booking over time?”
This is not just a collections task. It's an audit task because near-term departures with unpaid balances can expose weak records, broken reminders, failed retries, or exceptions granted informally by staff.
Filter departures inside your cancellation window and review every unpaid balance. Confirm whether the guest has an agreed arrangement, whether payment attempts failed, and whether the booking status still reflects commercial reality.
A clean report here tells an accountant something useful. It shows that receivables close to delivery have been actively reviewed, not left to surprise the business later.
Supplier overbilling usually hides where operators are tired. Guides, accommodation, transport, permits, and meal invoices often arrive after the operational rush, and by then the temptation is to approve them if they look familiar.
Instead, tie each supplier invoice to a departure that ran and compare headcount, dates, and agreed terms. If the departure changed size or dates, the invoice should reflect that.
What works is checking invoices against the operated trip file. What doesn't work is approving from memory.
Some errors don't show up when reviewing the month in summary. They only appear when one booking is read all the way through, from first deposit to final adjustment.
That's especially true with staged payments, refunds, and price changes. A booking can look fine at the top line while the documents underneath tell a different story.
The best approach is to review the full payment story in order. That means booking confirmation, deposit invoice, later installment invoices, any refund, any credit note, and final balance outcome.
UK VAT guidance says a credit note is valid only when it reflects a genuine mistake, overcharge, or agreed reduction in the value of the supply, and it must be issued within 14 days of the refund payment to the customer, according to VAT Notice 700. HMRC also says the document must include an identifying number, issue date, supplier details, customer details, the original VAT invoice number and date, a description of the supply, the amount of price reduction excluding VAT, and the VAT rate and amount credited, as listed in the HMRC internal manual on credit note requirements.
| Check | What to Verify | Where to Find It |
|---|---|---|
| Deposit document | The first invoice matches the booking amount and treatment applied at sale | Booking record and invoice log |
| Later installments | The same booking logic was carried through each later payment | Booking payment history |
| Refund event | The refunded amount appears in both payment records and customer paperwork | Payment ledger and refund record |
| Credit note | The credit note ties to a genuine reduction and references the original invoice | Credit note register |
| Final balance | The booking closes with no unexplained residual amount | Booking ledger and balances report |
Travel businesses also need to keep non-cash adjustments visible. TICO's trust accounting guidance says travel vouchers issued to customers must be included in trust reconciliations and kept in the books and records, and that documentation and an audit trail for customer refunds must be maintained in the trust accounting guidelines.
That matters because a voucher can otherwise disappear into operational notes while the accounting side still looks unresolved.
A practical way to support this check is a per-booking ledger that shows payments, installments, refunds, and disputes together with the related documents. If an operator wants examples of document structure, Samba's guide to credit note templates for tour operators is useful for seeing what needs to be present in the paperwork.
Useful lens: Don't ask whether a booking “looks right.” Ask whether every document in its timeline agrees with the one before it.
For broader small-business context on control discipline, this piece on how to reduce tax risks for SMEs is a helpful companion, especially for operators who manage much of the paperwork themselves.
Your accountant doesn't need every operational detail. They need the close to be supportable.
That means handing over the reconciled pieces that explain the month: payout tie-outs, channel remittance matches, the liability schedule for departures not yet run, matched invoices and credit notes, and a clean list of unresolved items that still need judgement.
A good month-end pack is usually short and specific:
If software assisted the record creation or review, keep the documentation proportionate. Recent UK guidance on AI tools in audit makes the same point: the audit file should carry proportionate documentation of how the tool was used, as covered in the ICAEW summary of the FRC AI audit guidance.
Not every difference deserves a lost afternoon. Some do.
Chase it when the discrepancy suggests one of these:
Write it off, with documentation, when the amount is small, the cause is understood, and the time to prove it would exceed the value of resolving it more precisely. The important part is consistency. Don't investigate one tiny fee variance for an hour and ignore a refund with no supporting credit note.
Internal controls matter here for more than neatness. In a study of U.S. public-company audit data for fiscal years ending between November 15, 2004 and December 31, 2007, a material weakness in internal control made a firm-year 1.24 percentage points more likely to have a future fraud revelation, and in a matched-pairs analysis the increase was 1.54 percentage points, according to the AAA study on internal control weakness and fraud. Small tour operators aren't public companies, but the lesson still travels well. Weak controls make bad records easier to hide inside normal month-end noise.
It is the last business day of the month. Two Stripe payouts hit the bank, three future departures still hold guest deposits, and one refunded booking was partly rebooked onto a new date. If those records are current, the close is routine. If they are not, you end up rebuilding the month from inbox searches and staff memory.
Audit-ready books come from habits that protect the trail while the work is happening. For tour operators, that means treating money for trips not yet run as a liability until the departure is delivered, and accepting that a batched net payout will rarely line up with one booking. Those are the two spots where generic audit advice usually falls short.
A workable routine usually includes:
One control is easy to underestimate. Keep a clear history whenever staff override payment status, move a guest between departures, or enter a manual credit. An audit trail system for tour operations helps keep those exceptions attached to the booking instead of scattered across chat and email.
For operators using Samba, the practical point is the money flow. You connect your own Stripe account, so payouts go directly to you and Samba does not hold funds. The fee structure also affects reconciliation. Pricing is 2% per booking on direct and OTA bookings, the first $10,000 of bookings is free, there is no setup fee and no contract, the 2% can be absorbed or passed to the traveler at checkout, and offline or bank-transfer payments can be recorded with no platform fee, as shown on Samba's pricing page. That matters because the booking record, fees, staged payments, and payout timing will not always map neatly to one bank line.
Clean books do not mean every line matches at a glance.
They mean you can explain why a deposit is still sitting in liabilities, why a payout is net of fees and refunds, and why a small variance was documented and left alone. When that discipline is in place all season, month-end stays boring, which is usually the best outcome.
Founder & CEO
Related posts
Payment Reconciliation Guide for Tour Operators
Tour payments rarely settle cleanly — deposits, installments, refunds, and fees land at different times. This guide shows operators how to reconcile all four layers without spreadsheet chaos.
Net of Commission: What Tour Operators Sign Away
When a channel pays you net of commission, your payout reflects multiple deductions — not just one rate. Here's what to check before you sign and how to reconcile accurately.
Refund Processing for Tour Operators Explained
A cancellation request triggers two jobs: deciding what's owed under the original policy, and executing the refund so payments, installments, and records stay clean.
Keep the 20–30% you would hand an OTA
Samba is the booking platform built for multi-day tour operators who want to run direct bookings — not pay a marketplace 20–30% of every departure.