Blog›Pricing

Reconciling OTA Commission Reservation by Reservation in Your PMS

Reconciling OTA commission one reservation at a time in your PMS catches errors a batch total hides, and this walks through setting up that workflow properly.

The Prime Host Partners team18 Nov 2026 · 7 min read

Checking OTA commission against a single invoice total tells you whether the sum looks roughly right, but it hides exactly which reservation, if any, was charged incorrectly. Reconciling reservation by reservation inside your PMS is slower per booking but far more reliable, and this covers how to set that workflow up without it becoming a full-time job.

Full guide on this topic
Why a batch total hides individual errors

A commission invoice or payout batch gives you one number for a period covering dozens of reservations. If that number looks approximately right, it's easy to accept it and move on, but an error on one booking — a promotion applied incorrectly, a modification not reflected, a cancellation charged commission it shouldn't have been — can sit inside a total that still looks plausible overall. The only way to catch that specific error is to check the reservation it happened on, not the total it's buried inside.

This doesn't mean auditing every single booking by hand forever — it means having a workflow where each reservation's commission is checked against what it should be, ideally as part of your normal PMS routine rather than a separate audit project.

What a reservation-level reconciliation actually compares

For each reservation, the commission actually deducted should be checked against your contracted rate for that room type and any promotion that applied to that specific booking, not your standard rate. It should also reflect the booking's final state — if it was modified or partially cancelled after the original booking, the commission basis may have changed along with it. Doing this per reservation means you catch the specific booking where something doesn't add up, rather than discovering a mismatch exists somewhere in a batch of fifty.

What to record per reservation during reconciliation
1Contracted rate appliedConfirm the commission percentage used matches your current contract for that room type and channel.
2Promotion or rate tier, if anyCheck whether a promotion changed the commissionable amount for that specific booking.
3Final booking stateIf the reservation was modified or partially cancelled, confirm commission reflects the final version, not the original request.
Building a workflow that doesn't take all day

Rather than reconciling every reservation retroactively at invoice time, check commission as each reservation is finalized — at check-out or at the point a booking's status is no longer likely to change — so the work is spread across the period instead of piled up at the end. Keep a simple running note of any reservation that doesn't reconcile cleanly, so by the time the invoice or payout arrives, you already know which bookings to expect a discrepancy on rather than starting from zero.

Reconciling reservation by reservation isn't slower overall — it's the same total work, done continuously instead of in one dreaded sitting at the end of the month.
Making this routine rather than exceptional
Check commission against each reservation at or near check-out, rather than waiting for the invoice period to end.
Confirm the contracted rate and any promotion applied for that specific booking, not your standard rate.
Note the booking's final state — modifications or partial cancellations can change the commission basis.
Keep a running list of reservations that don't reconcile cleanly, so nothing is rediscovered from scratch at invoice time.
Escalate only the specific reservations that don't reconcile after checking rate, promotion and final state.
How Prime Host stops this from happening again

Real commission per channel is built for exactly this — commission is measured from what each actual booking recorded, not a flat percentage applied to a total, so a reservation-level view is the default rather than something you have to reconstruct by hand. Prime Shield adds the guest-side check, comparing the rate you sent, the rate you intended, and what the guest actually paid, flagging any gap over 5% in plain money per booking. The public demo at try.primehostpartners.com is open to try without signing up.

Frequently asked
Isn't checking every reservation individually too slow for a small team?
It's manageable if done continuously — checking at check-out as each booking finalizes — rather than attempted all at once when an invoice arrives.
What's the most common error reservation-level reconciliation catches?
A promotion or rate tier applied to a specific booking that wasn't accounted for in a simple flat-percentage commission calculation.
Should I still check the overall invoice total if I'm reconciling per reservation?
Yes — the total should match the sum of your reservation-level checks, and a mismatch there tells you something was missed in the reservation review.
Want to see all of this working for real?
Walk through the actual system in read-only mode. Nothing to fill in.

Read next

© 2026 Prime Host Partners
Privacy PolicyTerms of Service