Bug Fixes 26.5.1.0 - 26.5.4.0

View the below list for bug fixes highlighted in this past month's releases: 

• 26.5.1.0 - Wednesday, May 6, 2026

• 26.5.2.0 - Wednesday, May 13, 2026

• 26.5.3.0 - Wednesday, May 20, 2026

• 26.5.4.0 - Wednesday, May 27, 2026

26.5.1.0 

• Mealtime Attendance Including Deleted Leaves – Fixed an issue where mealtime attendance counts were incorrectly including residents on deleted leave records that had no end date. Deleted leaves without end dates are now properly excluded. 

• HCM-Updated Email Not Carrying Over to Alert Center – When an HCM integration (e.g., UKG) updated a staff member's email on an existing profile, the new email was not being synced to the Alert Center; affected staff appeared with a 'No Email' badge or continued receiving alerts at their old address. The integration sync now updates email on alert subscriptions to match the staff's current profile email.

26.5.2.0 

• GL Journal Entry: Incorrect GL Account Selection – Resolved an issue where the Add GL Journal Entry feature was not displaying the correct GL Accounts when creating offsetting transactions, and was generating duplicate Deferred Revenue entries. GL Journal Entry now presents the correct accounts and creates clean offsetting transactions.

• Outstanding Invoices API: Missing Resident Balances – Resolved an issue where the Outstanding Invoices API was not returning balances for all residents at certain communities. Affected communities now return the complete set of residents with unpaid invoices.

• Emailing Prospects Becomes Unresponsive – Resolved an issue where the prospect email interface became unresponsive when attempting to send an email from a prospect record. Emailing prospects now completes as expected.

• All Residents: Room Filter Dropdown Not Working – Resolved an issue where the Room filter dropdown on the All Residents page was not functioning, preventing staff from filtering residents by room assignment. The filter now works as expected.

• API: Null Reference on Bulk Care Task Update with Deleted Tasks – Resolved an issue where the Scheduled Care Tasks endpoint returned a null reference exception when a bulk update included care tasks deleted by a new care plan publication. The endpoint now validates whether each task exists before processing, skipping deleted tasks cleanly.

26.5.3.0 

• Payments collected in the month prior will not apply to an invoice – Resolved an issue where a payment collected in a prior month would fail to apply to an invoice generated in the current month. Payments now apply correctly regardless of the calendar month they were collected in.
• Billing Center: ending a Medication Management package – Resolved an issue where ending a Medication Management package from the Billing Center did not behave as expected. The end date now saves correctly and the recurring charge closes out on the resident ledger.
• Duplicate PRN administration cannot be deleted due to an error – Resolved an error that prevented duplicate PRN administration records from being deleted. Duplicate PRN administrations can now be deleted from the resident's eMAR.
• Vital sign date recording issue – Resolved an issue where a vital sign entry could be recorded under the wrong date in some cases. Vital signs now save under the date the user selects at entry.
• Error when marking an Incident Report task as complete – Resolved an error that prevented Incident Report tasks from being marked complete. Incident Report tasks can now be completed and the resident's incident record updates as expected.

26.5.4.0 

• ALIS Pay: duplicate payment entry after a refund  – Resolved an issue where refunding an ALIS Pay payment could create a second, duplicate payment record on the resident profile. The funding job now correctly excludes credit (refund) settlements when building deposits, so refunds no longer trigger a duplicate.
• Observation Center visibility – Resolved an issue with Observation Center visibility where some observations were not displaying as expected for affected staff. Observations now appear correctly for all roles that should see them.
• Editing service end date also moved the start date – Resolved an issue where editing a resident's service end date also shifted the service start date. The start date now stays in place when only the end date is changed. 
• Unable to action fall risk compliance notifications – Resolved an issue where users could not remind or cancel fall risk compliance document notifications. Both actions now work as expected.
• Historical Census Report inconsistencies – Resolved an issue with the Historical Census report where census data did not display correctly for some date ranges. The report now renders accurately for all queried ranges.
• Empty Nickname fields populating with First Name on export – Resolved an issue where residents without a Nickname were exporting with their First Name in the Nickname column. The Nickname column now exports as blank when no nickname is set.
• Product type history not tracked for imported residents – Resolved an issue where residents created via Import had no starting Product Type history. As a result, the Historical Census and HQ Census by Product Type fell back to the resident's current Product Type and projected it backward across the entire reporting range. Imported residents now get a seed Product Type entry at their HireDate.
• AM time frame returned empty for scheduled med pass records API – Resolved an issue where the scheduled med pass records API endpoint returned an empty list when the AM time frame was selected. Other time frames returned correctly; the AM time frame now also returns the expected results.
• Billing items could not be disabled due to Billing Center Settings – Resolved an issue where three specific billing items could not be disabled because they were incorrectly tied to Billing Center Settings. The affected billing items can now be disabled as expected. 
• One user's actions affecting the view of unrelated users – Resolved an issue where one user's actions could change what unrelated users saw on their screens. Each user's view is now correctly isolated to their own actions, filters, and selections.