Real overpayment vs cent-level overpayment
Two very different types of “overpayment”:- Cent-level overpayment (0.01-0.03 €): rounding mismatch from OTA imports. See Cent-mismatch overpayments.
- Real overpayment: the customer was charged more than once, or the charge was bigger than the amount owed.
How to identify a real overpayment
Open the affected reservation
In the Payments tab, Guest transactions section, review the payment list.
Look for duplicate payments
A typical duplicate payment shows:
- Same date
- Same amount
- Same payment method
Common causes
- Double POS charge: the reader failed on the first attempt and the receptionist swiped again, but the first transaction did go through.
- Customer pays twice by mistake: makes a transfer and then another when the first one doesn’t show.
- Automatic OTA charge + manual charge: the hotel charged at check-in not knowing the OTA had already billed the customer.
- Unapplied refund: a refund was issued but wasn’t recorded properly.
What to do
You can’t delete the duplicate payment from the Roomdoo app. The process is:Confirm with the customer and/or the gateway
Before contacting support, make sure it was actually a duplicate charge (not a failed attempt followed by a successful one).
Decide how to handle the refund
The customer may prefer:
- Refund to the original method (card, transfer)
- Leave it as credit for a future stay
When to contact support
Always, once the duplicate is confirmed. Only support can:- Remove the duplicate payment from the folio
- Trigger the refund via gateway (Phone & Sell, Redsys) if applicable
- Adjust the folio balance back to zero