Summary

This Live release delivers error handling and data accuracy improvements across the API, covering webhooks, transactions, discounts, and reports.

Included in this Live release:

• Webhooks — Fixed 500 error on PUT /webhooks/{id} for inactive or non-existent webhook IDs; endpoint now returns 404 Not Found.
• Transactions — Credit card fee values submitted via POST /transactions/receipt are now rounded to 2 decimal places, preventing account balance mismatches and refund processing errors.
• Reservations — POST /reservations/discounts/search now correctly returns discounts with validation rules applied, instead of returning 204 No Content.
• Reports — POST /reports/auditTrail no longer returns a 500 error when glCodeIds is passed as an empty array.

👉 Beta details: https://releasenotes.rmscloud.com/rest-api-v10.26.118.1----beta-3CuvTy

Notes

• This release is now available in Live
• Release Date: 3 June 2026 (AEST)
• 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 delivers four fixes addressing error handling and data accuracy improvements across the API. Partners are encouraged to test the affected endpoints ahead of the Live release.

Fixes & Improvements

Webhooks — PUT /webhooks/{id} Returns 500 for Inactive Webhooks

Calling PUT /webhooks/{id} with an inactive or non-existent webhook ID was incorrectly returning a 500 Internal Server Error instead of a meaningful error response. This has been fixed. The endpoint now returns 404 Not Found in these cases, allowing integrators to handle the response appropriately.

• Endpoint affected: PUT /webhooks/{id}

Transactions — Credit Card Fee Rounding via POST /transactions/receipt

When a credit card fee was submitted via POST /transactions/receipt with more than 2 decimal places (e.g. 0.9608), the value was stored as-is in RMS. This caused a rounding mismatch on the account balance, which prevented users from processing valid refunds — the system would reject a refund that appeared within the available credit balance because the stored fee value didn't align to standard 2-decimal currency precision.

This has been fixed. Credit card fee values are now rounded to 2 decimal places at the point of storage, ensuring account balances are calculated correctly and refunds can be processed without errors.

This fix affects any integration using POST /transactions/receipt that submits credit card fee values with more than 2 decimal places.

• Endpoint affected: POST /transactions/receipt

Reservations — Discounts with Validation Rules Return 204 in POST /reservations/discounts/search

POST /reservations/discounts/search was returning 204 No Content for discounts that had validation rules applied (e.g. date made ranges, stay date ranges), even when the search criteria matched those rules. Discounts without validation rules were unaffected.

This has been fixed. The endpoint now returns all eligible discounts, including those with validation options configured, provided the request parameters fall within the defined rules.

• Endpoint affected: POST /reservations/discounts/search

Reports — POST /reports/auditTrail Returns 500 Internal Server Error

Calling POST /reports/auditTrail with an empty glCodeIds array was causing a 500 Internal Server Error. This affected all requests regardless of other parameters supplied.

This has been fixed. The endpoint now returns audit trail data without filtering by GL code when glCodeIds is passed as an empty array.

• Endpoint affected: POST /reports/auditTrail

Notes

• Release Date: June 02, 2026 Beta only
• Dependencies: None
• There is no impact to Live environments.
• Please report any issues through standard support channels: https://rmsapi.zendesk.com/hc/en-gb/requests

Resolved an issue where reservations created through IBE+ were being assigned check-in and check-out times from the property level, even when specific times had been configured at the category level.

IBE+ will now correctly honour category-level times where they have been set, falling back to property-level times only when no category-level configuration exists. This applies to both standard night bookings and day use bookings.

Traces are inter- or intra-departmental notes used to communicate or delegate tasks across various areas of the system, including the To Do Chart, Area, Reservation, Company, Travel Agent, Guest, and Groups.

When creating a Trace for an Allotment which is specific to a certain property, the trace is displaying for all properties on their To Do Chart. This has been resolved.

Help Article

An issue was identified where RMS Pay could not be activated for properties registered as Unincorporated Partnerships.

Properties completing KYC under the Unincorporated Partnership workflow can now successfully activate RMS Pay.

We are pleased to inform you that the issue affecting Dynamic Surcharging when only Regional (Domestic/International) levels were configured has been resolved.

What was fixed: Previously, if only Regional surcharges were set, the system defaulted to the Card Type fee, and the correct surcharge was not applied. This has now been corrected. The surcharge will correctly apply based on the Regional configuration when sub-levels (Funding Source and Card Variant) are not set.

Impact: Transactions will now calculate the correct surcharge automatically, ensuring accurate fee application.

Bug Fix for Channel Mapping Wizard in Channel management setup. Rate Type not populating when importing from CSV. After fix the Rate type with valid Rate Type setup is populated successfully.

Users are able to create Add Ons on Master Reservations. Add Ons added on Master Reservation do not post charges as they are not assigned to a Rate/Room/Reservation. We should not have the option to Add or Remove via the Master, it should only be done on the sibling reservation.

If the Security Profile option 'Hide Accomm Values (Show as XXXX)' has been set to 'Yes' then users will see 'XXXX' in place of any dollar values for the Rate Amount and Account Balance. We had an issue where users were still able to view the rates on the booking chart while viewing the credit status. We have fixed this issue and now the credit status on the booking chart displays as XXXX.

When guests chose to enter their address manually during checkout, all address fields were displaying as mandatory - regardless of how they had been configured in Field Maintenance in RMS 9+.

This has been resolved. Manual address entry now fully respects your Field Maintenance setup - mandatory, optional, and hidden fields will all behave exactly as configured, and field labels and display order will match as expected.

No action is required. This fix applies automatically for all IBE+ properties.