NOTE: This release is currently available to all Windows PC users. A notification will be sent to MAC Users once a new build for the macOS is available.
Microsoft OAuth 2.0 Authorization - Emails sent from RoomKeyPMS
As of September 2025, Microsoft will discontinue the use of App Passwords for SMTP outgoing email authentication. Going forward, all systems using Microsoft to send outgoing mail must be configured to use OAuth 2.0 Authentication.
If you currently use a Microsoft account to send emails from RoomKeyPMS, please download Version 11.0.0.49 and follow the instructions in the document below to configure your Registry Tab with OAuth 2.0 Authentication: Microsoft OAuth 2.0 Authorization - Emails sent from RoomKeyPMS
Completing this update is essential to ensure uninterrupted email functionality.
Enhancements/Updates:
Token expired message during SSO Login => In Version 11.0.0.45, a new "Token Expired" message was introduced to alert Clerks who remained logged into RoomKeyPMS for more than 24 hours. However, this message began appearing incorrectly for Clerks logged in via Microsoft SSO after approximately 20 minutes, even though it should not appear for SSO users.
This issue was initially believed to be resolved in Version 11.0.0.47. However, it was later discovered that the message would still appear for SSO users after being logged in for over an hour.
Further investigation and testing have now been completed, and this issue has been fully resolved. The "Token Expired" message will no longer appear for Clerks accessing RoomKeyPMS using Microsoft SSO.
CSV saving option not always available on Quickbooks Export => it was reported by a Client that when attempting to save the Quickbooks Export as a CSV file, the .CSV option would not always appear in the Save As drop down. This issue has now been resolved.
Unable to reverse/adjust a moved Payment => It was recently discovered that if a payment was moved more than twice between reservations, attempting to reverse that payment would trigger the "Previous Processor Reversal/Adjustment" screen, even though the payment was processed through the current processor. A server-side fix addressing this issue was deployed on July 21st, 2025. With this update, transactions can now be moved between multiple different reservations and still be reversed or adjusted properly, without prompting the "Previous Processor Reversal/Adjustment" screen.