At a glance
- An OTA invoice audit compares three records per reservation: the OTA invoice, the virtual-card settlement and the stay in your property management system.
- The leakage table sorts four discrepancy types by how an agent catches each, how dispute-window risk shows up, and who approves the dispute.
- Dispute windows come from each OTA agreement, so load them per OTA and rank open items by the time left.
- A recovery vendor and an in-house agent layer differ in who owns the match rules, the evidence trail and the link to your ledger.
- Owner reports should show found, recovered, open and written-off items by property, with evidence attached.
Why do OTA commission invoices not match what posted to the PMS?
An online travel agency (OTA) such as Booking.com or Expedia sells your rooms and takes a commission. A virtual card (VCC) is a single-use payment card the OTA issues so the hotel can collect for a booking. In one published version of Expedia's lodging agreement template (version 326), a property may elect to use a single-use credit card system to receive amounts due for Expedia Collect bookings, if Expedia makes that option available [1].
The invoice is built from the OTA's record of the booking, while your property management system (PMS) holds the folio. In Expedia's template, compensation on a standalone booking is a percentage of the Total Room Price, and for Expedia Collect bookings the property's remittance is the Total Room Price minus that compensation [1]. A difference in price, status or fee treatment between the records moves both the commission and the payment.
A RobosizeME co-founder, writing as an opinion contributor, lists the usual failure points: tax and city fee amounts that the interface splits incorrectly from the room revenue, currency rounding gaps on cross-border bookings, and PMS and OTA statuses that fall out of sync [2]. Her firm sells reconciliation automation [4], so read her list as one vendor's view.
- Stay changed: was the reservation cancelled, shortened or marked as a no-show after the OTA booked it?
- Different base: does the invoice line commission the room rate alone, or the rate plus fees and taxes?
- Different money: were the OTA amount and the PMS posting converted or rounded in different currencies?
This article does not describe Booking.com's commission or card terms. Load each OTA's commission rules from your own signed agreement, because the match is only as good as those terms.
How do I know if Booking.com or Expedia overcharged us on commission?
Recompute the expected commission for each reservation from your contract rate and the stay data, then compare it with the invoice line. Because Expedia's template ties compensation to the Total Room Price [1], check three inputs before you dispute anything.
- Base: the room price, fees and taxes the invoice line commissions.
- Rate: the percentage in the contract version in force for that stay.
- Status: whether the stay was completed, cancelled or a no-show.
Leakage-type table: what an AI agent catches, the dispute-window risk and who approves
An AI agent for this work is software that reads OTA invoices, card settlements and PMS records, applies the terms you load and drafts a list of differences. It follows the match-then-explain pattern on our financial reconciliation automation page. The table is our own framework: replace the window column with the terms in your agreements.
| Discrepancy type | How an AI agent catches it | Dispute-window risk | Who approves a dispute |
|---|---|---|---|
| Virtual-card underpayment | Matches each card settlement to the reservation's expected net amount and lists cards charged short, or never charged. | Expedia's agreement template tells the property to charge the card promptly following the guest's checkout. If it is not charged within 12 months of check-out, cancellation or no-show, neither Expedia nor the guest has further obligation on that booking [1]. Read your own terms for each OTA. | Finance lead approves the claim or write-off; property staff confirm the stay facts. |
| Commission overpayment | Recomputes the expected commission from the contract rate and the stay data you load, and lists invoice lines above it. | Expedia's template says to notify Expedia immediately if you believe it incorrectly derived amounts, and that a disputing party will promptly give written notice with reasonable detail [1]. Until you confirm the term, treat the invoice date as the clock's start. | Controller approves the dispute; revenue accounting supplies the evidence. |
| Rate-code variance | Compares the rate code and net rate on the OTA booking record with the PMS folio and the contract, and lists mismatches. | Runs on the same clock as the commission line, because a rate variance changes the commission base. Confirm the term per OTA. | Finance approves the dispute; revenue management owns any pricing question, which this audit does not decide. |
| Resort-fee leakage | Checks whether mandatory fees the property charges appear in both the OTA booking record and the PMS, and lists reservations where one is missing. | Expedia's template defines Hotel Fees as mandatory fees guests must pay, naming resort fees as an example [1]. A missing fee can change the base a commission is computed on, depending on how your agreement defines the price, so check it on the same cycle as the card. | Accounting approves the adjustment; the property's general manager confirms the fee policy. |
How do virtual-card underpayments happen, and who catches them?
The contributor's list above names tax and fee splits, currency rounding and statuses that drift between the PMS and the OTA as causes of short or missing card payments [2]. Whoever reconciles card settlements to reservations catches them: an agent lists each short or uncharged card, and a finance lead decides on the claim.
Dispute windows: why speed matters when you audit OTA invoices
A dispute window is the period in which a claim is still open; it comes from the OTA agreement and can differ by OTA and contract version. The RobosizeME contributor describes the failure plainly: the charge attempt fails silently, and the dispute window closes before anyone notices [2].
We recommend a ranked queue over a periodic review. An agent can compute the days left on every open item from the terms you load, so the item closest to its deadline reaches a person first. The agent ranks; finance chooses what to dispute.
- Load the window per OTA
Record the claim period and the notice requirement from each signed agreement, with the contract version and its date.
- Stamp every open item
Give each difference a start date, a deadline and a status, so nothing waits in an inbox without a clock.
- Rank by days remaining
Show the item nearest its deadline first.
- Route to the approver
Send each item to the approver in the leakage table with the evidence attached, and record the decision.
How much OTA leakage is normal for a hotel portfolio?
No independent benchmark is cited here. RobosizeME's release of May 7, 2026 refers to "industry data indicating that hotels lose between 1–2% of OTA revenue each month due to undetected inconsistencies" [3]. The release does not name the underlying study, so treat the range as one vendor's claim, not a norm.
The same release says reconciling OTA virtual-card balances by hand can take up to 30 minutes per OTA, per day, for each property [3]. Read that as the vendor's estimate, not a measured result; your own leakage rate is what matters.
- Sample: pick N reservations per property and OTA, where N is the sample size your finance team sets.
- Recompute: calculate the expected commission and card amount from your own contract terms.
- Measure: divide the total gaps by the sampled gross revenue, and report it by property and by discrepancy type.
Should we use a recovery vendor or build this in-house?
Commission-recovery and reconciliation vendors, such as RobosizeME, are firms that audit or automate OTA payment checks. RobosizeME, for example, documents the core checks: its Financial Reconciliation Suite page says that OTA and Travel Agent commissions are automatically verified against actual stay data, and that mismatches are flagged early [4]. We describe that product only as its maker does, and do not rank vendors.
| Decision factor | Recovery or reconciliation vendor | In-house agent layer on your stack |
|---|---|---|
| Scope | Fits when the problem is OTA-only and the vendor's checks match your contract terms. | Fits when the same evidence must also feed accounts payable, the ledger and owner reports. |
| Match rules | The vendor's configuration holds them; ask how a contract change reaches the rules. | Your team owns them, including each property's contract variations. |
| Evidence trail | Confirm what the vendor exports for a dispute file and for an owner report. | Stored beside your ledger entries, with the approver recorded. |
| Effort to maintain | Commercial terms vary by vendor; ask for them in writing. | Your finance and IT staff maintain the rules; plan for it before you build. |
We recommend starting with the narrowest tool that covers your OTAs and contracts. If the same workflow must also reach your ledger, an agent layer built through AI agent implementation keeps the rules and the approvals in one place, and our ledger matching workflow shows how those matches reach the books. The wider back-office context is on the hospitality operations page.
Reporting leakage findings to property owners
A management company reports to owners who may not see the OTA invoices at all. Check each management agreement for the reporting format and timing it asks for, and keep claim decisions with your own finance staff, as the document review with human approval pattern does for any extracted record.
- Found: each difference, the reservation, the OTA and the discrepancy type.
- Recovered: the amounts credited or paid back, with the date and the approver.
- Open: claims still within their window, ranked by days remaining.
- Written off: items closed without recovery, with the reason a finance lead recorded.
When this doesn't apply
- Your OTA contracts are hotel-collect only, with no virtual cards to charge: the card checks in the table have little to catch.
- A single OTA whose extranet already reports uncharged and short cards clearly: measure what it misses before adding a layer.
- Agreements with no commission terms on file: collect and date them first, because no agent can apply terms nobody loaded.
- Pricing or revenue-management questions: this audit never judges rates; it only compares records.
Frequently asked questions
Why does my OTA commission invoice not match what actually posted to the PMS?
The invoice comes from the OTA's record of the booking, while the PMS holds your folio. They diverge when a stay changes after booking, when fees or taxes are split differently, or when currencies round differently. List each reservation's gap, then trace it to one of those causes before disputing.
How do I know if Booking.com or Expedia overcharged us on commission?
Recompute the expected commission for each reservation from your contract rate and the stay data in your PMS, then compare it with the invoice line. Confirm the base, rate and stay status before disputing; your finance staff file the claim.
What's a normal amount of OTA revenue leakage for a hotel portfolio?
RobosizeME's May 7, 2026 release gives a monthly leakage estimate and cites unnamed industry data, so treat it as a vendor claim rather than a benchmark. Measure your own by sampling reservations at each property, recomputing the expected amounts, and dividing the gaps by the sampled gross revenue.
Should we use a commission-recovery vendor or build this reconciliation in-house?
It depends on scope. A recovery or reconciliation vendor fits when the problem is OTA-only and its checks match your contracts. An in-house agent layer fits when the same evidence must also feed your ledger, accounts payable and owner reports.
How do virtual card underpayments happen and who catches them?
A RobosizeME co-founder lists tax or fee splits, currency rounding and statuses that fall out of sync between the PMS and the OTA as causes of short virtual-card payments. Whoever reconciles card settlements to reservations catches them: an agent can list them, and finance approves the claim.
Related reading
- Financial reconciliation automation covers the match-then-explain pattern behind the table.
- Document review with human approval covers the approval step for each extracted record.
- AI agent implementation covers building and running the agent layer.
- Hospitality operations places this audit among a hotel group's back-office workflows.
- Reconciliation match rules and exceptions gives the general match-type and exception framework.
Sources
- Expedia Group, Expedia Lodging Agreement (template terms and conditions, version 326) (accessed 2026-10-29)
- Linda Girrbach (RobosizeME), How Much Money Is Sitting in Your OTA Virtual Cards Right Now?, Hospitality Net (accessed 2026-10-29)
- RobosizeME, Hotels Lose Up to 2% of OTA Revenue Monthly (press release, May 7, 2026), Hospitality Net (accessed 2026-10-29)
- RobosizeME, Financial Reconciliation Suite (accessed 2026-10-29)
More in Finance operations
Deal Jacket and Title/Registration Automation for Multi-Rooftop Dealer Groups
Deal jacket and title/registration automation for multi-rooftop dealer groups: a completeness checklist table, audit-gap handling and cross-store standards.
Auto DealershipsFranchise Brand-Standards Audit Documentation: Automating the Paper Trail Behind the Inspection
Franchise brand-standards audit documentation: how an agent turns photos, PDFs, forms and emailed fixes into one packet per location, ready when asked.
Multi-Unit Franchise OperatorsGroup and Folio Billing Audit: Catching the Leak Types a Normal Error Check Misses
A group and folio billing audit for hotel management companies: a leak-type table of rate code mismatches, missing closes, adjustments, orphaned charges.
Hotel Management Companies