- Print
- PDF
ACE Release Notes - 12/05/2021Below are the updates and fixes we will be pushing out to all of our customers. We can’t wait to deliver further improvements to you in the months ahead!
We are expecting the downtime for deploying this update to be ten to fifteen minutes. |
Regulation FCheck out the "Take a Closer Look" section where we outline the fifth phase of new features and tools in ACE being rolled out with this release to help you manage Regulation F requirements. |
Cool New Upgrades |
Regulation F Bonus DevelopmentIn addition to the scheduled development we are including in each release, needs continue to be identified and put in place. This release, we've added the following three new features.
Client profile Boolean valueTo accommodate customers with business that may not be required to meet Reg F requirements, there is a new Boolean option in the Client Profile Preferences section where "Obey Compliance Rules" can be set to false. |
Manual New Account Itemization & Itemization Transaction EntryAgents who enter accounts are now able to enter itemization fields and itemization transactions at the same time in this new section on the New Account page.
The date will populate only if the associated Itemization Date Source field is populated in the account. The "Add" button on the right allows new itemization transaction (those between the date of itemization and the date of assignment) to be added as well. |
Itemization Mapping InterfaceWhen itemization transactions and account transactions are entered into ACE, itemization fields (used for the validation notice) are updated according to defaults in place based on the bucket, operator (owing/received) and numeric operator (+/-) associated with the transaction entered.
A new compliance feature has been added to allow customers the flexibility to modify the way those values will be reflected in the itemization fields.
Please note: many customers will not need to use this feature. If you are unsure, please reach out to support.
To modify itemization mapping, go to Setup -> Compliance -> Itemization Mapping.
Per the defaults, the screenshot below shows the following.
All buckets are available for this mapping, even though many customers do not need to use all available buckets. |
In addition to the ability to adjust itemization mapping, a Boolean option has been added which can be used to exclude transactions associated with accounts that have been cancelled and reactivated from being included with itemization. |
When entering manual itemization transactions, a helper function has been added so before saving, it will be clear which itemization field the itemization transaction will be evaluated in.
Please note: If $25.00 is entered as shown in the example and -$25.00 is entered after that, per the defaults, they will both be evaluated as "FEES" and would show a net value of zero excluding the existence of other data. |
Please note: any changes you make to the Itemization Mapping page will be applied globally to accounts in your application. |
Consent to Contact Notate Account FieldCustomers have expressed an interest in being able to display notate account fields in the columns on the right or left as they were before the "Consent to Contact" field was introduced to the account page notate account section.
A new permission, called ACCOUNT_DEBT_CONSENT_CONTACT_
Two permission roles, assigned by default to collector agents, where you may need to remove that permission are (1.) Agents and (2) Menu - Accounts. You may have others on your application.
To ensure an administrative or managing user has the ability to use the "Consent to Contact" field, be sure to add it back to a role they have that the agent users do not.
Please note: There are additional roles that start with "ACCOUNT_DEBT_CONSENT_CONTACT. |
Last Letter Update &Last Letter Return DatesA new field is now visible to show the last letter likely returned based on returned mail updates to the address. The last date the letter was updated has also been added. |
Take a Closer Look |
Regulation F Development - Phase 5The CFPB's 12 CFR Part 1006 (Regulation F) went into effect November 30, 2021. With that in mind, InterProse is continuing to develop features and tools in ACE to help customers better manage Regulation F requirements. Per documentation shared with customers September 25th and October 1st via email, the fifth phase of this development work will be released on December 5th as outlined in the details below. |
In the last set of release notes, these three items were erroneously identified as deferred to phase 4. They were actually deferred as shown here. Need: Firewall restriction from campaign files -Deferred to Phase 7* Need: Model form template (email) -Deferred to Phase 7* Need: Email link to opt out - Deferred to Phase 6*
The following item originally scheduled for Phase 5 was deferred. Need: Improve postdated secure payment workflow -Deferred to Phase 7*
In its place, three additional Regulation F needs were identified and developed for this release as listed here.
Please see Regulation F Bonus Development in the "Cool New Upgrades" section near the beginning of the release notes for the detail related to each of these three new features. |
*Please Note: Due to the evolving understanding of priorities surrounding Regulation F, you can expect development tasks to continue to be rearranged in the schedule.
Whenever possible, we will clearly define the various changes to the originally scheduled development work here in the release notes.
Thank you for your patience! |
Making Things Right
- Extra itemization notes are no longer showing in account notes - Fixed a problem with selecting multiple zip codes via logic block - Updated API for Intelligent Contacts click to call through ACE - Fixed duplicate vendor import call records - Fixed session timeout issue - Fixed problem with pdf attachments failing to attach on subsequent email attempts |