A practical method for tracking refunds issued across different OTAs and your own booking engine, so your records match what actually happened on each channel.
A refund on Booking.com, one on Agoda, and one through your own booking engine's payment link all work slightly differently, and tracking them in one inconsistent place is how finance and the front desk end up disagreeing about what was actually returned to a guest. This covers a practical method for tracking refunds across channels that keeps everyone looking at the same numbers.
Each OTA processes a refund through its own extranet, on its own timeline, and reflects it in its own payout or commission reporting differently. A refund on a direct booking collected through a payment link follows your payment gateway's own refund process and timeline instead. If your property is logging refunds informally — a note at the front desk, a line in an email — rather than pulling the actual figure from each channel's own record, small discrepancies between what was logged and what was actually processed accumulate quietly.
The front desk usually knows a refund was promised; finance usually knows what actually left the account. The gap between those two is almost always a tracking problem, not a dishonesty problem.
The channel it was processed on matters, since that determines where to verify the actual figure and timeline. The amount and date it was actually processed, not promised, since there can be a meaningful gap between when a guest is told a refund is coming and when it's actually issued. And the reason — cancellation, service issue, overcharge correction — since that affects whether it should also prompt a rate or policy review rather than being treated as a one-off.
Pull the refund report or log from each OTA extranet and from your payment gateway separately — most channels will show you refunds issued within a period if you look in the right report rather than the main reservation list. Match each one against your own internal log by reservation ID rather than by guest name or date alone, since names and dates are more prone to small mismatches than a unique reservation reference. Any refund promised to a guest that doesn't appear in a channel's own record within a reasonable window is worth following up on directly, since that's the gap most likely to become a dispute later.
Bank-level reconciliation matches payout batches and computes expected payment dates for Booking.com, which gives finance a verified figure to check refunds against instead of reconstructing it from separate extranet exports each time. Activity history then records who processed what and when, across 39 action types kept for 400 days, so a disputed refund has a clear trail rather than relying on anyone's memory of the conversation. If refund tracking is a recurring source of disagreement internally, that's the structural fix — try it on the public demo at try.primehostpartners.com without signing up.