OPERA: Order posting into the PMS

The following content was translated using AI and reviewed by our team. Please note that some images are still being updated.

Sales and, if desired, redemptions are posted by incert directly into Oracle OPERA using Paymasters, Payment Methods, and Transaction Codes.

If you are interested in this interface, we would be happy to hear from you at sales@incert.at. OPERA must provide OHIP, and we require the ability to create an interface user.

Postings and terminology

A posting in OPERA always consists of a “Paymaster” and either a “Transaction Code” or a “Payment Method”.

  • Paymasters are rooms in OPERA, with predefined “accounting rooms” used for bookkeeping purposes. Typically, there is a dedicated room for voucher postings.
  • Transaction Codes and Payment Methods are purpose-specific posting accounts. OPERA distinguishes Transaction Codes for charges and Payment Methods for payments. They correspond to what Fidelio referred to as revenue groups (Transaction Codes) and payment groups (Payment Methods).

Sales postings

Payment Posting the full order amount to Paymaster and Payment Method.
  • For the payment method “Room Charge”, no posting is made.
Item Posting the item value to Paymaster and Transaction Code.
  • One posting per item.
  • A custom Transaction Code may be assigned per item.
  • For sponsoring purchases, an alternative Transaction Code can be defined and used instead of the item’s Transaction Code.

Shipping costs

(only if shipping charges apply in the order)

 Posting the shipping amount to Paymaster and Transaction Code.
  • Posted without VAT.

Discounts

(only if a discount was applied)

 Posting the difference between items and payment to Paymaster and a discount account.
  • Posted as a discount product.

Voucher as payment method

(only when a voucher is used as a payment method during the purchase of tickets or products)

 Posting the voucher amount used for payment to Paymaster and a designated Payment Method for voucher payments.
  • Additionally, the voucher redemption is posted if applicable (see redemption postings).

Redemption postings

Reversal of sale Posting the redemption amount to Paymaster and Transaction Code.
  • Reverses the original item posting made during the sale.
  • For vouchers not posted in OPERA at the time of sale, custom posting accounts may be defined.
Redemption posting Posting the redemption amount to Paymaster and Payment Method.
  • Reverses the payment posted by a POS, PMS, or the incert redemption posting interface for the consumption invoice paid with a voucher.

Required configuration

To configure the interface, you must provide the desired posting accounts. These typically include:

  • Paymaster for incert vouchers and, if desired, separate Paymasters for sponsoring vouchers (and optionally for imported legacy vouchers)
  • Transaction Codes for voucher sales (and optionally for ticket or product sales), and if required, separate codes for sponsoring vouchers.
  • Payment Method for voucher redemption (and optionally for ticket redemption), including for redeeming sponsoring vouchers.
  • Transaction Codes for discounts and for shipping/fees.
  • Payment Methods for all payment types used in the incert system (online and internal), including sponsoring, and optionally separate accounts per card brand for online credit card payments.

Once commissioned, you will receive a configuration form and support documentation. We will also require information about your OPERA instance (chain and property code, version, property URL, cashier number), and an “Integration User” must be authorized in OPERA. Your project manager will provide further details after commissioning.

Important notes

  • Voucher redemptions are recorded in both OPERA and incert. There is also a separate (and compatible) redemption posting interface, which allows voucher redemptions in incert to be posted directly to a guest invoice in OPERA.
  • This interface is not suitable for portal systems and is designed for a single OPERA instance. Multi-property scenarios are supported only by the redemption posting interface.
  • If necessary, individual items can be configured so that their sale and/or redemption is not posted.
  • Redemption posting is optional and can be completely disabled if desired.
  • Redemptions of imported legacy vouchers can also be posted. Separate posting accounts can be defined for these.

Was this article helpful?

0 out of 0 found this helpful