Skip to main content

Full Revenue Push | Toast to Opera Cloud (new)

By Omniboost

Guide Overview:

This guide provides detailed instructions on setting up and configuring your integration between Toast and Opera Cloud via Datahub, for both room charges and direct Toast payments. It includes the following sections:

  • Integration Setup Requirements

  • Accessing Datahub

  • Setting Up Two-Factor Authentication (2FA)

  • Starting the Integration Setup

  • Configuring POS Settings

  • Configuring PMS Settings

  • Configuring the Mapping​

  • Testing the Integration

Integration Setup Requirements

Before you can begin setting up the integration, please ensure the following steps are completed.

Toast integration Request:

To start the setup process, you must first request the “Toast to Opera Cloud by Omniboost” integration via the Toast Marketplace.

This step is required for two reasons:

  • It allows Omniboost to receive the necessary credentials and information from Toast

  • It automatically triggers the onboarding process on the Omniboost side

    • You will automatically receive an email from Omniboost DataHub with instructions guiding you through the next required steps.

If you have not done so already, you can find more information on how to submit the request in the Toast Marketplace here: How to request the Toast integration in the Toast Marketplace?

PM Accounts in Opera Cloud:

Depending on the level of detail you want in your reports within Opera Cloud, you can choose between two setup options.

Option 1 - More Detailed Reporting

  • Create a PM Account in Opera Cloud for each Toast Payment Method, with the same names as your Toast payment methods:
    e.g. Toast: "Cash" -> Opera Cloud: "Toast Cash"

Option 2 - Simplified Reporting

  • Create one PM Account in Opera Cloud for all Toast payments:
    e.g. "Toast Payments"

PM Accounts start as pseudo rooms. These may need to be created if they do not already exist. You can do so by navigating to:

  1. Admin → Inventory → Acommodation Management → Room types

  2. Click ‘new’:

    1. Enable: pseudo

    2. Room class : ALL

    3. Room type : PM

Once the pseudo PM rooms are created, charges can be posted to them, typically in a block situation.

Steps to configure a PM Account:

  1. From the OPERA Cloud menu, select Bookings → Blocks → Manage Block.

  2. Enter the search criteria and click Search or create a new block by clicking "create"

  3. Select a block from the search results, then click I Want To… and select Posting Master.

  4. The confirmation message is displayed.

  5. 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.

  6. 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.

Note

If you prefer to use PI or PF accounts in Opera Cloud instead, please inform pos-support@omniboost.com, as additional configuration is required on the backend of the integration.

Standard Transaction Codes:

To map revenue from Toast to Opera Cloud, you must create transaction codes in Opera Cloud. Depending on the level of detail you want in your financial reporting, you can choose one of the following setup options:

Option 1 - Maximum Detail

Create transaction codes based on:

  • Revenue Center

  • Meal Period (e.g., breakfast, lunch, dinner)

  • Sales Category (e.g., food, beverage, alcohol)

E.g. "Restaurant Food Breakfast"

Option 2 – Detailed

Create transaction codes based on:

  • Revenue Center

  • Sales Category

E.g. "Restaurant Food"

Option 3 – Limited Detail

Create transaction codes based on:

  • Revenue Center or Sales Category

E.g. "Food" or "Restaurant"

Option 4 – Simplified

Create:

  • One unified transaction code for all Toast revenue

E.g. "Toast"

Use this link to learn how to create a transaction code: Configuring Transaction Codes

Important

“Manual posting’’ must be enabled for every transaction code. If this is not enabled the transaction code will not be loaded in to the DataHub.

Tax transaction codes

To map tax from Toast to Opera Cloud, you must create transaction codes in Opera Cloud. Depending on the level of detail you want in your financial reporting, you can choose one of the following setup options:

Option 1 - Detailled

Create a transaction code for every tax percentage used in Toast.

E.g. "F&B Sales Tax 4%" and "F&B County Tax 5%"

Option 2 – Simplified

Create one general transaction code for tax mapping.

E.g. "F&B Sales and County Tax 9%"

Additional transaction codes within Opera Cloud:

In addition to your standard transaction codes in Opera Cloud, you must create several additional transaction codes to properly handle fallback postings and non-revenue transactions from Toast POS.

These transaction codes ensure that all transactions are correctly recorded, even in cases where standard mappings are missing, instead of turning to errors.

  • A transaction code called 'Fallback Toast'

  • A transaction code called 'Service Charge Toast'

  • A transaction code called 'Gratuity Toast'

Use this link to learn how to create a transaction code: Configuring Transaction Codes

Adjustment transaction codes:

For all of the above transaction codes in Opera Cloud, you must create a corresponding adjustment code.

