Summary
This Live release delivers stability fixes from the September 3 Beta cycle: resolving a timeout on the Debtors Ledger report and correcting a configuration retrieval error affecting PABX integrations.

Included in this Live release:

• Debtors Ledger Report — Fixed a timeout that could prevent the report from completing. 👉 Beta details: https://releasenotes.rmscloud.com/rest-api-v10.26.227.1----beta-28DD1u
• MFI PABX Configuration — Fixed an error that could interrupt configuration retrieval for PABX integrations. 👉 Beta details: https://releasenotes.rmscloud.com/rest-api-v10.26.227.1----beta-28DD1u

Notes

• This release is now available in Live
• Release Date: September 3, 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 two stability fixes: resolving a timeout on the Debtors Ledger report, and correcting an endpoint error affecting PABX configuration retrieval for MFI integrations. No new endpoints, fields, or breaking changes are included.

Fixes & Improvements

Debtors Ledger Report — Timeout Resolved

Some calls to the Debtors Ledger report were failing to complete and returning a timeout error rather than the report data. This is now resolved; the endpoint returns the full report as expected.

• Endpoint affected: POST /reports/debtorsLedger

MFI PABX Configuration — Configuration Retrieval Fixed

An internal error could prevent PABX configuration data (transaction method, and accounting system date) from being retrieved for properties using the MFI PABX integration, which could interrupt call logging, transaction creation, and related billing operations. This is now resolved.

Notes

• Release Date: September 3, 2026 — Beta only
• Please report any issues through standard support channels: https://rmsapi.zendesk.com/hc/en-gb/requests

Summary

This Live release promotes the v10.26.202.1 Beta, which includes two bug fixes addressing reservation cancellation handling and owner record completeness for areas within interconnecting rooms.

Included in this Live release:

• Reservation Cancellation Fix — Resolved a 400 error when cancelling reservations where a cancellation policy rule had no sundry configured. 
• Interconnecting Room Owner Records Fix — Corrected incomplete owner history returned for individual areas within an interconnecting room. 
• 👉 Beta details: https://releasenotes.rmscloud.com/rest-api-v10.26.202.1----beta-R7c76

Notes

• This release is now available in Live
• Release Date: August 18, 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 two bug fixes: one resolving a reservation cancellation error when no sundry is configured on a cancellation policy rule, and one correcting incomplete owner records returned for areas within an interconnecting room.

Fixes & Improvements

Reservation Cancellation — 400 Error When No Sundry Configured

Fixed an issue where PUT /reservations/{id}/status returned a 400 error — "Cancellation Fee: no Sundry is configured on the Cancellation Rule or in Account Options" — when a cancellation policy rule was set up but no sundry had been configured. Reservations can now be cancelled successfully in this scenario. A cancellation charge will only be posted if the policy rule is met and a valid sundry is configured.

• Endpoint affected: PUT /reservations/{id}/status

Areas — Incomplete Owner Records for Interconnecting Rooms

Fixed an issue where GET /areas/{id}/owner returned incomplete owner records for areas that form part of an interconnecting room. Only the interconnecting (parent) area was returning the full owner history; the underlying individual areas returned only a single owner record. The endpoint now returns all applicable owner records for each area, including historical entries.

• Endpoint affected: GET /areas/{id}/owner

Notes

• Release Date: August 18, 2025 (AEST)— Beta only
• Please report any issues through standard support channels: https://rmsapi.zendesk.com/hc/en-gb/requests

Summary

This Live release delivers enhancements to reservation requirement responses, a new guest image upload endpoint, full CRUD support for Requirement Category Access, and a fix for a 503 error on reservation search by guest surname.

Included in this Live release:

• Reservation Requirements — chargeRequiredDaily and chargeDailyIncludeToDate fields added to requirement responses, enabling accurate fee calculation in kiosk and self-check-in flows.
• Guest Image Upload — New PUT /guests/{id}/image endpoint allows guest images to be uploaded directly via the API.
• Requirement Category Access — New endpoints to get, add, replace, and remove category access entries on master Requirements.
• Reservation Search Fix — POST /reservations/search no longer returns a 503 when filtering by guest surname.

👉 Beta details: https://releasenotes.rmscloud.com/rest-api-v10.26.191.2----beta-1Ph3uE

Notes

• This release is now available in Live
• Release Date: July 14, 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 adds new fields to reservation requirement responses, a new endpoint for uploading guest images, and a new set of endpoints for managing Requirement Category Access. It also includes a fix for a 503 error returned by POST /reservations/search when filtering by guest surname. 

New Features

Reservation Requirements — chargeRequiredDaily and chargeDailyIncludeToDate Fields

Two new boolean fields have been added to reservation-level requirement responses. chargeRequiredDaily indicates whether a requirement is charged on a per-day basis; chargeDailyIncludeToDate controls whether the departure date is included in that daily charge calculation. These fields allow integrators to accurately calculate requirement fees without relying on additional lookups or UI-side logic.

