We have resolved an issue in the RMS Booking Engine (IBE+) where Google tag data was not being recorded upon booking confirmation.

Previously, Google tags were failing to fire on the confirmation page after a guest completed payment. This meant that transaction data - including booking conversion events - was not being captured in your connected Google Analytics account, resulting in incomplete or missing reporting data.

This issue has now been fixed. Google tags will fire correctly on the confirmation page, ensuring that all transaction and conversion data is accurately recorded as expected.

We have resolved an issue in the RMS Booking Engine (IBE+) where the Area URL modifier was not functioning correctly when check-in and check-out dates were not included in the URL.

Previously, when a guest landed on the booking engine via a URL containing only an Area parameter (without dates), the Area filter would be dropped once the guest manually selected dates and clicked Search - resulting in all categories being displayed rather than only those mapped to the specified area.

This issue has now been resolved. The Area filter will now persist correctly in both scenarios: when dates are included in the URL, and when a guest manually selects dates after landing on the page. Only categories mapped to the specified Area ID will be displayed, as intended.

If you have any questions or require further assistance, please reach out to our support team.

What was the issue?

For IBE+ bookings where guests paid via RMS Pay, staff were unable to process refunds directly from within RMS (9+). Attempting to do so returned an error, leaving teams with no option but to manually intervene at the payment gateway level — a time-consuming workaround that also carried financial risk if not actioned promptly.

What's been fixed?

RMS Pay refunds for IBE+ bookings can now be processed directly from within the reservation in RMS, just as you'd expect. Both full refunds and partial refunds are supported. When a refund is submitted, it communicates with RMS Pay, returns the funds to the guest's original payment method, records the transaction in the reservation ledger, and updates the balance — all in one smooth step.

If a refund attempt fails at the gateway, the system will now correctly prevent the refund from being recorded, keep the original payment intact, and display an error message so your team knows what's happened.

What do you need to do?

Nothing — this fix is automatic. Refunds for RMS Pay transactions made through the new Booking Engine can now be processed directly from the reservation in RMS as normal.

What was the issue?

When a property configured specific card types in Online Options (for example, Visa and Mastercard only), the new Booking Engine was not respecting that configuration for RMS Vault payments. Guests could still complete a booking using a card type that wasn't assigned - such as Amex or Diners - bypassing the intended payment restrictions entirely.

What's been fixed?

The Booking Engine now correctly validates card types against your Online Options configuration at the point of payment. Only card types that have been assigned to the IBE will be accepted. If a guest enters a card type that isn't configured, the card field will be flagged and they won't be able to proceed with that card.

This applies to both desktop and mobile.

What does this mean for your guests?

The checkout experience remains smooth for guests using an accepted card - they'll see clear visual confirmation that their card is valid. Guests using an unsupported card type will be prompted to use an accepted alternative before completing their booking.

Do you need to do anything?

No action is required. Just make sure your accepted card types are correctly configured in Online Options - the Booking Engine will handle the rest.

What was the issue?

For properties using the Book by Area category setup with the "Show area on confirmation email" option not enabled in Online Options, an internal Area ID number was incorrectly appearing on the booking confirmation page and confirmation email when a guest booked via the rates listing. 

What's been fixed?

The Booking Engine no longer shows the area name or ID when the toggle is not activated in Online Options when the categories are setup to be book by area. The behavior is now consistent with what you'd expect based on your Online Options settings.

What do you need to do?

Nothing - this fix is automatic. If you have "Show area on confirmation email" not enabled in Online Options and your category is set to Book by Area, your guests will now see the correct area name in their confirmation communications.

When searching with a guest count higher than a rate table's maximum occupancy, the booking engine was displaying categories as simply Unavailable — leaving guests with no way forward and no explanation.

This has been fixed. IBE+ now intelligently handles over-occupancy scenarios by offering guests the option to split across multiple rooms where available, or surfacing a clear message explaining the limitation when it isn't. No more mystery dead ends. 🎉

Previously, it was possible to save a reservation with a Tariff Type that was not assigned to the selected Company when creating a booking. The system showed a warning but still allowed the reservation to save, which could lead to incorrect rate usage and under-quoting.

This has now been corrected. When Use Rate Types for Companies is enabled and a user attempts to save a reservation where the selected Tariff Type is not assigned to the chosen Company the reservation will not save.

Help article

We’ve fixed an issue where derived-from-derived rate types that include additional person pricing were not calculating correctly.

Previously, when a rate type was derived from another derived rate and configured to adjust additionals, the system reused the original additional amount for both adjustment levels. This could cause the final price (e.g. for 3 adults) to be under-calculated in Quick Quote and when creating a reservation and posting tariff.

Summary

We have rolled back the REST API Live version for Australia-based customers only to address an issue affecting reservation workflow endpoints.
The Live environment in AUS is now running v10.25.319.113. A release note will be published once the fixed version is available.

If you require access to the latest fixes and improvements in the meantime, please use the Beta environment.

Reference Live release:
https://releasenotes.rmscloud.com/rest-api-v10.26.19.2---live-2kTXfG

What happened

Following the Live deployment, an issue was identified that impacted a small number of customers in Australia.
This was related to backend database changes for a limited set of properties, where the API was not yet fully aligned with the updated environment.

To minimize disruption and restore stability, we have rolled back the Live API version for AUS-based customers only to the previous stable release.

Impact

• Scope: Limited to a small number of customers in Australia
• Affected functionality: Reservation workflow endpoints
• Current Live version for AUS: 10.25.319.113
• No action is required from partners at this time
• API behavior has returned to the previous stable state for impacted customers

What’s next

• A fix will be validated before a future Live release is scheduled.
• A release note will be published when the fixed version is deployed
• Partners who need access to the latest fixes and improvements should continue using Beta in the interim

Please report any issues or questions through standard support channels:
https://rmsapi.zendesk.com/hc/en-gb/requests

We’ve fixed discrepancies with category banners and messaging on the Booking Engine 🏷️. Sold-out banners and minimum night stay restrictions now display correctly, even for multi-night bookings where some nights have no available inventory.

What’s Changed?

• Sold-out banners now accurately reflect availability.
• Minimum night stay restrictions are correctly applied and shown.
• Multi-night bookings display accurate messaging when some nights are restricted or unavailable.
• Guests now see consistent and reliable information when selecting dates and categories.