The Lumary 26 release includes improvements for enhanced funding period management, DEX Stage 3 extract changes, automatic household creation, smart file uploader support, travel & transport budgeting fixes, enabling incident submission with third-party systems, enhancements to custom extract features, CHSP Client contribution fee overrides, and other improvements and fixes.

We'll publish confirmation of what's been included by updating this page when the release is made available in production environments.

If your organisation uses Lightning Sync (for example, to sync sessions to Outlook), Microsoft is retiring the underlying technology (Exchange Web Services) in October 2026, which will permanently break Lightning Sync with no workaround available. It is recommended that you complete the below steps as soon as possible to allow time for testing before the October EWS retirement:

1. Migrate from Lightning Sync to Einstein Activity Capture (EAC) using the built-in Migration Assistant in Salesforce Setup.
2. Upgrade your Microsoft connection from EWS to Microsoft Graph API.

This release includes improvements for funding period management, DEX extract updates, automatic household creation, incident management submissions, custom extract enhancements, smart file uploader, fixed travel & transport budgeting, PMHC MDS Version 5.0 changes, and other improvements and fixes.

Centre Capital Cost (CCC) improvements: 

• ability to override centre capital cost quantity on service agreement items
• disable auto-generate service delivered records on centre capital cost (CCC) line items

CHSP Client contribution fee overrides:

• override CHSP client contribution fee (negotiated client contribution)

Funding Period Enhancements:

• edit individual period amounts independently
• modify period start and end dates
• prior period rollover transparency, and
• enhanced funding period visibility

General contacts:

• automatic household creation

Incident management:

• enabling submission with third-party systems

Lumary engagement console:

• console improvements
• multi-recipient support, and
• SMS templates.

NDIS July 2026 price guide changes:

• service changes for 1 July 2026 pricing, and
• updated Support Item Code suffixes

PMHC MDS Version 5.0:

• version 5.0 overview
• reporting Veteran Status
• IAR-DST Practitioner Reason for Override,
• Program Type updates, and
• new MMHC system tags for referrals

Self serve Custom Extracts:

• guided, step-by-step pathway for custom extracts, and
• enhanced SortBy capability

Smart file uploader:

• supporting documents, and
• smart file improvements

Travel & Transport budgeting and billing:

• fixed travel & transport budgeting

Updates for DEX extracts:

• DEX Stage 3 changes, and
• Service Delivery Entry (SDE) includes new DEX Stage 3 fields

The release also includes several bug fixes and other changes.

We’ve also included updates to permission sets.

Centre Capital Cost (CCC) improvements

Ability to override Centre Capital Cost quantity on Service Agreement Items

You can now set a specific quantity for Centre Capital Cost (CCC) charges on Service Agreement Items, allowing you to accurately bill for the actual hours a participant attends a centre, rather than the hours billed for the support. This ensures CCC charges reflect true centre usage, specifically in scenarios like 2:1 supports.

When the Override Centre Capital Cost quantity field is set on a Service Agreement Item, the Quantity on any Centre Capital Cost Service Delivered records created for this item will be overridden with this amount.

This update improves billing accuracy and transparency for centre-based services.

Back to links

Disable auto-generate Service Delivered Records on Centre Capital Cost (CCC) line items

The Auto-generate Service Delivered Records option is now hidden for Centre Capital Cost (CCC) line items. This change helps prevent accidental duplicate service delivered records when the parent service is already generating CCC child SDs, reducing the risk of double claiming for CCC services.

For organisations that wish to continue to enable the ‘Auto-generate Service Delivered Records’ option for Centre Capital Cost (CCC) line items, it can be re-enabled via the Lumary Custom Setting Allow CCC Service Delivery Item Schedule. If you have any issues, please raise a ticket with our Customer Success team or reach out to your account manager.

Back to links

CHSP client contribution fee overrides

Override CHSP client contribution fee (negotiated client contribution)

Providers can now select a Client Contribution Rate directly on individual service agreement items for CHSP individual service agreements. Where multiple contribution rates exist for a service, the appropriate rate can be chosen at the time of creating or editing the Service Agreement Item, giving greater control over how client contributions are configured per service line.

Selected rates can be further adjusted by applying either a percentage discount or a negotiated dollar amount (supporting up to two decimal places) to override the standard fee waiver on a funded client. If a Client Contribution discount is already applied at the funded client level, a warning will be displayed so users are aware of both settings.

