You can expect up to 15 minutes of downtime to deploy this release.
Image Displays Summer Field
In This Issue
Global Lookup Forms
Email Logs
Auto-Retry NSF
Run Action Paths
Action Manager Updates
Joined Accounts
Client-Charge Remittance
Commercial ACH
ACE2ACE Forwarding
Probate Forward Type
Inactive Clients
Security Credentials
Job Scheduling
Responsible Party Itemization
Legal Case Fields
API Delete Endpoint
API FlowAction
VA 2.0 Custom Text
Commission Rate Logic
Payment Plan Commission
Account Settlement Rules
Global Lookup Forms
A global Lookup Form Config Type is now available where customers can create and store reusable data in reference tables. The stored data can be configured to later be selectable from other Form Config Types in ACE.
Key Features:
Create standalone LOOKUP forms to store reusable datasets
Define a primary key field to be used when choosing records in that dataset
Add LOOKUP fields to other Form Config Types (Debt, Client, Transaction)
Manually enter data or import data using the Lookup Form ETL Load Method
View lookup record details via Manage Lookup Rows
Access lookup data in reporting and SQL queries
For more information read: Global Lookup Forms.
Image Displays Global Lookup Form Example
Email Logs
The account's Email Log page now includes a "Download All Emails" option. Using this option, a zip file will the emails on the account can be created and downloaded.
Image Displays Download All Email Logs
Please Note:
If an account has a high volume of email history, this process may take some time.
Auto-Retry NSF Options
There are new options on the Payment Destination page to configure "Auto-Retry NSF Days" and "Auto-Retry NSF Max Count".
Image Displays Auto-Retry NSF Days Field
Image Displays Auto-Retry NSF Max Count Field
Run Action Paths from Account Manager
A new option is available in Account Manager to run action paths directly.
Key Updates:
Execute action paths from within Account Manager
Account Manager job logs include the name of the action path that was executed for clearer tracking and visibility
Image Displays Action Path Selection in Account Manager
Account Manager Updates
Account Manager now includes improvements to note creation and Account Flag consistency.
Account Manager can now be used to add user type account notes.
Image Displays Add Note Selection in Account Manager
All Account Manager "Account Flag Add" actions will convert to upper case with underscores in place of spaces. This ensures the behavior will match that of Account Flags added manually.
Image Displays Account Flag Add Upper Casing
Joined Accounts
A note is now added to both joined accounts at the time either account is joined to another or removed from another.
Direct Client Charges
Direct Receiver payments were previously being included with "Client Charges" and "Client Charges Returned" in the same way that Owner Receiver payments were.
That will no longer be the case.
This change is intended to reduce adjustments needed to prevent the inclusion of Direct Receiver payments to client charges.
Please Note:
Direct Receiver payments will continue to be included in the transaction portion of the an invoice, but will no longer be charged or returned with identified remittance or owing values.
Commercial ACH Payments
Commercial ACH payments sent through Nuvei now auto-fill with company name into the required first and last name fields when a business payment is missing one or both personal name values.
This helps ensure those payments continue processing so settlement results can be returned to ACE as expected.
ACE2ACE Forwarding
ACE2ACE Forwarding is a feature now available so customers are able to forward accounts between ACE applications.
Please see additional details in this article: ACE2ACE Forwarding.
Image Displays Example ACE2ACE Forwarding Configuration
Probate Agency Forward Type
ACE now includes a Probate Agency Forwarding Vendor Type, allowing forwarding configuration to distinguish probate-specific vendors.
Image Displays Probate Agency Selection Options for Forward Vendor Type
Inactive Clients
Inactive clients are no longer displayed in client selectors. They remain visible on the client profile page and can be included or excluded from view using filters.
Security Credentials
The username field in Security Credentials records can now take an email address as a username.
Image Displays Security Key Credentials
Jobs & Scheduling
Users can now schedule a monthly job task on the 29th, 30th and 31st of the month. If the date is unavailable for a month selected, the user will see an error and can adjust the schedule accordingly.
Image Displays Job Scheduling Options
Responsible Party Itemization
Updates to Responsible Party Itemization data in one account will now be updated to itemization data for each account in the Responsible Party Bundle.
Legal Case Fields
There are new Legal Case fields available for entry in the "Additional Legal Fields" section.
Image Displays Additional Legal Fields
API Delete Endpoint
A new API DELETE endpoint at account/{debtID}/note/{noteID} is now available.
Image Displays Delete Note API
API FlowAction Endpoints
New API endpoints are also available for managing and executing flow actions.
Image Displays The FlowAction API
VA 2.0 Custom Text
VA 2.0 Profiles include default custom text. The JSON Custom Text file supports many optional fields that can be added to customize profile text.
One optional field, "contact_options_text_notice," does not appear in the file unless the default text has been customized. This field is associated with the text shown on the VA 2.0 Contact Options page under Phone number when the number may be used for SMS or MMS.
The default "contact_options_text_notice" text has been updated with the following changes:
Removed: “and weekly reminders”
Added: “Message Frequency Varies”
Added: a reference to the Privacy Policy below
These updates apply only to default-generated custom text. If you have customized the Custom Text file and modified "contact_options_text_notice," your changes will not be overwritten.
See Custom Text in VA 2.0 article for more information relate4d to customizing text that is visible in the VA 2.0.
Commission Rate Logic Effective Date
There is a new option available in Commission Rate Logic to filter applicable commission by Effective Date.
A payment transaction date prior to the effective date will not be eligible for that configured commission rate. The next eligible rate in the configured Commission Rate Logics will be applied. If multiple Commission Rate Logics are using effective dates, the rate with the latest effective date should be evaluated first.
See this article for additional details: Create and Configure Client Commission Rates.
Image Displays Commission Rate Logic Effective Date Field
Image Displays Commission Rate and Commission Rate Logic Sections
Payment Plan Commission Rate
There is now an option, configurable on the Client Profile, to use payment plan commission rates. When set to true, the eligible Commission Rate Logic associated with the account at the time the plan is created will become the commission rate for the payment plan and payments on the account as long as the same payment payment plan is active.
See this article for more information: Payment Plan Commission Rates.
Image Displays Use payment plan commission rates in Client Profile Preferences Section
Image Displays Payment Plan Client Commission Rate Notification During Payment Plan Setup
Image Displays Payment Plan Commission Rate Notification During Payment Processing
Account Level Settlement Restrictions
Settlement restrictions can now be configured at the Account level.
If an account has populated settlement details, those will be used regardless of any settlement restrictions populated in the Client Profile or VA Profile.
For Bundled Accounts associated with a Payment Plan, the most restrictive account settlement details populated between accounts will be used.
If any settlement fields, stored at the account level, are null, zero, or empty, the most restrictive settlement details stored stored in the Client Profile or the VA Profile will be used, per prior behavior.
Image Displays Account Level Settlement Restriction Fields
Please Note:
It continues to be best practice to manage settlement options broadly, where appropriate, to ensure consistent behavior and validation of results.
Fixed These:
When the "Newest Account" primary account selection option is chosen in bundling settings, and an account was added and bundled immediately but had a different address/e-mail address/phone number, the new demographics were not saving as expected. They are now.
Some account search fields were hidden when there were no archived accounts. That is no longer the case.
The assigned_balance field in the debt table was not including court_cost_assigned in its calculation at the time of debt save. This is fixed and as of any time a debt is now saved, it will now add court_cost_assigned to its assigned_balance.
There was a scenario when opting a phone number out for text messaging was resulting in the incorrect status for the phone number. This has been fixed. Only the data associated to the phone number being opted out will now be saved at the time the phone number is opted out for text messages.
The new invoiceBucketTotals fields available for invoice templates were not working in sub-invoice loops. Now they are.
An issue with Repay Credit Card No Fee to Biller configuration resulted in erroneous service fees being applied to all scheduled payments. This has been fixed.
A scenario was discovered where offset transactions created from previously invoiced payments, including returned payments, could remain linked to the original invoice period instead of the period when the offset occurred. Those will now be included in the correct invoice period.
A scenario was discovered where fees were not recalculating as expected for the Repay No Fee To Biller payment destination when a settlement amount is changed. Now, if fees don't recalculate as expected, Repay will reject the payment with a fee mismatch error.
Authentication was still working after the removal of an API key. This has been fixed and an attempt to use a removed API call will now result in a 403 forbidden error.
Fixed an issue where system status requests could cause performance problems under certain conditions. This update improves reliability and ensures system status responses remain stable and efficient.
Fixed an issue where users with the Override Settlement permission were unable to create payment plans outside of configured settlement restrictions. Users with this permission can now successfully apply settlements below the minimum threshold, while users without the permission remain restricted.
An application exception was being thrown when bundling a new account using "New" from the account page. This has been fixed.
Searching for accounts by phone number was slow. Performance has been improved.
TCN phone log results were loading very slowly. Performance has been improved.
Account notes were not being created when the Account Manager was used to move accounts from one worklist to another. They are now.
When a payment plan was being configured or modified in such a way as to result in an excessive number of payments, an Out of Memory Exception was occurring. Now a warning will be displayed and the excessive number of payments will not be displayed. The limit is 480 payments.
PayNSeconds ACH transactions were failing when a state fee was applied. That has been fixed.