Routing Limits

Use routing limit to impose a limit on the total value of transactions that can be routed to a sub-account. For example, a guest’s company might only agree to pay a certain amount or percentage of the bill or only pay certain expenses for their employee. This agreed amount or percentage of the reservation account can be routed to a specific sub-account so that payment is made by the company’s credit card and the remaining balance in another sub-account is settled by the guest.

Routing limits are defined on the routing instructions as either an Amount, Percentage or Covers.

• With an Amount limit, you can specify a maximum amount for the routing instruction. For example, if you set a limit of 200 on a window routing instruction for transaction code 1001, the first 200 charged by the guest to transaction code 1001 would be routed per the instruction to sub-account #2. Any overage will automatically be split and transferred to sub-account #1. If the routing instruction was set up for room routing, the first 200 would post to sub-account #1of the target room and any overage would automatically be split and transferred to sub-account #1 on the originating reservation account.

• With Percentage limit, you can route a percentage of the transactions associated with the routing instruction. For example, if 10 is defined for the routing instruction percentage, 10% of each charge is routed. Generated charges such as taxes and service charges are also split by the specified percentage.

• Covers limit is used for interface for example, POS) postings only. Specify the number of covers the value of which s to be routed by the routing instruction. When charges are made through an interface against any of the transaction codes included in the routing instruction, OPERA Cloud divides each charge by the number of covers specified by the interface. If the number of POS covers is greater than or equal to the number of covers on the routing instruction, the per-cover charge is multiplied by the number of covers on the routing instruction and that amount is routed. If the number of POS covers is less than the number of covers on the routing instruction, the charge will not be routed.

Reference Field Notations when Routing Limits are Applied

When routing limits are applied to a charge, the Reference field has details of the original charge and how the charge was split.

For example:

Assume routing is set up for transaction code 5500 with a 20% limit. Charges are to be routed from Room 600 to Room 601 and the guest in Room 600 posts a charge to transaction code 5500 of $200.

The Amount field in the charge details is $160 and the Reference field would read: 200.00 auto routing split into 40.00 and 160.00 For the reservation account (Room 601) receiving the split charge, the Amount field in the charge details would is $40.00 and the Reference would read: 200.00 auto routing split into 40.00 and 160.00. Routed from Guestname Of Room #600.

The following rules govern the behavior of routing limits:

• Routing limits cannot be defined when the * routing code is selected.

• Package wrapper transaction codes cannot be selected.

• When the routing instruction is set up for multiple routing codes (or multiple transaction codes or a mix of transaction codes plus routing codes), the routing limit applies to the sum of charges against all transaction codes included in the routing instruction.

• When routing a charge for an inclusive transaction code, the value is routed. This includes the generates (taxes and service charges).

• When routing a charge for an exclusive transaction code, the value of any generates is not routed.

• If the limit is changed after a transaction has been routed, a folio refresh shows an increase or decrease in the routed amount, if appropriate.

• When transferring postings to a target room, the routing limit for the routing instruction is observed. Only an amount up to the routing limit can be transferred to the target folio.

• When moving charges between sub-accounts, the routing limit for the target sub-account is observed. Only an amount up to the routing limit can be moved to the target window.

• Routing limits and splitting behavior are observed by End of Day and Point of Sale (POS) postings.

• Routing limits can be set up for selected dates of a multi-night stay.

• Routing limits for multi-night stays are based on the business date when the revenue is realized. A pro forma folio or advance bill for a multi-night stay with routing applied separately to each date of the stay reflects routed charges and routing limits by business date. For example, assume a 4 - night reservation has a rate code of 100 per night. Routing instructions are configured such that each night's room charge is routed to a separate window with a 50 limit for each routing instruction. When an advance bill for the entire stay is generated, routing limits are applied by date.