1. On the Reports => Statistics => Daily Operating Report, the last two digits in the last column were being cut off
2. On Invoices, when making more than one payment on one invoice, with the same payment credit on the account was displaying improperly on the Payment Tab on the Invoice.  For Example the Total charges would display as $100.00, the payment could display as $250.00 but the balance of the invoice was still displaying as $0.00.  Overall the Invoice was correct, with a balance of $0.00 but the display was incorrect
3. In Groups, if a Tag Was assigned on the Contacts & Billing Info Tab and a clerk were to edit something on the tab (such as address or contact name), upon clicking post, the tag would revert back to the first Tag available in the list of tags

1. An error message was occurring when payments were above $1,000.00 due to the comma. Interface has been change to take on the comma when the amounts are communicated between RoomKey and Heartland
2. Error message was being caused by the interface not being able to read "masked" credit cards.  This was due to a different change made in Version 8.23.0.1
3. Error was occurring on certain transactions where the card was swiped when doing a refund, where it would show as a charge instead of a reversal

For properties using version 8.23.0.2 or older, we have disabled the feature that allows you to select which dependent Rate Plans you would like to update, when updating the Master Rate Plan.  For more information on this feature that was originally launched in Version 8.23.0.1 - CLICK HERE:

For guests that make reservations through eRes, a "Forgot Password" option has been added to the Guest Login portal should they return to "Modify/Cancel" a reservation:

1. Reports => Forecasts => Occupancy and Revenue Forecast - Room Revenue associated to Group Block was recognizing the "Days Before" setting on the group; it is now releasing properly based on the cutoff date associated to the Group Arrival Date
2. Operations => Wholesale => Reports => Block Space - the report was showing total block for all accounts on each individual account
3. Operations => City Ledger => Reports => Aged Balance - transfers from other invoices that were at a different age date, were still showing in the different age column when transferred to a new invoice
4. BI Reports => Statistics => by Source of Business - reservations made on the eRes Booking Engine were not being counted
5. If Reservations were checked in after midnight but before 2:00 am, the status was not automatically changing to dirty at 2:00 am
6. Eres was not properly respecting Maximum Length of Stay setting
7. Payments => Credit card fields that used to be manual entry only now support swiped cards including: City Ledger – Multiple invoices, Adding additional cards, and Sundry sales

1. Voice/Forced Authorization code entry is now supported
2. Improved processor response messaging
3. Clerk is now prompted to swipe the credit card when card present is selected to ensure best processing rates
4. Enhanced transaction logging

When running the Aged Balance Reports is City Ledger, there is now an option to include Account Credits.  Go to Operations => City Ledger => Reports => Aged Balance Report => by default, the "Include Account Credits" check box will not be checked:

When the check box is checked, the report will have "Including Account Credits" at the top (when box is un-checked, will say "Not Including Account Credits".  On the Summary report, the Credit will appear as part of the total balance and will show in the appropriate age column based on the date the payment was posted:

On the Detail Report, the credit will show as it's own line and will include the payment type originally used when the credit was posted.  If several different credits exist, each will show based on their age date:

1. For the Siteminder Interface, a field was added that identified the "Primary" guest on the reservation; this has been mapped to RoomKey so that this name will be used as the "Master" guest on the reservation
2. When Reservations that were made from the GDS/IDS Interfaces, were modified to a Group Block, the rooms were not "picking" up properly with the group, thus effecting forecast reports
3. GDS/IDS reservations flowing into RoomKey were not picking up the set Policy properly
4. Issue for some properties on eRes in regards to the sort order on Rate Categories; issue has been resolved