What it answers
Five questions your own records already answer
Nobody is going to tell you the answers. They are sitting in four systems that never compare themselves to each other. Send CactusStay one month of exports and it answers these five for that month — and every one of them traces back to something the vendor documented itself.
One past month free, for every property in your organisation. No card needed, and the findings and evidence packs are yours to keep whether or not you go any further.
- 01
Are there Expedia Collect virtual cards from the month you send that were never charged?
On an Expedia Collect booking, Expedia charged the guest and owes the property a net remittance — but the property has to actively claim it by charging a single-use virtual card. Nothing chases this for you. If the card was never charged, the stay looks complete in every system except the one that holds the money. One month of exports answers this for that month; a twelve-month sweep needs twelve months of exports.
- Records compared
- Departed Expedia Collect stays in the PMS against Gateway settlement records
- If the answer is yes
- Still recoverable, until the twelve-month window closes. After that the obligation is gone entirely.
- Deadline
- Twelve months after checkout
- 02
Were you invoiced commission on a cancelled or no-show booking at the booked amount rather than the penalty you actually charged?
On Hotel Collect, the property collects from the guest, so Expedia does not know what was actually charged on a cancellation or no-show. The property has to reconcile the reservation and state the penalty amount. Miss the window and, in Expedia's words, the invoice includes the booked amount — commission assessed on revenue that was never collected.
- Records compared
- Commission invoice line against The penalty actually posted to the folio
- If the answer is yes
- A disputable invoice line, and a recurring process gap worth closing before the next month end.
- Deadline
- The 4th of the month after checkout
- 03
Did Booking.com bill commission on a fee you waived, or a no-show you correctly marked without charging?
Booking.com commission is decoupled from whether the guest stayed: it accrues on non-refundable bookings either way, and on cancellation and no-show fees the property actually charges. But it is not chargeable where the property waived the fee, correctly marked a no-show without charging, or reported the card invalid. That gap is the disputable signature.
- Records compared
- Booking.com commission invoice against Reservation status and postings in the PMS
- If the answer is yes
- A commission line the vendor's own documentation says should not have been charged.
- Deadline
- The invoice dispute window
- 04
Does your gateway's settled total actually tie to your bank deposits?
A successful batch close is not proof of funding. Elavon states it outright: a batch response does not indicate that transactions were funded properly or completely, and the only way to confirm funding is bank deposit information. A virtual card can authorise cleanly, batch cleanly, and never fund — and nothing in the PMS or the OTA statement is wrong when it happens.
- Records compared
- Gateway settlement batches against Bank deposits
- If the answer is yes
- Money you have already counted as received. This is the class no single-source report can surface.
- Deadline
- Next business day
- 05
Where the OTA kept its commission, does what landed match what your folio said it should be?
The commission percentage is not in your system of record — Cloudbeds documents that its PMS does not receive or calculate it. So a virtual card that arrives short has to be explained against a documented list of causes: taxes on commission, tax-inclusive versus exclusive configuration, service or occupancy fees missing from the rate setup, extra-person rules, promotions, rate-plan mapping, conversion and rounding. That list is explicitly incomplete.
- Records compared
- Amount settled against The net your folio and rate configuration imply
- If the answer is yes
- Either a recoverable shortfall or a configuration error quietly repeating on every booking of that rate plan.
- Deadline
- No clock — but it repeats every month until it is fixed.
One month, four exports
No change to any system you run today: CSV, Excel or PDF files that you export yourself. All four are needed for all five answers. You can choose to run without one; the result then says which checks it could not make, rather than reporting them as clean.
Your PMS reservation export, for stays checking out in the month
Every stay with a checkout date in the month, cancellations and no-shows included: confirmation number, guest name, arrival, departure, status, rate plan, amount, and the card's last four where your system has it. Your system's own CSV or Excel export is the place to start — but the first file from a system we have not seen before may need its format added on our side. If it does, we will tell you, and your file is kept until it can run.
Both OTA statements: Expedia and Booking.com
For the same stays. From Expedia Partner Central, an export of the same stays. The exact report is still being confirmed with pilot properties; it needs the Special Requests text, so if yours has no such column, tell us. From the Booking.com extranet, the reservation statement and the month's commission invoice.
Gateway settlements, from three days before the month to the 7th of the next
Every settled batch with its date and amount, and the card's last four where the report has it. The extra days at each end catch the virtual cards charged after checkout and the batches that close across the month boundary.
Bank credits, from the 1st of the month to the 7th of the next
Deposits only, from the account your card processor pays into. A deposit lands a day or more after its batch closes, so the first week of the next month is what tells a late deposit from a missing one. Payroll, rent and other debits are not needed.
Leave guest names in where your agreements allow: they are how Booking.com stays are matched to your PMS. If you must remove them, delete the name column rather than overwrite it — a placeholder such as 'REDACTED' makes every guest look alike and pairs the wrong stays. Never send full card numbers. The last four is all CactusStay uses, and a file containing a full card number is refused rather than stored.
The Greater Phoenix pilot
What we cannot tell you is how much actually leaks at a property your size, or whether it is worth your time to fix — there is no credible public figure, and we are not going to invent one. That is exactly why we want to look at one real month.
- Who it is for
- Independent and boutique hotels and small hotel groups in Greater Phoenix that sell through Expedia or Booking.com.
- What you get
- One past month reconciled free, for every property in your organisation, with every discrepancy shown against the records behind it.
- What you send
- Four exports for that month: PMS, OTA statements, gateway settlements and bank credits. Card numbers stay at the last four.
- What we ask
- A call to walk through what it found, and your honest view of whether it was right and worth your time.
Where these come from
Published vendor documentation, accessed September 9, 2026. One entry is marked indirect: that domain blocks automated retrieval, so the wording was confirmed through search-index snippets and corroboration rather than read on the page itself.
- 01
Booking.com — commission on cancellations, no-shows and overbookingsIndirect
https://partner.booking.com/en-us/help/reservations/reduce-cancellations/handling-cancellation-fees-and-commission - 02
Expedia — two settlement pipelines
https://myfrontdesk.cloudbeds.com/hc/en-us/articles/360047222133-Expedia-FAQ - 03
Commission is not derivable from PMS data
https://myfrontdesk.cloudbeds.com/hc/en-us/articles/360047222133-Expedia-FAQ - 04
Mismatch cause taxonomy (explicitly non-exhaustive)
https://myfrontdesk.cloudbeds.com/hc/en-us/articles/360047222133-Expedia-FAQ - 05
The two clocks
https://developers.expediagroup.com/supply/lodging/ - 10
Settlement is not funding
https://developer.elavon.com/products/fusebox/v1/settlement-transactions