Same pattern as cent-level overpayment
This is the other side of the same issue described in Cent-mismatch overpayments.
When a reservation comes in from an OTA through the channel manager, the lines (room, breakfast, tourist tax, extras) are distributed and rounded independently. The sum can end up 1-3 cents above or below the total the OTA reports.
If the mismatch is in the customer’s favour (the sum is bigger), Roomdoo flags it as overpayment.
If the mismatch is against (the sum is smaller), Roomdoo shows the imported total, but breaking it down you find the lines don’t add up exactly.
When it’s a normal cent-level mismatch
- It’s 0.01 € to 0.03 €
- The reservation comes from an OTA (Booking, Expedia, Airbnb, etc.)
- There are several lines (room + extras)
In those cases, the real charge is fine — it’s just Roomdoo’s internal split that doesn’t add up perfectly.
When it’s NOT a normal mismatch
- The mismatch is larger than 0.05 €
- It only affects one specific reservation and the rest add up fine
- There’s a clear pattern (always the same OTA, always the same breakfast)
In those cases, it’s more than rounding and worth reviewing.
What to do
For small recurring mismatches:
- Don’t fix each reservation one by one
- Accumulate them and ask for batch cleanup at month-end in a single message
For larger mismatches or patterns:
- Contact support with several sample references
- We review the mapping between the channel manager and Roomdoo for that OTA
- The mismatch is more than a few cents.
- There’s a clear pattern (same OTA, same rate, same period).
- It affects monthly reporting and throws off the close.
Don’t manually edit the price in Roomdoo to “fix” the mismatch if the reservation is already charged. Breaking the coherence between charged and invoiced amounts leaves a different accounting mismatch from the original.