Endpoints affected:

• GET /reservations/{id}/requirements — Returns requirements for a reservation, now including chargeRequiredDaily and chargeDailyIncludeToDate
• GET /reservations/requirements — Search reservation requirements, now including chargeRequiredDaily and chargeDailyIncludeToDate

Guest Image Upload — New Endpoint

Integrators can now upload an image (such as a passport or ID document scan) directly to a guest profile via the REST API. Previously this was only possible through the RMS UI.

New endpoint:

• PUT /guests/{id}/image — Upload an image to a guest profile

Requirement Category Access — New Endpoints

A new set of endpoints enables integrators to manage Category Access on master Requirements. Category Access controls which property categories a Requirement appears in, using an allow-list model. This gives integrators programmatic control over Requirement visibility across a multi-category property setup, without requiring manual configuration in the RMS UI.

New endpoints:

• GET /requirements/master/{id}/categoryAccess — Retrieve the category access list for a master Requirement
• POST /requirements/master/{id}/categoryAccess — Add categories to the access list for a master Requirement
• PUT /requirements/master/{id}/categoryAccess — Replace the category access list for a master Requirement
• DELETE /requirements/master/{id}/categoryAccess — Remove categories from the access list for a master Requirement

Fixes 

Reservation Search — 503 Error When Filtering by Guest Surname

POST /reservations/search was returning a 503 Service Unavailable error when the request included a guestSurname filter. The endpoint now returns a valid result set, or an empty array when no matches are found.

Notes

• Release Date: July 14, 2026 — Beta only
• Please report any issues through standard support channels: https://rmsapi.zendesk.com/hc/en-gb/requests

Summary

This Live release delivers two fixes to reservation tariff handling. Properties using Nightly Rate accounting will now see correct per-night tariff records from API-created reservations, and pencil reservations will correctly recalculate tariffs when the rate type is updated more than once.

Included in this Live release:

• Reservations — Nightly Rate accounting — API-created reservations now generate per-night tariff records when the property is configured for Nightly Rate accounting. 
• Reservations — Pencil reservation tariff recalculation — Tariff values now recalculate correctly on every rate type change, not just the first assignment.

👉 Beta details: https://releasenotes.rmscloud.com/rest-api-v10.26.167.3----beta-20B5m0?psig=Mpx7z7vJgO61MKzP9abenS5geFulmT0aAI2Nubz

Notes

• This release is now available in Live
• Release Date: 24 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 two fixes to reservation tariff behavior. Reservations created via the API now correctly inherit the property-level Nightly Rate accounting configuration, and rate type changes on pencil reservations now trigger a full tariff recalculation in all cases. 

Fixes & Improvements

Reservations — Nightly Rate accounting now applied correctly on creation

When a property was configured to use Nightly Rate from their accounting configuration, reservations created through the API were incorrectly generating a single total tariff for the entire stay rather than individual nightly tariffs. The API now correctly inherits the property-level accounting configuration.

Affected endpoint: POST /reservations

Reservations — Tariff recalculation on pencil reservation rate type change

When updating a pencil reservation's rateTypeId via PATCH /reservations/{id}, the tariff was only recalculated the first time a rate was assigned. If the rate was subsequently changed to a different rate type, the baseRate and totalRate values in actualAccount retained the original rate's amounts instead of reflecting the new rate. The recalculation logic now triggers whenever the rate type changes to a different value, covering both first-time assignment and subsequent rate changes.

Affected endpoint: PATCH /reservations/{id}

Notes

• Release Date: 23 June 2026 (AEST)  — Beta only
• Please report any issues through standard support channels: https://rmsapi.zendesk.com/hc/en-gb/requests

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 Live release enforces a maximum record limit of 50,000 on key search endpoints. The change improves platform stability and ensures consistent behavior across high-volume query patterns. Requests exceeding the limit now return HTTP 400 Bad Request rather than being silently truncated.

Included in this Live release:

• Breaking Change: Maximum Query Limit — A cap of 50,000 records is now enforced on transaction, guest, and reservation search endpoints; requests exceeding this value return HTTP 400 Bad Request.
  👉 Breaking Change Details: https://releasenotes.rmscloud.com/rest-api-v10.26.105.2----beta-only-breaking-change---maximum-query-limit-4CTw1q
• Beta release: 👉 https://releasenotes.rmscloud.com/rest-api-v10.26.105.2----beta-4BL7va

Notes

• This release is now available in Live
• Release Date: 2 June 2026 (AEST)
• Partner notification sent 17 April 2026: https://mail.rmscloud.com/hey-partner-your-rms-live-release-is-here-0-0-0-0-0?hs_preview=TVgGuAQq-211134018457
• Please report any issues through standard support channels: https://rmsapi.zendesk.com/hc/en-gb/requests