ZenotiHelp

Connect Oracle Opera PMS

ZTZenoti Docs Team Updated September 5, 2026 12 min readGuide

Integrate Zenoti with Oracle Opera so service, retail, class, membership, and package charges post directly to a hotel guest's Opera folio. Zenoti supports both on-premise Opera (via HTNG 2008B SOAP) and Opera Cloud (via REST API), configured at the center level.


On this page


Supported deployment models

Opera ships in two deployment models. Zenoti integrates with both, but the setup and credential fields differ.

Deployment Zenoti integration type Protocol Endpoint style
Opera on-premise (installed at the property) Opera HTNG SOAP/XML over HTNG 2008B Hotel-hosted URL (HTNG2008B_URI)
Opera Cloud (Oracle-hosted) Opera Cloud REST/JSON https://<host>.oraclehospitality.com

Pick the model that matches your property. A single Zenoti center connects to exactly one Opera deployment. If your organisation operates hotels on both models, configure each center according to its property.

Note: "On-premise cloud" is not a supported deployment model. If you see this term in legacy documentation, treat it as obsolete and configure either Opera HTNG or Opera Cloud based on where your Opera instance runs.


Before you begin

Permission: You need organization administrator access to configure PMS integrations.

  • Opera version: HTNG integration is certified for Opera 5.0.04.03 and above. Opera Cloud integration requires an Opera Cloud subscription with REST API access enabled.
  • Opera-side service account: your hotel Opera administrator must create an HTNG service account (for on-premise) or an OAuth client (for Opera Cloud) with permission to post charges, look up reservations, and send reservation status notifications.
  • Oracle portal access: for Opera Cloud, you need credentials obtained from the Oracle Identity Self-Service Portal (OAuth username/password, scope, client id, client secret) and the Oracle Hospitality Developer Portal (AppKey, HostName).
  • Network connectivity: your Opera server must be able to reach Zenoti's HTNG notification endpoint over outbound HTTPS (port 443). Work with your network team to whitelist the Zenoti URL provided during setup. Plain HTTP is not supported.
  • Sandbox / test property: validate the full posting flow (charge, refund, walk-in, cross-center if applicable) against a test Opera property before enabling the integration for live bookings.
  • Prerequisite in Zenoti: create a custom payment method named "Charge Room" (or similar) to represent room charges β€” covered in the next section.

If you do not have direct access to the Oracle portals, open a ticket with Zenoti Support before starting; Zenoti cannot obtain Oracle credentials on your behalf, but Support can confirm exactly which values are required.


Create a custom payment method in Zenoti

Before you connect Opera, create a custom payment method that represents a room charge. The PMS accordion asks for it as the Agent Name.

  1. Navigate to Configuration > Payments > Custom payments and add a custom payment method, for example "Charge Room". See Configure custom payment methods.
  2. Make the payment method available at every center that posts to Opera.

This payment method appears in the POS (Point of Sale) when staff post a charge to a room folio.


Open the PMS accordion

The Opera connection is configured per center on the center's settings page.

  1. Select the center in the scope selector, then navigate to Configuration > Payments > Settings (at center scope the Payments section row is captioned Settings).
  2. Expand the PMS accordion. It renders only when property management integration is enabled for both your organization and the center; if the accordion is absent, the integration has not been enabled for that center. The accordion notes: If you enable the setting, Enable PMS Integration at the center level from the Payment section, you can change the PMS settings.
  3. Turn on Enable PMS Integration. The accordion holds the provider, the credential fields for that provider, the posting switches, the payment mapping grid, and manual sync.

Connect Opera HTNG (on-premise)

Use this path when Opera is installed at the hotel property.

  1. In the PMS accordion, choose the on-premise Opera provider in Provider (the list opens on Select Provider). Zenoti shows the integration's Id once settings are saved.

  2. Enter the following credentials. All values come from the hotel's Opera administrator; Zenoti does not supply defaults.

    Field Source What to enter
    Username HTNG service account (hotel Opera administrator) The HTNG basic-auth username created on the Opera side. Do not use a placeholder string.
    Password HTNG service account (hotel Opera administrator) The HTNG basic-auth password. Do not use a placeholder string.
    HTNG2008B_URI Hotel Opera administrator The primary SOAP endpoint URL for HTNG 2008B messages. Request this from the hotel's Opera integration consultant.
    HTNG2008BExt_URI Hotel Opera administrator The extended SOAP endpoint URL for profile and reservation lookups. Request this alongside HTNG2008B_URI.
    CashierEmpId Hotel Opera POS administrator The Opera POS cashier identifier used on posted charges. The admin obtains this from the hotel's Opera POS configuration.
    ServerEmpId Hotel Opera POS administrator The Opera POS server/employee identifier. Same source as CashierEmpId.
    RevenueCenterCode Hotel Opera POS administrator Opera revenue center classification.
    VendorId Hotel Opera administrator Opera vendor identifier.
    ResortId Hotel Opera administrator Opera resort/property identifier.
  3. Choose the custom payment method in Agent Name (required).

  4. Configure BinMode and GroupCode β€” see the sections below.

  5. Select Save. Zenoti confirms with PMS Settings saved successfully, or rejects an empty form with PMS settings must not be empty.

