Release Notes 10/18/2026

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

Release Notes

Rainmaker Intake

Rainmaker Intake now features updated Review Queue, Upload Documents, and Profiles screens, making it easier to manage document imports and account creation.

The following improvements are available:

• Expanded document support: Process PDF, TIFF, Word, Excel, and mixed ZIP files.

• Improved Review Queue: Edit and save multiple items at once, with options to approve, requeue, reject, or delete selected items.

• Enhanced profile setup: Analyze sample documents, configure reusable field mappings, and clarify missing or conflicting information before creating accounts.

• Background processing: Run Rainmaker Intake jobs in the background, continue working in ACE, monitor job progress, and receive alerts when processing is complete.

• Improved data validation: Calculate assigned balances from mapped amounts and identify missing information or potential duplicate accounts before approval.

To access these features, go to Accounts → Rainmaker Intake.

Performance Enhancements

• Improved Rainmaker Insights Chat Performance

  The Rainmaker Insights (RI) Chat experience has been improved to provide faster, more responsive interactions when creating or updating reports. Enhancements to how RI Chat locates existing reports, tables, and fields help reduce delays, particularly in environments with large numbers of saved reports.

• Large-Bundle Payment Workflow Performance

  Large-bundle payment workflows now complete more efficiently, reducing waits during account actions.

Enable or Disable Action Path Steps

Administrators can now mark individual Flow Actions, Logic Conditions, and nested Action Paths as Inactive to temporarily skip them during workflow execution.

Inactive steps remain visible and retain their settings, allowing administrators to reactivate them without rebuilding or rearranging the Action Path.

Send User Alerts to Multiple Users

The Create User Alert action now supports multiple recipients within a single Action Path. Each recipient receives an individual alert with the same message, timing, and associated account information.

To configure multiple recipients, set User Method to Specific User and enter the recipients in the Users field, separated by commas.

For more information, see Creating User Alerts with Action Paths.

Rainmaker Preferences

Administrators can now select and test GPT-6.0 Luna for Rainmaker AI interactions. The current default model is GPT-4.1 Mini.

InterProse will automatically transition all customers to GPT-6.0 Luna with the November 15, 2026 release. Customers are strongly encouraged to switch to GPT-6.0 Luna before this date and test their existing custom Rainmaker prompts to ensure expected responses and workflow behavior.

The selected model applies to consumer-facing chat, text, email, and Test Rainmaker responses.

To change the model, go to Setup → Rainmaker → Model, select GPT-6.0 Luna, and click Apply.

For more information, see Rainmaker Preferences.

For step-by-step instructions, see Rainmaker Preferences Test Rainmaker Tool.

Please Note:

Before the November 15, 2026 automatic transition, customers are strongly encouraged to review their existing custom Rainmaker prompts and test them with GPT-6.0 Luna to ensure expected responses and workflow behavior.

• Review and back up custom prompts: Download and save a copy of your current Rainmaker prompt file before making changes. AI responses may vary between models, so prompts may require adjustments.

• Select GPT-6.0 Luna: Go to Setup → Rainmaker → Model, select GPT-6.0 Luna, and click Apply.

• Test using Test Rainmaker: Follow the testing instructions to validate chat, text, and email responses. Pay particular attention to prompts that initiate Action Paths, generate account summaries, or update account fields.

• Always use test accounts: Load a test account in ACE before testing, as configured workflows may execute during testing.

RI Chat Reasoning Effort Options

RI Chat now offers Low, Medium, and High reasoning effort settings, allowing users to balance response speed and AI reasoning when creating or modifying RI Visuals.

Lower settings prioritize faster responses, while higher settings allow more detailed reasoning for complex requests.

Medium is the default setting, and your browser remembers your selection for future use.

See Creating an RI Visual for more information.

Rainmaker Insights Client Selection

Rainmaker Insights now simplifies client selection for large client lists. Choosing Select all or Deselect all for a primary client automatically selects or deselects the primary client and all associated sub-clients.

Rainmaker Insights Dashboard

Rainmaker Insights dashboard panels now support saved sort preferences. Administrators can set a default sort column and order for each panel when editing a dashboard.

Users can also customize their sorting preferences:

1. Open a dashboard and select the column to sort.

2. Adjust the sort order (ascending or descending).

3. Click the Save (disk) icon to save the selection.