When generating service delivered records, any configured rate and override are applied automatically — covering both the parent DEX service delivered record and the linked client contribution child record. This ensures client contribution charges accurately reflect the rate and any discount or negotiated amount set at either the service agreement item or funded client level, improving billing accuracy and consistency.

Service delivered records now use the specific Client Contribution Rate selected on the service agreement item when calculating the client contribution (including updated rates). If no rate is set on the service agreement item, Lumary will continue to automatically select the most appropriate Client Contribution Rate based on existing rules. This improves accuracy and consistency for CHSP client contribution charging when different rates apply to the same service.

Back to links

Funding Period Enhancements

Edit individual period amounts independently

Providers can now manually edit individual funding period amounts on service agreements, to match a participant's actual plan structure including front loaded first periods and uneven initial allocations. Previously, allocations were automatically distributed based on the number of days in each period, which did not always align with the monthly splits used in a participant's NDIS plan. You can now override these calculated amounts to reflect the actual agreed funding for each period, ensuring service agreements accurately represent what has been negotiated and reducing discrepancies during billing.

Back to links

Modify period start and end dates

Providers can now edit the start and end dates of individual funding periods directly from the view all periods modal on a service agreement aligning to a participant's actual plan structure. Previously, date adjustments required deleting and rebuilding the service agreement entirely. When a period's end date is changed, the following period's start date automatically adjusts to maintain continuity, and the same applies in reverse when a start date is modified. This makes it straightforward to accommodate NDIS plans that start mid-month, include plan reviews, or have unequal period lengths.

Back to links

Prior Period Rollover transparency

The rollover amount carried forward from a prior funding period is now displayed as a standalone value in the funding period UI, giving providers clear visibility of how much of the available balance is new allocation versus rolled-over underspend from previous periods.

When a period closes with unspent funds, the balance automatically rolls over to the next period. The upcoming period card always reflects the current period's projected rollover in real time, calculated as: Allocation + Rollover − Delivered = Unspent Balance.

The rollover amount appears in two places:

• The "View All" funding periods modal, as a dedicated column after the Total column.
• The inline funding period component on the Service Agreement, shown on the active (highlighted) period, positioned below the Total row and above the Delivered and Committed rows.

Previously, the rollover amount was factored silently into the Remaining Balance, making it difficult to reconcile available funds or distinguish between plan-allocated totals and carry-forward amounts.

Back to links

Enhanced funding period visibility

Inside each Support Category on a service agreement, the Funding Periods panel now shows a set of period cards designed to give you the most relevant information at a glance. Based on provider feedback, the panel displays exactly three periods:

The rollover amount appears in two places:

• One completed period: the most recently closed period, showing what was delivered and what rolled over.
• One current period: the active funding period with live balance figures.
• One upcoming period: the next period, with the projected rollover already reflected based on the current period's unspent balance.

Each period card shows the following six figures:

Back to links

General contacts

Automatic household creation

Lumary now supports automatic Household Account creation for General contacts, bringing this capability in line with the existing behaviour for Client and Intake contacts.

A new setting, Create General Contact Household Accts, has been added to the Lumary Settings > General tab. When enabled, a Household Account named "[Last Name] Household" is automatically created and linked to a General contact at the point of save, provided no existing account has been selected. The new setting is off by default.

The existing Create Household Accounts setting has also been relabelled to Create Client/Intake Household Accounts, with updated help text for clarity.

Note for organisations with existing custom solutions: If your organisation currently has a custom flow in place to handle Household Account creation for General contacts, you should deactivate that flow before enabling the new Lumary Setting to avoid conflicts.

Back to links

Incident management

Enabling submission with third-party systems

Organisations that manage client incidents using a third-party system can now configure Lumary to redirect users to their external incident submission form, rather than using the built-in Lumary incident flow.

When the new Custom Incident Submission Form URL setting is populated in Lumary Extended Settings, clicking the Submit Incident / Feedback button will display a prompt directing users to the external system, with a link that opens the setting’s URL in a new tab. If the setting is left blank, the existing incident submission experience is unchanged.

Back to links

Lumary Engagement Console

This release includes updates that apply to organisations using the Lumary Engagement Console, powered by the Pendula for Salesforce Managed Package (version 3.0).

Console improvements

