Release Notes 08/17/2025

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

In This Issue

• ZeroBounce

• Client Charges

• Payment Backdating

• Worklist Logic Filter

• Report Runner Format

• Date Range Selectors

• VA 2.0 Payments

• Text Logs

• ETL Account Updates

• VA 2.0 Address, Phone and Email Address

• VA 2.0 for Reflection

ZeroBounce

A new job task, "ZeroBounce: Scrub Emails," is now available to simplify the process of validating and enriching email addresses using the ZeroBounce Email Vendor.

Keep an eye out for explicit configuration examples and best use case workflow provided with an upcoming Tips and Tricks email.

Please see this article for contact details related to the vendor: ACE Third Party Vendors.

Client Charges

In order to enter or adjust Client Charges when posting an adjustment to an account bucket's balance, the user will now need to have the CLIENT_CHARGES Permission. It is included by default in the "Manage - Client Charges" Permission Role.

In addition, users were not able to successfully update client charge amounts to zero when entering adjustments. Now they are able to.

Client charges are also now visible in the adjustment page so the user will be able to see the amount that is going to be a client charge per client charge configuration before deciding if they need to alter it.

If you are unable to modify your permissions or permission roles to meet your needs, please reach out to Support.

Payment Backdating

Client Access Users were previously unable to enter a payment with a Transaction Date prior to the end date of the last invoice. They were able to enter a payment with a Transaction Date matching the end date of the last invoice.

Now Client Access Users are unable to enter a payment with a Transaction Date up to and including the end date of the last invoice.

Worklist Logic Filter Updates

The following updates impact users who have the permission role, "Worklist - Logic Filter" allowing them "View List" access from the Worklist dropdown option in the ACE Toolbar.

The Find Usage button is now only visible to users with the LOGIC_MANAGE permission.

The Test button remains available but now limits results to accounts in the selected worklist when used from list view.

For details on using Worklist Logic Filters, see this article: Worklist Logic Filter Overview.

Report Runner File Format

When configuring the “Report Runner: Client” and “Report Runner: Run as User" job tasks, selecting a new Format for the report to be generated in will automatically override the Output File Name extension and deliver the report in the selected format.

Date Range Selectors

Date range selectors throughout ACE have been updated. Now, when any date range option, other than Custom, is selected, the date fields will be grayed out. The date fields will not be disabled, but changing them does not override the range option selected.

To change the dates selected, the "Custom" option should still be selected before modifying the dates.

There will also be a visible label shown identifying the date range option selected.

Duplicate Payment in VA 2.0

When a user with an active payment plan logs into VA 2.0 and attempts to make an additional payment, a warning message will now appear.

Text Logs

A column has been added to Text Log Lists so the user may show the “Txt Msg Vendor Identifier."

ETL Account Updates

The Account Updates - Optimized ETL Import Load Method now includes most of the Data Options that are available for the Account Updates - Legacy Load Method.

The “Overlay" option is not included because the “Account Updates - Optimized” Load Method will overlay existing data by default.

VA 2.0 New Address, Phone and Email Address

The onAfterVirtualAgentPersonUpdate trigger can now be used to load a new address, phone number or email address that has been added or updated by a consumer using VA 2.0.

We’re providing an example of JavaScript that can be used to simultaneously verify and set the new demographic address, phone number or email address as priority 1. We’re also providing an example of a SQL report that can be used to identify changes initiated in this way so they may be reviewed as necessary.

The JavaScript and report examples can be found in this article: How VA 2.0 Handles Consumer Contact Updates.

VA 2.0 for Reflection

Virtual Agent 2.0 is now available to be configured for Reflection customers. For more information, please contact Sales at sales@interprose.com.

Fixed These:

• There was an issue where the VA 2.0 default profile logo appeared instead of the client’s consumer logo; this is now fixed.

• There was an issue where resolving a dispute incorrectly displayed the message 'New Dispute'; this now correctly shows 'Dispute Resolved.”

• There was an issue where the FORWARD_TO_<vendor_id> flag was removed before export file generation was complete. This has been fixed.

• There was an issue where text or email templates were using a different VA Profile Company Name associated with the phone number or email address than the one the text or email message was being sent from. Now, the template uses the VA Profile from the account that most recently contacted the number.

• There was an issue where documents were logged for MMS validation texts that were not actually sent. Adjustments have been made to ensure documents are only created for successfully attempted messages.

• There was an issue where client access users could not cancel accounts when those accounts were bundled with accounts from a different client. This is fixed.

• A scenario was discovered where attempts to respread legal transaction batch payments that had been unspread were failing. This has been fixed.

• MMS messages were erroring out when an associated file (uploaded as the Text Msg Profile’s MMS Document) included an upper case extension. This has been fixed.

• There was a scenario, when debts were deleted, which resulted in orphaned debt_stats. Now debt_stats will be deleted at the same time a debt is deleted.

• There was a scenario where mail return reasons were loaded to the demographic, but not the demographic address. Subsequently, saving the account was resulting in removal of the mail return reason from the demographic record. Now if the account is saved, the primary demographic address will be updated to match the mail return reason on the demographic record.

• Reordering account page sections under Setup → User Interface → Account View was not working as expected and sections associated with a future feature were visible. This has been fixed. In addition, the section label for “Notate Account” has been updated to “Work Account” to match the user interface view of the Account Page.

• Previously, there was a scenario where a payment could be entered by a consumer in the VA 2.0 and then a subsequent duplicate payment could be entered while the first payment was still processing (having a Status of INITIALIZE). This has been fixed and now, if they attempt the same payment a second time within 10 minutes of the first, the consumer will receive an error with this message, “A payment for this amount is still processing. Please feel free to contact us if you require assistance.”

• Passing in a primary demographic to the Create Debt API call was causing an error. That’s been fixed.

• There was a scenario occurring where the full amount of a payment associated with an account being archived was being removed along with the archived account even if a portion of the payment had been spread to a different bundled account that was not being archived. That is no longer occurring.

  • Please Note:

    • 1) The spread transactions are now retained for both archived and unarchived accounts associated with the payment, but the payment data originally recorded in a batch is not retained.

    • 2) Before archiving accounts, it is important to be sure payment batches have been deposited and any payment data required for records is otherwise retained.

• The “Document: Transfer From” job task “Only Download New Files” option was resulting in an error when a file in the destination folder had a null filename value (even though the file name label was visible). That has been fixed.

• The Client Access User fix for Additional Authentication released in July was not working as expected. It is now. Client Access Users will not be expected to authenticate twice even if additional authentication is configured for all ACE Users and separately for Client Access Users.