Jan 19, 2026

You can now update multiple alerts at once by uploading a CSV file, streamlining your case management workflow when handling similar alerts or completing review cycles.

To bulk update alerts, prepare a CSV file with the alert IDs and desired status changes, then upload it through the bulk update interface. You'll be able to include notes and dispositions for each alert in your file.

The upload guide can be found when you click the Bulk updates button.

You can now add persons or entities associated with a business who have no control over the entity. This allows you to track relationships beyond controlling parties like shareholders or directors. Associated persons can also be screened.

Rule R-128 now screens associated parties and business partners in addition to legal names, directors, and shareholders.

This ensures complete coverage of your business relationships for sanctions, PEP, and adverse media checks, including parties with no controlling interest.

To enable this screening, configure rule R-128 in your screening rules settings. The rule will automatically apply to all relevant parties when screening business entities.

You can now add bank address and SWIFT code under correspondent bank details for SWIFT payments.

This additional information helps you maintain complete transaction records and perform more thorough monitoring of intermediary banks involved in cross-border payments.

See the API documentation for details on how to include correspondent bank details in your SWIFT payment requests.

You can now retrieve a list of all failed webhooks to help monitor and troubleshoot your integration.

This feature allows you to identify delivery failures and take corrective action. You can also add a timestamp to specify a starting cutoff date and time, letting you focus on failures within a specific period.

See the API documentation for details on how to retrieve failed webhooks and use timestamp filters.

Webhooks sent when alerts or cases are closed now include the email of the person who took the action.

This additional information improves audit trails and helps you track which team members are handling specific cases and alerts, making it easier to monitor workflow accountability.

When data is sent to Flagright in batches via the batch API, webhooks are now sent after the rules and risk scoring processes are complete.

This ensures you receive webhook notifications only after all processing is finished, giving you accurate and final results for your batch operations.

You can now screen multiple entities at once by uploading a CSV file through the batch screening feature.

To use batch screening, download the CSV template, add names under a single "name" column header, then upload the file after selecting your entity type (person or business), screening profile, and fuzziness level. The system validates and processes your file, displaying results for each name that you can navigate through sequentially.

Access your import history in the top right corner to review past batch uploads and download historical screening data.