Your payout arrives by transfer. Every booking posts and reconciles itself.
Saves 1,5%
Ovimore Pay
Your OTA payments, handled.
The money arrives by transfer instead of by card, the booking posts itself at check-in, and the payout is matched against it.
Running live on Mews and Apaleo.
The route
You are paying 3% to avoid the bookkeeping.
A virtual card costs around 3%, and it posts and closes itself. That is why hotels take it. A bank transfer costs about 1,15% and leaves the bookkeeping on your desk. Ovimore Pay takes the cheaper route and does the bookkeeping.
Virtual card
Booking.com
virtual card
Your card terminal
Your account
No admin
~3%
Bank transfer
Booking.com
bank transfer
Your account
Admin by hand
~1,15%
With Ovimore Pay
Booking.com
bank transfer
Your account
No admin
~1,15%
The channels we support
Your payout arrives by transfer. Every booking posts and reconciles itself.
Saves 1,5%
Payouts already arrive by transfer. Every booking still posts and reconciles itself.
Saves the bookkeeping
Per booking
Follow one booking through.
A guest books in June, checks in on 12 August, and Booking pays out two weeks later. Ovimore does something at each of those three moments.
-
12 Jun
€ 486,00
The booking arrives
Recognized as Booking.com. The expected amount follows from the nights and the charges you agreed.
-
12 Aug
€ 486,00
The guest checks in
The payment posts into Mews, carrying the note "Ovimore Pay check-in capture". Nobody typed anything.
-
26 Aug
Settled
Booking pays out
The payout is matched against what was posted. Equal, so the reservation settles itself.
-
And when they disagree
€ 18 short
The difference is named, not averaged away
€ 198,00 expected against € 180,00 posted. It moves to your worklist with the gap on it, and it stays there until someone looks.
The boundary
Where it stops.
It posts what was agreed for your property and leaves the rest of the folio alone. These are not settings you have to remember.
Only the charges you named
Accommodation, plus whatever your property adds to it, such as a tourism fee. Everything else on the bill is left where it is.
Cancelled nights are not money
When a guest moves a stay, the cancelled nights stay on the same order in your PMS. They are never part of what posts.
Nothing from before you started
Reservations that checked in while we were setting you up are blocked, so nothing gets settled twice.
A cancelled reservation is left alone
It is skipped rather than guessed at. If money was already posted against it, it is flagged for a human.
One switch stops it
A property can be paused and it stops posting. Anything it posted can be reversed.
Everything carries our name
In your PMS each payment is noted as an Ovimore Pay capture, so what came from us is never a guess.
Getting live
You do not implement this.
One conversation about what counts as a channel stay at your hotel. The rest is our work, it takes a few hours, and a property can be live the same day.
-
1
We agree what counts with you
Which products belong to a channel stay at your hotel. Accommodation always, plus the extras you name.
-
2
We check it against your own numbers
Your reservation report against what Pay would post, line by line, and every reservation where the two disagree is put in front of you.
-
3
We post one real reservation
A real booking and a real amount, checked in your PMS, before anything else is switched on.
-
4
We block what came before
Everything that checked in during the setup is excluded, so no stay is settled twice.
-
5
We switch the payout route, you pick the day with you
Your PMS and your channel account go to bank transfer, and we go live on a date that suits you.
After that you look at the exceptions. That is the whole job.
What it runs on
Your PMS, as it is.
Pay reads and writes through the systems you already run. Nothing changes about how your front desk works.
