How often should you run AML screening? Ongoing monitoring frequency explained

AML screening frequency is how often a customer or transaction is re-checked against sanctions, PEP, and adverse-media lists after the initial onboarding screen. Because lists and customer circumstances both change over time, a single screen at onboarding only reflects risk as of that moment. FINTRAC does not mandate one universal frequency; the requirement is that a compliance program's monitoring, including screening cadence, be reasonably designed and risk-based, which is the standard Bill C-12 reinforced across every FINTRAC-regulated program.

Onboarding screening is only the starting point

A customer who passes sanctions, PEP, and adverse-media screening on day one is not permanently cleared. 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 after onboarding. Treating the onboarding screen as sufficient on its own leaves a program blind to exactly the changes screening exists to catch.

What drives screening frequency

• Customer risk rating. The risk tier your AML risk assessment assigns should set how often that customer is re-screened, with high-risk relationships re-screened more often, or continuously, and low-risk relationships on a longer cycle.
• List update frequency. Sanctions lists can change with little notice, particularly around new ministerial directives, so a program's re-screening cadence needs to keep pace with how often the underlying lists actually change.
• Nature of the relationship. A one-time transaction has a different monitoring profile than an ongoing account relationship that persists for years.
• Regulatory posture and sector. Sectors under heavier scrutiny, or with a recent history of enforcement activity, generally warrant a more conservative, more frequent cadence.

Batch re-screening vs. continuous monitoring

Batch re-screening runs an entire customer book against updated lists on a fixed schedule, daily, weekly, or otherwise. It produces a large alert spike every time it runs, since the whole book is matched at once, which floods reviewers on run day and then goes quiet until the next cycle. It also leaves an exposure window open: a customer who becomes a sanctions match the day after a batch run would not be caught until the next scheduled run, which could be days or weeks away. Continuous monitoring instead applies matching to each relevant change as it happens, whether a list update or a change in customer data, producing a steadier, more manageable queue and closing that exposure window to close to real time.

Setting a risk-based screening cadence

A defensible cadence is not one fixed number applied to every customer. A workable structure looks like this: continuous or daily re-screening for high-risk relationships and any PEP or previously escalated customer, a shorter periodic cycle, such as weekly, for medium-risk relationships, and a longer periodic cycle, aligned with your standard review schedule, for low-risk relationships. Whatever structure is chosen, it should be written into policy, tied explicitly to the risk ratings your risk assessment produces, and revisited when the risk assessment itself is updated.

How BriteBase runs ongoing screening

BriteBase re-screens continuously against refreshed sanctions, PEP, and adverse-media lists rather than on a fixed batch cycle, so new matches surface for disposition close to when they actually occur rather than at the next scheduled run. Agentic entity resolution is applied to every change as it happens, which keeps the resulting queue prioritized and manageable instead of producing periodic floods. The detail on how each list type is screened sits on the screening software page, and the product itself is on the AML screening solution page.

FAQ