Operational automation
How to Reconcile OTA Invoices Against the Bookings You Actually Fulfilled
· Tourbo
OTA statements are not the same as the tours you ran, and the gap is rarely in your favor. Reconciling each invoice against the bookings you actually fulfilled catches commission charged on the wrong base, payouts that never arrived, charges for cancellations that shouldn’t bill, and fee discrepancies — money that’s otherwise lost in line items nobody checks. Here’s how to do it without losing a day to spreadsheets.
Why the statement and reality drift apart
Between a booking and a payout, a lot happens: discounts, promotions, cancellations, no-shows, currency conversion, and the platform’s own fees. Each is a place for the number to diverge from what you’re owed. At low volume you might eyeball it. At scale, the statement becomes a wall of line items, and “it’s probably fine” becomes your accounting policy — which is exactly what an error-prone process counts on.
What to look for
When you match a statement against fulfilled bookings, the recurring culprits are:
| Discrepancy | What it looks like |
|---|---|
| Commission on the wrong base | Charged on a pre-discount or incorrect amount |
| Missing payout | A tour you ran with no matching payout line |
| Charged cancellations | Billed for a cancellation inside the free window |
| No-show handling | Fees applied (or not) against your actual policy |
| Duplicate / mismatched lines | The same booking billed twice, or amounts that don’t match |
| Fees and FX | Unexpected deductions or conversion gaps |
None of these is huge on its own. Across a season, they add up to real money — and they only come back if you find them.
A reconciliation process that works
- Get the fulfilled-booking record — what you actually ran, with the correct amounts and your real cancellation outcomes.
- Match each statement line to a booking. This is where the time goes.
- Flag the exceptions — anything missing, extra, or mispriced.
- Dispute with evidence. A clean match record makes a dispute fast and credible.
- Track recoveries so you know which platforms and error types are worth watching.
The work is almost entirely in step 2 — the matching. It’s tedious, rules-based, and high-volume, which is the textbook profile of a task to stop doing by hand.
Automating the matching
Validating OTA invoices against the bookings you fulfilled is a matching problem, and matching is exactly what Operational Automation is built to take off your plate: line up the statement against fulfilled bookings, apply your cancellation and pricing rules, and surface only the exceptions that need a human to review and dispute. It pairs naturally with OTA Manager — one keeps your listings and pricing right going in, the other makes sure you were paid correctly coming out. (And every point of commission you reclaim is part of the same fight as reducing OTA dependence.)
The bottom line
Reconciliation isn’t glamorous, but it’s found money — the difference between what the statement says and what you actually earned. Match every line to a fulfilled booking, dispute the exceptions, and automate the matching once volume makes it a chore. The operators who check get paid correctly; the ones who assume “it’s probably fine” subsidize the platform.