What’s new in AML TM?

🚀 Summary 

The March release marks the official completion of our Legal Entity support, providing a comprehensive framework for managing complex corporate structures and customer types. Alongside this milestone, we are excited to announce the General Availability (GA) of our SAR Agent, a powerful tool designed to automate and streamline the Suspicious Activity Reporting process. These updates collectively enhance operational efficiency, ensuring that our users have the most robust tools for both data organization and regulatory compliance.

✅ Legal Entities Support

Our latest update streamlines how you manage risk for corporate and individual customers. By applying tailored risk strategies and entity-specific thresholds, you can now minimize noise and focus on what matters most. We’ve ensured that legal entity data is fully optimized throughout your entire workflow. Whether you are ingesting data, analyzing transactional activity, or generating SAR reports, you will experience a more robust and integrated process designed to improve accuracy and save your team valuable time.

• Eliminate Manual Silos: Legal entity data is now fully integrated into your end-to-end flow, removing the need for manual workarounds during ingestion or SAR filing.
• Smarter Alerting: By using dedicated thresholds for corporate customers, you can fine-tune your TM solution to match business behavior, cutting down on false positive alerts.
• Complete Audit Trail: Track everything from the first transaction to the final assessment in one place, ensuring your risk strategy is both consistent and defensible.

To know more about Legal Entities support please check our updated documentation here.

🤖 SAR Agent now in General Availability (GA)

Following our dedicated communication earlier this month, SAR Agent is now officially available to all users that are using Feedzai's SAR manager. This feature leverages the use of agentic capabilities to assist in the drafting and filing of Suspicious Activity Reports, significantly reducing manual effort and improving the quality of your submissions.

• Velocity, Not Just Speed, this reduces operational burden significantly by shifting human investigators from "writers" to "editors." We are drastically reducing the time-to-file.
• Narrative Consistency Fidelity, it eliminates "human variability." Every report follows the same high standard, providing the consistent "voice" that regulators crave.
• Content Accuracy,  we don't just 'read' data; we synthesize your entire investigation—from rules to analyst notes—into a cohesive narrative.
• Regulatory Fidelity, we don't just 'write' text; we calibrate every output to the specific mandates of your national FIU and institutional history.
• Human-in-the-Loop (The "Safety" Sell), we aren't replacing the expert. The Agent handles the heavy lifting of synthesis, but the final sign-off always remains with the human, ensuring total accountability.

To know more about the SAR Agent please check our updated documentation here.

📚 Documentation Updates

• Expanded Legal Entity Support on risk strategy flow: the documentation has been updated to include Legal Entity (LE) workflows. These improvements provide clearer guidance on how to monitor business organizations, ensuring your team can track and manage risks at the entity level with greater precision. More details here.
• Unified Case Management & Ad-hoc Reporting Guides: We have updated our Case Management and Ad-hoc reporting documentation to reflect recent Legal Entity (LE) enhancements. These updates ensure that users have a consistent and accurate reference point when configuring reports or managing entity-based cases across the platform. More details here.
• Reference Data API Expansion: The Reference Data API documentation now includes details for the legal_form field. This update provides technical teams with the necessary specifications to integrate more granular customer data, and downstream assessing. More details here.

Important Bug Fixes

This release includes the following fixes in Case Manager:

• Previously, when both a “type” (for example, OAuth2) and a “token” were defined in webhook authentication, the system would always default to the Bearer method, ignoring the configured type. This has now been fixed. The system correctly respects the defined authentication type, ensuring webhook configurations behave as expected.

• Previously, webhook integrations using OAuth2 authentication could fail if the authorization server returned a token that was not in JWT format. This has now been fixed. Webhooks now support both JWT and non-JWT tokens, ensuring compatibility with different authorization servers.
• Previously, users could not open alert links in new tabs using right-click or keyboard shortcuts. This has now been fixed, restoring the ability to open alerts in multiple tabs and improving investigation workflows.
• Previously, using the  filter with a null value did not return expected results, even though the same behavior worked with the “eq” filter. This has now been fixed. Searches using  null values now return consistent and accurate results.
• Previously, an error related to a missing widget was repeatedly logged, even though it did not impact system functionality. This has now been fixed. Unnecessary log entries have been removed, improving log clarity and making it easier to identify real issues.
• Previously, importing page configuration files could fail when incomplete widget information was present, preventing configurations from being applied. This has now been fixed. Configuration imports now complete successfully, ensuring smoother migrations between environments.

This release includes the following fixes in Pulse:

• A warning is now shown when users write expressions that could result in division by zero in any PQL editor. This helps prevent errors during real-time scoring and avoids disruptions caused by unsafe expressions. For example, if a user types an expression like "amount / 0", a warning will appear to alert them before saving or publishing.

• Previously, users could not create Windowless Metrics even when the relevant setting was enabled globally. Now, the option to create Windowless Metrics is available whenever the global configuration is active, making metric creation more flexible and consistent with user expectations.

• The "beta" label has been removed from the changes workflow window, reflecting that this feature is now fully released and available for general use. This update helps avoid confusion and ensures users know they are working with a finalized feature.

• Previously, when a job was stuck in the "Waiting for execution to start" state, it could not be cancelled through the interface, forcing users to request manual intervention to free up execution slots. With this fix, it is now possible to cancel these jobs directly, making job management easier and reducing the need for support. This helps prevent delays in planned executions and improves overall usability.

• Previously, during system shutdown, an error could occur if messages were still being processed while the workflow was closing. This happened because the system would mark all messages as finished before actually completing their processing, which sometimes led to a misleading error about the workflow being in a stopped state. With this fix, the system now waits for all messages to finish processing before closing the workflow, preventing confusing errors and ensuring a smoother shutdown process.

Interested in a particular feature?

For the new features that require specific actions in order to be active, please contact your Feedzai Representative or simply submit a request in support.feedzai.com and choose others as request type.

Find the Incremental Release Update summary in Feedzai UI

Now, you can also navigate to the Product Announcements tab in the Resource Center to quickly see a summary of the latest incremental product updates.