• Message status visibility — messages are now colour-coded to indicate outgoing queued (dark grey), sent (green), and error (red) states, making it easier to identify delivery issues at a glance.
• Console refresh — the messaging window can now be refreshed manually or set to auto-refresh every 30 seconds, without reloading the full page.
  
• Activity Timeline — inbound and outbound SMS messages now appear chronologically in the Activity Timeline on any Salesforce record.
• Permission sets — the package now ships with native permission sets for controlling access to Console features, making it easier for Salesforce Administrators to manage user access without custom configuration.

Find more information on the related Lumary Engagement Console features.

Back to links

Multi-recipient support

The Console now supports messaging multiple recipients from a single client record. A common scenario where a client has nominated all communications to be directed to the primary contact. Rather than storing the primary contact number on the participant’s record (creating duplicate data), users can now toggle to the client’s primary contact from the console and send messages directly to the appropriate person.

This reduces replicated contact data across your organisation and removes the risk of duplicate messages being sent to the same number.

Back to links

SMS templates

You can now create and reuse SMS templates directly within Lumary. Templates are created by users with the Pendula Template Designer permission set and can be selected from the Console when composing a message.

This update means:

• Staff can send standardised messages without needing to build or manage Pendula flows, reducing dependency on trigger- or schedule-based automation.
• Users without prior Pendula knowledge can author and send templated communications entirely within Lumary.

Find more information on SMS Templates.

Back to links

NDIS July 2026 price guide changes

Service changes for 1 July 2026 pricing

Lumary has been updated to reflect the updated NDIS Pricing Schedule effective 1 July 2026. This includes new services added to the support catalogue, services with updated support item number suffixes, and services that have been removed. See our service changes for 1 July 2026 pricing for the full list.

The Pricing Arrangements and Price Limits (PAPL) has been rebranded as the ‘Pricing Schedule’.

Back to links

Support Item Code Suffixes

ALREADY FIXED IN Lumary 25 Patch  To align with the NDIA's July 2026 pricing update, we’ve updated the Service Delivered extraction process for applicable Allied Health services with a delivery date on or after 1 July 2026. When an applicable service has a claim type such as cancellation, non-face-to-face, provider travel, NDIA requested report (report writing), or telehealth, Lumary will append the suffix (_CA, _NF, _PT, _RR, or _TH) to the support item code automatically and append the Claim Type to the Service Name on the extract item when creating an extract.

These changes apply across the NDIS extract, financial extract, AR Management bulk invoice extract, and Invoice PDF. Additionally, Claim Type and Cancellation Reason will no be included in these extracts but will continue to be retained on the Service Delivered for your records.

For example, an SD with the support item 15_610_0128_1_3 - Assessment Recommendation Therapy or Training - Art Therapist with Claim Type of Non face-to-face, when extracted the item will use the support item code 15_610_0128_1_3_NF, and the name “Assessment Recommendation Therapy or Training - Art Therapist - Non Face-To-Face”

This change ensures compliance with the new NDIA reporting requirements while allowing users to continue to record SDs and claim types as they do today.

Back to links

PMHC MDS Version 5.0

Version 5.0 overview

We've enhanced Lumary PMHC MDS reporting capability, with this release incorporating updates to support Version 5.0 of the PMHC MDS data specification, including:

• support for reporting Veteran Status on Intake and Episode records
• ability to report the IAR-DST Practitioner Reason for Override,
• Program Type updates, and
• new MMHC system tags for referrals.

As part of this update we will not be including the updates to support the collection of Universal Aftercare data, as this is only required where organisations are providing the Universal Aftercare program. 

Back to links

Reporting Veteran Status

Functionality has been added to PMHC MDS reporting to support the collection of Veteran Status, as required under Version 5.0 of the PMHC MDS data specification. This update aligns with DVA recommendations and other health data set standards for capturing veteran status.

A new Veteran Status field is now available on both Intake and Episode records. Once the Veteran Status field is populated on a client's Intake or Episode record, this data will be included in the PMHC MDS extract using a standardised code set. Validation has been added to ensure the field is completed before an extract can be processed, as it is a required field under the 5.0 specification.

Back to links

IAR-DST Practitioner Reason for Override

A new Practitioner Reason for Override field has been added to IAR-DST Assessment records. This allows practitioners to record the reason they recommended a different level of care than the level calculated by the IAR Decision Support Tool, and will be included in the PMHC MDS extract.

