Case management: Custom dispositions
You can now define your own dispositions (the reasons an analyst records when actioning an alert or case) instead of relying on a fixed set, and control which ones are available for each action. Cases, and alerts each have their own independent statuses, actions, and dispositions. See the full guide here.
Fig: Custom dispositions under Settings > Case Management
Key updates include:
Create custom dispositions for cases, and alerts, each configured independently.
Require an analyst to pick a reason before an action can be completed, enforced when the status actually changes.
Scope reasons to specific rule types or queues, so analysts only see the reasons relevant to what they’re reviewing.
Case management: Create manual cases from transactions, alerts, and more
Manual case creation previously worked only from the Users touchpoint. You can now start a manual case from several more places, and the related users are pulled in automatically. See the full guide here.
Key updates include:
Create or add to a manual case from transactions (the transactions list, a transaction’s page, or an alert’s Transactions tab), from alerts, or with no subject attached at all.
When creating from a user, optionally include that user’s transactions or alerts automatically using a direction and date-range filter.
The responsible user is pulled in automatically when you start from transactions or alerts.
Management API: Manage accounts programmatically
You can now create, read, and disable accounts directly through the Management API, rather than only in the console.
Key updates include the ability to:
Disable an account via the API (note: it's a disable, not a hard delete).
Custom rules: Custom object variables for rules
You can now use your custom object fields as typed variables (data type defined) in rules.
You can set up your own custom objects from settings > Custom Objects
Fig 1: Example of a custom object
Once you have these objects set up, you can send them to Flagright via the API. They will be available for use as variables in Custom Scenario builder rules.
Fig 2: This is how custom objects would show up on the variable list
You can then build custom logic for rules using these custom object values
Fig 3: Using custom objects in the rule logic
Case management: SAR subject auto-filled from the case or user
When you create a FinCEN SAR from a case page or a user's page, the associated subject is now filled in automatically instead of being entered by hand. You can still add other subjects manually when a report needs subjects beyond the associated case.
Key updates include:
Subject auto-populated on SARs generated from a case or user.
Manual addition of further subjects still supported.
Fig 1: A mapped out Subject details page with user details data
Fig 2: You still manually add subject details like by clicking on the Subject details button
Screening: Whitelisting for internal list hits
The whitelisting logic that already applies to screening hits now extends to alerts created from internal lists, so you can whitelist internal-list matches the same way, with the same hit visibility you get for screening.
Key updates include:
Whitelist internal-list hits using the same user/transaction matching logic as screening whitelisting.
Screening: Address matching in screening rules
You can now screen on addresses, with fuzzy matching. This lets you create matches against any entity sharing an address, even when the names don’t match.
Fig: The address search field on the screening variable configuration in red
Screening: Richer PEP status on Dow Jones hits
Dow Jones screening hits now show the PEP/RCA status at the row level, with a clear active/inactive indicator, so you can quickly judge how relevant a PEP match is.
Key updates include:
PEP/RCA status shown per hit (Level 1/2, RCA, active/inactive), next to the relevance column.
New active/inactive indicator: a PEP/RCA marked inactive for 7 years or more is tagged Inactive; under 7 years is Active; blank defaults to Inactive.
SAR filing: Add more transactions from the STR view
When preparing an STR, you can now pull in additional transactions in bulk directly from the STR view, instead of being limited to the transactions already attached to the originating case or alert.
Key updates include:
Filter transactions by user ID and add them in bulk from within the STR.
Step 1: Click on the Select transactions button on STR view
Step 2: Add transactions after selecting relevant filters
Case management: Independent locks for KYC status and user status
You can now lock KYC status and user status separately, rather than with a single shared lock. Any existing lock carries over to both, so current behavior is preserved.
Fig: Separate lock controls for KYC status and user status.
FRAML API: Correspondent bank details for generic bank accounts
The generic bank account payment method now supports a correspondentBankDetails array, matching what was already available for SWIFT payments, so correspondent banking information can be captured and screened for more payment types. You can find the changes listed in our latest API docs.
Fig: CorrespondentBankDetails now available under GenericBankAccountDetails
Compliance: FINTRAC filing enhancements - STR templates
FINTRAC reports now support default template fields and additional field mappings, reducing manual entry when preparing a report. You can use these features to improve your STR filing process.
Fill out the field values by going through Settings > SAR filing. Once the template has been set up, these will apply for all STRs.
Fig: FINTRAC STR template