Available from: 22 July 2026

What's New

A new Invoice To field is now available on the Reservation Account screen, allowing you to specify the person or entity receiving services separately from the person or entity paying or receiving the invoice.

This is particularly useful for properties that need to issue invoices to a service recipient for GST/VAT claims, while billing a different party.

How It Works

• Bill To — the person or entity paying or receiving the invoice (unchanged from current behaviour)
• Invoice To — the person or entity receiving the services from the property

The Invoice To field:

• Defaults to the same entity as Bill To (no action required if both are the same)
• Can be changed independently to a different Guest, Company, or Travel Agent
• Appears directly beneath the Bill To drop downs on the Reservation Account screen
• Once set, it is retained even if Bill To is subsequently changed
• Drives the recipient details shown on generated invoices (Tax Invoice, Statement, Grouped Tax Invoice, Receipt, Refund, and Print Transaction)

Example Scenarios

What You Need to Know

• No configuration is required — the field is available automatically on the Reservation Account screen
• Existing reservations will default Invoice To to the current Bill To value
• If you do not change Invoice To, your invoicing behaviour remains exactly as it is today
• Generated invoices will reflect the Invoice To entity as the recipient

Who Benefits

Properties operating in regions with GST/VAT requirements where the payer and the legal service recipient may differ — ensuring compliant invoices can be issued to the correct party for tax claims.

Click here to read more in our help articles

We've resolved an issue where the price displayed on the results screen did not match the price shown in the cart when a guest searched for more people than a category's maximum occupancy allows.

Previously, the displayed rate was calculated using the full guest count entered in the search, while the cart recalculated the price based on the category's maximum occupancy — resulting in a price drop between the two screens, which could cause confusion or distrust for guests at checkout.

The displayed rate now caps at the category's maximum occupancy, ensuring the price a guest sees on the results screen is always consistent with what appears in their cart.

Cancellation policies are now displayed accurately throughout the entire booking journey, respecting the hierarchy in which they are configured in the PMS.

Previously, the IBE did not consistently honour the cancellation policy hierarchy, meaning lower-level policies (such as those set at the Rate Type level) could display even when a higher-level policy had been configured to override them. This affected the rates page, the confirmation page, and the confirmation email.

The IBE now correctly applies the following hierarchy, with higher-level policies always taking precedence:

1. Control Panel
2. Rate Table
3. Rate Period
4. Rate Type Property Rule
5. Derived Rate Type
6. Rate Type

Guests will now see the correct cancellation policy at every step — from browsing rates through to their confirmation email.

We've resolved an issue where a new guest profile was being created in the PMS each time a returning guest made a booking through the IBE, rather than linking the reservation to their existing profile.

This resulted in duplicate guest records building up in the system, creating extra overhead for property staff and affecting the integrity of guest data.

The IBE now correctly detects when a guest's details match an existing profile and associates the new reservation with that record — keeping guest data clean and accurate.

Rates that cannot be booked due to restrictions are now displayed on the booking engine rather than hidden, giving guests full visibility of all available rate options for a room or category.

Previously, restricted rates were removed from the results entirely, leaving guests to assume a rate didn't exist rather than understanding why it was unavailable. This could lead to unnecessary drop-off or guests booking elsewhere.

Restricted rates now appear greyed out with the "Book Now" button disabled and a clear inline label explaining the restriction. The following restriction types are covered:

• Closed to Arrival — "Can't arrive on [days]"
• Closed to Departure — "Can't depart on [date/days]"
• Minimum Length of Stay — "[X] Night Minimum"
• Maximum Length of Stay — "[X] Night Max" (shown as an informational label even when the rate is still bookable, and as a restriction when the stay exceeds the limit)

Guests can use these messages to understand what date adjustments are needed to access a rate, reducing confusion and improving booking confidence.

Summary

This release fixes two issues with GET /properties/{id}/discounts where the endpoint was returning duplicate discount records and discount records that are no longer active in the system. The endpoint now returns only valid, configured discounts for the property.

Fixes & Improvements

Property Discounts — Duplicate and Removed Records Returned

GET /properties/{id}/discounts had two issues that caused it to return incorrect records:

• Duplicate records — the same discount could appear multiple times in the response.
• Removed records — discounts that are no longer active in the system were still being included in the response.

The endpoint now returns only valid discounts configured against the property, with each discount appearing once. Note that expired discounts continue to be returned, as these remain valid configured discount records until explicitly removed or deactivated.

• Endpoint affected: GET /properties/{id}/discounts 

Notes

• This release is now available in Beta & Live
• Release Date: 15 July 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 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

We're at the halfway point of the year, and your RMS environment has been busy. This quarter's update brings payment automation to RMS, real performance data from Apple Pay in the wild, a visual booking upgrade that's rolling out now, and a new community platform built for operators like you.

Here's what's new 👇

Payments that run without you

Advanced Payment Schedules

The chase is over. Advanced Payment Schedules are now generally available — set your deposit, instalment, and balance rules once, and RMS collects automatically, on schedule, without follow-up. Works across all property types and stay lengths, and connects directly with RMS Pay so every collection happens without a manual trigger. 

🔗 Learn more.

Automated Payments Dashboard

Every transaction across your property, in real time. The Automated Payments Dashboard gives you a single view of what's paid, what's pending, and what needs attention — covering credit card, direct debit, and SMS payment links. No more running reports to find out where you stand. 

🔗 Learn more.

Apple Pay with RMS Pay — what we're seeing

Apple Pay has been live with RMS Pay since Q1, and the numbers are worth talking about. Tokenisation means the card number is never shared with your property, which cuts online fraud by around 30%. Approval rates are up — Visa reports up to 4.6% more online transactions going through on average. Our RMS Pay users who have enabled Apple Pay are seeing authorization rates of over 96%. And properties enabling Apple Pay are seeing around 18% more bookings completed at checkout, simply by removing the friction of card entry.

The other thing worth knowing: when a guest's card is lost, reissued or expires, their Apple Pay token updates automatically. No failed renewals. No chasing guests for new card details. It just keeps working. 

A better way to book, visually

Interactive Maps — now rolling out

Guests can now pinch, zoom, and click their way to the perfect spot. Interactive Maps are rolling out across the RMS Booking Engine, letting guests browse your property visually — sites, amenities, availability — and book directly from the map. If you already have a map, it'll be updated automatically. If you don't have one yet, reach out and we'll get you set up. 

🔗 Learn more.

Something new: RMS Community

Your seat at the table

RMS Community is live at community.rmscloud.com. It's the central place where RMS customers connect with each other, get answers, and have a direct say in where the product goes next.

Three spaces to explore:

• News & Announcements — product updates, events, and company news straight from RMS
• Member Lounge — peer discussion, networking, and industry conversation with operators across every vertical and region
• Support Desk — fast answers from people who've been there, linked back to the Help Centre

Getting started takes a few minutes: visit community.rmscloud.com, create your account, and follow the setup wizard. Once you're in, click + New Post to start a conversation or jump into one already happening. 

🔗 Join RMS Community

From the field: Sadie AI in the wild

Beachport Caravan Park — first 30 days

Beachport Caravan Park switched to RMS from Newbook and added Sadie AI in their first month. Here's what happened.

Sadie handled 684 calls. 376 of them — 55% — were resolved entirely without staff involvement. 42 bookings were captured, worth $9,720 in revenue. 122 rates and availability enquiries were tracked for retargeting, and 49 offers sent on behalf of the property, representing $11,346 in potential booking value.

One month. One integration. A materially different operation.

Sadie AI is available now as an RMS Partner integration — and for a limited time, new RMS customers can try Sadie free for one month. 

🔗 Learn more about Sadie AI.

Ready to get started?

These updates are live in your RMS environment now. Whether you want to activate payment automation, explore Interactive Maps, or join the RMS Community — your mid-year upgrade is ready and waiting.

🔑 To activate new features in your RMS subscription, contact our expansion team.

🎬 See it all in action. Watch our Mid-Year Momentum webinar, available on demand.

Payment schedules are now managed exclusively at the individual reservation (child) level within group bookings. The system no longer creates or applies payment schedules at the master reservation level, providing a clearer and more predictable experience when working with grouped reservations.