Saved user preferences override the administrator's default settings and remain in place when returning to the dashboard.

The Recent Files to Download panel now sorts by Create Date (descending) by default, displaying the newest files first.

RI Visual Downloads

In Reports → RI Visuals, the CSV button has been renamed to Download. The button now downloads reports in their configured default format, including PDF, CSV, TSV, and fixed-width text, instead of always using CSV.

ITMS and TrueDialog Phone Number Pools

The ITMS and TrueDialog text messaging services now support multiple outbound phone numbers (Origination Numbers*), allowing ACE to rotate numbers until a consumer responds. Once a consumer replies, ACE continues using the same number to maintain a consistent conversation.

Administrators can configure how ACE handles messages when all numbers in the pool have been used.

To discuss obtaining additional outbound phone numbers, schedule a meeting with InterProse Sales.

For setup instructions and additional details, see Configuring ITMS and TrueDialog Phone Number Pools.

New Phone Fields in Templates

ACE account templates now support up to 10 primary demographic phone numbers using individual field variables, allowing phone numbers to be included in emails, text messages, AI prompt files, and other supported exports.

• Existing field variable: ${primaryDemographicPhone.phoneNumber} continues to return the primary demographic's highest-priority phone number.

• New field variables: Use ${primaryDemographicPhone1} through ${primaryDemographicPhone10} to access phone numbers individually in priority order.

• Missing phone numbers: If a phone number is unavailable for the specified priority, the field returns a blank value.

Examples:

• ${primaryDemographicPhone1} – First-priority phone number

• ${primaryDemographicPhone2} – Second-priority phone number

• ${primaryDemographicPhone3} – Third-priority phone number

VA-Branded Email Opt-In and Opt-Out Links

Email opt-in and opt-out links now use the configured Virtual Agent 2.0 custom hostname when available. This keeps consumer-facing links consistent with other branded Virtual Agent links.

Existing links remain unchanged and continue to use the address originally generated.

Create Personal Worklists from User Profiles

Administrators can now create and configure a Personal Worklist while creating a user. The new user is automatically assigned as the Worklist's Primary Agent and can also be automatically mapped to the Worklist.

Personal Worklist settings can also be viewed from an existing User Profile, and when cloning a user, administrators can choose to copy the existing Personal Worklist settings, use default settings, or create the user without a Personal Worklist.

For more information, see Adding Users.

Separate Letter Permissions

Letter permissions are now separated so users can view letters from an account without receiving access to Workflow → Scheduled Letters.

For more information, see Restricting Letter Access.

Client Access 2FA Data for RI Reporting

Client Access 2FA information is now available for SQL reporting in Rainmaker Insights (RI) Visuals. Reports can include 2FA text message history, email history, and trusted device information using the newly available 2FA tables.

To use this data, go to Reports → RI Visuals, open or create a Visual, and select Refine → SQL to build or modify a SQL query.

For more information, see Editing an RI Visual and Configuring Client Access Additional Authentication.

Phone Log ETL

Phone Log ETL profiles can now map and import Outbound Caller ID. This value is stored separately from the dialed Phone Number and Provider Call ID, allowing all three values to be retained on the imported phone log.

ETL Skip Count

Completed ETL imports now display a Skip Count in the Delta Log, allowing users to see how many source records were skipped during processing.

Itemization Transaction Misc Fields

Itemization Transactions now include five optional Misc fields with customizable labels. These fields are available when managing Itemization Transactions, importing data through ETL, and creating accounts through Client Access.

To customize the field labels, go to Setup → Accounts → Labels → Itemization Transaction Labels.

RePay ACH Transaction Batches

RePay ACH transactions with the same settlement effective date are now grouped into a single ACE transaction batch, making it easier to reconcile ACE batches with consolidated bank deposits.

If an effective date is not available, ACE continues to group transactions using the RePay batch ID.

Scheduled Deploy Maintenance Windows

Administrators can now configure maintenance windows for scheduled ACE deployments under Setup → System → Maintenance Settings.

Select the deployment day and set the maintenance window start and end times.

New API Endpoints

• Active Forwarding Record: A new API endpoint retrieves the active forwarding record for an account using its debtID. The response includes the complete forwarding record, including the forwardID and commissionRateID.

