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.

Summary

This Live release brings together the improvements and fixes previously delivered across the Beta cycle, with a focus on availability and rate calculation workflows, guest correspondence support, and reservation reliability.

Included in this Live release:

• Availability & Rate Calculation Enhancements
  Improvements to availability and rate calculation workflows, along with new API support for managing guest correspondence notes.
  👉 Beta details: https://releasenotes.rmscloud.com/rest-api-v10.26.10.1----beta-3ECvn2
• Reservation Workflow Fixes & Stability Improvements
  Fixes to reservation creation and update workflows, ensuring rate-based configuration fields are correctly applied and resolving timeout issues when overriding rates.
  👉 Beta details: https://releasenotes.rmscloud.com/rest-api-v10.26.19.2----beta-1eL7Q4

Notes

• This release is now available in Live
• Release Date: February 11, 2026 (AEDT)
• Partners can begin using these changes in production immediately
• Please report any issues through standard support channels:
  https://rmsapi.zendesk.com/hc/en-gb/requests

Summary

This Beta release includes a fix for an issue impacting the reports/npsResults endpoint in the Beta environment, where a 500 error was being returned. Partners are encouraged to validate this fix in Beta and report any issues via standard support channels.

Fixes & Improvements

NPS Results Report Endpoint

• Issue: A 500 error was being returned for the reports/npsResults endpoint in Beta.
• Fix: The endpoint no longer returns a 500 error and now processes requests as expected.

Endpoint:
POST/reports/npsResults
https://app.swaggerhub.com/apis-docs/RMSHospitality/RMS_REST_API/1.4.43.1#/reports/npsResultsReport

Notes

• Release Date: February 11, 2026 (AEDT) 
• This issue was environment-related and has been resolved in Beta.
• There is no impact to Live environments.
• Please report any issues through standard support channels:
  https://rmsapi.zendesk.com/hc/en-gb/requests

Property is using Associated Rooms to get best value out of renting out apartments at the property. When the apartment is no longer able to be rented out, there is no way of removing the association. 

Help article

Automatic Check-out will prompt users exiting an account on the departure date with the option to update the Reservation Status.

an issue was identified where this functionality was not working if the check out time was prior to 9am

We’re pleased to confirm that the issue affecting the Credit Card Token Details window has now been resolved.

This was a UI issue that occurred only for specific properties. While the credit card information was still visible when clicking the token, the details window would not open when selecting ‘View Token’ or double-clicking the token.

You should now be able to:

Select ‘View Token’, or

Double-click on the credit card token

and the Credit Card Token Details window will open as expected.