Back to links

Program Type updates

The Program Type field on Intake and Episode records has been updated to reflect current program naming:

• MMHC, for episodes being delivered through the national Medicare Mental Health Centre program.
• Head to Health has been renamed to Head to Health Clinic. This response is only to be used by remaining temporary Head to Health Clinics in New South Wales and Victoria.
• Supporting Recovery, for supports being provided under the Supporting Recovery pilot.

Back to links

New MMHC system tags for referrals

Mental Health Data has published a new requirement for Medicare Mental Health Centres (MMHC) to capture referrals to the Medicare Mental Health Centres Centralised Tele-psychiatry and Tele-psychology Service (Centralised Service) in the PMHC MDS.

Two new fields, ‘RHC referral – psychology' and 'RHC referral – psychiatry’, have been added to PMHC MDS Episodes to support this. When either field is selected on an Episode, the corresponding system tags (!rhcpsychology and/or !rhcpsychiatry) will be automatically included in the PMHC MDS extract.

As these tags are only intended for use by MMHCs, and the PMHC MDS enforces this requirement, a validation rule has been introduced that restricts these fields to episodes with a Program Type of MMHC.

Back to links

Self serve Custom Extracts

Guided, step-by-step pathway for custom extracts

Custom Extract configuration is complex, requiring users to understand JSON structures and field mapping concepts. To make it easier to configure custom extracts, we'e redesigned the Custom Extract page with a guided, step-by-step pathway. 

Users progress through four stages: Extract Configuration, Field Mapping, CSV Mapping, and Review & Complete. The pathway offers contextual instructions at each step, lets users navigate between stages, and removes outdated quick action buttons for a streamlined experience.

Back to links

Enhanced SortBy capability

The current Custom Extract Sort By requires users to write SOQL ORDER BY clauses manually, creating a barrier for non-technical users. This enhancement replaces free-text SOQL input with an intuitive, sentence-style interface that lets users build sorting rules via dropdowns.

Back to links

Smart file uploader improvements

Supporting documents

A Supporting Documents object is now available, allowing providers to attach client-related files to associated Supporting Documents records rather than directly to the client. The Smart File Uploader now handles the Supporting Documents object, making it easier to manage and organise client files. Desktop users will see updated related lists and a new Link Supporting Document button on the packaged client page, and updated permission set access.

Back to links

Smart file uploader improvements

A loading spinner now appears in the Smart File Uploader while the file type list is loading. This provides clear feedback to users and ensures the available file types are displayed immediately once the modal opens, improving the upload experience.

You can now upload .msg email files using the Smart File Uploader. The Migrate Client Files feature also supports transferring .msg files from Client records to related records. This enhancement makes it easier to manage and migrate email correspondence within client records.

The smart file uploader has been updated to reduce the component’s height, providing a more streamlined appearance. 

Back to links

Travel & Transport budgeting and billing

Fixed travel & transport budgeting

Providers can now configure fixed travel and transport amounts directly on NDIS service agreements. When the Enable Fixed Travel and Transport Budgeting setting is turned on, an agreed fixed travel and/or transport value can be set per service agreement item, and is automatically applied to services delivered to claim the fixed amounts. 

This includes total distance and time travelled to and from the appointment, total distance transporting the client, and whether a modified vehicle or bus was used. Users will still be able to record actual travel and transport values that will be stored separately when completing appointments.

Back to links

Updates for DEX extracts

DEX Stage 3 Changes

To support the Australian Department of Health's updated Data Exchange (DEX) requirements, we’ve introduced new mandatory fields for CHSP services, as per Data Exchange (DEX) Stage 3 Changes, effective from 11 August 2026.

The Stage 3 fields included are: Delivered By Third Party, Volunteer Direct Service, DEX Service Location Setting, Overnight Support Included, Engagement Time Minutes, Trip Distance (KM), Trip Time (mins), Meal Provided, Meals Cooked Offsite, Meals Texture Modified, Main Meal Count, Light Meal Count, Dessert Count, Beverage Count, and Snack Count. To view the new XML fields under the Session Node check out our DEX XML mapping to CM fields and objects article.

To enable this we have included the above fields on Service Delivered and Extract Items records, and have also introduced translations for DEX Service Location Setting. Validation has also been added to the DEX extract generation process to ensure the DEX Service Location Setting field is correctly populated before an extract is submitted.

