Skip to main content

RMS 2-Way integration | How to Connect

Alon
Updated
This article explains the steps required to enable the two-way integration between Duve and your RMS account. To begin, you must have an active Duve account and a working RMS connection.
Two-way sync is an opt-in addition to your existing RMS connection. You do not need to create a new connection, and nothing is written back to RMS until you turn it on.

Before you start

Have the following ready:
  • Your RMS Client ID and Client Password. These are the same details you use to log in to your RMS account. Your ID can be found in the top left corner of your RMS dashboard.
  • The sundry ID (charge code) in RMS that Duve upsell charges should post to. Charges cannot post without it.
  • The online agent ID in RMS (your online distribution channel), used for live availability during room upgrades.
Setup note: You do not need to look up your RMS API address. Duve resolves your regional RMS host automatically when the connection is created.

How to set it up?

  1. In Duve, go to your PMS connection page and open your existing RMS connection. If you are connecting RMS for the first time, select RMS as your PMS system, enter your Client ID and Client Password, and click Connect to sync the accounts.
  2. Reopen the connection to configure it. The RMS configuration fields are only shown when you edit an existing connection, not while you are creating one.
  3. In the Write permissions section, turn on the permissions you want:
    • Basic two-way connection: the master opt-in for writing data back to RMS. Guest profiles, companions, the arrival time, the online check-in note, and reservation status all depend on this.
    • Guest orders connection: posts upsell charges and Duve-processed payments to the RMS folio.
    • Upload documents: pushes the documents a guest uploads during online check-in to the RMS reservation.
  4. Fill in the RMS configuration fields:
    • Upsell sundry ID: the RMS charge code used for upsell charges. Must be a positive number.
    • Online agent ID (live availability): the RMS online distribution channel used for availability and rate queries.
    • Payment receipt type: how Duve-processed payments are recorded in RMS. Defaults to journal.
    • Receipt card ID: the RMS card record used when posting payment receipts. Optional.
    • Charge source: the transaction source stamped on upsell charges. Defaults to standard.
    • Allow update reservation status: turn this on to let Duve push check-in and check-out to RMS.
    • RMS API base URL: an advanced override, only needed if Duve's automatic host resolution needs to be corrected. Leave it empty in normal use.
  5. Save the connection. Duve validates every field at save time, so an invalid base URL, an unsupported receipt type or charge source, or a sundry ID that is not a positive number will block the save with an error.
  6. If you turned on Allow update reservation status, create or edit a Duve trigger that updates the PMS status. For RMS, the trigger offers two options: checked-in, which Duve sends to RMS as Arrived, and checked-out, which Duve sends as Departed.
  7. Run a test reservation end-to-end: complete online check-in on a test booking, then confirm the guest profile, the arrival time, the folio, and the reservation status in RMS.
When the connection is saved, Duve automatically registers your RMS webhook subscriptions, so changes made directly in RMS start reaching Duve without waiting for the next scheduled sync. Disconnecting the source removes those subscriptions again.

Allowed values

Charge source: electric, extras, gas, kiosk, membership, pos, pabx, standard, water.
Payment receipt type: cash, cash3, cash4, cash5, cashExpense, creditTransfer, cheque, cheque3, cheque4, cheque5, creditCard, directCredit, eftpos, eftposMachine, existingToken, forexCash, giftCard, guestCredit, journal, voucher.

Notes

  • Two-way sync is never enabled automatically on an existing RMS connection. It is always an explicit opt-in per connection.
  • You can turn two-way off at any time. Duve stops writing to RMS immediately, and the connection reverts to one-way behavior. Data already written to RMS stays there.
  • Create a dedicated sundry code in RMS for Duve upsells rather than reusing an existing one. It keeps the folio readable and makes reporting on Duve-sold upsells straightforward.
  • To push a guest's passport number or title to RMS, map the matching custom question to the RMS guest field in your online check-in settings. These are not pushed automatically.

For Expansions

Contact RMS support to ensure that the module for Duve is turned on for each property.
If you also want RMS to push inventory changes to Duve in real time, rather than Duve querying availability when it needs it, raise an RMS Service Request for availability push. This is a later phase and is not required for the two-way integration to work.

Related Articles:

RMS 2-way integration specs

Related articles

Comments

0 comments

Article is closed for comments.