The Lumary 25 release will include improvements for notional rates in financial extracts, smart file uploader, incident ownership and notifications, DEX extracts, sessions improvements and more. 

Lumary has made some technical changes as part of a wider strategy to enable functionality moving forward. If you have any issues, please raise a ticket with our Customer Success team or reach out to your account manager.

This release also includes improvements for:

• Salesforce spring '26 updates
• include notional rates in financial extracts
• introducing smart file uploader
• incident ownership and notifications
• DEX extract changes
• sessions improvements
• restricting file sharing and downloads on mobile
• other bug fixes and improvements.

Salesforce Spring '26 updates

List view sorting

Blank or empty values in list views appear at the bottom when sorting in ascending order (previously appeared at top). Please be aware that if you have any custom or private list views where you expect blank values to appear first, they will now appear last when sorting in ascending order. This change will reflect in your environment when the Salesforce Spring '26 upgrade is deployed, likely the weekend of February 21st 2026.

SAML Single Sign-On migration

If your organisation uses SAML for single sign-on (SSO), you must migrate to the multiple-configuration SAML framework before the Salesforce Summer '26 release to prevent SSO login disruptions. Check Setup → Release Updates to see if this applies to your environment.

Run Flows permission

To ensure your users do not encounter any issues using features with flows, follow the steps below for profiles assigned to users in your environment. 

This can be done before your environment is upgraded to Salesforce Spring '26.

Back to links

Notional rates

Include notional rates in financial extracts

We've introduced a new opt-in feature to handle notional rates consistently in both NDIS and financial extracts. This feature improves accuracy for providers using financial extracts and aligns the behaviour with NDIS extracts.

With this option enabled, extracts generated after enablement will follow the new settings:

• when a notional rate is used, the unit price is set to $1 and the quantity is increased to the total Service Delivered value accordingly, ensuring compliance with NDIS guidelines and preventing claim rejections by plan managers.

• users will now see the notional rate set on the Extract Item for NDIS and Financial Extracts, previously this was implemented at the point of file generation for the NDIS Extract.

• to indicate to which Extract Item records have been processed using the new feature and whether the rate is notional, we’ve introduced a new checkbox field for NDIS Notional Unit Price on Extract Item to easily identify these records.

You can enable or disable the ‘Enable Notional Unit Price on Extract’ setting directly from the General tab in Lumary Settings.

Back to links

Smart file uploader

Introducing our new client smart file uploader feature

We’ve introduced a new Smart File Uploader, providing a central interface for uploading client files. This improvement streamlines documentation, enhances compliance, and makes it easier to track and locate key client information.
With the Smart File Uploader, from a client record users can simply drag and drop or browse to select a file, choose the relevant file type, and then either link it to an existing open record or create a new record—all from one place. This eliminates the need to navigate across related lists to find or create the correct client-related record for the file.

Available options and actions will depend on the user's object and record type permissions.

Check out our article about adding and storing files on a client's record.

If your organisation uses custom Lightning record pages for client records, you can add the component by following the guidance in this article:

• Add a tab and/or component to a customised Lightning page layout.

Back to links

Incident ownership and notifications

New incident ownership and notifications feature

We’ve introduced new Incident Management ownership and notification features to make it easier to configure, manage, and automate how incidents are assigned and communicated across your organisation. When enabled, incident ownership is automatically assigned on creation based on the incident’s type and sub-type, with new incident notifications sent according to your configuration.

Key highlights:

• A new Incident Management Settings screen provides a central place to manage incident ownership and notification rules.
• Automated incident assignment ensures incidents are routed to the correct owner for both site-related and non-site-related incidents.
• Email and bell notifications are sent based on your setup.
• Incident owners receive email notifications when ownership of open incidents is reassigned, including a direct link to the record.
• Flexible override options allow ownership and additional notifications to be configured by incident type and sub-type, with support for users, groups, roles, and queues.
• A new default Incident Management Queue ensures incidents are always assigned when no specific configuration is found.
• Improved visibility with the Owner field added to Incident record page, and the Site field displayed when applicable.
• If this feature is disabled, incident ownership will remain as the submitter, or according to any other ownership customisations you may have in your environment.

These enhancements simplify configuration and provide a more consistent, transparent incident management experience. Find out more about managing incident ownership and notifications.

To use this feature you must follow the steps below for any profiles your organisation has assigned to users submitting incidents:

Back to links

DEX extract changes

Improved DEX Extracts: Now handling large data sets

The DEX Extract will now automatically separate extracts when more than 2,500 records are included within the extract. Lumary will create a Parent DEX Extract record with multiple child extracts. 

This update improves reliability and performance for high-volume days by splitting the DEX Extract into manageable files, ensuring all data is included and reducing the need for manual intervention.

When the DEX Extract is divided into multiple extracts:

• Only the Parent DEX Extract appears on the Lumary Extracts screen.

• The Parent DEX Extract record will have no records in the Extract Items related list. Instead,  there will be related child Extract records in the ‘Extract’ related list.

• When creating the file for the DSS, this will be attached to both the Parent DEX Extract and to the Child DEX Extract.

• Deleting a Parent DEX Extract does not delete its child extracts. After the Parent DEX Extract is deleted, child records will appear on the Lumary Extracts screen.

Refer to our create a DEX extract guide for additional guidance.

Exclude Cancellation Service Delivered in DEX Extract

