Release Notes 12/14/2025

You can expect up to 15 minutes of downtime to deploy this release.

In This Issue

• New Reporting Update

• Garnishee/Employer

• Click-to-Call

• Client Access Payments

• Client Access Overpayments

• MMS Validation Notices

• Text Message Profiles

• Email API Endpoints

• Max Report Rows

• SQL Queries

• Job Last Run Duration

New Reporting Update

To ensure a smooth and accurate transition to the new HI (Helical Insights) Reporting tools, the full migration has been delayed. We now expect to retire the original core reports, original dashboards, and original custom reports between now and the March 2026 Release.

Custom reports will be migrated individually at the customer level to ensure accuracy and continuity. Our team will reach out directly to coordinate your custom report migration and to confirm successful recreation in the new reporting environment.

Your current reporting experience remains unchanged for now.

The HI Reporting Preview continues to be available for exploration.

We appreciate your patience and understanding as we take the time necessary to deliver a reliable, intuitive, and future-ready reporting experience. Our goal is to ensure every customer has a smooth transition — with the right tools, support, and communication along the way.

Garnishee and Employer Updates

Demographic Employer records can now be populated by selecting an employer from those stored in Garnishee records.

1. The list of Garnishee records will be available in a drop down list from the Employer field.

   1. Please note, selecting an employer from the drop down list does not auto-save and the Demographic record must be saved in order to store the data populated to the Employer record.

2. The Employer record in the Demographic record now has four additional fields that can be populated:

   1. Employer Source → populated from a static list of available options.

   2. Employer Status → populated from a static list of available options.

   3. Previous Employer → open text field.

   4. Employment Verified → selectable field.

3. The Account Search page now has an option to search by Employer Name.

   1. Please Note: In order to search by Employer Name, the user must have a permission role including the permission, “ACCOUNT_SEARCH_DEMOGRAPHIC_EMPLOYER” which is not included in any permission roles by default. You may need to reach out to a support representative to add this permission to a permission role.

   2. The Employer Name may be selected from a static list of garnishee options.

   3. The Employer Name may still be entered as text above the open drop down list if it does not exist in the list of garnishee options. When searching based on a text entry, wild cards can be used. For example, “French%” will return accounts where the Employer name is “French and Company.”

Click-to-Call

When using click-to-call to initiate a non-U.S. phone call, the phone number will now display and use its country code for dialing.

Client Access Payments

When a client access payment batch is being automatically created so client access users can post transactions, the payment batch will now include, “DIRECT-CLIENT_ACCESS,” inside the parentheses of the label regardless of the payment destination used which will continue to be included in the Label.

Please Note

Client Access User Interface payment patches that are automatically created will continue to identify the Receiver as “DIRECT.”

Client Access Overpayments

There is a new option in the Client Access User Interface configuration to allow or prevent Overpayment by client access users.

Please Note

Because client visible buckets may not include the full balance that a consumer owes, the client may still post a payment that exceeds the visible amount owing that they see even if “Enable Overpayments” is set to False. In addition, when “Enable Overpayments” is set to True, overpaid amounts will not show up for clients if the Overpayment Bucket is not a client visible bucket.

MMS Validation Notices

The documents associated with Validation Notices sent via MMS that are stored to the account will now be “VA Visible” by default. “VA Visible,” values will not be altered for existing documents.

Text Msg Profiles

The Text Msg Profile page now has a new “Parsed Body” field where the user can see how a message will appear when it includes field variable data associated with the current or most recently viewed account.  

In addition, there is a new “Recalculate Cost” button that will display the expected cost for the message based on the “Parsed Body.”

Email API Endpoints

API endpoints for creating, updating, and retrieving demographic emails addresses are now available. They can be found under “The Account API” section.

Max Report Rows

The Setup → System → Max Report Rows field has been locked down to reduce system stability problems experienced by customers when running reports. If a customer needs this number altered, please reach out to our support team to help assess reports and make necessary changes.

SQL Queries

If an executed SQL query is about to exceed available memory, the query will be aborted and an error will be presented.

Job Last Run Duration

A “Last Run Duration” column is now available to be added to the jobs list (similar to the “Duration” column available for the Job Logs page).

Fixed These:

• Selecting any non-primary demographic email address from the summary section was resulting in an error indicating, "Resource Not Found". This has been fixed.

• Overpayments were sometimes caused in error when multiple responsible party accounts were included in the same judgment. This has been fixed. Now payments will only spread to one responsible party account in the same responsible party bundle and the payments will continue to be reflected to all responsible party bundle accounts as expected.

• After archiving a primary bundle member account, the other bundle members were no longer returned when searching for archived or unarchived accounts. This has been fixed. It is important to note that a new primary bundle member account will be assigned based on the customer’s account bundling configuration.

• Two legal_case fields, “Serve Response By Date,” and “Serve Response By Date Age”, were showing up null for logic blocks. That has been fixed. They are now available and working as expected for logic blocks. Please Note: When searching for accounts by “Serve Response By Date Age,” those with a “Serve Response By Date” in the future will only show up when including a negative number in the range, a positive number in the range will include those with that date in the past.

• Previously, account documents loaded via API were not respecting the vaVisible parameter if that was being included in the request. Now they are.

• In the account demographics page and summary section “DOB Age in Years” included the word “Days” next to the number of years. This has been corrected.

• When a consumer attempted to log into an account with a protected status, they were seeing an error. That has been fixed. Now they will be directed to the page identifying the account as Ineligible for the Virtual Agent.

• A recent NACHA file failure pointed out issues resulting in a bank refusing the file. These issues have been fixed. In addition, it was identified that a value needs to be populated in the “Nacha Statement Label” field on the Transfer Method.

• When a phone number had zero received or sent text messages, text templates were not available from the text log page. They are now.

• When an important note had previously been saved to a primary account, using “Apply To” to apply other changes was adding the important note to the other accounts. That has been fixed. Now only Important notes entered immediately prior to using “Apply To” will be added to the accounts selected at that time.

• A parsing error was occurring in some scenarios when enforcing IP restrictions. This has been fixed.

• There was a logi error appearing for dashboards. That has been fixed.

• When the Create Payment Plan API Method (under "The Account API" list in API Documentation) was used, it wasn't working for the Promise Plan payment destinations. Now it is.

• When reference numbers were used with addresses being loaded via address ETL, erroneous errors were being generated. This has been fixed.

• Logi login failures were preventing logins. Now Logi login failures will timeout allowing logins to succeed after 10 seconds.