1. Introduction
Purpose of the Integration
The purpose of this integration is to ensure that not only room charges are seamlessly shared between Toast POS and Opera Cloud PMS, but also direct payments such as cash and credit card transactions. All postings are transferred based on the mapping and settings configured within the DataHub. This guide will walk you through how to properly configure these settings so that transactions are processed and reported accurately.
Benefits for Operations
Time savings: automated posting reduces the need for manual reconciliation.
Fewer human errors: consistent mapping ensures accurate reporting and folio postings.
Better guest experience: faster, more reliable charge-to-room and settlement handling.
Improved financial accuracy: direct payments and charges are correctly categorized and accounted for.
Intended Audience
Hotel IT staff responsible for system setup.
Front desk managers overseeing folio postings.
F&B managers ensuring accurate restaurant postings.
Accounting staff who typically manage and validate financial mappings and reconciliations.
Note: Typically, this setup should be completed by the person handling the hotel’s accounting or by a designated system administrator.
AI Video Walkthrough
For a step-by-step explanation of the onboarding process, you can watch our AI-powered video guide here: Toast to Opera Cloud - Full Rev Push
2. Guide overview
This guide offers comprehensive instructions on establishing and customizing the integration between Toast and Opera Cloud through DataHub to be able to post room charges. It comprises the following sections:
Introduction
General Info about the integration
Guide Overview
Overview over the sections of the document.
Preparations
List with Preparations that need to be setup in the Toast and Opera cloud.
Why Adjustment Mapping is Required
Explains why you must have the adjustment mapping
Disclaimer ⚠️
If adjustment mapping is not set up correctly, Omniboost cannot guarantee support in case of discrepancies with the full revenue push. In such cases, data must be manually corrected by the property’s accounting team.
Opera Cloud Configuration
Explains important configurations requirements with in Opera cloud for the integration.
Toast Configuration
Explains important configurations requirements with in Toast for the integration.
DataHub Configuration
Configuring POS (Toast) Settings
Configuring PMS (Opera) Settings
Configuring the mapping
Common issues
Common issues and how to resolve them.
Summary & Support
Summary on who to contact and were to contact them.
3. Preparations
Before beginning the integration setup, several transaction codes must be created in Opera Cloud.
A transaction code called ‘Fallback Toast’
A transaction code called ‘Fallback Payments Toast’
A transaction code called ‘Service Charge Toast’
A transaction code called ‘Gratuity Toast’
A transaction code for your local tax
Use this link to learn how to create a transaction code: Configuring Transaction Codes
Important: Each of the above transaction codes must also be created as an Adjustment Code in Opera Cloud.
Properties should also define their own transaction codes by Revenue Center or Meal Period, with matching Adjustment Codes.
Example:
Restaurant Food + Restaurant Food Adjustment
Restaurant Beverage + Restaurant Beverage Adjustment
Restaurant Liquor + Restaurant Liquor Adjustment
Restaurant Wine + Restaurant Wine Adjustment
Toast Preparations:
Sales Categories (align with Opera transaction codes)
Service Charges (e.g., gratuity, delivery charge)
Revenue Centers (e.g., Restaurant, Bar, Room Service)
To access DataHub, you'll also require an Authenticator app on your phone for the 2FA. We recommend using one of the following free apps:
Apple: Google Authenticator
Apple: Microsoft Authenticator
All must be configured before mapping in DataHub.
4. Why Adjustment Mapping is Required
Toast allows edits within a 90-day history window, while Opera Cloud folios (PI, PM, PF) may only remain open for a day, week, or month. Once a folio is closed, Opera cannot accept adjustments, but Toast may still generate them.
To solve this, Adjustment Codes are used:
The original receipt is voided in Opera using the Adjustment Code on the day the adjustment is made.
The corrected receipt is reposted on the day the adjustment was made.
Benefits:
Ensures adjustments from Toast are always reflected in Opera.
Maintains accurate and auditable records.
Keeps reconciliation consistent.
Disclaimer ⚠️
If adjustment mapping is not set up correctly, Omniboost cannot guarantee support in case of discrepancies with the full revenue push. In such cases, data must be manually corrected by the property’s accounting team.
5. Opera Cloud Configuration
5.1: Setup / Configure a PM.
PM Accounts start as pseudo rooms. These may need to be created under Admin → Inventory if they do not already exist. Once the pseudo PM rooms are created, charges can be posted to them, typically in a block situation.
Steps to configure:
From the OPERA Cloud menu, select Bookings → Blocks → Manage Block.
Enter the search criteria and click Search.
Select a block from the search results, then click I Want To… and select Posting Master.
The confirmation message is displayed.
Block Status: The block must be set to Definite (active/open) to allow Posting Master creation. Creating a PM for a Prospective or Tentative block may fail.
Rate Code Setup: The block’s rate code must include the PM room type and have a zero-rate schedule. Without this, OPERA will not allow PM reservation creation.
5.2: Setup / Configure a Transaction Code for Collecting Revenue
Navigate to via the burger menu to administration → Financial → Transaction Codes.
Than Press new on the right hand side of the screen.
Here you will see the following screen.
For revenue codes such as food beer wine etc its important that “Manual posting’’ is enabled. If this is not enabled the transaction code will not be loaded in to the DataHub.
For a payment transaction code it is important to have you payment type set to Other and to make sure that your Subgroup is also a payment subgroup.
5.3: Setup / Configure a Transaction Code & Payment Method
Navigate to Configuration → Financial → Payment Methods.
Create/confirm Cash, Credit Card, Room Charge.
Assign each to unique transaction codes.
6. Toast Configuration
6.1: Sales Categories
Log in to Toast Admin.
Navigate to Menu’s → Settings →Sales Categories.
Create categories (Food, Beverage, Wine, Liquor).
Save and publish.
6.2: Revenue Centers
Go to Revenue by using the search bar on top.
Create/confirm outlets (Restaurant, Bar, Room Service).
Save and publish.
7. DataHub Configuration
7.1: Configuring POS (Toast) Settings
Select the “On Room Payment Type”:
Choose the payment type that corresponds to Room Charges. Typically, this is labelled as Room Charge.
Configure “Tip Name”:
Customize the description for tips based on your preferences. For example, you can name it Tips, Gratuity, or any term you prefer. This description will be used for the transaction code.
Meal Periods & Split Tax:
If you are using meal periods or planning to map the transaction codes with breakfast, lunch and dinner; enable the Use Meal Periods checkbox.
Be sure that all hours are the same as on the Toast Web under the function ‘Service Hours’. Use the following link to learn how to view the Service Hours: Set Up Restaurant Hours and Services
Enable the Split Tax checkbox if you want to split out the different taxes. Otherwise, the system will use the total tax rate
7.2: Configuring PMS (Opera) Settings
The PMS settings define how Toast transactions are posted into Opera Cloud. Defaults can be applied globally or per Revenue Center and Meal Period. You can either setup a generic PMS settings page. Or you can configure this per revenue and meal period.
Important: If you want to break down by revenue center and meal period please and sure that all of them are filled out. Even if you do not use that meal period or revenue center.
Default Analysis Code
Fallback Toast code, used if a mapping is missing.
Default Analysis Code Adjustment
Fallback Adjustment code, used if an adjusted receipt originally used the fallback code.
Default Payment Code
Fallback Payment code, used if a payment method is not mapped.
Default Payment Code Adjustment
Fallback Payment Adjustment code, used if a fallback payment is adjusted.
Folio Window Number
Which folio window receives Toast charges. Default is 1.
VAT/TAX Inc. checkbox
Enable if prices from Toast include VAT (e.g., Europe). Leave unchecked in tax-exclusive countries (e.g., US, Canada).
Auto Balance Account checkbox
Enable to let Opera auto-balance debits and credits.
Use Package Allowance checkbox
Enable if Opera package allowances (e.g., meal credits) are used.
Select Payment Accounts
Map Toast payment methods to Opera accounts. Defaults to Pool PM accounts. Contact pos-support@omniboost.io to change to PI/PF.
VAT/TAX Buckets
Tax rates pulled from Toast must be linked to Opera codes (Tax %, Tax % Adjustment).
Service Charge Code
Opera code for generic service charges from Toast.
Service Charge Code Adjustment
Adjustment code for service charges.
Service Charge with VAT Code
Opera code for VAT-inclusive service charges.
Service Charge with VAT Code Adjustment
Adjustment code for VAT-inclusive service charges.
Tip Code
Opera code for tips from Toast.
Tip Code Adjustment
Adjustment code for tips.
Receipt Description
Defines how receipts from Toast appear in Opera folios (e.g., 'Restaurant Charge').
7.3: Configuring the mapping
The Mapping Page links Toast data to Opera Cloud transaction and payment codes.
Default Mapping Options:
Configure mappings as default per Revenue Center.
Or configure per Revenue Center and Meal Period for detailed reporting (e.g., Breakfast, Lunch, Dinner).
Mapping Page Layout:
Sales Categories → Transaction Codes
Service Charges → Transaction Codes
Payment Types → Payment Methods
Adjustments:
Each mapping must also include the related Adjustment Codes to handle changes within Toast’s 90-day window.
8. Common issues
If you are not receiving any transaction codes in our system, please check the following settings in Opera Cloud.
Menu > Administration > Enterprise > Opera Controls > Cashiering > Transaction Code by User Role
Make sure this setting is marked as inactive.
If a Toast popup displays “No guest found,” it’s likely because the room charge is not enabled in Opera Cloud.
How to resolve this issue:
Go to the ‘Check In Reservation’ of the guest in Opera Cloud and have a look at the ‘Payment Instruction’ settings and see if ‘No Post’ is disabled.
If a Toast popup displays "Payments through Opera Cloud are currently unavailable," double-check that all sales categories are properly linked to the items in Toast.
How to resolve this issue:
Go to ‘Menus’.
Navigate to ‘Advanced Properties’.
In the dropdown menu on the right, select ‘Sales Category’.
Ensure that every ‘Sales Category’ is filled in.
Click ‘Save’ and then ‘Publish’.
9. Summary & Support
Summary
You have now completed the full setup of the Toast ↔ Opera Cloud Integration via Omniboost DataHub, including:
Preparing required transaction codes and adjustment codes in Opera Cloud.
Configuring Sales Categories, Revenue Centers, and Menus in Toast.
Setting up POS and PMS Settings in DataHub.
Completing the DataHub to link Toast with Opera Cloud.
Reviewing the most Common Issues and their resolutions.
Once this setup is complete and verified, your property will benefit from:
Accurate and automated financial postings.
Reduced manual reconciliation.
Improved operational efficiency across F&B and Front Office.
Support Contact
If you encounter issues with the DataHub configuration or Data:
Omniboost Support
📧 pos-support@omniboost.ioIf you encounter issues with your Toast configuration.
Toast Support
📧 integrations-support@toasttab.comIf you encounter issues with your Opera configuration you need to open a Ticket via their support portal.