E.g. "Restaurant Food" and "Restaurant Food Adjustment".

Adjustment transaction codes are used for reconciliation purposes when a receipt in Toast POS is modified after it has already been closed and posted to Opera Cloud.

Use this link to learn how to create a transaction code: Configuring Transaction Codes

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 resolve this, Adjustment Codes are used:

  1. The original receipt is voided in Opera using the Adjustment Code on the day the adjustment is made.

  2. 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.

Payment Transaction Codes and Payment Methods

To send payments from Toast to Opera Cloud, you must configure payment transaction codes and link them to Opera payment methods in Opera Cloud.

Since payment types cannot be mapped directly in Omniboost DataHub, the mapping works as follows:

Toast Payment Method → Opera Payment Method→ Transaction Code

  1. Create Payment Transaction Codes

    • Create transaction codes of type Payment in Opera Cloud.

    • Depending on your desired level of detail, you can choose:

      • Detailed setup:

        • Create a transaction code per Toast payment type

          E.g., "Toast Cash", "Toast Credit Card"

      • Simplified setup:

        • Create one general transaction code for all Toast payments

          E.g., "Toast Payments"

    • Important:

      • Set the Transaction Code Type to "Payment"

      • Set the Payment Type to "Other"

      • Ensure the Subgroup is a payment-related subgroup

  2. Create Payment Methods and Link Transaction Codes

    • Next, create (or confirm existing) payment methods in Opera Cloud and link them to the transaction codes created above.

      • If using a single transaction code:

        • Create one general payment method

          E.g., "Toast Payment"

      • If using multiple transaction codes:

        • Create a payment method per Toast payment type

          E.g., "Toast Cash", "Toast Credit Card"


​Additional payment types within Opera Cloud:

In addition to your standard payment transaction codes and payment types in Opera Cloud, you must create one additional payment transaction code and payment type to properly handle fallback postings and non-revenue transactions from Toast POS.

These ensure that all transactions are correctly recorded, even in cases where standard mappings are missing, instead of turning to errors.

  • A transaction code called "Fallback Payment Toast" linked to a payment type "Fallback Payment Toast"

  • A transaction code called "Fallback Payment Toast Adjustment" linked to a payment type "Fallback Payment Toast Adjustment"

Accessing DataHub

To access DataHub, follow these steps:

  1. Obtain Login Credentials:

    • After requesting the integration in the Toast Marketplace you will receive your person login credentials via email. If you haven't received them, kindly request them from your designated contact at Omniboost or send an email to 'pos-support@omniboost.com'

  2. Navigate to DataHub:

  3. Enter Your Credentials:

    • Use the email and password provided Omniboost

  4. Select “Remember Me”:

    • Check the Remember me box to save your login details for future access.

  5. Click “Login”:

    • Press the Login button to proceed.

Setting Up Two-Factor Authentication (2FA)

When logging into Omniboost DataHub for the first time, you will be prompted to set up Two-Factor Authentication (2FA).

This step is required and must be completed carefully, as you will need your 2FA device each time you log in going forward.

  1. Download a 2FA Application

  2. Scan the QR Code

    • Open your 2FA app

    • Select the option to add a new account

    • Scan the QR code displayed on the DataHub screen

    This will link your account and start generating authentication codes.

  3. Generate and Enter 2FA Code

    • Your 2FA app will generate a new code every 30 seconds

    • Enter the current code into the DataHub screen to verify your setup

  4. Save Recovery Codes

    • Carefully store the recovery codes shown on the screen

    • These codes allow you to regain access if you lose your phone or 2FA app

Important

You will need your 2FA app every time you log in to DataHub.

Starting the Integration Setup

  1. Access the Next Screen:

    • After successfully creating your user and setting up Two-Factor Authentication (2FA), you will be directed to the next screen.

  2. Click “Start Setup”:

    • On this screen, click the Connect button to begin configuring the integration.

Configuring POS Settings

Configuring the 'On Room Payment Type'

  • Select the payment type that represents room charges (typically named Room Charge)

  • This ensures that these transactions are recognized and sent to Opera Cloud as revenue only (not as payments)

If you do not see the Room Charge option in the drop down menu, please do send an email to 'pos-support@omniboost.com'.

Fill in the 'Tip Name'

Define the description used for tip-related transaction codes in Opera Cloud.

  • Enter a name such as:

    • Toast Tip

    • Gratuity

This name will be used as a description for the corresponding transaction code.

Enable or disable 'Use Meal Periods'

Choose whether you want to include meal periods (e.g., breakfast, lunch, dinner) in your revenue mapping.

Please refer to the section “Standard transaction codes” above:

If you selected Option 1 - Maximum Detail, meal periods must be enabled and configured.

