1 Business Context
This implementation guide explains the best practice usage of Oracle Hospitality API operations to post charges from In-house property systems (such as, Phone, Video, Minibar, Point-of-Sale, HSIA in-room Internet, or other Guest Services systems) to Oracle Hospitality OPERA Cloud reservations or posting accounts.
Note:
API usage and capabilities are subject to change. For more information on API versioning, see the Versioning topic in the Oracle Hospitality Integration Platform User Guide.
For the most comprehensive and up-to-date information, including additional query parameters and detailed descriptions, always refer to the latest API specifications in GitHub. This will ensure that you are accessing the most current and complete set of features available.
Table 1-1 Use Cases
| Use Case | Description | Operation Id |
|---|---|---|
|
Post Simple charges to the guest account |
Posting charges with a single final amount against the reservation.
|
postBillingCharges |
|
Inquire to Reservation Information (Post Inquiry) |
Retrieving guest or reservation information prior to performing a charge posting and to verify if the reservation is eligible for receiving posting to the guest's account. This can also be used for guest information verification. For example, when a guest enters a room number and name, the partner system retrieves guest information that must be verified with the entered values before granting access to a partner system service. |
getReservations |
|
Post Point-of-Sale (POS), Golf, SPA or in-room-Internet charges to the guest account |
If a reservation is still checked in, posting charges with multiple sub-amounts for one guest check following an inquiry.
|
postBillingCharges |
|
Post non-room charges |
Post charge to Posting Master accounts. Usually revenue which guest has paid at partner system (Cash, AMEX, VISA etc). Related information shall be sent into OPERA Cloud PMS for accounting. |
postBillingCharges |
|
Post charges with auto-balance option |
Post additional automatic balance posting against the payment transaction code See below (Bookmark) for more details |
postBillingPayments |
The below functional diagram explains typical use cases for generating charges by a hotel guest during their stay.
Table 1-2 Workflow
| Diagram | Journey |
|---|---|
 |
Journey: Guest arrival The guest arrives at the hotel and checks in. The partner system retrieves the roomId, reservationId, and confirmationId. The partner system enables guest access to make phone calls, watch Pay TV, consume minibar, and so on. Journey: The guest consumes the available systems in the room. The guest makes billable phone calls, watches Pay TV, consumes the minibar, and so on. The partner system calculates the charge to post. The partner system posts the charge to OPERA Cloud PMS. OPERA Cloud posts the charge against the guest's reservation account. Journey: The guest consumes food and beverages in the restaurant and posts the bill amount to the room. The guest consumes food and beverages in the hotel restaurant and bar and requests to have bill posted to room. The guest writes name and room number on the check. The partner system user enters the guest’s room or name into the partner system and sends the reservation information request to OPERA Cloud PMS. OPERA Cloud sends back the reservation information. The partner system user compares and verifies the reservation information with the information the guest wrote down. The partner system user confirms the reservation information is correct and posts the charge to OPERA Cloud PMS. OPERA Cloud posts the charge against the guest's reservation account. OPERA Cloud PMS confirms the posting to the partner system. The partner system closes the guest’s check/bill. (Optional) The partner system generates the guest’s check and prints it out. (Optional) The partner system sends the guest’s check details to OPERA Cloud PMS. OPERA Cloud PMS stores the guest’s check details to the guest’s reservation. Journey: Guest consumes food and beverages in the restaurant and pays the bill by cash. Guest consumes food and beverages in the hotel restaurant and bar and requests to pay the check with Cash. The partner system posts the charge to the OPERA Cloud PMS defined posting account for cash payments. OPERA Cloud posts the charge against the posting account. OPERA Cloud PMS confirms posting to the partner system. (Optional) The partner system generates an auto-balance payment. The partner system posts the auto-balance payment to OPERA Cloud PMS. OPERA Cloud PMS confirms the auto-balance posting to the cash posting account. The partner system closes the guest’s check/bill. Journey: Guest wants to access high speed Internet (HSIA) in the hotel. The guest opens landing page on his device. The guest must enter room number and last name to authenticate being a checked in hotel guest. The partner system sends reservation information request to OPERA Cloud PMS. OPERA Cloud sends back reservation information. The partner system verifies the reservation information with the info the guest entered. The partner system confirms the reservation information is correct and posts the charge to OPERA Cloud PMS. OPERA Cloud posts the charge against the guest's reservation account. OPERA Cloud PMS confirms the posting to the partner system. The partner system grants access to the Internet. |