Configuring Transaction Diversion

Adding Transaction Diversions Rules

From the Administration menu, select Financial, select Transaction Management, and then select Transaction Diversion Rules.
Click New and complete the following.
1. Property. Confirm or select the property
2. Level: Select a level from the list
  1. Property: Rule applies to all reservations at the property.
  2. Reservation: Rule applies to selected reservation(s)
3. Code: Enter the code that identifies the transaction diversion rule. Up to 20 alphanumeric characters can be entered.
4. Description: Enter the description for the transaction diversion rule.
5. Rule Type: Select the rule type
  1. VIP: (Available when the VIP OPERA Control is active)
    1. VIP Level: Select a value from the list
  2. Membership.
    1. Membership Type: Select the membership type from the list.
    2. Membership Level: Select a membership level from the list (optional).
6. Transaction Codes: Click to search for and select the transaction codes. The list of transaction codes does not include package wrapper, generate transaction codes, package profit and package loss transaction codes, and OPERA Cloud system transaction codes.
7. Room: Search for and select the pseudo room reservation to which postings for this transaction diversion rule will be diverted.
8. Sequence: Enter a unique sequence number that determines the priority this transaction diversion rule has when OPERA Cloud must decide which pseudo room charges will be diverted to in the event that the same transaction code is attached to a membership rule and a VIP rule, both of which apply to the same reservation.
9. Thresholds (optional)
  1. Based on: Select a value from the list
    1. Count: Diversion occurs after a number of postings. Each posting may be more Qty > 1.
    2. Minutes: Diversion occurs based on the minutes attribute of the posting time.
    3. Quantity: Diversion occurs after a quantity is posted. Each posting may be more Qty > 1.
  2. Minimum Required: Enter the Counts, Quantities, or Minutes value that must be posted before diversion takes effect
  3. Calculation: Select a value from the list
    1. Per Day: The Minimum Required and Complimentary values apply to each day of the stay
    2. Per Stay: The Minimum Required and Complimentary values apply to the entire stay
  4. Complimentary. The Diversion Rule will be executed based on the complimentary value, after the Minimum Required number satisfied. For example: if Count is set to Minimum Required = 3 and Complimentary = 5, the following result will occur: OPERA Cloud will post 3 counts of charge for any of the selected transaction codes to the reservation folio; the diversion will begin when the 4th count of the charge is posted; OPERA Cloud will divert 5 counts of the charges to the designated PM reservation.
Click Save.

Editing Transaction Diversions Rules

From the Administration menu, select Financial, select Transaction Management, and then select Transaction Diversion Rules.
On the Transaction Diversion Rules screen, search for and select the required transaction diversion rule that you want to edit and then click on the vertical ellipsis.
Enter search criteria and click Search.
Select the diversion rule, click the vertical ellipsis and then click Edit.
1. Update the configuration as needed.
2. Inactive: Select checkbox to inactive the rule.
Click Save.

Deleting Transaction Diversions Rules

From the Administration menu, select Financial, select Transaction Management, and then select Transaction Diversion Rules.
Enter search criteria and click Search.
Select the diversion rule, click the vertical ellipsis and then click Delete.
Click Delete to confirm.