5
min read

More control, less noise: Customise your sanctions matching

Published on
2025-08-11 9:29
Updated on
2025-09-16 10:58
Try Strise
Author

With this latest update, team managers have control over how Strise matches sanctions alerts, based on your company’s risk policy, not just default thresholds.

Tailor sanctions matching to your risk appetite

Instead of casting a wide net and filtering later, you can now define:

  • How strict or broad you want your sanctions matching to be
  • What match percentages Strise uses when flagging entities
  • How alerts are triggered across your team

This means you’re no longer bound to one-size-fits-all risk thresholds. You’re in control of what gets flagged.

How it works

Head to sanctions settings and you can:

  • Adjust match percentage thresholds (e.g. name similarity)
  • Test and experiment with data results in real time
  • Apply chosen thresholds across your entire team

Once you set the match confidence level you’re happy with, the system will use that logic across your workflows, keeping things consistent, auditable, and aligned with your internal policy.

Why it matters

This update empowers compliance teams to:

  • Reduce false positives without missing real threats
  • Make sanctions screening more aligned with your policy
  • Fine-tune controls as your risk appetite evolves

Data and workflows working together—that’s the Strise effect.

This is some text inside of a div block.

Who are the top vendors in 2025?

Leading providers include Sayari, Kyckr, Refinitiv, Strise, Lucinity, Napier, Salv, and Sumsub.
This is some text inside of a div block.
This is some text inside of a div block.

What is the difference between KYC and KYB?

KYC verifies individuals, while KYB verifies companies, their ownership, and legal status.
This is some text inside of a div block.
This is some text inside of a div block.

What is perpetual KYC/KYB?

It replaces periodic reviews with event-driven monitoring that updates risk profiles whenever new data emerges.
This is some text inside of a div block.
This is some text inside of a div block.

What is a risk-based approach?

It tailors checks to customer risk, applying lighter verification for low-risk and deeper reviews for high-risk.
This is some text inside of a div block.
This is some text inside of a div block.

What are the biggest challenges?

Poor data quality, fragmented integrations, inconsistent standards, and friction between business and compliance teams.
This is some text inside of a div block.

Goodbye, backlogs
Hello, AML automation

We're entering a new era where AML teams eliminate compliance backlogs and fight financial crime with unmatched efficiency. No longer just a cost center, financial crime units become a vital driver of business success. AI is powering this transformation, and it's happening now!

Try live demo now

With this latest update, team managers have control over how Strise matches sanctions alerts, based on your company’s risk policy, not just default thresholds.

Tailor sanctions matching to your risk appetite

Instead of casting a wide net and filtering later, you can now define:

This means you’re no longer bound to one-size-fits-all risk thresholds. You’re in control of what gets flagged.

How it works

Head to sanctions settings and you can:

Once you set the match confidence level you’re happy with, the system will use that logic across your workflows, keeping things consistent, auditable, and aligned with your internal policy.

Why it matters

This update empowers compliance teams to:

Data and workflows working together—that’s the Strise effect.