Ongoing AML monitoring

Monitoring re-screens approved customers daily against updated lists and moves the session when a new hit crosses your threshold, at $0.07 per person a year.

#Why a one-time screen isn't enough

Screening at onboarding tells you what the lists said that day. Designations get added, adverse media accumulates, and someone who was clean in March can be sanctioned in August. If your obligation includes keeping customer due diligence current - and for most regulated businesses it does - a single screen doesn't meet it.

#How it works

Monitoring is automatically available for sessions where an AML check ran, with no additional integration work:

1. Daily automated checks. Every approved session with monitoring on is re-screened against the full watchlist and sanctions database.
2. Threshold comparison. New findings are compared against the same review and decline thresholds you configured in your workflow.
3. Status change. A new hit above your review threshold moves the session to In review. Above your decline threshold, it moves to Declined.
4. Webhook. Your application receives a status.updated webhook with the updated status and the details of the new hits, in the same format as any other webhook.
5. Console. The change appears on the session with the new hits ready to resolve.

#The thing to build for

An approved session can change status later. If your integration treats Approved as final and stops listening, you'll miss exactly the events monitoring exists to deliver.

Concretely:

• Keep handling status.updated for sessions you've already marked verified.
• Don't ignore a webhook because the session is one you closed weeks ago.
• Make your own user state able to move back out of "verified" - which is usually the harder change, because it's a product decision, not just a handler.

#What it costs

$0.07 per year per monitored person. It is paid from your plan credit or balance.

Priced annually rather than per screen, so the daily cadence doesn't multiply the cost - which is what makes continuous monitoring affordable at volume rather than something you ration.

#Turning it on and off

There are three switches, and each needs write access to verifications:

• In the workflow, alongside the AML step, for new sessions. It's off by default.
• For sessions you already have, select them in User verifications and press Ongoing monitoring in the bar that appears, then Turn on for all of them. Sessions without an AML step are skipped.
• On one verification, with the Ongoing monitoring switch in its AML section.

Turning it off stops the daily re-screen from that day; what was already found stays on each verification.

#Staffing the consequence

The part teams underestimate isn't the integration - it's that monitoring generates a recurring queue. A new hit needs the same resolution work as an onboarding hit: is it your customer, does it matter, record the reasoning. See working through AML hits.

If nobody owns that queue, monitoring produces alerts that sit unread, which is worse than not monitoring - you now have evidence you were told and did nothing.

#Monitoring is not transaction monitoring

Two different things with similar names:

• AML monitoring re-screens the person against lists over time. This article.
• Transaction monitoring evaluates transactions against rules as they happen. See how transaction monitoring works.

You may well need both, and they're billed separately.