Zamaira / Hotel Owner Guide
How to reconcile Expedia and Booking.com hotel payments.
Published October 20, 2026 · Zamaira Hospitality
A reservation marked prepaid does not necessarily mean a hotel has received funds. The OTA booking, the PMS folio, the card processor and the hotel's bank statement may record different events on different dates. A good reconciliation follows each reservation from the channel to its actual settlement, rather than comparing only monthly totals.
The first step is to determine who is supposed to collect payment. Expedia and Booking.com both support more than one payment arrangement. What appears to be a missing payout under one arrangement could be a correctly unpaid guest balance under another. The specific booking terms and your property's channel agreement take precedence over any generic checklist.
Step 1: Separate OTA-collect and hotel-collect reservations
For Expedia Group bookings, distinguish reservations under an Expedia-collect arrangement from those where the property is responsible for collecting payment. Do not assume the same merchant, commission, refund or virtual-card process applies to both. The Expedia Partner Central account and reservation details are useful places to confirm the appropriate payment handling.
For Booking.com, separate reservations using Payments by Booking.com from reservations where guests pay the property. Booking.com's technical payment documentation explicitly distinguishes these models. It also describes virtual credit card and bank transfer payouts, which may have different processing and reporting details. Your team's first reconciliation column should therefore say expected collection method, not simply "OTA booking."
Step 2: Create a reservation-level matching worksheet
Start with one row per booking and keep its history of amendments available. A useful worksheet has fields for OTA channel, channel reservation ID, arrival and checkout dates, room revenue, relevant taxes or fees, booking status, expected collector, payout method, expected payment amount, payment reference, and settlement status. Include a separate column for any documented discrepancy and the action required.
Export only the records you are authorized to handle. Record payment references but do not include full card numbers, security codes or guest personal information in a shared spreadsheet. Reconcile credit memos and reversals against the original booking instead of creating duplicate "new" balances.
Step 3: Match virtual-card payments to actual processor activity
A virtual credit card (VCC) is a payment instrument, not proof of deposited cash. Review the card's permitted activation and expiration information, current amount or balance, payment status, and any charge or refund already posted. Then match the processor transaction to the property's payout or bank deposit. A card can be valid, partly charged, fully charged, cancelled or no longer available; the outcome must be established from actual records.
Booking.com's developer reference describes VCC status, activation and expiry fields, and also distinguishes reservation-level payment and payout data. Those documents are technical references for connected partners; a hotel's own extranet may expose the information differently. They do not establish that every hotel can access the developer APIs directly.
Step 4: Reconcile bank transfers as transfers, not as VCCs
When an OTA pays the property by bank transfer, compare the reservation or settlement grouping with the transfer reference, payout date, fees or commission treatment, currency, and bank deposit amount. Gross and net payment models can yield different deposited totals. A lower-than-room-revenue deposit might be correct after authorized deductions; investigate the breakdown before classifying it as missing money.
Booking.com's connected-partner documentation distinguishes gross payouts from net payouts and describes a bank transfer reference that can help reconcile payments. The exact details a hotel can see depend on its payout configuration and access. Keep any unexplained difference in an exception queue until the underlying records agree.
Step 5: Review cancellations, no-shows and amended stays separately
A cancelled reservation is not automatically a zero-commission reservation, and a no-show is not always a collectible booking. Compare the final PMS outcome to the status and conditions recorded by the OTA. Check what was actually communicated to the channel, which fee or penalty was permitted, and whether the applicable reconciliation or dispute window remains open.
Keep commission adjustments distinct from payment recovery. A successful commission credit is not necessarily a cash refund and must not be counted twice if it later appears on an invoice. Platform rules, taxes and cancellation policies can vary, so do not rely on a blanket deadline quoted in an unrelated online guide.
Step 6: Investigate tax and fee differences without guessing
The guest's total booking price can differ from the amount payable to the hotel if certain taxes, commissions or fees are collected, withheld or remitted by another party. An owner should reconcile the reservation's hotel-view financial breakdown to the PMS folio and applicable local tax responsibilities. In some configurations, the channel may remit eligible taxes directly; in others, the hotel may remain responsible for remitting them.
Booking.com's payment-clarity reference illustrates different tax-and-fee collection and remittance combinations. Do not assume those examples automatically match your jurisdiction or contract. Ask the hotel accountant or tax advisor to verify material tax treatment before issuing a correction.
Step 7: Record an audit trail and an approval decision
A reconciliation should tell the owner what is confirmed, what needs evidence, and what was actually resolved. Each potential claim should have the reservation ID, discrepancy description, source documents, applicable platform rule where verified, claim status, owner authorization and final outcome. Mark items that were explained or ineligible so the same apparent exception is not resubmitted.
Illustrative example: suppose an OTA booking shows a $120 payable amount but only a $100 processor record. Do not immediately call $20 recoverable. Check whether the processor captured a second payment, a fee adjustment applied, an authorized refund occurred, or a net payout was expected. The example is hypothetical, not a Zamaira client result.
A nine-point monthly OTA payment checklist
- Set the audit period and identify the properties and OTA accounts in scope.
- Classify reservations by payment collection model and final booking status.
- Match OTA reservation IDs, dates and amounts to final PMS records.
- Separate virtual-card, bank-transfer and guest-at-property payment paths.
- Compare permitted VCC charge details with card processor transactions.
- Match bank transfers using payout references and the correct net or gross breakdown.
- Check commissions, cancellations, refunds and tax treatment against documented agreements.
- Classify open exceptions and obtain owner approval before any dispute.
- Close the loop using accepted credit memos and actual settlement evidence.
Which sources should your team verify?
Start with the property's current Expedia Partner Central or Booking.com extranet records and the authorized booking agreement. The following official references help explain the payment-model distinctions; some links document APIs intended for authorized connectivity partners, not end-user hotel portals:
- Expedia Group partner portal — hotel access to Partner Central.
- Booking.com: Understanding the Payments API — Payment by Booking versus pay-at-property coverage and scope.
- Booking.com: Managing payment and payout details — payout methods, amounts and VCC information.
- Booking.com: Payout use cases — gross/net and bank transfer distinctions.
The exact screens, eligibility, terminology and policy details can change. Consult the current property-specific partner resources before pursuing a charge, dispute or tax correction.
When does an owner need outside help?
A property may benefit from independent review if the PMS, OTA and payment reports cannot be reliably reconciled, if exceptions persist across several billing cycles, or if the staff needs a clearly documented process. Zamaira offers OTA payment reconciliation and revenue recovery services with an evidence-first approach and owner approval before claims. Accurate OTA distribution mapping and hotel rate management can support the wider commercial process, but they are distinct services.
Request a confidential consultation about the records your hotel needs to reconcile, or visit our introductory guide to OTA revenue leakage. We do not guarantee a recoverable amount and we never request guest card numbers through the inquiry form.