For Providers required to report any of the new stage 3 fields, you will need to configure the DEX Service Type Specific Requirements in Lumary according to the requirements in your organisational data provided by DEX.

Back to links

Service Delivery Entry (SDE) includes new DEX Stage 3 fields

To support the Australian Department of Health's DEX Stage 3 reporting requirements as per Data Exchange (DEX) Stage 3 Changes, the Service Delivery Entry (SDE) screen now dynamically displays the relevant DEX fields based on the DEX Service Type Specific Requirements selected. Users only see the fields relevant to the service being delivered.

The new fields cover a range of service-specific information, including whether a session was delivered by a subcontractor or involved a volunteer, overnight support, session location setting, engagement time, and time.

Further capturing meal details, trip distance and travel time, and assistance items.

Back to links

Bug fixes and other changes

The following bug fixes and changes are also included in this release.

Client Contact improvement - The Contact Type formula field on the Client Contact object has been updated to display the relationship or type, instead of displaying a value of Other if none of the checkbox options have been selected.

Client Summary PDF fix - Client Summary PDFs now regenerate successfully when triggered by record updates by any user, including workers using the mobile app. This update ensures that PDF generation no longer fails due to insufficient permissions, providing reliable and up-to-date client summaries across all user roles and workflows.

DEX Statistical Linkage Key (SLK) generation fix - We resolved an issue with the generation of the Statistical Linkage Key (SLK). Previously, when a client's first or last name was less than two characters long, the missing character positions in the SLK were incorrectly populated with '2'. These positions are now correctly filled with '9' to indicate that the name information is unknown, in line with the DEX SLK algorithm requirements.

Incident Management fixes:

• Resolved an issue where a "Hmm, that didn't work" error message was displayed to mobile users immediately after submitting an incident, despite the incident being created successfully. This fix provides a smoother experience for mobile users.
• We’ve increased the character limits for key fields in the Log Incident and Feedback workflows to help prevent errors when special characters or formatting are included. Users will now see a clear validation message if their input exceeds the new limits, allowing incidents and feedback to be submitted successfully without data loss. This update improves reliability when entering detailed information, especially for fields involving summaries and descriptions.

New Task button fix - Resolved an issue where the New Task activity button was missing for certain user profiles on Contact (client, worker) and Enquiry records. The button appeared for some profiles but not others depending on how Salesforce resolved the underlying quick action, but is now available consistently.

Planned Services fixes:

• We’ve resolved an issue that allowed a block service agreement item to be selected in a planned service for a funded client that was expired (outside of the start and end dates). Now, only valid service agreement options will be displayed to add as a planned service to a session.
• When creating a session that included both a mix of Face-to-Face service and Non Face-to-Face components, and the participant's support agreement contained multiple service agreement items(SAI’s) with different claim types and delivery ratios, the system was linking planned services to the wrong service agreement items. An incorrect delivery ratio was also occasionally applied. Planned services are now linked to the correct SAI based on their claim type and the delivery ratio selected at the time the session is created.
• When entering a planned service quantity above 99 in the session wizard or the Modify Clients & Services right-click action, users received a The number is too high validation error. The cap has been raised from 99 to 999 to support use cases where quantity represents kilometres or other high-value units.

Purchase Order Items improvement - The Quantity field on Purchase Order Items now supports decimal values, making it easier to enter and view quantities such as hours. Previously, users could capture decimal values but these were visually displayed as whole numbers.

Recurrences improvement - A new frequency of services field has been added to recurrences, providing a clear and readable summary of how often services are scheduled (e.g., "every day", "every 3 months", or "every fortnight – Monday, Wednesday, Friday"). This enhancement makes it easier for users to understand service schedules at a glance.

Related Files component fix - We’ve fixed an issue where the Related Files component on Contact records could fail to load and show no files when a provider’s environment contained a custom field with the same API name as a packaged Assessment Lumary field. The component now correctly targets Lumary packaged fields, preventing conflicts with custom Assessment fields and ensuring Related Files load as expected.

Service Agreement rollover fix - Service Agreement rollover has been updated to maintain the original recurrence end date for any line items that had already ended before the new agreement start date. This prevents auto-scheduled Service Delivered records from being generated for past dates after a rollover. In addition, automated scheduling will now stop generating Service Delivered records when either the Service Agreement Item end date or the recurrence end date occur before the next scheduled delivery date.