If you chose a less detailed setup (Options 2–4), enabling meal periods has no added value and should be left disabled.

When enabled:

  • You can map revenue in more detail, allowing for more detailed reporting in Opera Cloud

  • Example:

    • "Restaurant food breakfast"

    • "Restaurant food lunch"

    • "Restaurant beverage breakfast"

    • "Restaurant beverage lunch"

When disabled:

  • Mapping will be simpler and less work

  • Example:

    • "Restaurant food"

    • "Restaurant beverage"

Tip:

Only enable meal periods if you plan to map all additional fields and mapping pages required for this higher level of reporting.

It increases setup complexity but allows for more granular insights in Opera Cloud.

Enable or disable 'Split Tax'

Enable the Split Tax checkbox if you want to split out the different taxes. Otherwise, the system will use the total tax rate.

Configure the 'Set Meal Periods' (only if 'Use Meal Periods' is enabled)

If you have enabled “Use Meal Periods”, you must define your meal periods. Transactions will be assigned to a meal period based on the opening time of the receipt in Toast, and will be mapped accordingly in Opera Cloud.

In order to do so please complete the next steps:

  • Select a meal period from the dropdown menu

  • Enter a name for the meal period (e.g., Breakfast, Lunch, Dinner)

  • Set the start time and end time

    • Meal periods must cover the full 24 hours of the day

    • There may be no gaps or overlaps between meal periods

    • Each meal period must start immediately when the previous one ends

Repeat these steps for each meal period you want to configure.

Important:

Incorrect configuration will result in mapping issues.

Configuring PMS Settings

On top of the PMS settings page, you will find two tabs:

  • Default settings

  • Settings per revenue center

Complete the Default Settings first, following the instructions below. These settings will automatically apply to all revenue centers and meal periods.

If needed, you can customize the settings for specific revenue centers by overriding the default configuration in the Settings per Revenue Center tab.

Default and Adjustment Codes

These settings define where transactions are posted when no specific mapping is applied; for example, when a new sales category is added in Toast but not yet mapped in Omniboost DataHub, or when a new sales item is created in Toast that is not linked to an existing sales category.

  • Default Analysis Code → Select: Fallback Toast

    • Used for revenue items without a mapping

  • Adjustment Default Analysis Code → Select: Fallback Toast Adjustment

    • Used for adjusted revenue items without a mapping (when a receipt in Toast is modified after it was already closed)

  • Default Payment Code → Select: Fallback Payment Toast

    • Used for payments without a mapping

  • Adjustment Default Payment Code → Select: Fallback Payment Toast Adjustment

    • Used for adjusted payments without a mapping (when a receipt in Toast is modified after it was already closed)

Note:

These fallback categories act as a safety net.

If mappings are missing or incorrect, transactions will be posted here.

Select Folio Window Number

The Folio Window Number is set to 1 by default. You can adjust this value using the arrow controls (up/down) on the right-hand side.

Enable or disable 'VAT/TAX Inc'

Enable if prices from Toast include VAT (e.g., Europe). Leave unchecked in tax-exclusive countries (e.g., US, Canada).

Select PM, PI or PF accounts

You must map each Toast payment method to the correct PM, PI or PF Account in Opera Cloud. For more information regarding these accounts, please refer to section "Integration Setup Requirements".

Note

Using a payment account is required if you want to enable Full Revenue Push.

It is not possible to use Full Revenue Push without configuring a payment account.

Tip and Service Charge Configuration

Configure how tips and service charges are posted in Opera Cloud:

  • Service Charge Code → Service Charge Toast

  • Adjustment Service Charge Code → Service Charge Toast Adjustment

  • Service Charge With VAT Code → Service Charge Toast

  • Adjustment Service Charge With VAT Code → Service Charge Toast Adjustment

  • Tip Code → Gratuity Toast

  • Adjustment Tip Code → Gratuity Toast Adjustment

Enter the Receipt Description

Defines how receipts from Toast POS will appear in folios within Oracle Opera Cloud (e.g., Restaurant Charge).

This description will be visible to hotel staff and guests, so we recommend using a clear and recognizable name that reflects the origin of the charge.

Once all fields are completed:

  • Click Next Step to continue

Configuring the mapping

In this step, you will map all sales categories, service charges, and payment methods from Toast to Opera Cloud within Omniboost DataHub.

Navigation Tabs

At the top of the screen, you will see different tabs (e.g., Pool, Bar, Patio, Dining Room, Adjustment, etc.).

  • Each tab represents a (Toast) revenue center, meal period, or adjustment type

  • The first page acts as the default mapping for all tabs that are not configured

  • The “Adjustment” tab acts as the default for all adjustment-related tabs

  • Mapping additional tabs is not mandatory, however, configuring them allows for more detailed and accurate reporting in Opera Cloud

  • Any additional tab you configure will override the default mapping for that specific revenue center, meal period, or adjustment type

