Blog · 8 min read

OTA Reconciliation and Payouts: Keeping the Numbers Straight

The payment is never wrong in the way you first think it is.

A payment arrives from a platform. It does not match your bookings for that month, it does not match the month before, and after twenty minutes with a spreadsheet you decide it is probably fine and move on. Most operators have done this. Some have done it every month for years.

The uncomfortable part is that "probably fine" is a decision not to know whether you were paid correctly. This covers why platform payments never line up the way you expect, how to match them properly, and how to spot a genuine shortfall among the noise.

Why it gets messy across channels

Three structural reasons, and none of them are anyone doing anything wrong.

Three dates that never align

Every platform booking has a booking date, a travel date and a payout date, and they can sit months apart. A tour booked in February, run in July, is typically paid some weeks after July closes. If you compare a payment against the bookings you took that month, nothing will ever match — you are looking at three different populations of bookings.

Almost every reconciliation headache traces back to this. Platforms generally pay on travel, so that is the date to reconcile on.

One payment, many bookings

You receive a single figure covering dozens of bookings, frequently spanning several weeks, with adjustments from earlier periods folded in. A refund processed for a June booking may appear as a deduction against your July payment. The number in your bank account is a net result, not a list.

Net, not gross

Platforms remit after deducting commission, and sometimes after other items — promotional programme fees, refunds, occasionally tax withholding depending on your jurisdiction. Comparing a payout against your gross booking value guarantees a mismatch. You need the expected net figure for each booking before you can check anything, which means knowing your actual commission rate rather than the range you read somewhere.

Matching bookings to payouts

Work from the remittance, not your bookings

Most operators start from their own booking list and try to find the money. It is faster the other way round. Download the platform's remittance statement — every major platform provides one, listing the bookings covered and the deductions applied — and match each line back to a booking in your system. Anything on the statement you cannot find, and anything in your system that should have been on the statement and is not, becomes your exception list.

What every booking needs to carry

Reconciliation is only difficult when the information was not captured at the time. Every booking should record:

  • The channel it came from
  • The platform's own booking reference, exactly as they show it
  • Gross value, expected commission and expected net
  • Travel date, separately from booking date
  • Currency, if it differs from your accounting currency
  • Any modification or partial refund, with the date it happened

With those six fields present, matching becomes mechanical. Without the platform reference in particular, you are matching on guest name and date, which fails as soon as two people share a surname or a booking is amended.

Different schedules and currencies

Schedules

Each platform runs its own cycle, and they rarely coincide. Most settle monthly after the travel period, though some offer faster settlement in certain markets in exchange for a slightly higher commission. Write down each platform's schedule and expected arrival window somewhere permanent — it turns "has this been paid?" from an investigation into a glance, and it tells you when a payment is genuinely late rather than merely not yet due.

The cash-flow consequence is worth stating plainly: you deliver the tour, pay the guide and fuel the vehicle, then wait weeks for the revenue. Across several platforms with different cycles, that gap is not theoretical — it is the reason a busy season can still feel tight.

Currencies

If a platform collects in one currency and pays you in another, an exchange rate has been applied somewhere and it is rarely the rate you would find online that day. Record what the platform actually paid in the payout currency, alongside your accounting figure and the rate used, and reconcile in the payout currency first. Otherwise a currency movement and a genuine underpayment look identical — and operators dismiss real shortfalls as exchange-rate noise.

Spotting missing or short payments

When a payment looks light, work through the ordinary explanations before assuming an error. In rough order of likelihood:

  • A refund from an earlier period deducted from this one
  • Commission at a different rate than you had in mind — particularly if a promotional or promoted-placement programme is active
  • Currency conversion between the booking and the payout
  • A booking modified after the fact — guests removed, date changed, partial refund agreed
  • A booking that moved into the next cycle because the travel date shifted
  • Tax withholding, depending on your jurisdiction and the platform's obligations

If none of those account for the gap, raise it — with specific booking references, expected amounts and what you received. Platforms generally correct genuine errors, but a query saying "the payment seems low" goes nowhere. One naming a booking reference and a figure gets resolved.

