Sanctions screening vs. PEP screening: what is the difference?
Sanctions screening checks whether a customer appears on a list a government or body has ordered you not to do business with, a strict prohibition. PEP screening checks whether a customer holds, or is closely connected to, a prominent public position, which is not a prohibition but a trigger for enhanced due diligence. Both are mandatory for Canadian reporting entities, both run through the same AML screening workflow, and both produce false positives for different reasons. This guide breaks down what each actually checks, where they overlap, and how they are handled together in practice.
Sanctions screening and PEP screening are both mandatory checks for Canadian reporting entities, but they answer different questions. Sanctions screening asks: is this person or entity someone the law prohibits you from dealing with? PEP screening asks: does this person hold, or have a close relationship to someone who holds, a position of public trust that raises their corruption or bribery risk? Confusing the two leads to the wrong response when a match surfaces, since one calls for refusal and the other calls for closer scrutiny.
What does sanctions screening actually check?
Sanctions screening matches a customer or transaction against lists issued under Canadian and international sanctions regimes, including the lists that flow from ministerial directives under the PCMLTFA. A confirmed match is strict-liability territory: the regulated entity is legally barred from proceeding, and the obligation is to screen, detect, and act, not to weigh the match against other factors. Because the consequence of a missed match is severe, sanctions screening tends to run with tighter, more conservative thresholds than PEP screening, which produces its own share of false positives from common names and transliteration variants.
What does PEP screening check?
PEP screening identifies politically exposed persons, heads of international organisations, and their family members and close associates, at onboarding and through ongoing list refreshes. Unlike a sanctions hit, a PEP match does not prohibit the relationship. It triggers enhanced due diligence: senior management approval, a source-of-funds inquiry, and more frequent ongoing monitoring. PEP status is also inherently tiered, since a former minor municipal official and a sitting head of state both qualify as PEPs but carry very different risk, and a well-built program reflects that tiering rather than treating every PEP hit identically.
Where do sanctions and PEP screening overlap and differ?
| Dimension | Sanctions screening | PEP screening |
|---|---|---|
| What a match means | Prohibited relationship, in most cases | Elevated risk requiring enhanced measures |
| Response to a confirmed hit | Refuse or exit the relationship, and report as required | Apply enhanced due diligence and closer monitoring |
| Legal basis in Canada | Sanctions regimes and ministerial directives under the PCMLTFA | PCMLTFA enhanced due diligence requirements |
| Ongoing requirement | Continuous re-screening against refreshed lists | Continuous re-screening plus periodic re-assessment of risk tier |
| Common false-positive driver | Transliteration variants of listed names | Homonyms, since PEP registers recur common names more often |
Why do most programs treat them as one workflow?
In practice, sanctions and PEP screening, along with adverse-media screening, run through the same technical process: real-time matching at onboarding, continuous re-screening afterward, and a disposition recorded on every alert. What differs is the response logic layered on top, refusal for a confirmed sanctions hit, enhanced due diligence for a confirmed PEP hit, so a well-designed screening program routes the two differently downstream even while running them through shared matching and entity-resolution logic. Adverse media typically sits alongside both, since a negative-news finding can affect either a sanctions investigation or a PEP risk rating.
How does BriteBase handle both together?
Our platform screens every customer against sanctions, PEP, and adverse-media lists through one entity-resolution engine, so the near-duplicate matches that plague PEP screening in particular are cleared with the same logic that resolves sanctions homonyms. Each hit still carries the specific rationale and response its type demands: a sanctions match routes to refusal and reporting, a PEP match routes to enhanced due diligence, and both produce the recorded disposition a FINTRAC examiner would expect to see. The full detail on how each list is handled is on the screening software page, terms are defined in the AML and KYC glossary, and the product sits on the AML screening solution page.
FAQ
Is a PEP hit the same as a sanctions hit?
No. The two answer different questions and demand different responses. A sanctions hit is a prohibition finding: a confirmed match means the regulated entity is legally barred from proceeding, and the obligation is to screen, detect, and act, not to weigh the match against other factors. A PEP hit does not bar the relationship at all. It is a risk-tiering signal that triggers enhanced due diligence, including senior management approval, a source-of-funds inquiry, and more frequent ongoing monitoring. Confusing the two leads to the wrong response when a match surfaces, since one calls for refusal and the other calls for closer scrutiny. PEP status is also inherently tiered, because a former minor municipal official and a sitting head of state both qualify as PEPs but carry very different risk, whereas a sanctions match is binary. Getting the distinction right is what routes each confirmed hit to the correct downstream action.
Are Canadian reporting entities required to run both?
Yes. Sanctions screening and PEP screening are both mandatory checks for Canadian reporting entities under the PCMLTFA. Sanctions screening matches customers and transactions against Canadian and international sanctions regimes, including the lists that flow from ministerial directives, and it is strict-liability territory: the obligation is to screen, detect, and act. PEP screening is required as part of the enhanced due diligence framework, identifying politically exposed persons, heads of international organisations, and their family members and close associates. Adverse-media screening is increasingly expected as part of a risk-based program alongside the other two, since a negative-news finding can affect either a sanctions investigation or a PEP risk rating. In practice all three run through the same screening workflow, so meeting the requirement is less about choosing between them and more about running them together while applying the right response logic to each type of confirmed hit.
Why does PEP screening generate more false positives than sanctions screening?
Because common names collide with PEP registers far more often than with sanctions lists. Political and public-sector roles exist in vastly greater numbers than sanctioned individuals or entities, so a given common name is statistically more likely to match a PEP entry than a sanctions listing. That makes homonyms, distinct people who happen to share a name, the dominant false-positive driver on the PEP side. Sanctions screening produces its own false positives, but they tend to come from transliteration variants of listed names rather than sheer volume of shared names, and sanctions screening usually runs with tighter, more conservative thresholds because the consequence of a missed match is severe. The practical result is that PEP screening generates more near-duplicate noise, which is why entity resolution matters most there: consolidating the candidates that actually represent the same underlying identity is what keeps a PEP queue reviewable rather than flooded with names that merely coincide.
Do sanctions and PEP status need to be re-checked after onboarding?
Yes. Both change after onboarding, so both require continuous re-screening rather than a single check at the start of a relationship. Sanctions lists are updated on an ongoing basis as new designations are issued, and a person's PEP status can shift when they take on or leave a prominent public role. A PEP relationship also needs its risk tier periodically reassessed, since the associated risk can change over time even without a new list match, a former minor official and a sitting head of state sit at very different points on that scale. Running both continuously against refreshed lists is what catches a customer who was clean at onboarding but has since become a sanctions match or a newly exposed PEP. The two obligations run through the same ongoing screening process, so re-checking one alongside the other is a matter of workflow, with the response to each confirmed hit still differing downstream.
Can sanctions and PEP screening run through the same tool?
Yes, and most programs run them together, along with adverse-media screening, through one matching and entity-resolution process. The technical work is shared: real-time matching at onboarding, continuous re-screening afterward, and a disposition recorded on every alert. What differs is the response logic layered on top once a hit is confirmed, refusal and reporting for a sanctions match, enhanced due diligence for a PEP match, so a well-designed program routes the two differently downstream even while running them through the same underlying screening technology. Running them together also lets one entity-resolution engine clear the near-duplicate matches that plague PEP screening in particular, using the same logic that resolves sanctions homonyms. Adverse media sits alongside both, since a negative-news finding can feed either a sanctions investigation or a PEP risk rating. Consolidating the checks into one workflow is what keeps a single reviewer able to act on both.
Sources
Screen for both, and respond to each correctly.
Book a demo and we will show you sanctions, PEP, and adverse-media screening in one workflow, with the right response routed automatically and every disposition recorded.
Book a demo