Configuring Screening Using Screening Flows
In this section, we'll walk you through the configuration process for Screening at Salv, which is centred around Screening Flows. Screening Flows allow for granular control over how Person or Transaction data is screened, providing the ability to customise key settings like matching types, list types, and Segment inclusions/exclusions. Follow the steps below to define and configure a Screening Flow.
1. Selecting a Screening Flow Type
When setting up a new Screening Flow, the first decision is whether you want to define a Persons or Transactions Screening Flow.
Navigate to Configuration page → Screening tab.
Under Screening Flows, select either Person Screening Flow or Transaction Screening Flow based on your need
Click +New Flow
❗️Important note before moving forward: overlapping Screening Flows can lead to duplicate alerts.
For example, if you have two Screening Flows where the screened field is company_name—one targeting All entities and the other targeting the LEGAL customers Segment—LEGAL customers will be screened in both flows. This overlap will generate duplicate alerts if a match is found.
To prevent this, we highly recommend avoiding overlap by keeping your Screening Flows granular and specific.
2. Selecting Fields for Screening
After clicking to add a new Screening Flow, the next step is to select one or more fields to be screened. These fields will be combined together and used as a single unit when performing the screening.
The fields you can select are those defined within the Schemas and made visible.
For Person data, nested fields are also available.
How Field Selection Works:
When you select fields to screen, they are treated as a unified search phrase. For example, if you choose first_name and last_name the screening system will combine these fields to match against the same entry on a screening list.
Example: If you select both
first_nameandlast_namein a person screening flow, the system will search using the combined value "John Smith" instead of screening the two fields independently.
The order of the screened fields does not affect screening results, i.e. if you selected first_name + last_name, it would yield the same results as field selection of last_name + first_name.
Important Limitations:
You need to define one cohesive set of fields per screening flow. This means you cannot select an overly broad combination of fields, as doing so will likely yield no results or create inefficiencies.
A simple combination like
first_name+last_name(i.e., "John" + "Smith") of the data you want to screen is recommended.Complex combinations of many fields, such as
first_name+last_name+shareholders[].first_name+shareholders[].last_name+company_name+middle_nameare not allowed. Such combinations would be too broad and may result in no relevant matches because the fields are being screened as a single unified phrase.
This approach ensures that the screening process is focused and effective by combining a reasonable number of relevant fields in each flow.
3. Configuring Goodlisting Keys (Transaction Screening Only)
When configuring a Transaction Screening Flow, you have the option to define Goodlisting Keys, which help reduce false positives by automatically goodlisting certain matches.
You can select up to 3 goodlist keys.
These keys must be based on fields defined in the Transaction Schema.
4. Selecting Segments for Screening
You can now define which Segments will be included in the Screening Flow.
For example, you might only want to screen LEGAL customers in a Screening Flow where company_name is being screened.
When selecting Segments to include in a Screening Flow, consider factors such as the types of Persons and Transactions involved, risk profiles, regulatory requirements, your company’s risk appetite, and other relevant factors.
Included Segments are joined using an AND condition.
This means that only entities matching all selected segments simultaneously will be screened. For example, if you select both the INCOMING Transactions segment and the INSTANT Payments segment, the system will screen only incoming instant payments—not all incoming transactions or all instant payments individually. This ensures that only transactions meeting both criteria are included in the Screening Flow.
5. Excluding Segments from Screening
You also have the option to exclude specific Segments from being screened.
Exclusion overrides inclusion, meaning any excluded segments will not be screened, even if they were previously included.
Excluded Segments are joined using an OR condition.
This means that entities matching any of the excluded Segments will be omitted from the Screening Flow. For example, if you configure the Screening Flow to include Incoming Payments but exclude both the Card Payments Segment and the Internal Payments Segment, transactions matching either Card Payments or Internal Payments will be excluded.
6. Defining Matching Types
Next, you'll need to specify how the value of the selected screened fields will be compared against the list entries.
The available matching types are:
Fuzzy: Compare values with a degree of fuzziness (matching accuracy between 90-100).
Exact: Look for an exact match.
Contains: Check if the field contains the specified value.
Prefix: Compare the prefix (the beginning) of the value.
Fuzzy contains: Applies both fuzzy matching and contains matching.
Learn more about Matching types here.
7. Selecting List Types for Screening
Next, select the list types against which the screened fields will be checked. You can screen against one or multiple list types, including:
Dow Jones Sanctions
Dow Jones PEP/RCA
Dow Jones Adverse Media
Custom Lists (if any have been created)
When selecting a Custom List, you must specify the usable field for Screening Flows — that is, the data that the screened field should be compared against.
❗️ You can screen transactions only against:
Dow Jones Sanctions
Custom lists
Use of Dow Jones PEP, Adverse Media, or Adverse Media Entities lists is not supported for transactions.
8. Selecting DJ Sanction List Groups (Sanctions Screening Only)
If you select Sanctions as a list type, you must choose which DJ Sanction List Groups will be used for screening.
Ensure that your List Groups are configured before beginning the Screening Flows setup.
9. Reviewing and Saving the Screening Flow
Once all settings have been configured, you will be prompted to review the entire Screening Flow before saving. Currently, there is no option to save the flow as a draft.
Review your settings carefully to ensure everything is correct.
If needed, you can discard the setup at this stage or save it to activate the Screening Flow.
10. Drafting and Testing Screening Flows
Before a Screening Flow goes live, you can build and refine it as a draft. Drafts can be tested in isolation against historical data and never touch live traffic. There are two ways to create a draft, depending on your starting point.
Creating a standalone draft
Use this when you're building a Screening Flow from scratch and want to test it before it ever goes live, for example, while onboarding and setting up all your flows for the first time, or when launching a new product and wanting to validate screening behaviour before switching it on.
From the list of all Screening Flows, click New draft flow.
Configure the flow as described in steps 1–8 above.
Add an optional note to help identify the draft later.
Save it as a draft.
Standalone drafts appear as their own rows in the main list of Screening Flows, highlighted with a yellow background and labelled Draft. They exist independently — since there's no live version yet — and do not screen or affect any live traffic until they're activated.
Duplicating a live flow as a draft
Use this when you already have a live Screening Flow and want to experiment with it, for example, adjusting matching thresholds, adding a list, or changing Segments, without affecting production screening while you iterate.
From the list of all Screening Flows, find the live flow you want to experiment with and open its ⋯ menu.
Select Duplicate as draft.
Adjust the settings as needed and save.
Unlike standalone drafts, a draft created this way is attached to its originating live flow rather than appearing as its own row in the main list. You'll find it on the live flow's own page, shown alongside the active version and labelled Draft.
Testing a draft
Both types of drafts can be run against historical data before going live. Open the draft and use its ⋯ menu to Run test or review Test runs. Read more about testing screening flows here:
Activating a draft
When you're happy with a draft's results:
Open the draft and select Activate from the ⋯ menu.
For a standalone draft, this makes it live for the first time.
For a draft attached to a live flow, activating it automatically promotes it and replaces the currently live version.
If you decide not to proceed with a draft, you can Discard draft instead.
10. Editing an existing Screening Flow
At any point in time you can edit an existing Screening Flow. Any changes you make will be applied during next Screening event.
