You can expect up to 15 minutes of downtime to deploy this release.
Image displays Monthly Release Notes for September 13, 2026
Release Notes
Extract Accounts into a New Bundle
Selected accounts can now be extracted from an existing bundle and placed together in a new bundle using one of these methods:
Manual Extraction: Select accounts from the Bundle section and use Apply Action → Extract to New Bundle.
Automated Extraction: Use the Extract Bundle Accounts Flow Action to move accounts that match configured Logic into a new bundle.
Accounts not selected for extraction remain in the original bundle.
For releated information, see this article: Account Bundling.
Image displays Extract to New Bundle in Bundle section
Image displays Extract Bundle Accounts flow action
Note
If extracted accounts still meet the configured Bundle Settings, future bundling activity may place the accounts back together. Therefore, before extracting accounts to new bundles, it is important to consider and update existing workflow accordingly..
For example, if this capability is used to segregate accounts into separate bundles, those bundles should be assigned a status code or status code group excluded in the Bundle Settings. Otherwise, automatic or manual rebundling of new assignments or other existing accounts, could produce unexpected results that require significant time to correct.
Additional Preferred Languages
Additional options are now available for selection from the Preferred Language list for demographics, including Creoles and pidgins, Haitian Creole, and Kabuverdianu (Cape Verdean Creole).
Image displays Preferred Language selections
Employer Name Character Limit
Demographic Employer Names can now contain up to 128 characters when entered on the Account Demographics page or imported via ETL, allowing longer employer names to be stored without truncation or errors.
Reassigned Number Database (RND) Monitoring
Reassigned Number Database (RND) monitoring can now be configured to help identify phone numbers that may have been reassigned to a new consumer.
Customers can select which accounts and phone numbers to monitor and set a recheck interval. Enrichment export and import jobs manage the monitoring process, including when phone numbers are eligible to be checked again and the identification of confirmed reassigned numbers.
RND Enrichment is a package add-on. Contact sales@interprose.com for more information.
See this article for additional details: Configuring Reassigned Number Database Monitoring.
Additional ITMS Opt-Out Terms
ITMS now recognizes additional Spanish and French opt-out terms, allowing consumers to opt out of text messages using supported terms in either language.
In place of the word, "stop," the following terms also result in an opt out now:
Spanish | French |
|---|---|
alto | annuler |
baja | arret |
cancelar | arrêt |
darse de baja | arreter |
detener | arrêter |
parar | desabonner |
salir | désabonner |
quitter |
For more details see this article: ITMS Opting In and Opting Out.
Text Log ETL: Text Message Triggers
ETL profiles using "Text Message Logs" Load Method now include a Fire Text Message Triggers option.
When enabled, the loading of this data will initiate the onAfterTextInbound trigger which can be configured to update data like the associated phone number as a Wrong Number.
The option is disabled by default for existing profiles.
Image Displays the Fire Text Message Triggers option in the ETL Import Data Options section.
Payment Plan Duration Limit
ACE and Virtual Agent 2.0 now limit payment plans to payments scheduled within 40 years.
If a proposed plan exceeds this limit, the consumer is prompted to increase the payment amount or contact the agency for another arrangement.
VA 2.0 Credit Card Expiration
Virtual Agent 2.0 profile configuration for, "Do Not Allow Payment Plans Past Credit Card Expiration" prevents consumer's from creating a payment plan if the identified credit card expires before the final scheduled payment.
The message the consumer sees has been improved. Now, when the identified credit card is expired, the consumer is prompted to adjust the payment plan or select another payment method.
Pay N Seconds ACH Credits and Refunds
ACH payments processed through Pay N Seconds can now be credited or refunded in the ACE application.
NACHA Block Padding
NACHA files can now be configured to meet financial institution requirements for a blocking factor of 10.
The setting is available for:
NACHA Transfer Methods – Used when generating NACHA files for outgoing remittances from a Trust Account.
NACHA Payment Destinations – Used when generating NACHA files for incoming consumer ACH payments.
When enabled, ACE automatically pads the generated NACHA file with records of 9s until the total record count is divisible by 10.
For more information about NACHA files see this article: Configuring NACHA Transfer Methods.
Image displays Nacha Blocking in Payment Destination and Nacha Block Padding in Trust Account Transfer Method.
Forward Placement Descriptions
Forward placements can now include a description, making it easier to identify and group related placements. The placement description is also available in account summaries and Logic Blocks.
Image displays Placement Description field in Forward Distribution
Clone Configuration Settings
Clone functionality is now available in several areas, making it easier to create similar configurations without recreating the settings manually.
Clone is available for:
Worklists
Client, User, and Attorney Commission Rates
States
Payment Destinations
Transaction Spreaders
Action Codes
Image displays Clone button in an Action Code
Fixed These:
There was a scenario where new account assignments were placed in separate bundles instead of matching existing bundles during the ETL load process. This issue is fixed.
Pay N Seconds credit card refunds could fail when the original transaction did not include a service fee. This issue is fixed.
Failed Pay N Seconds credits and successful Pay N Seconds refunds were sometimes remaining in a CREDIT_PENDING status. This has been fixed. Now after settlement, these failed credits are updated to FAILED and the successful refunds are updated to CREDIT.
ACH payments with a Company Name could be assigned an incorrect SEC code. Payments with a Company Name are now assigned the CCD SEC code.
There was a scenario where cancelling an account could break the Responsible Party (RP) bundle it was part of. This has been fixed.
nvoices using certain OpenDocument templates could fail to generate, resulting in an error and no downloadable invoice file. This issue is now fixed.
Tax amounts did not automatically recalculate when commission was manually adjusted or removed from a payment. This issue is now fixed, and tax amounts recalculate based on the updated commission amount.
Virtual Agent could display different balances between the Summary and Account Details when a Bundle Group Filter was configured. This issue is now fixed, and balances, account details, and payment selections consistently reflect only the accounts included by the Bundle Group Filter.
The Extra Payment confirmation window in Virtual Agent 2.0 could proceed before the consumer made a selection. This issue is fixed, and the consumer must select Yes to confirm the extra payment before continuing.
Archiving accounts could leave bundle totals out of sync, which could cause subsequent archive jobs to fail. This issue is fixed and ACE keeps bundle counts and balances synchronized as accounts are archived.
Payments could encounter a deadlock error during collection cost processing, causing transactions to remain unspread. This issue is fixed, allowing payments and collection costs to process successfully.
Client Access users could receive permission errors after saving profile changes or updating their password. This issue is fixed, and configured Client Access features remain available without requiring the user to sign out and back in.
The Bankruptcy screen could display unmasked SSNs for users assigned the SSN - Always Masked role. This issue is fixed, and debtor and co-debtor SSNs are masked according to the user's permission role.
Date and time values could appear clipped in RI report parameters, making the full selected range difficult to view. This issue is fixed, and Date/Time Range fields display the complete selected values.
Rainmaker Insights HTML reports sent using Report Runner: Run as User could arrive as unusable HTML attachments. This issue is fixed, and supported HTML reports display directly in the email body. Reports that cannot be embedded continue to be delivered as attachments.