Late payment on a rejected booking

A guest can pay after the booking has already been rejected for non-payment. That happens when someone leaves the payment screen open and clicks pay a few minutes later: the payment link in the e-mail is blocked by then, but the screen that was already open is not. So the payment simply arrives on a booking whose slot has been released.

What i-Reserve does

i-Reserve works out where "paid" should lead from the automatic transitions you configured on the product. Transitions count when all three apply:

• the action is Change status;
• the trigger is the moment the booking is paid or payment schedule paid;
• the transition sits on this product (or on the main product this one belongs to).

What counts is the number of distinct target statuses, not the number of rows. With 10 NEW → 30 PAID and 20 OPTION → 30 PAID you have two rows and one target status, 30. That is unambiguous.

When is the booking reinstated?

If the target status is unambiguous and the slot is still free, i-Reserve moves the booking to that paid status itself. The guest then receives the confirmation that belongs to that status. Nothing has to be configured for this and nothing lands on the check list.

In every other case the booking appears on the Check list, with the reason next to it:

• Slot taken — the target status was clear, but the slot has been sold to someone else in the meantime. i-Reserve does not put the booking back on top of it.
• No paid status — this product has no automatic transition on payment, so there is nothing to derive.
• More than one paid status — the payment transitions of this product point at different statuses. i-Reserve does not pick one, because that would be guessing.

What you can configure

• To let late payments sort themselves out as often as possible, make sure the payment transitions of a product all point at the same status.
• If you already configured an automatic transition from the rejected status — for instance 80 REJECTED → 30 PAID on "is paid" — i-Reserve leaves it to that transition and stays out of the way. Note that such a transition of your own does not check whether the slot is still free.
• Switch on the notification A guest paid for a booking that was no longer valid in your profile. It is sent in both cases, including when the booking was reinstated automatically: the guest saw a rejection earlier and deserves a call.

See also

Reviewing and processing a late payment — what to do when a row is waiting on the check list.