Improvements in Automatic Settlement Policies
We would love to see more intelligence when it comes to the automatic settlement policies. For example if we have a booking that pays 25% at time of booking, and 75% a week before arrival, the system will not take into account any payments made in between those two events. If the customer decides to pay their booking early, we rely on human intervention to cancel the scheduled payment, or the guest will get charged twice. We also have the option to close the bill to avoid re-charging, however this is impractical for us due to other complications with closed bills during the guest stay.
Ideally - the system would read the balance of the booking (balance of the booking - not of the profile, in case guest has multiple bookings) and charge accordingly. So if no balance remains, the guest would not get charged.
Rebecca Lane
shared this idea
-
Veronica
commented
Currently guests can online check-out with a balance to be paid on their bill, usually Food and Beverage items. This needs to be mitigated to streamline the customer's journey. As of now, automated settlements can be created for stays with only ONE trigger, however there needs to be the allowance for TWO triggers. The first one to charge for the start of the stay, and the second to charge at the end of the stay for items that were consumed after the first automatic settlement.