Skip to main content

OHIP Routing instructions

Gil H
Updated

Overview

Duve now supports routing instructions with OHIP PMS. This means configuring which transaction codes will be ignored for the Guest Folio when reservations sync to Duve. This feature ensures a better guest experience regarding payments in the online check-in. Hosts can now control over which transactions should be excluded from Duve’s folio sync.

Introduction

This functionality is particularly useful for excluding unnecessary or irrelevant charges, and keeping the folio clean and relevant for both guests and hosts.
This configuration can be done easily from the Duve connect & sync page, ensuring a smooth and tailored integration experience.

How to Set It Up

  1. The first setup should occur in the Oracle interface:
 
To create routing instructions:
  • From the OPERA Cloud menu, select Client Relations, select Profiles, and select Manage Profile.
  • Search for and select a profile and then click Financials.
  • Click New and then select a property.
  • On the Search and Select Routing Instructions screen, search for routing codes or transaction codes.
  • Select one or more Routing Codes or Transaction Codes from the Available list and then click Add.
  • Click Auto Populate Routing to attach the routing instructions to any associated profiles.
  • You can update routing instructions on a reservation billing window that has existing instructions if no overlapping transactions or codes exist for the same dates. To update routing instructions:
  • From the OPERA Cloud menu, select Bookings, select Reservations, select Manage Reservation, and then search and select the reservation.
  • Click the Actions link, click Routing, click Edit, change the desired code or other information, and then click Save Instructions.
 
  1. Setup on Duve's end:
 
Access the PMS Settings:
Add Transaction Codes to Ignore:
    • In the connection settings, locate the Ignored Transaction Codes field.
    • Enter the specific transaction codes that should not be synced with the Guest Folio.
Mapping the Codes:
    • Scroll to the bottom of the connection page to review and finalize mapping for your PMS integration.

How It Works

  1. Transaction Code Mapping:
    • Duve receives the TPT (Transaction Posting Type) from OHIP.
    • The TPT is then mapped to the corresponding TRX code based on routing instructions.
    • For example, if the TRX code is 7531, Duve will recognize this as a charge to ignore, and the guest will not be asked to pay.
  2. Routing Instructions:
    • Identify the routing instruction in OHIP that defines charges that should not appear for guest payment.
    • Ensure that the transaction codes listed here match what you intend to exclude from payment requests.
  3. Transaction Code Setup:
    • The required TRX codes must be:
      • Created in Opera OHIP first.
      • Manually added in Duve to align the configuration.
  4. Consistency Between Lists:
    • Verify that the routing instructions at the top of the connect and sync page align with the Transaction codes listed below.
    • The TRX codes configured in Opera must match the codes listed in Duve to ensure proper payment routing.
 
 
Connect & sync page:
Top part -
 
 
Bottom part:
 

Use Case

For Hotel Managers:
You can exclude irrelevant transaction codes, such as specific internal fees or operational charges, from appearing in the Guest Folio. This ensures the folio remains clean, accurate, and guest-friendly.
For Finance Teams:
The ability to ignore specific transaction codes streamlines reporting and reconciliation processes, minimizing errors and irrelevant entries.
For Guests:
By excluding unnecessary transactions, guests will only see relevant charges in their folio, creating a clearer and more professional presentation.

Related articles

Comments

0 comments

Article is closed for comments.