Opera Cloud configurations

1. Create a new External System under Interfaces > Business Events. We recommend to name it MOBIPAID. The External Database can be auto configured.
   
2. Create the following 3 Business Events under Interfaces > Business Events. All Business Events should be assigned to the External System created in step 1. The module for each Business Event is RESERVATION.
1. Business Event for NEW RESERVATION. The recommended Data Elements and Conditions are RATE CODE and PAYMENT METHOD.
   
2. Business Event for UPDATE RESERVATION. The recommended Data Elements and Conditions are RATE CODE and PAYMENT METHOD.
   
3. Business Event for CANCEL. The recommended Data Elements and Conditions are RATE CODE and PAYMENT METHOD.
   
3. For each Business Event created in step 2, ensure that all Data Elements available are selected.
4. Deposit Rules must be created for each deposit, which should be collected by the Connector. If more than one deposit payment is to be collected for a certain Rate Code, then these deposit rules must be percentage based, and the due dates set as days offset arrival.
   
5. Deposit Rule Schedules must be created for each rate code, for which the Connector should manage deposit payments. The Deposit Rule for each Rate Code should be the first deposit which is to be collected. Any subsequent deposit payments will be managed by the Connector.
6. We recommend to create a separate Cashier for the Connector. Transactions posted by the Connector will then be assigned to this Cashier.
   
7. We also recommend to create a separate Payment Method for the Connector. This creates flexibility when setting the conditions for the Business Events created in step 3 above.
   

When setting the Conditions for the Business Events, we recommend using the IN operator for the RATE CODES.

The first deposit to be collected, must be assigned to the Rate Code in the Deposit Rule Schedules. If there are multiple deposits to be collected for a particular rate code, the Deposit Rules must be percentage based and scheduled based on the date of arrival.

Connector Configuration

1. For Rate Codes, which have more than one scheduled deposit payment, the Deposit Rules must be setup on the Connector. Opera will post the first deposit defined in the Deposit Rule Schedule. Subsequent deposit rules will be posted to the reservation on the day they are due, and payment instructions are sent to the guest.
   
2. By default the Connector will post deposit payments directly against the deposit policy it relates to. This ensures that the outstanding balances for each deposit payment are settled. If requested, this can be switched off. To avoid unallocated payments on the reservation, hotel staff would have to manually allocate the payment.
   
3. In a multicurrency environment the rate currency may differ from the base currency. In such cases, the Connector can collect deposits in rate currency instead of the system base currency. This must be activated for the hotel in the Connector.
   

Posting payments directly against the corresponding deposit policy, may affect stationary management in Opera. If your hotel handles stationary in Opera for deposit payments, the post direct option may have to be disabled. Refer to point 2 above.