Refunds issued across different OTAs and direct bookings are easy to lose track of, and this covers how to build a simple audit that actually catches a missed or wrong one.
A refund for a cancelled or adjusted booking can be issued by the OTA, by your payment processor, or by you directly, depending on the channel and how the original payment was collected, and tracking all of them in one place isn't something most small properties set up until a specific refund goes missing or looks wrong. This walks through a practical audit you can actually run across channels without specialized tools.
A payment usually arrives through one predictable path per channel, but a refund can be issued by different parties depending on the situation — the OTA refunding a guest directly from money it's holding, your payment processor reversing a charge you collected yourself, or you manually refunding a direct booking. Each path has its own record, and none of them automatically shows up in the others, which means a refund audit has to pull from several places rather than one ledger.
The risk isn't usually a refund going completely unprocessed — OTAs and processors are generally reliable about that — it's that nobody at the property reconciles whether the refund that was issued matches what should have been refunded for that specific cancellation or adjustment.
A cancellation policy that allows a partial refund can result in a refunded amount that looks wrong if you're expecting a full refund, when a partial one was actually correct under the terms the guest booked. A refund issued by the OTA on your behalf reduces what you'd otherwise have received in payout, so it can look like a missing payment rather than a processed refund if you're only looking at your payout total. And a refund processed through your own payment terminal for a direct booking needs to be manually recorded somewhere, since nothing automatically logs it against that reservation unless you do it yourself.
Start with a list of every cancellation or stay adjustment for the period you're auditing, pulled from each channel's extranet or your PMS cancellation log, not from memory. For each one, note which party should have issued the refund — the OTA, your processor, or you directly — based on how that channel and policy work. Then check the actual record for that specific path: the OTA's payout deduction, the processor's transaction log, or your own manual note, and confirm the amount matches what the cancellation policy for that booking actually allowed.
Bank-level reconciliation matches payout batches and computes expected payment dates, including the deductions tied to cancellations, so an OTA-issued refund shows up as something already accounted for rather than a surprise gap in your payout. Real commission per channel and activity history give you a per-booking record of what changed and when, which turns a refund audit from rebuilding the story from several logs into checking one that's already kept. You can see both on the public demo at try.primehostpartners.com without signing up.