About Reservation Transaction Diversion
Prerequisites for Reservation Transaction Diversion
Transaction diversion is a process whereby charges for selected transaction codes are automatically "diverted" to a pseudo room reservation based on the membership type and level, or the VIP level of the primary profile linked to a reservation.
Transaction diversion rules determine the conditions under which the posting will be diverted. For example, a transaction diversion rule could state that charges for Internet access are to be diverted to pseudo room 9020 for reservations that have a Platinum level Priority Club membership attached.
The transaction diversion panel indicates if the threshold rule is property-level or reservation-level and if it is based on Count, Quantity, or Minutes. You can manage reservation-level diversion rules.
Note:
If a reservation has two threshold rules attached, either Property or Reservation lebel or a combination of the two , that both contain the same transaction code; the sequence associated with the rule will determine how the charge is processed and which PM room it is diverted to. The rule with the lowest sequence number has the highest priority.User Activity Logging of Transaction Diversions
A record is entered into the Changes Log (link: c_logs_changes_log.htm) under the Posting Activity Group : DIVERTED TRN. CODE <transaction code> FOR <amount> <local currency> FROM <guest name> OF ROOM #<room no> CONF. #<confirmation no> TO <guest name> OF ROOM #<room no> CONF. #<confirmation no>