• Letter Retrieval and Deletion: Two new API endpoints are available:

  • GET /api/letter/{letterID}: Retrieves scheduled, sent, or standalone letters. Requires the LETTER_VIEW permission.

  • DELETE /api/letter/{letterID}: Deletes eligible letters. Requires SCHEDULED_LETTERS_DELETE for scheduled letters or LETTER_DELETE for historical letters.

Both endpoints enforce customer and account access permissions. API administrators are also permitted access.

To view endpoint details, go to Help → API Documentation in ACE.

Fixed These:

Workflow & Automation

• Action Code Letter Downloads: Printing letters through an Action Code that runs an Action Path could create a true.htm file instead of downloading the configured PDF letters. This is now fixed. Each configured letter is downloaded with the correct filename while the account page remains open.

Rainmaker Insights & Reporting

• Rainmaker Insights Worklist Summary Links: Links were missing from the Rainmaker Insights Worklist Summary, preventing users from opening worklist settings, account lists, or the next account to work. This is now fixed, and empty worklists no longer cause an error.

• Rainmaker Insights Currency Formatting: SQL report columns using AS currency or AS amount could lose their currency formatting when converted to Rainmaker Insights, causing amounts to display incorrectly. This is now fixed. Converted reports retain the correct currency formatting.

• RI Custom Form Field Recognition: Rainmaker Insights did not reliably recognize custom form fields when requests used configured form and field labels, requiring users to provide technical field mappings. This is now fixed.

• RI Active Account Count Timeout: Rainmaker Insights could time out when generating a total active account count because it queried individual account records instead of available summary data. This is now fixed.

• Scheduled RI Export Failures: Scheduled Rainmaker Insights exports could fail when large reports exceeded the size limit used for displaying visuals in ACE. This is now fixed.

• RI Visual Role Selector: The Copy columns to role selector in Rainmaker Insights Visuals could display only the first set of available roles, preventing users from browsing additional roles in large lists. This is now fixed.

• RI Right-Party Contact Visual Criteria: Rainmaker Insights could incorrectly change the criteria used for an existing right-party contact (RPC) visual when updating its date range or averaging period, causing valid results to be excluded. This is now fixed.

• RI Payment Channel and Vendor Mapping: Rainmaker Insights could incorrectly assume how payment channels and vendors were mapped when creating or updating reports, resulting in zero or inaccurate totals. This is now fixed. RI asks for clarification when payment-channel definitions are not available instead of assuming the mapping, while preserving the requested dates and commission criteria.

• RI Chat Encrypted Field Recognition: RI Chat could incorrectly report that an SSN or National ID field remained encrypted even when decryption was successful, causing it to continue revising an already working Visual. This issue is now fixed.

• Agent Performance CSV and Excel Exports: CSV and Excel exports of the Agent Performance report could include incorrect or hidden columns. This is now fixed. Exported columns now match the columns and order displayed in the report.

• Agent Performance PDF Export Column Alignment: Agent Performance PDF exports could display values under the wrong grouped column headers, causing Scheduled, Future Scheduled, Phone Calls, and Communications data to appear misaligned. This issue is now fixed.

Virtual Agent & Messaging

• VA 2.0 Custom Color Schemes: Custom color scheme files were not applied correctly in Virtual Agent 2.0 for Canadian-hosted environments. This is now fixed, allowing custom color scheme files to display the configured styling as expected.

• VA 2.0 Contact Us Keyword Display: The Virtual Agent 2.0 Contact Us page could display "using keyword undefined" when a text vendor did not have a keyword configured. This is now fixed. The keyword is displayed only when configured, and Keyword Identifier is now available for TrueDialog text vendors.

• VA 2.0 Payment Plan IP Address Capture: IP addresses were not being captured on VA 2.0 post-dated payment plans, even when the IP address was available from the associated Virtual Agent session. This issue is now fixed.

• Email Recipient and Account Information: Emails prepared while working across multiple account tabs could use a recipient from one account with information from another unrelated account. This issue is now fixed.

Accounts & Bundling

• Minimum Settlement Percentage Change Notes: Saving an account with a blank Min Settlement Percentage could create an unintended change note showing the value changed from empty to 0%. This is now fixed. Blank percentage values remain blank, and account change notes now clearly distinguish between Not set and 0%.

• Bundle Primary Agent Assignment: When a new Primary Account without a Primary Agent was added to a bundle, the existing Primary Agent assignment could be removed. This is now fixed, and the existing Primary Agent assignment is preserved.

