Skip to main content
Version: 2.3.0

Release notes

Version 2.3.1

About Release
  • Release date: August 14, 2026
  • Compatible platform version: Work.AI 10.3+

The Isaac v2.3.1 release expands transaction coverage with new internal transfer types, enhances narratives, and eliminates unused processing flows.

  • Isaac now supports the internal_transfer_debit and internal_transfer_credit transaction types, allowing for more comprehensive handling of internal transfer activity.

  • To make Isaac's narrative more accurate and easier to review, the following changes have been introduced:

    • Final narratives use the counterparty name deduced from the Organization Classification Skill parameter to ensure consistency.

    • Significant counterparties are highlighted in narratives, making it easier to identify those counterparties that represent a substantial portion of alerted funds.

    • Industry information is shown alongside the counterparty name in narratives, giving reviewers more context about the organizations involved in the alerted activity.

    • The alerted transaction status is updated from the matching all-transactions list after pre-built rules are applied. This improves transaction analysis and ensures alerted transaction details reflect the latest rule-based processing results.

  • Business Processes that created mock data have been removed to reduce unnecessary processing paths.

Version 2.3.0

About Release
  • Release date: July 7, 2026
  • Compatible platform version: Work.AI 10.3+

The Isaac v2.3.0 release enhances investigation efficiency and the quality and clarity of outputs. It introduces new capabilities to better manage counterparty data, refine narratives, and facilitate processing of large data volumes. With this release, we also announce the upgrade to Java 21 to deliver improved security and performance.

New features

  • Isaac can now automatically switch to CSV output when transaction counts exceed Excel file limits. You can set the maximum transaction threshold for this switch in the Output step of the configuration interface. The feature enables reliable handling of high-volume outputs without manual intervention or data loss.

  • You can explicitly include trusted counterparties or exclude selected ones from processing, which helps reduce unnecessary alerts and focus investigations on relevant entities. The feature uses a rule-based API that extracts counterparty names from transaction descriptions and evaluates them against configured whitelists and exclusion lists to determine a disposition status:

    • Whitelisted: the extracted name matched an alias in the whitelist.

    • Excluded: the extracted name matched a term in the exclusion list.

    • Requires External Research: there was no match found in either list.

  • Isaac now offers counterparty classification and risk assessment, enabling enrichment of counterparty data with relevant risk insights. The new capability improves investigation quality, supports consistent decision-making, and reduces manual analysis effort.

  • The configuration interface now includes settings to fine-tune narrative generation, allowing you to create clear, consistent investigation summaries at both entity and alert levels. In the Output step, you have options to generate entity- or alert-level narratives and to include expected and actual transactions in alert-level narratives. The enhancement lets you tailor report detail, improve transparency, and support efficient reviews.

  • You can configure counterparties to be displayed in a tabular format in Word transaction reports by enabling the Format the counterparty transactions in the Word transaction report as a table? setting in the Output step. This feature improves report readability and structure, making result analysis easier.

Improvements

  • Isaac's Word transaction report has been updated to include additional elements, which makes generated outputs more complete and easier to understand.

  • To improve Isaac's performance and reliability, enhancements were made to the processing of large transaction volumes.

  • We have upgraded Isaac to Java 21 to align with modern technology standards. This update also enhances security and improves concurrent workload handling for more efficient processing.