Sanctions screening
Your team and your AI agents resolve sanctions, PEP, and adverse-media hits in one inbox. Continuous re-screening against OFAC, EU, UN, and PEP lists, with audit logged.
Forest is where your team and your AI agents work sanctions screening. List feeds stream in, hits queue up, homonyms resolve, decisions log. One workflow above any data provider you trust.
One hits inbox across providers
ComplyAdvantage, Refinitiv, Dow Jones, Moody's, LexisNexis hits aggregate into one queue on Forest. Your team stops bouncing between provider portals.
Continuous re-screening on list updates
When OFAC, EU, UN, or PEP lists update, Forest triggers re-screening on the affected records and surfaces new hits as cases. Sanctions stops being point-in-time.
Homonym resolution as a workflow
AI agents pre-process common false positives (homonyms, partial matches, low-confidence scores). Your reviewers focus on real risk, with the resolution path logged on each case.
Maker-checker on every decision
Forest applies maker-checker approval on cleared and confirmed hits. Reviewer, approver, timestamp, and reason are part of the case record.
Tipping-off controls built in
Forest enforces tipping-off controls at field-level. Customer-facing teams see only what regulation allows, while compliance retains the full case view.
Regulator-ready export
Every hit, every decision, every reviewer action logs to the case with the full causal chain. Filtered exports for ACPR or any supervisor run in one click.

Built for regulated fintechs at scale
A single hits view per customer
Sanctions matches, PEP flags, adverse media, and historical decisions on the same record. The screening story lives in one place.
Governance for humans and AI agents
Maker-checker, tipping-off, RBAC, and audit apply to your reviewers and your AI agents the same way. One trail, one set of rules.
Sanctions data, fully connected
OFAC, EU, UN, HMT, PEP, and adverse-media feeds from ComplyAdvantage, Refinitiv, Dow Jones, Moody's ready to tap from your workflows.
Vendor agnostic
Frequently asked questions
You still have question ?
Book a conversation with a forest expert
What lists does Forest screen against?
Forest does not maintain its own list, your provider does. Forest plugs above ComplyAdvantage, Refinitiv, Dow Jones, Moody's, LexisNexis, and similar to cover OFAC, EU, UN, HMT, national PEP lists, and adverse media. Your workflow picks the provider and list per step.
How does Forest resolve homonym false positives?
Forest combines AI pre-processing (DOB match, address match, additional identifiers) with reviewer judgement. Your AI agents propose a homonym verdict, your reviewer approves or escalates. The reasoning chain logs to the case.
Can I keep my existing screening provider?
Yes. Forest is provider-agnostic. ComplyAdvantage, Refinitiv, Dow Jones, Moody's, LexisNexis, Sayari and others connect through MCP connectors or direct APIs. You can run two providers in parallel for coverage and consolidate the hits in one queue.
How does ongoing screening differ from initial screening?
Initial screening happens during onboarding (see [[identity-verification]]). Ongoing screening on Forest re-runs against the updated lists, on a schedule and on list-update triggers. Surfaced hits route to the AML workflow as cases.
How do AI agents help with sanctions screening?
Your AI agents pre-process hits, propose homonym resolutions, and draft reviewer notes. On Forest, every AI agent action runs with human-in-the-loop approval and logs to the case audit trail.
How does Forest log screening decisions for the regulator?
Every hit, every reviewer action, every maker-checker approval, every override is logged with the full causal chain inside your own infrastructure. Filtered exports run in one click.