• Large Account Bundling Performance: Bundling large numbers of accounts by Account fields could take an extended amount of time to complete. This is now fixed. Account field bundling has been updated to process accounts more efficiently.

  Note: Account field matching is now case-sensitive.

• Duplicate Notes During Account Bundling: Bundling accounts with matching phone numbers or addresses could duplicate existing note text, causing notes to grow unnecessarily after repeated merges. This issue is now fixed.

• Forward Distribution Dropdowns: The Distribution dropdowns in the Forward: Forward Accounts and Forward: Model Account Distribution job tasks displayed only the first 25 configured distributions. This is now fixed. Both dropdowns display the full list of available distributions.

Payments & Settlements

• Speed Posting Multiple Payment Plan Accounts: An error could cause Speed Posting to stall when processing multiple accounts associated with payment plans. This issue is now fixed.

• Nuvei Initial Payment Processing: The first payment in a Nuvei payment plan could be incorrectly identified as a repeat payment, causing some payment plans to fail. This is now fixed. The first payment is correctly processed as the initial payment for credit card, Apple Pay, Google Pay, and ACH payment plans.

• Payment Commission Calculation: Commission could display as blank when entering a payment amount even when a commission rate applied. This is now fixed. Commission automatically calculates using the applicable rules for the payment receiver.

• REPAY Credit Card Settlement Warnings: REPAY credit card settlement warnings could incorrectly identify declined transactions as unknown transactions. This is now fixed. Declined card transactions are excluded from unknown transaction warnings, while successful unmatched transactions continue to be reported. When provided by REPAY, the issuer response code is also retained for failed payments.

• Single-Account Bundle Settlement Recalculation: When a user selects one account from a bundle for a payment plan, settlement and payment amounts now recalculate immediately after the settlement percentage changes.

• Attorney Fee Commission on Judgment Payments: Attorney Fee amounts in direct payments and judgment spreads now generate the configured attorney commission on the original account without duplicating it on the judgment account.

• Speed Posting Transaction Batch Destination: Speed Posting transactions could use a payment destination that did not match the selected Transaction Batch. This issue is now fixed.

• Settlement Payment Plan Blank Percentage Error: Setting up a settlement payment plan could result in an application error when the settlement percentage was blank. This is now fixed.

Letters & Documents

• Restricted Letter Cancellation Status: Previously, cancelling a letter from Workflow → Restricted Letters did not update its Sent Status to CANCELLED. This is now fixed. Cancelled letters are removed from the Restricted Letters list, and their Sent Status is updated from RESTRICTED to CANCELLED.

Note: The letter remains available from Account Page → Letter Actions → View Letters and retains its Restricted Reason and Restricted indicator.

ETL & Data Imports

• ETL Field Layout Export with Lookup Forms: The Help → Layout → ETL Fields export could fail when lookup forms were configured. This is now fixed. The ETL field-layout workbook downloads successfully and includes the lookup form Form ID mapping along with configured lookup-form fields.

• Phone Number ETL Blacklist Validation: Phone Number ETL imports could fail when updating an existing phone that matched a Phone Blacklist rule. This is now fixed. Existing phone records can be updated when the phone number itself is unchanged. New or changed blacklisted phone numbers continue to be rejected.

Client Accounting & Invoicing

• Invoice Access and Regeneration: Opening a remitted or unremitted invoice could result in an application error, preventing users from accessing the invoice to regenerate or redeliver it. This is now fixed.

• Primary Client Ledger Posting: The Post to Primary Client Ledger option could incorrectly post invoice ledger entries to the sub-client instead of the primary client. This is now fixed.

System Administration & Security

• Account Viewer Warning and Session Timeout: The account viewer warning could incorrectly affect user visibility and prevent inactive sessions from timing out. This is now fixed. Dismissing the warning no longer removes the user from the list of users viewing the account, and account viewer checks no longer extend the login session.

• Release Notification Pop-Up at Login: The release notification pop-up was not appearing at login when a new ACE version was ready to deploy. This issue is now fixed.

• Password Reset Email Vendor: Password reset emails requested from the ACE login screen could be sent from noreply@interprose.com instead of the customer's configured default email vendor. This is now fixed. Password reset emails use the configured default email vendor when available and fall back to noreply@interprose.com when no default vendor is configured.