Orca SystemsHow to reconcile OTA payments against your hotel's ledger
On Google Search you can choose the sites whose articles you want to see more often.
Every month the same thing happens. The online travel agency (OTA) statement arrives. The hotel's own records say one number; the statement says another; the bank says a third. Someone, usually the accountant or the owner late in the evening, spends hours finding out why.
The gaps are almost never fraud and almost never a single big mistake. They are many small, explainable differences. The way out is a repeatable method that treats one booking as the unit and follows it from the reservation to the statement to the money. This article sets out that method. It works on a spreadsheet, and it works better in a system that does the matching for you.
Why the numbers differ
The usual causes, which are worth knowing before you start:
- Net versus gross. Some payments arrive with the commission already deducted, so the payout is lower than the room rate on the reservation.
- Commission differences. A different contracted rate, an extra programme, or a fee on a no-show.
- Changed bookings. A shortened stay, a cancellation with a fee, a refund, a date change.
- Timing. The stay date, the date of the payout and the date of the invoice can fall in different months.
- Money handling. Currency conversion, processor fees, a receiving-bank deduction.
These are the causes a reconciliation guide published in September 2026 lists for one OTA's payouts (SmartOrder, 18 September 2026, a software vendor's guide, secondary); they apply in broad terms to any OTA, but each OTA's payment terms differ, so read the terms in your own extranet.
The method: follow one booking at a time
The principle in that guide is the one we use ourselves: follow one reservation from the OTA record to the payment, the commission, the bank and the property management system (PMS), and the batch becomes easy to close once each booking is correct.
Step 1. Decide the key. The booking reference is the key. Everything is matched on it. Before you match, tidy it: remove spaces and dashes, and note whether a prefix is used on one side and not on the other.
Step 2. Mark how each booking is paid. At the time of booking, record whether the guest pays you directly, whether the OTA collects and pays you, or whether you receive a virtual card to charge. This one field answers half of the later questions. In our reservation form the payment type is a choice between direct (pay the hotel), virtual card, and prepaid (agency or OTA collects), and the options follow the booking source.
Step 3. Build your list from the PMS. For the statement period, export every stay from that source: checked out, no-show, and cancelled with a fee. Include the booking reference, dates, rate and the amount the guest or OTA owed you.
Step 4. Get the OTA statement or invoice for the same period, in the format the OTA gives you.
Step 5. Match on the reference and sort the result into five piles:
| Pile | What it means |
|---|---|
| Matched, amounts agree | Done |
| In the PMS, not on the statement | The OTA has not paid, paid in another month, or the booking was cancelled on their side |
| On the statement, not in the PMS | A booking you did not record, or a reference typed wrongly |
| Matched, amounts differ | Commission, a fee, a changed stay, or currency |
| Matched, paid by virtual card | Check the card charge against the booking, separately from the statement |
Step 6. Explain each difference in a sentence. "Stay shortened by one night." "No-show fee charged at 100 percent." "Commission rate differs from contract." Do not move to the next line until the sentence is true.
Step 7. Keep exceptions open. The temptation is to post a small "adjustment" to make the totals agree. Resist it. An exception that stays visible is a task; an adjustment that hides it becomes next quarter's argument. The SmartOrder guide makes the same point: keep exceptions open rather than forcing a match through revenue adjustments.
Step 8. Close against the money. Match the statement total to the bank deposit or the virtual card charges. The difference between the two is what you chase.
A monthly rhythm that does not take over your life
- Weekly: look at the "In the PMS, not on the statement" pile for bookings that are already old enough to have been paid.
- Monthly, within a few days of the statement: run the full method, and write the explanations down.
- Quarterly: compare the commission you actually paid, by OTA, with what your contract says. If you cannot find the contract, that is the first job.
Assign one person. A reconciliation that is "everyone's job" is one that is done when someone is angry.
Two habits that prevent most gaps
- Record changes when they happen, not at month-end. A shortened stay entered the day it happens costs a minute; found later it costs an hour.
- Keep the booking reference clean and consistent. If staff type it in different ways, matching fails for reasons that look like money problems.
What a system can do, and what it cannot
A PMS cannot make the OTA pay on time, set your commission, or decide whether a no-show fee should be charged. It can do the dull part: take a statement, match each line to a booking by reference, and flag what is missing or different, so the human work starts at the list of gaps and not at line one.
This is product information. The system we run at Royal Ivory Nana Hotel, a 91-room hotel in Bangkok, can take an OTA statement, match it against the ledger and flag the gaps. It does not decide anything about commissions or fees, and it does not promise that every line will match; unmatched lines are shown to a person. We make no claim about how much time this saves.
If you reconcile in a spreadsheet and it works, keep it: the method above works there too.
If you read us on Google Search, you can choose Orca Systems as a preferred source there.