Security note: HTNG credentials are property-specific. Never reuse credentials across properties, and rotate them if staff with access leave the hotel. Zenoti stores the credentials encrypted at rest.


Connect Opera Cloud

Use this path when Opera is hosted by Oracle.

  1. Open the center's PMS accordion as described in Open the PMS accordion.

  2. In the PMS accordion, choose the Opera Cloud provider in Provider. With Opera Cloud selected, Search room numbers in Opera is unavailable, and the mapped payment type in the payment mapping grid is fixed by Zenoti.

  3. Enter the following credentials.

    Field Source Purpose
    Authentication type Zenoti configuration OAuth method (password or client_credentials)
    Username Oracle Identity Self-Service Portal OAuth username for token requests
    Password Oracle Identity Self-Service Portal OAuth password for token requests
    Scope Oracle Identity Self-Service Portal OAuth scope
    EnterpriseId Oracle Identity Self-Service Portal Enterprise identifier (required for multi-property chains)
    Client Id Oracle Identity Self-Service Portal OAuth client identifier
    Client Secret Oracle Identity Self-Service Portal OAuth client secret
    AppKey Oracle Hospitality Developer Portal Application key sent as x-app-key header
    HostName Oracle Hospitality Developer Portal Base URL for Opera Cloud REST API (for example, https://hostname.oraclehospitality.com)
    HotelId Hotel Opera administrator Hotel property code sent as x-hotelid header
    CashierId Hotel Opera administrator Cashier reference ID for charge posting
  4. Choose the custom payment method in Agent Name (required).

  5. Configure BinMode and GroupCode β€” see the sections below.

  6. Select Save. Zenoti confirms with PMS Settings saved successfully, or rejects an empty form with PMS settings must not be empty.

If you do not have access to the Oracle portals, open a Zenoti Support ticket. Support can confirm which values are required; the hotel's Oracle administrator must retrieve the actual values.


Configure transcode mapping (Bin Mode)

A Bin is an Opera transcode bucket β€” a grouping that tells Opera how to classify a posted charge for revenue reporting. Every charge Zenoti posts includes a transcode that must match a transcode configured in Opera.

BinMode controls how Zenoti maps its service categories to Opera transcodes:

BinMode Maps charges by When to use
Category Zenoti service category (for example, Hair, Spa, Nails, Retail) Your Opera property reports revenue by service type. Each Zenoti category resolves to one Opera transcode.
BU Zenoti business unit (for example, Resort Spa, City Spa) Your Opera property reports revenue by business unit or outlet. Each business unit resolves to one Opera transcode.

Map Opera transcodes to Zenoti items

Transcodes are defined in the hotel's Opera system by the hotel's finance team. For each category or business unit you plan to post, record the Opera transcode and enter it into Zenoti.

  1. In the PMS accordion, select Configure BIN mappings. A separate Configure Tax BIN mappings link covers tax transcodes.
  2. For each category or business unit row, enter the Opera transcodes: the main transaction code and the codes for tax, tip, support staff gratuity, fee, and discount.
  3. Save.
  4. You can apply mappings at the Resort ID level (one set for the whole property) or at the BU level (separate sets per business unit). Choose based on how your Opera property is configured.

Getting transcodes wrong causes postings to land in the wrong Opera revenue bucket β€” charges still post, but reporting is inaccurate. Verify the mapping with the hotel's Opera administrator before going live.


Configure PM rooms and auto-balancing (Opera side)

Some postings β€” walk-in guests, non-room service sales, cross-center postings for checked-out guests β€” cannot target a live guest room. Opera handles these via Payment Method (PM) rooms: pseudo-rooms that act as placeholders for each payment type.

These are configured in Opera, by the hotel's Opera administrator:

  1. Log in to Opera as an administrator.
  2. Create one PM room per accepted walk-in payment type (for example, one for Cash, one for Card, one for Cheque). The room number convention is your choice β€” some properties use a 9000–9003 pattern, but any numbers that do not conflict with real rooms work.
  3. Enable auto-balancing for PM rooms. The exact menu location varies by Opera version and is typically found under Financial Settings or Account Preferences. Refer to your Oracle documentation for the version-specific path.
  4. Record the PM room numbers β€” you will enter them in Zenoti in the next section.

Zenoti cannot validate PM room setup from its side. Incorrect setup surfaces as failed postings in the Opera transaction audit.


Configure payment mapping for walk-in guests

Once PM rooms exist in Opera, map each Zenoti payment type to its PM room in the PMS accordion.

  1. Turn on Post Non Room Charge to PMS.

  2. Under Payment Mapping, complete a row for each payment type offered to walk-in guests: Payment Type Name, Mapped Payment Type, Payment Method, and Mapped Room Number (the PM room configured in Opera), then select Add. Zenoti requires the mapped payment type and room number (Please select a Mapped Payment Type, Please select a Mapped Room Number) and confirms with Payment mapping saved successfully.

    Zenoti payment type Example PM room Notes
    Cash 9000 The number is hotel-side; it is not mandated by Zenoti.
    Card 9001 β€”
    Cheque 9002 β€”
    Other 9003 Configure additional PM rooms as needed.
  3. Select Save.

When a walk-in guest pays at the POS, Zenoti routes the posting to the PM room matching the payment type. The hotel's auto-balancing in Opera reconciles PM-room postings against the end-of-day payment totals.

Two further switches sit above the mapping grid: Ignore guest status updates stops Opera check-in and check-out messages from changing guest status in Zenoti, and Search room numbers in Opera lets the POS look a room number up in Opera (on-premise Opera only).


Re-post transactions manually

Under Manual Sync Transactions, pick a business date in Choose a date and select Post Pending to send that day's unposted charges, or Post Failed to retry the charges Opera rejected.


Configure the room reservation notification URL

For Zenoti to show in-house guests and their reservations during booking, Opera must send reservation status updates to Zenoti.

  1. Ask Zenoti Support for your tenant's HTNG reservation status notification URL.
  2. Share the URL with the hotel's Opera administrator or Oracle support so Opera can be configured to POST HTNG reservation status messages to it.
  3. Opera must reach this URL over outbound HTTPS (port 443). Ensure the URL is whitelisted on the Opera network.

If the network change is pending, Zenoti still accepts manual room-number entry at the POS, but live reservation lookups will not appear.


Enable cross-center posting

Use GroupCode when multiple Zenoti centers should be able to post charges to the same Opera property β€” for example, when a single hotel group operates several spas, salons, or retail outlets that all bill to a shared set of guest folios.

  1. Agree on a GroupCode value with the hotel's Opera administrator and the Zenoti administrator. Any string works; common choices are the hotel brand or property code.
  2. In each participating center's PMS accordion, enter the same GroupCode value.
  3. Save.

Centers that share a GroupCode can post charges to any room in any participating center's Opera property. The revenue still belongs to the center that performed the service β€” only the posting is routed to the guest's host property. See Post charges to Opera PMS for the cross-center workflow and revenue-attribution details.


Sync secondary guests (Opera Cloud)

Opera Cloud integrations retrieve all guests registered under a reservation (primary plus accompanying guests) so staff can select the right person when booking or billing. This applies to active reservations received from Opera; historical invoices are not retroactively updated with secondary-guest links. Room charge configuration and posting behaviour are unchanged.

This capability is available for Opera Cloud only. HTNG (on-premise) integrations do not support secondary guest sync.


Verify the integration

After saving all settings:

  1. Create a test reservation in Opera with a non-production guest.
  2. Book a small service in Zenoti and post the charge to the test room using the Charge Room custom payment method.
  3. Confirm the charge appears on the folio in Opera with the correct transcode.
  4. Issue a refund in Zenoti and confirm a negative posting appears on the Opera folio.
  5. Clean up the test reservation when done.

If any step fails, see Troubleshooting below.


What to configure next

Required:

  • Post charges to Opera PMS β€” complete the day-to-day workflow for posting, refunding, editing, and reconciling charges.

Recommended:


Tips

  • The BinMode setting must match the revenue bucket convention configured in Opera. Confirm with your Opera administrator before choosing Category vs BU.
  • Use GroupCode only when multiple Zenoti centers genuinely share Opera folios β€” otherwise leave it blank.
  • If the property uses more than one currency or tax regime, confirm that the Opera transcodes are configured to handle the secondary values before enabling posting for those centers.
  • After connecting, always run the verification flow (Verify the integration) against a test reservation before exposing the integration to live bookings.

Troubleshooting

Symptom Likely cause Resolution
Postings fail with an authentication error (HTNG). Wrong Username / Password, or the HTNG service account is disabled on the Opera side. Ask the hotel Opera administrator to verify the service account is active. Re-enter the credentials in Zenoti exactly as provided β€” leading/trailing whitespace is a common issue.
Postings fail with "endpoint unreachable". Network path between Zenoti and Opera is blocked, or HTNG2008B_URI is wrong. Verify outbound HTTPS from the Opera server to the Zenoti URL is allowed. Re-check the URI value with the hotel admin.
Charges post, but reservation lookups return no rooms. Opera is not sending reservation status notifications to Zenoti. Confirm the hotel's Opera admin has configured the Room Reservation Notification URL and that outbound traffic from Opera to that URL is allowed.
Charges post but land in the wrong Opera revenue bucket. BinMode or transcode mapping is incorrect. Review transcode mapping with the hotel finance team.
Walk-in charges are rejected. Post Non Room Charge to PMS is disabled, or PM rooms are not configured in Opera. Enable the setting and confirm PM rooms exist in Opera with auto-balancing on.
Secondary guests do not appear at booking. HTNG integration (not supported) or the reservation has no accompanying guests. Secondary guest sync is Opera Cloud only. For HTNG, staff selects the primary guest.

Was this article helpful?
Your feedback helps us improve our documentation.