Release notes
Version 2.0
- Release date: November 26, 2025
- Compatible platform version: Work.AI 10.2.9+
Isaac v2.0 introduces new features and enhancements to help you reduce operational costs, accelerate decision-making, and strengthen risk defenses. The new features include ingesting data via API, three specialized Business Processes instead of a single all-in-one flow, a no-code rule engine to help guide Isaac's automated decisions, and an optional fraud investigation path. In addition, significant improvements have been made to optimize Isaac’s data schema and enhance reporting.
New features
To streamline alert review and enhance your flexibility in data handling, we have split the single Isaac Transaction Monitoring Investigator Business Process (BP) into several separate flows, each serving its own purpose:
The Transaction Monitoring Core BP is recommended for batch alert processing. The BP is used in combination with the Transaction Monitoring File Ingestion and Transaction Monitoring Alert Investigation BPs. It completes operations, such as fetching and consolidating deferral and alert data, notifying about potential deferrals, and generating a final alert summary report.
The Transaction Monitoring Alert Investigation BP is recommended for alert-by-alert real-time processing. The BP fetches and evaluates alerts, enriches them with manual review data (if any) and additional transaction details, and passes them through the transaction monitoring or fraud detection flows. It can be used on its own or in combination with the Transaction Monitoring Core BP.
The Transaction Monitoring File Ingestion BP is mainly intended for historical data evaluation. It lets you manually ingest lists of deferrals and alerts uploaded to S3 buckets and triggers the Transaction Monitoring Core BP.
You now have the option to ingest alert and deferral data directly from your internal transaction monitoring system using an API. This capability supports data schemas and contracts for seamless integration with alert systems, reducing manual effort and operational overhead required to get Isaac up and running.
For historical data evaluation, manual input upload remains available as a separate process through the dedicated Transaction Monitoring File Ingestion BP. During configuration, you can choose your preferred method for submitting data: API for real-time integration or File ingestion for manual uploads, giving you flexibility to align with your operational needs.
To help you automate transaction evaluation against specific criteria (for instance, risk level), we have introduced a rule engine. The engine is basically a sequence of no-code Decision rules steps you can configure to suit your business purposes. Isaac examines each transaction against preconfigured conditions and assigns an evaluation flag (for instance, labels a transaction as low-risk).
Isaac now offers an optional fraud investigation path as a separate flow within the Transaction Monitoring Alert Investigation BP. This new flow enables you to assess transactions for potential fraud risks. By integrating fraud evaluation into alert investigations, you can further strengthen compliance, reduce financial exposure, and enhance overall risk management.
In addition to the final summary and preliminary deferral report, Isaac now offers two more reporting options to ensure consistent information delivery with minimal manual effort. Both report types are supplied with default templates you can customize to your needs.
The transaction report allows you to export transaction data in a structured, easy-to-use format to an Excel or Word document. With the report, you can quickly review, filter, and share transaction details for audits, compliance checks, and operational insights without relying on manual data compilation.
The fraud summary report consolidates all critical fraud-related information coming from the fraud investigation path into a Word document. The report provides a comprehensive case overview: case summary, scope of review, involved parties, and detailed narratives on fraud transactions.
Improvements
To improve data completeness and Isaac's decision-making capabilities, a new process structure was added to enrich transactions with additional details (for instance, data from images or external systems). As a result, you can get a more comprehensive overview of each transaction without investing extra manual effort.
To provide richer data for downstream investigations and application of rules specifically related to Anti-Money Laundering and fraud detection, Isaac's data schema was updated to cover extended transaction details.
Now, transaction analysis takes into account customer and industry profiles, allowing you to improve the fraud detection accuracy and provide deeper insights into operational data. The enhancement enables you to compare each transaction against the customer’s historical behavior and benchmark it against patterns typical for similar customers in the same industry. By identifying deviations from expected norms, your teams can detect anomalies faster and make more informed risk decisions.