Cancelled Service Delivered records can now be excluded from the DEX Extract, in line with CHSP guidelines. A new setting 'DEX Include Cancellations' on Rate Type reference data allows you to control whether cancellations are included, giving you flexibility to meet reporting requirements. This means that when a service is marked as cancelled, it will no longer appear in the DEX Extract or its generated XML, ensuring compliance and reducing unnecessary data for providers.

Reporting of MAC ID in DEX Extract

Functionality has been added to DEX Extracts to support providers that are now required to capture whether a client is registered for My Aged Care (MAC) and their unique My Aged Care Id, as part of  Commonwealth Home Support Program (CHSP) reporting requirements.

To enable this reporting Provider’s can add the HASMACID to the DEX Activity Specific Requirements on the Rate Type.

Once the DEX Activity Specific Requirements includes HASMACID, clients with a My Aged Care Number in Lumary will now have this data available in the DEX Extract. To view the new XML fields RegisteredForMAC and MacId under the Client Node. Check out our DEX XML mapping to CM fields and objects article.

Validation has also been added to ensure that when the DEX Activity Specific Requirements include HASMACID, a valid My Aged Care (MAC) Number must be provided for the client. The MAC Number must start with 'AC' and contain exactly eight numerical digits. If this information is missing or incorrectly formatted, users will receive a clear error message during the extract process. Ensuring providers are meeting upcoming mandatory reporting requirements.

Back to links

Sessions improvements

Improved support category picklist

We have improved visibility of support categories when adding a planned service using the sessions wizard. Users can now see all available options, and will not need to scroll. This makes it easier to view and select support categories during session creation.

Resolved visibility of available clients when creating group sessions

We’ve resolved an issue where the Select Clients field could be empty when creating group sessions, preventing users from adding clients to planned services. This fix applies to both the Client Calendar and Sessions Calendar.

Cancelled workers hidden from sessions on mobile

Workers with cancelled worker appointments will no longer appear on sessions in the mobile app.

Editing sessions with recurrences

The recurrence dropdown now consistently appears the first time users edit a session with recurrence in the Session Edit modal. This resolves an issue where the option was missing on initial edit, making it easier to apply changes to individual or multiple sessions in the series.

Users will also see clear error messages when attempting to edit sessions that are completed, cancelled, or in progress, providing a more user-friendly experience.

Saving recurring sessions with conflicting appointment warnings

Users can now save new recurring sessions, even if there is a conflicting appointment warning on the last page of the New Session Wizard. This fix restores the ability to save or roster sessions in these scenarios, ensuring that users are presented with warnings but not blocked from completing their scheduling tasks in the Sessions, Client, and Worker calendars.

Session Error When Adding Planned Service

We’ve resolved an issue where users encountered a component error when adding a planned service in the Session Wizard, for clients with multiple service agreements and different funding management.

The Funding Management field is now correctly displayed and validated, ensuring planned services can be saved and sessions created without error. This improves reliability when rostering sessions for clients with complex funding arrangements.

Back to links

Restricting file sharing and downloads from mobile

To enhance client information privacy within the mobile app, follow these steps to restrict mobile users from saving, sharing or printing files. 

Back to links

Other Bug Fixes and Improvements

Block Grant Service Agreements improvement - The creation and editing of Block Grant Service Agreements now consistently set the Funding Type to ‘Block Grant’ and the Rate Type fields to the selected rate type. This update ensures data consistency across all Block Grant Service Agreements, improving the accuracy of reporting and related workflows.

Funded Client improvement - The Funded Client batch update process has been improved to handle large numbers of records without error. Funded Client statuses will now update reliably, even when more than 200 records require processing, ensuring accurate and timely status changes for all affected records.

Funding Period fix - A warning is now displayed in Funding Periods when the combined total of Committed and Delivered funding exceeds the allocated amount. This update helps users identify potential overspend earlier, ensuring better management of funding allocations and reducing the risk of claim rejections.

Travel Non-Labour Expenses fix - Travel Non-Labour Expense Child Service Delivered records now correctly populate the Site Services/Program field based on a hierarchy of available matches, ensuring alignment with the parent service details. This issue only impacted Travel Non-Labour Expense Child Service Delivered records when the parent Service Delivered matched a Site Services/Program, but the Provider travel - non-labour costs service did not have a corresponding Site Service Program record.

Bed Allocation start and end date validation improvement - A new validation rule has been added to Bed Allocations to ensure the Start Date/Time cannot be set after the Expected End Date/Time. Both fields are now required when creating or editing a Bed Allocation. This update prevents invalid date entries and ensures consistency across all booking methods.

Default Dates when creating Assessments, Consents, and Personal Support Plans improvement - When creating new records in the objects below, the listed date field will now default to the current date, with the option to adjust the value when applicable:

Permissions

Permission sets

We've made updates to the permission sets shown in the following table. If you have custom or cloned permission sets that include these objects, we recommend that you add these permissions.

Back to links

Follow us to get update notifications

You can follow sections in Lumary's Help Centre with your Help Centre account. If you follow a section, you'll receive email notifications  whenever a new article is published in that section, or when an article is republished.

To follow the section that contains this article:

1. Go to the CM release notes section. This section currently appears under Releases > CM releases.
2. Click on the Follow button.
3. If you're not already logged in, you'll be prompted to log into the Help Centre. You'll need a Help Centre account.
4. Select New Articles.
5. A message will appear confirming that you are now following this section and the label on the button will change to Following. The system will send you an unstyled version of new or updated pages.