Skip to main content

​
Why a cent-level overpayment appears

When a reservation comes in from an OTA (Booking, Expedia, Airbnb, etc.), it reaches Roomdoo through the channel manager (your channel manager (Wubook, the channel manager, etc.)). During the process, the system spreads the total amount across the reservation’s lines: room, breakfast, tourist tax, extras, and so on. Each line rounds independently to the cent. Added up, the lines can end up 1 or 2 cents above the total the OTA reported as paid. Roomdoo reads this as an overpayment and tags the reservation accordingly (on the calendar it shows in a specific colour).
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 non-refundable reservation is cancelled, the guest has already paid the full amount. If breakfast or other extras aren’t invoiced, that amount stays as a remainder and the folio may show a credit balance, even though there’s no refund to process in reality.

​
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 the reservation came from an OTA, 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), 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.You can’t fix it from the Roomdoo app — contact support with the booking reference. We sort it in minutes.
When a non-refundable booking is cancelled, the guest has paid the full amount but only part is invoiced (for example, only the room, not breakfast). The remaining amount is logged as an overpayment.This is by accounting design. Also can’t be cleaned from the Roomdoo app — contact support 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 Wubook or 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

Always when you need to adjust an overpayment — payments and accounting adjustments can’t be modified from the Roomdoo app. 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 delete the existing payment. Any manual accounting adjustment outside the proper flow leaves the books off-balance at month-end.