Skip to main content
This article is about overpayments (more was charged than the reservation is worth), not overbooking (selling a room with no availability). If you have an overbooking, see OTA synchronisation.

​
Why a cent-level overpayment appears

Some OTA reservations are prepaid: the OTA or your booking engine charges the guest online and pays you out later. On those reservations, the prepayment comes into Roomdoo on its own together with the reservation, through your channel manager. When the reservation is created, that payment never exceeds the reservation total. The reservation amount is spread across its lines (each night, breakfast, extras, and so on), and each one is rounded to the cent. If the OTA later modifies the reservation, Roomdoo updates the payment with the amount the OTA reports, while the reservation total comes from adding up its already-rounded lines. If that sum ends up 1 or 2 cents below what was charged, the reservation shows an overpayment of those cents: in the reservation header you’ll see the amount followed by “overpayment” and, if your property uses the colour legend with payment status, the reservation shows in the planning’s overpayment colour (see Planning colours). If it’s the other way round (the lines add up to a few cents more than what was charged), you won’t see an overpayment but a few cents pending to charge. On OTA reservations where you charge the guest yourself, no payment comes in with the reservation, so this case doesn’t happen.
The “overpayment” here is accounting-only, not real. The OTA charged the guest the correct amount. The only mismatch is the rounding cents between lines inside Roomdoo.

​
It also appears on non-refundable cancellations

When a prepaid non-refundable reservation is cancelled, the guest has already paid the full amount, but the cancellation penalty Roomdoo generates only covers the nights. What breakfast or other extras cost stays as a remainder and the folio may show a credit balance, even though there’s no refund to process in reality. In this case the overpayment isn’t a few cents: it’s the amount of those extras.

​
How to confirm it’s a false cent-level overpayment

1

Open the reservation

From the planning, click the reservation. The payment status shows in the top-right corner.
2

Check the amount

If the overpayment shown is 0.01 € to 0.03 € and it’s a prepaid OTA reservation (the payment came in on its own with the reservation), it’s almost always a rounding mismatch, not a real extra payment.
3

Review the payments

In the Payments tab, check there’s no duplicate payment. If there’s only one payment and its amount matches what the OTA reported, it’s confirmed: a rounding mismatch.
If the overpayment is for a larger amount (several euros) and doesn’t come from a non-refundable cancellation, it’s no longer a rounding issue: it’s likely a duplicate charge, an unapplied refund, or a payment error. See Real overpayment or go straight to contacting support.

​
Common cases

The most typical case. Rounding between room, breakfast, and tourist tax generated a 1-3 cent difference. The reservation has been charged correctly; only the accounting layer needs cleaning.Since that payment came in automatically with the OTA reservation, don’t edit or cancel it yourself: contact support with the booking reference and we’ll adjust it.
When a non-refundable booking is cancelled, the guest has paid the full amount but the penalty only covers the nights, not breakfast or other extras. The remaining amount is logged as an overpayment.This is the expected behaviour. Since the payment came in with the OTA reservation, check with support before changing it and we’ll adjust it.
If you spot a recurring pattern (several reservations on the same day with small mismatches), send us the list in a single message to support. We’ll process it in batch and check whether there’s a systemic issue with the channel manager mapping.
For day-to-day operations, yes: the real payment is complete. But for accounting and month-end closing, those cents leave the folio balance off. If your property runs strict monthly closes, it’s worth clearing them. If not, you can accumulate several and ask us to fix them in bulk.

​
When to contact support

When you need to adjust the overpayment. Although Roomdoo lets you edit and cancel payments, the ones that come in automatically with the OTA reservation are best adjusted by support. When you contact support, include:
  • Booking reference (or several if it’s a batch)
  • Overpayment amount
  • Origin OTA (Booking, Expedia, etc.)
Don’t try to “undercharge” the guest’s next reservation to compensate the mismatch, or cancel the payment that came in with the OTA reservation. Any manual accounting adjustment outside the proper flow leaves the books off-balance at month-end.