The December 2025 release of Alinity was deployed to Test environments on December 9th and was deployed to Production environments on December 18th. A summary of the changes included in this release appear below.
Product Release Webinar
New Features
Inbound Email | Email
With this release, we’ve introduced a new feature that allows administrators to forward emails directly into their Alinity system, including any attachments. There are multiple ways to make use of this feature; such as adding the registrant number in the email subject line or configuring it through your system’s general email address. To learn more about how to make use of the feature, please visit our knowledge base. This includes the ability to forward an email into a complaint or consultation.
Feature Improvements
Register Restriction Functionality Added to UI | Admin
Alinity has long supported the ability to automatically apply a restriction or condition when a member enters a specific register (or section), and to automatically remove that condition when they leave the register. However, until now there was no user interface to add, update, or remove these register-level restrictions, even though the underlying table has existed for years. This meant that you would require support to make updates. We’ve now added a dedicated UI to manage these settings, making the process much more accessible and user-friendly.
Consultation Contacts | Consultations
Alinity now supports adding additional contacts to a consultation with a new “Contacts” tab. This allows for easily linking 1 consultation to multiple profiles as may be necessary.
Bug Fixes
Invalid Transaction Locked Date | Accounting
Previously it was possible to set the accounting transaction locked date to today’s date. The impact of setting it to the current day was that members would suddenly be unable to complete payments that day. There was already a rule in place to prevent lock dates from being set into the future, but we’ve now extended that rule to include the current date as well to prevent this issue.
Renewal Administrators cannot withdraw person form renewals | Admin
Previously if someone had the “Renewal Administrator” permission and attempted to withdraw a person-form renewal, they would experience an error message. This issue has now been corrected.
Allowing Org Reviewers a Read-Only Option for their submitted reviews | Reviewers
Previously, when an organization reviewer finished their review and submitted it, the submission moved into a locked status while regulator staff completed their administrative review. While in the locked status, the reviewer could not see what they had submitted until the final PDF was produced — a process that could take months. We’ve now added a configuration option that allows the regulator to let reviewers view their submitted information immediately, even before the final PDF is generated. This gives reviewers timely access to their own submission while it’s under administrative review.
Provinces & States Searching | Admin
Under the Setup menu, administrators can manage the list of provinces and states in their system. A UI bug was discovered where running a search on that page caused icons to appear in the column headers. This issue has now been fixed.
Detecting a Cancelled/Approved Payment With multiple tabs open | Admin
Previously, Alinity prevented almost all scenarios where a user could access the same payment page twice at the same time. However, there was one edge case: if a pending invoice was opened in two browser tabs and “Pay” was clicked in both, it could result in a payment being approved and then immediately cancelled. We’ve now resolved this issue. While it was a rare situation, additional safeguards are now in place to prevent it from occurring in the future.
Recoding GL Transactions as Deferred Revenue | Accounting
Alinity allows you to bulk-update General Ledger (GL) accounts on GL transactions. However, the deferred revenue account codes were previously missing from the selection list when performing a bulk update. This has now been corrected, and the deferred revenue accounts are fully available for use.
Adjusting Invoice Catalog Items With Deferred Revenue | Accounting
This is along a similar them to the bug just above. Previously, if an invoice contained a catalog item that qualified for deferred revenue (e.g., a renewal) and that item was later changed, the system would no longer treat the resulting transactions as deferred. We’ve updated this behavior so that even when a catalog item is modified, it will still correctly qualify for the deferred revenue account.
Export Page Load Speed | Exports
This month, we’ve optimized the underlying queries used when generating exports to improve overall system efficiency. The user interface and functionality remain unchanged, but the time it takes for the export to run after clicking the export button should now be significantly faster.
Files uploaded to org review forms | Org Form Reviewers
Previously, in some cases where an organization form reviewer uploaded a file to an org form, the document preview displayed the message “File Deleted From Library.” We’ve updated the system so this message will no longer appear when the file is still present.
Designation name appearing across all form sets | Member Portal
In previous releases, we introduced updates to the member experience for databases with multiple designations. For example, if a member had two individual license renewals in progress, both would appear with their associated designation names on their dashboard. However, when the member clicked into one of those renewals, the designation name no longer appeared at the top, making it unclear which one they were viewing. This has now been corrected so the designation name consistently remains visible at the top.
Next release
The January 2026 release of Alinity is scheduled for deployment to production sites January 15th.
English 
French