Categories

Map each Sales Category from Toast to the corresponding Transaction Code in Opera Cloud.

For each Sales Category (e.g., Beer, Food, Liquor, Wine):

  • Select the preferred Opera Cloud Transaction Code

You can configure this in four different ways, depending on the level of detail you want in your Opera Cloud reports:

Option 1 - Maximum Detail

Map transaction codes based on:

  • Revenue Center

  • Meal Period (e.g., breakfast, lunch, dinner)

  • Sales Category (e.g., food, beverage, alcohol)

E.g. "Restaurant Food Breakfast"

When using meal periods, you do not need to map the revenue center pages without a meal period assigned.

All transactions are assigned to a meal period based on the receipt opening time, so the default revenue center pages without a meal period will not be used.

Option 2 – Detailed

Map transaction codes based on:

  • Revenue Center

  • Sales Category

E.g. "Restaurant Food"

Option 3 – Limited Detail

Map transaction codes based on:

  • Revenue Center or Sales Category

E.g. "Food" or "Restaurant"

Option 4 – Simplified

Map:

  • One unified transaction code for all Toast revenue

    • You can select a PMS category at the top Select PMS Category to apply to all and click Apply to assign it to all

E.g. "Toast"

Helpful Links:

Learn how to create a transaction code: Configuring Transaction Codes

Learn how to create Sales Categories in Toast: Configure Sales Categories

Both transaction codes and sales categories are fetched in real time.

After creating new ones, simply refresh the page and they will appear in the dropdown options.

Service Charges

Map all POS service charges to the correct Opera Cloud service charge transaction codes.

Examples:

  • Delivery Fee

  • Gratuity 10% / 18% / 20%

For each:

  • Select the corresponding Opera Cloud service charge transaction code.

Payment Methods

All POS payment methods are listed on the left-hand side of the screen. Map each POS payment method to the corresponding Opera Cloud payment method. These payment methods need to be linked to a transaction code of the type "payment" in Opera Cloud. For more information, please refer to the "Integration Setup Requirements" section in this guide.

Examples:

  • Amex → Toast Amex

  • Visa → Toast Visa

  • Cash → Toast Cash

Some payment method mappings may not be actively used (see examples below). However, all fields must be completed before the mapping page in DataHub can be saved. For any unused POS payment methods, map them to the Fallback Payment Type.

  • Room Charge, House account:
    These transactions are processed through the real-time integration. Transactions will be sent using the transaction codes configured in the Sales Categories Mapping and PMS Settings sections.

  • Other payment options:
    You may not use every payment method displayed on this page. Some payment methods are hardcoded in DataHub or included as default options by Toast.

Final Step:

Click Save Mapping at the bottom of the screen. Make sure all required fields are completed, otherwise the page will not save.

After clicking Save Mapping & Continue, the integration setup is complete.

Important: Full Revenue Push (direct payments) is not enabled automatically: you must email 📧 pos-support@omniboost.com to request activation.

The integration is now ready for Room Charge transactions, and you can run a test using the Room Charge payment method in Toast (see testing section below).

Once Full Revenue Push is activated by our team, all direct payments will be synced to Opera Cloud every 15 minutes.

Afbeelding met tekst, schermopname, software, ontwerp Automatisch gegenereerde beschrijving

Important: If you have multiple locations in Toast (e.g., Market, Rooftop), you must configure the integration for each location separately by following the same steps.

You can switch between locations using the dropdown menu in the top-left corner of Omniboost DataHub.

Testing the Integration

You can now test the integration using a Toast POS handheld or terminal with a checked-in room in Opera Cloud.

How to run a test:

  • Create a new receipt on a Toast handheld or terminal

  • Select the payment method Room Charge

    • Note: this may be located under “More payment options”

  • Search for and select the correct room number

  • Close the receipt

Verify in Opera Cloud:

  • Check the Logs page in Omniboost DataHub

  • Check if the transaction appears correctly in Opera Cloud

Test Adjustment (Recommended)

  • Void the receipt in Toast

  • Verify that the transaction is also voided or adjusted correctly in Opera Cloud

All transactions and potential errors can be reviewed in the logs within Omniboost DataHub, accessible from the left-hand menu.

Important:

If you need to modify a receipt in Toast after the room charge has already been sent to Opera Cloud, you must void the entire receipt, make the necessary changes, and create a new room charge.

Updating an existing receipt will not be reflected correctly in Opera Cloud.

Support

Support Contact

Did this answer your question?