Sanctions, PEP, and adverse-media screening software for Canada

Screening checks a customer, and increasingly a payment, against sanctions lists, politically exposed persons lists and adverse media, to confirm the party is one you are permitted to deal with and to apply enhanced measures where they are required. The three list types answer different questions. Sanctions screening is a prohibition check, where a confirmed match generally means you cannot proceed; it is strict-liability territory. PEP screening is a risk-tiering check, where a match does not bar the relationship but triggers enhanced due diligence and closer monitoring. Adverse-media screening surfaces relevant negative news that sharpens the risk picture around both. For Canadian reporting entities, sanctions and PEP screening are mandatory, and adverse-media screening is increasingly expected as part of a risk-based program. Run well, the three sit in one workflow with a recorded disposition on every alert, rather than as three disconnected tools a team reconciles by hand.

No. Screening is a continuing obligation, not a one-time check completed at account opening, because both the lists and the customer change after onboarding. Sanctions lists are updated on an ongoing basis as new designations are issued, a person can newly assume a public role that makes them a PEP, and adverse media can surface about a customer at any point. A party who cleared cleanly on day one can become a match the next day. Our screening system re-screens against refreshed lists and surfaces new matches for disposition, so the screening picture reflects today's lists rather than the day the account was opened. This continuing view is part of what keeps a program effective under the Bill C-12 standard, and the cadence itself should be risk-based, with higher-risk relationships and PEPs re-screened more frequently than low-risk ones, and the whole approach documented so an examiner can see why the frequency was set as it was.

Our screening platform uses agentic entity resolution, which is designed to reduce false positives by up to 80% so alerts stay meaningful instead of overwhelming the team. Rather than loosening match thresholds, which would trade false positives for missed true matches, resolution scores identity coherence across candidate matches and collapses near-duplicate hits caused by spelling variants, transliterations and homonyms into one scored identity. The reduction comes from precision, not from screening less thoroughly. Every match that survives still carries its own plain-language rationale, and every disposition is recorded for the FINTRAC file, so cutting the noise never costs you the audit evidence an examiner expects. The causes behind screening false positives, and how entity resolution addresses each of them, are covered in more depth in our false positives guide. The practical effect is a shorter, higher-value queue a lean compliance team can actually work without growing headcount in proportion to alert volume.

Yes. Every match, the decision made on it and the reviewer who made that decision are recorded, producing an examiner-ready trail as a by-product of the work rather than something assembled afterward. That record is what shows an examiner not only that you screened, but specifically what you found and what you did about it, which is the distinction that matters under the Bill C-12 effectiveness standard. A bare confidence score cannot be defended in an examination the way a stated rationale can, because an examiner reviewing a sample of historical decisions can see exactly why each one was resolved as it was, without asking your team to reconstruct the reasoning under examination-day time pressure. Because alerts, evidence and dispositions are captured as one connected case history rather than scattered across separate systems, the file is also far faster to produce on request than one rebuilt from multiple disconnected tools.