|
|
|
Comp Accounting and Messages
The comp accounting functionality is available with the following license codes.
OPERA provides the means to assign guest charges on a transaction basis to comp windows for settlement. When the license code OPP_GCA is activated, an additional eight comp windows are available. As transactions are moved to a comp window, OPERA notifies the PTS of the comp request if the license code OPX_GA2 is active and the proper business events are setup. The PTS is responsible for determining whether the comp is allowed and responds appropriately.
A sample folio detail window is displayed below:
OPERA configuration includes the ability to set up Authorizers. You must select an authorizer from the list of OPERA application users and can choose to assign a default accounts receivable number (to which the Comp folio will be settled), and transactions codes, which the authorizer is allowed to comp. If you choose to not enter an accounts receivable number, when the cashier checks out the guest or the folios, a payment method must be selected for the comp windows.
As OPERA needs to move charges manually and automatically to the comp folios, the ability to setup comp routing instructions is available. When routing instructions are entered to a comp window, the associated authorizer code will be validated to ensure that the authorizer is eligible to comp the selected transaction codes. An application setting determines whether an authorizer password is required at this time. OPERA will not allow you to set up comp routing instructions to two or more different authorizers within the same comp window.
The same rules above will be applied when attempting to use the posting transfer option. The authorizer code will be checked and it will be validated that the associated transaction codes are linked to this authorizer before the posting move is allowed.
As charges are moved to and from the associated comp folios, these postings will be sent to the PTS for guests with the appropriate membership type (as defined in the application setting) and player ID in the profile. The membership will be defined as part of the business event conditions in OPERA. Each time a transaction to or from a comp folio takes place, the interface will transmit these charges in real time to the PTS. In the event of rejection by PTS, these postings will still remain on the respective comp folio, but will internally be marked, allowing for review through a report/screen that in turn will allow the operation to handle the rejection accordingly.
The OXI part of the interface has a conversion setup allowing the translation of OPERA transaction codes into PTS revenue codes to ensure that the appropriate association between the two different systems takes place.
At any time the user can view the comp folios and print them as necessary. If the authorizer attached to the comp window does not have an Accounts Receivable account attached, the user must settle these windows using a payment method. OPERA will only auto-settle these comp folios if an AR number has been attached to the respective authorizer. If this is not the case, the checkout will not be allowed until the balance is equal to zero.
During the normal guest check out any associated comp charges on the comp folios will automatically be posted to the respective authorizer’s AR account, if that has been setup. Users will be able to see them after the night audit has happened and the folio has been transferred into AR should it be necessary to view the detailed comp charges per authorizer per guest. The property will be responsible for writing off or billing the charges to the casino based on the respective operational business rules. When comp transaction codes are created, it is associated with the main transaction code.
Example: Transaction code 1000 (room Revenue) has been created. Comp Transaction code 6000 (Comp Room Revenue) has been created and is associated to transaction code 1000. This indicates that if a transaction code 1000 is moved from a cash window to a comp window the charge will be deducted from transaction code 1000 and reposted to 6000. OPERA has the can set up generates (automatically generated transaction codes) to a transaction code. In the example of Room Revenue, transaction code 1000 may have transaction code 8000 (Room Tax) automatically post 10% of the price when posted. When setting up the comp transaction code 6000, the property also can set up a generate as well. The determination needs to be made from the property if when comping a charge is it taxable?
Transaction code 1000 (Room Revenue) with Generate 8000 (Room Tax) 10%.
Transaction code 6000 (Comp Room Revenue) no generate
A Guest bill shows $200.00 under transaction code 1000 and 20.00 for transaction code 8000. When the $200.00 charge is moved to a comp window, a negative posting to transaction code 1000 for $200.00 and 8000 for $20.00 will be made on today’s business date and a new posting on the comp window will be posted at $200.00 for transaction code 6000 (no generates, as the comp transaction code 6000 does not have generates associated.
Transaction code 1000 (Room Revenue) with Generate 8000 (Room Tax) 10%.
Transaction code 6000 (Comp Room Revenue) with Generate 8050 (Comp Room Tax) 10%
The only change in this example from the first example is when the comp transaction is posted it will have $200.00 for transaction code 6000 and $20.00 for transaction code 8050.
An application setting exists for STAGED TRANSACTIONS DURING CHECKOUT. If a comp posting was sent to the PTS and the PTS system did not send back an 'approved' message (or does not choose to use this functionality), OPERA needs to know what to do upon checkout if the posting is not approved.
The application setting allows a property to indicate:
Any charges moved to or from a comp folio need to be sent to the PTS through the use of the OPERA business events.
An appropriate permission determines that charges currently residing on the guest folio can be moved to the comp folio.
A CompPostRequest message is sent by OPERA pursuant to a business event created upon activity on a comp folio. The PTS should respond with a CompPostResponse message indicating whether the comp is approved or declined. If that response is successful, it will also contain the PTS comp ID.