Service agreement rollover improvement - When rolling over a service agreement and the Transfer Appointments checkbox is ticked, a new banner now appears explaining what that option does. This makes it clear what will happen to the appointments before you confirm the rollover.

Service Delivered improvement - Service Delivered records will now automatically flag Delivered By Third Party when the selected Rate includes an Agency, removing the need for manual updates. This enhancement ensures more accurate tracking of third-party service delivery across Service Delivery Entry, Purchase Orders, and Sessions. This logic has been applied for all rate types, in preparation to support CHSP stage 3 changes where provider’s will need to report when a Session/appointment is delivered by a sub-contractor.

A subcontractor delivered the session where the person(s) who provided the service directly to the client is not an employee or volunteer of the funded organisation.

Service Delivery Entry (SDE) fixes:

• We've resolved an issue on the Service Delivery Entry screen where clicking the edit (pencil) icon on a Service Delivered record would fail to open the edit modal. This occurred when a field such as Client Contribution was included the SD field set, causing the record to be uneditable. The edit modal now opens correctly regardless of custom field configuration.
• A fix has been applied to the Service Delivery Entry screen where apostrophes and double quotes in participant names, comments, and case notes were being incorrectly displayed as HTML character codes (such as ' and ") instead of the actual character. Participant names, comments, and case notes will now correctly display these characters as literal text throughout the Service Delivery Entry screen.

Session fix - When the address on an Education Setting (Account) or Site record was updated, the new address was not reflected on any rostered sessions at the related location. This could lead to the incorrect and old address appearing on the session. Now, when an address is updated, the relevant sessions are also updated to reflect the new address. Furthermore, the latitude and longitude values of the new address are also updated on the session to ensure maps and location based services have the correct geolocation.

Travel & Transport fix - We've resolved an issue when editing a Worker Travel (Appointment Travel) record, the Worker Appointment field was displaying as read-only and blank, which meant it was impossible to save any changes made due to a validation rule.

Worker Contact improvement - Worker end date can no longer be set to a date before the start date. A validation rule now prevents a worker record from being saved if the end date is earlier than the start date.

AR Management

AR Management Settings fix - resolved an issue where an unhandled error appeared when viewing invoice templates in the AR Management settings. Users can now reliably view invoice templates without encountering errors, improving the experience for both admin and non-admin users.

Invoice PDF fix - We have resolved an issue where adding a child relationship field to the Invoice Item Field Set would cause an error on the invoice PDF generation. For example Service Delivered > Comments. Users can now include these fields without errors, ensuring all relevant details can be included and display correctly.

Invoice PDF improvement - Invoice templates now include an option Exclude Worker from service details to hide the Worker name in the Service Details section of the Invoice PDF, protecting worker privacy when practitioner details aren’t needed. This can be managed within the AR Management tab. When this option is enabled, the Worker is not included on the invoice.

Invoice reminder and overdue email template fix - We’ve resolved an issue with the invoice reminder and overdue email template fields in AR Management, causing emails to be sent with the Send Invoice Email Template content instead of the selected template content.

Journal Extract fixes:

• GST Collected was being posted as a credit on credit notes, incorrectly increasing the ATO liability. This is now correctly posted as a debit.
• Accrued Income and Trade Debtors figures were transposed on credit notes, amounts are now posted to the correct accounts.
• Payment refund journals were not being created in AR Management, these have now been added.

NDIA Payment reconciliation improvement - We have enhanced the invoice generation process for NDIS claims to resolve timing issues between claim submission and payment. Where NDIA has already processed payment before invoice generation runs (A claim is already marked as paid before an invoice has been generated), Lumary will now automatically create the invoice and the corresponding payment record simultaneously. This ensures that invoices are immediately transitioned to a 'Paid' status and correctly reconciled, removing the need for manual workarounds and preventing orphaned records.

NDIS Remittance File fix -  We've resolved an issue where processing a large NDIS remittance file would fail with a SOQL query row limit error, preventing payment records from being created and leaving the NDIS extract stuck in an unreconciled state. Payment records are now created successfully for remittance files of any size within supported platform limits, allowing the extract to reconcile and the billing workflow to continue without interruption.

Back to links

Permissions

Permission sets

We’ve made updates to permissions on 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.

Apex Classes

The below Apex Classes have been assigned to the relevant permission sets as part of this release.

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.