How does Thynk use OPERA Cloud transaction codes as accounting categories?

In Thynk, each Accounting Category corresponds to a transaction code in OPERA Cloud. This one-to-one link keeps the revenue Thynk sends to the PMS aligned with the property's existing financial set-up.

When a property is connected to OPERA Cloud through the Oracle Hospitality Integration Platform (OHIP), Thynk can fetch its transaction codes directly through the API and import them as Accounting Categories. Hotels don't need to export lists from OPERA or type codes in by hand, and for new OPERA Cloud customers this import is part of onboarding.

Once the Accounting Categories are in Thynk, the set-up follows three simple steps:

• Import: fetch the OPERA transaction codes into Thynk as Accounting Categories, with the transaction code stored in each category's Code.
• Map to Revenue Categories: link each Accounting Category to the right Revenue Category, such as rooms, food, beverage or meeting space.
• Assign to Products: set the Accounting Category on each Product, referencing the familiar transaction code.

When Thynk posts charges to OPERA Cloud, it uses the transaction code from the Accounting Category, so every charge lands on the correct code in the PMS without the product itself needing to exist in OPERA. OPERA's own export mappings to the general ledger stay in place, so the property's back-office and finance interface continues exactly as before.