Query within the cycle. Most platforms limit how far back a payment can be disputed, so a discrepancy found at the end of the season may no longer be recoverable — which makes the habit of checking each payout worth more than the hour it takes.

A monthly routine that takes an hour

  1. Download the remittance statement from each platform that paid you.
  2. Match each line to a booking using the platform reference.
  3. Compare actual against expected net, in the payout currency.
  4. List every exception — unmatched lines, and gaps beyond a tolerance you set.
  5. Explain each exception using the causes above.
  6. Query anything still unexplained, with references attached.
  7. Record net revenue by channel while you have the numbers open.

Step seven is the one to keep. Reconciliation is the only moment you handle real net figures per channel rather than gross booking counts, so it is the natural point to update what each platform actually earns you — the number that should drive how you allocate capacity and how hard you push direct bookings.

What software can automate

Reconciliation is mechanical work, which makes it a poor use of a season's evenings. What a system can do:

  • Capture the fields automatically. Channel, platform reference, gross, expected commission and net recorded as the booking arrives rather than typed in later.
  • Hold one booking record per reservation, wherever it came from, so there is a single list to match against rather than several exports.
  • Track modifications and refunds against the original booking, so a later deduction is traceable to what caused it.
  • Report net revenue by channel without a manual export and a formula.

What no software eliminates is reading the remittance statement — the platform's own record of what it decided to pay you. The realistic goal is not zero minutes; it is reviewing a short exception list instead of rebuilding the entire month.

How Travelity helps

Because every reservation — from any connected marketplace, your own widget, or entered by your team — lands in one booking queue with its source and reference attached, the record you need at reconciliation time already exists. There is no rebuilding the month from three exports.

That also makes net revenue per channel something you can read rather than assemble, which is the number worth having when you next review your channel mix or negotiate a commission rate.

Frequently asked questions

Why does my OTA payout never match my bookings?

Usually because you are comparing the wrong things. Platforms pay on the travel date rather than the booking date, remit net of commission rather than gross, and often deduct refunds from earlier periods. A single payment can cover dozens of bookings from several different weeks with adjustments applied on top.

When do OTAs pay tour operators?

Generally after the experience has taken place rather than when the customer books, and typically on a monthly cycle with the payment arriving some weeks after the travel period closes. Some platforms offer faster settlement in certain markets in exchange for slightly higher commission. Check the specific schedule in your own agreement, because they differ.

What should I do if an OTA payment looks short?

Work through the usual causes before raising it: a refund or cancellation deducted from a prior period, commission applied at a different rate than you expected, currency conversion, a booking modified after it was made, or a promotional programme fee. If none of those explain the gap, query it with the booking references attached — platforms generally correct genuine errors, but only if you can point to specific bookings.

How do I handle OTA payouts in a different currency?

Record the amount in the currency the platform actually paid you, alongside the amount in your own accounting currency and the rate applied. Reconciling in the payout currency first removes exchange-rate noise from the matching process, so a genuine shortfall is not mistaken for a currency movement or the other way around.

How often should I reconcile OTA payments?

Every payout cycle, while the bookings are still recent enough to remember. Reconciliation left until the end of a season becomes archaeology, and most platforms have time limits on querying a payment — so a discrepancy found six months later may no longer be recoverable.

Can reconciliation be automated?

Largely, provided every booking carries its channel, its platform reference and its expected net amount from the moment it arrives. Software can then match a remittance against expected values and surface only the exceptions, which turns a day of spreadsheet work into reviewing a short list of genuine discrepancies.

Bottom line

Reconcile on the travel date, against expected net rather than gross, in the currency you were actually paid — and start from the platform's remittance rather than your own booking list. Most of what looks like an error is one of six ordinary causes, and the remainder is worth querying while the cycle is still open.

It is the least interesting hour in the month and one of the more valuable ones. It is also the only point at which you see what each channel truly earns — which makes it less an accounting chore than the moment your distribution strategy gets its evidence.

Related guides

Get started

See Travelity in action. Book a Personalized Demo.

30 minutes that can completely change the way you run your travel business. See how Travelity can help you work smarter, sell more, and operate with less stress.

No credit card · 21-day free trial · Cancel anytime