Release Notes 01/18/2026

New
  • Published on Jan 15, 2026
  • 3 minute(s) read
  • Gina Magana
 Prev Next

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

Image Displays Winter Scene

In This Issue

  • Joined Accounts

  • HI Reporting

  • New Formatting

  • VA 2.0 Login

  • Chat Escalation

  • Account Summary

  • Speed Posting

Joined Accounts

There is a new feature allowing customers to connect related accounts. In ACE, these related accounts are referred to as, "Joined Accounts."

When multiple individuals (like members of a household or family members) have debts that are not directly related, this feature allows the accounts to be joined together for reference.

They are distinguished from bundled accounts or responsible party accounts because they are joined to be a source of related information and are not configured to have demographic data merged to or propagated from them. Payments do not spread to the other joined accounts.

Please see the article for additional information related to this new feature: Joined Accounts.

Image Displays Joined Accounts Section

HI Reporting – Ongoing Enhancements

The HI (Helical Insights) reporting and dashboard Preview remains available while we continue refining the user experience.

Please see this article for basic steps to access the Preview New Reporting feature: Preview New Reporting.

New Formatting Functions for Text and Email

Dates, zip codes, and currency in Email Templates and Text Templates can now be formatted as show in these examples:

  • format_date(${debt.assignedDate}, "MM-dd-yyyy")

    • formats 2025-01-07 to be displayed as 01-07-2025

  • format_zip(${client.zip})

    • formats 123456789 as 12345-6789

  • format_currency(${debt.currentBalance}, "###,###,###,###.##")

    • formats 34567.5 as $34,567.50

Please see these articles which include a variety of date formats available:

VA 2.0 Login

The Google Authorization option for Virtual Agent login with ACE has been removed due to low usage.

Chat Escalation SQL Field

The debt.escalated field is now available to be added to queries in the SQL Designer. This field will return t (true) if a consumer has escalated a chat conversation to a human. Otherwise it will be f (false).

See this article for additional details regarding Rainmaker chatbot escalation: Escalation Request.

Image Displays Example Chat Escalation SQL Query & Report

Account Summary Section

Original Demographic fields can now be added to the Account Summary Section.

Speed Posting to Judgment Accounts

Before this change, in the Speed Posting page, when you enter an account number to search for, the search results will include any account that has that entered number as its reference number, client account number, or customer account number.

After this change, the results list will also include any account that has a judgment case ID that matches any of those original results (i.e. if the original search returns 3 matching results, and each of those results has 1 other account with a matching judgment case ID, then the new search results will return 6 total results).

The agent will be able to select the judgment account to post the payment to it.

Fixed These:

  • Jobs scheduled for the last day of the month were sometimes failing. This has been fixed.

  • Emails related to accounts across multiple clients were not visible in email logs for users who didn't have data roles for all of the clients associated with the included accounts. This has been fixed. Now, if a user has data role(s) to one or more of the clients, they will now be able to see associated email in the email logs.

  • When using Clear Cache from the Help -> About page, API cache was not being cleared, sometimes resulting in an error. API cache is now being cleared.

  • Repay $0.00 (zero dollar) Credit Card and ACH auth transactions were not processing as expected. They are now.

  • Previously, when switching between phone numbers in the text message log, an error was presented. That is no longer occurring.

  • When using these three fields in Logic Blocks—Primary Agent Username, Primary Agent Informal Name, and Previous Primary Agent Username—and applying these conditions (=, <>, or "not empty"), an error was presented. Using those same search criteria no longer results in an error.

  • When single payment promo codes (with settlement type = true) were used by a consumer, they were receiving an error. That has been fixed.

  • Original Demographic fields were not all available for invoices and correspondence. They are now.

  • When entering an ACH payment using a wallet, the Preferred Contact Method wasn't available. It is now.

  • Bundle propagation following a debt save was causing a deadlock. This has been fixed.

  • The Apple Domain ID has been removed from the VA Profiles page because customers do not need to populate it with a distinct variable (the required value is not distinct and it is now being automatically populated).

  • While speed posting, after entering payment details, if an account with a different client commission was selected, the commission was not being recalculated. It is now.

  • Searching for archived accounts was resulting in an error. That has been fixed.

Related articles