Summary

This release adds support for POS supplied tax values when posting charges, improves how per-person requirements are returned, and improves property access handling across reports and related endpoints. Charges can now carry the tax amounts from the source system. Per-person requirement quantity and amount now match RMS 9+, and property information is now returned only to tokens with access to the specified property. There are no breaking changes in this release.

New Features

Charges: POS supplied tax valuesFix 

You can now send the tax amounts from your source system when posting a charge, instead of RMS calculating them. Both fields are optional, and charges sent without them behave exactly as before.

• inclusiveTaxOverride: { "taxAmount": 0.00 } sets the inclusive tax amount for the charge.
• exclusiveTaxOverrides: [{ "taxId": 0, "taxAmount": 0.00 }] sets the amount for each exclusive tax, using the RMS tax ID. Tax IDs can be found in RMS.

How it works:

• Overrides apply as sent, whatever the tax setup of the sundry. An inclusive override does not remove an exclusive tax line the sundry would normally post.
• A value of 0, an empty array or an empty object posts the charge with no tax. 
• A taxId sent without a taxAmount is treated as 0.00.
• Values are stored exactly as sent, in the same currency as amount.
• Overridden tax appears in the folio and reports in the same way as calculated tax.
• In a bulk request, each charge is handled independently.
• The charge is not posted and a 400 error is returned if an amount is negative, the tax is higher than the charge, a tax ID is repeated within one charge, or a tax ID doesn’t exist or is inactive.

Affected endpoints:

• POST /transactions/charge - Swagger documentation
• POST /transactions/charges - Swagger documentation

Fixes & Improvements

Per-person requirements: quantity and amount now match 9+

Requirements that are charged per person now show the same quantity and amount in the REST API as they do in 9+ and on the guest account.

Before this update, the API could show a quantity of 0 and an amount that didn’t match what the guest was charged. Quantity is now the sum of the adults, children and infants set on the requirement, and amount is the sum of the per-adult, per-child and per-infant charges.

The response now also returns noOfAdult, noOfChild and noOfInfant for each per-person requirement.

If a per-person requirement is added through the API with its own price override, the requirement doesn’t store guest counts, so these three fields return 0. Quantity is the total number of guests on the reservation, and the amount is calculated from the override prices. Both match 9+.

Affected endpoints:

• GET /reservations/{id}/requirements - Swagger documentation
• POST /reservations/requirements/search - Swagger documentation

Property access: information is only available to tokens with access to the property

We improved how property information is handled so that it is only available to tokens with access to the specified property. If a request references a property, category, area, reservation or account the token cannot access, the API returns a 400 error (for example, “Invalid propertyId for the supplied token.”) and no data is returned or changed. Requests for properties the token can access work as before.

What to expect:

• Where a request leaves out properties or areas, results now cover only the properties the token can access. This applies to History Forecast, Area Income Summary and Audit Trail search.
• Audit Trail search no longer returns reservation entries for properties the token cannot access.
• An unknown property ID on these endpoints now returns a 400 error.

This improvement applies to the following reports and endpoints:

Reports:

• POST /reports/areaIncomeSummary
• POST /reports/cash
• POST /reports/charge
• POST /reports/debtorsLedger
• POST /reports/expensesAreaSummary
• POST /reports/flash
• POST /reports/historyForecast
• POST /reports/nightAudit
• POST /reports/npsResults
• POST /reports/occupancy
• POST /reports/occupancyByArea
• POST /reports/occupancyRevenueComparison
• POST /reports/pace
• POST /reports/pathfinder
• POST /reports/performanceII
• POST /reports/revenueAndExpense
• POST /reports/villa/financialExtract

Other endpoints:

• POST /auditTrail/search
• POST /messageCentre/guestportal/acknowledgement

Swagger documentation: https://app.swaggerhub.com/apis-docs/RMSHospitality/RMS_REST_API/1.4.48.1

Notes

• Release Date: November 10, 2026 (AEDT), Live and Beta
• 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