View the below list for bug fixes highlighted in this past month's releases:
26.7.1.0 - Wednesday, July 1, 2026
26.7.2.0 - Wednesday, July 8, 2026
26.7.3.0 - Wednesday, July 15, 2026
26.7.4.0 - Wednesday, July 22, 2026
26.7.1.0
Resident Transfer: Missing ICD 10 Codes – Resolved an issue where ICD diagnosis codes were not carried over to the receiving community when a resident was transferred between communities.
Invoice Balances Negative from Discount Applied After Payment – Fixed an issue where invoice balances could go negative when a discount was applied after payments had already reduced the balance. Discounts are now capped at the remaining invoice balance, and applying any discount to a zero-balance invoice is blocked with a warning. This applies to invoice-level discounts, charge-level discounts, and discounts auto-applied during billing events.
Physician Order Report Pulling Billing Address – Resolved an issue where the Physician Order Report pulled the billing address.
26.7.2.0
Care Plan PDF display updates – Several display improvements were made to the Care Plan PDF so information appears clearly and consistently. Long Diagnosis, allergy, and diet entries now resize to show the full value instead of getting cut off, and the resuscitation status badge (DNR, CPR, Coding Allowed) displays its full label without cropping. Bold formatting was restored on the Mental Health Status labels (Remote, Recent, Attention Span) and the alignment of the Room and Room Phone fields was corrected.
Physician Order PDF display updates – Corrected two display issues on the Physician Orders PDF report. Service level badges other than "Administer Routine" now print correctly next to orders, and for companies with the E-Signing Physician Documents entitlement enabled, e-sign functionality now appears on the report as expected.
26.7.3.0
Staff Access to ALIS HQ – Clients whose security role was set to "N/A" for ALIS HQ access were still able to click into the ALIS HQ dashboard and view HQ reports. This has been corrected so those clients no longer see the ALIS HQ navigation option and are properly blocked from opening the dashboard or its reports.
Duplicate Residents in Evaluation Center and Reports – The same residents appeared as several identical entries in the Evaluation Center and on the resident's evaluation history, even though only one evaluation existed. The same duplication could appear on related reports such as the Rent Roll and Charge Card. Each evaluation now appears exactly once, and the care level and rate shown reflect the resident's own facility configuration. Affected reports and resident profiles also display one accurate entry per resident.
Missing Care Items from Service and Care Plans – Some care items selected during a resident evaluation were silently not appearing on the resident's care or service plan. Copying now correctly reconnects that content to the destination community, so all evaluated care items reliably flow through to the care plan.
26.7.4.0
Restored ALIS HQ access for corporate and leadership staff – A recent update that correctly hid ALIS HQ from staff without HQ access also unintentionally removed access from some corporate and leadership staff who were entitled to it. Access has been restored, and ALIS now keeps manually granted HQ access separate from role-based access, so only role-based access adjusts automatically when a staff member's role changes.
Unit Occupancy Summary report now matches the Unit Occupancy report – The Summary report could show slightly higher occupancy than the Unit Occupancy (detail) report when a unit's primary occupant moved out mid-month but a secondary occupant remained. The Summary now counts occupancy by primary occupant, matching the Unit Occupancy report, Weekly Occupancy, and Welltower, so the two reports reconcile. Only the Summary report changed; the detail report is unaffected.
Payer profile no longer errors when a saved card is missing its card type – When the payment gateway returned a saved card without an account type, the payer profile, payer accounts, and recurring payment preferences pages could throw a full-page error. Those cards now display normally (holder name, masked number, nickname, and expiry) with no card-brand label, and no data correction is needed.
Voided payments no longer appear on generated statements – A voided payment could still render as a normal payment line item on generated statements, making it look like the payment had been made and understating the outstanding balance. Statements now exclude voided payments the same way they exclude deleted ones, across the Account Balance Forward, Payer Balance Forward, and Payer Open Items statement types and their emailed versions. Voided payments remain visible on the resident's Payments grid for record-keeping. Note: statement PDFs are cached, so any statement that already shows a voided payment must be deleted and regenerated (Statements tab, Options, Delete, then Generate) to correct it.