SecurePoint USA
SecurePoint USAEnterprise Compliance
Book Demo
Back to Compliance Academy
Visitor
Trade
Education
Compliance Manager
Admin

What is an AML / financial-watchlist hit?

A screening match against an anti-money-laundering or financial-crime watchlist — a different regime from export/sanctions, often "reviewed, not relevant" for a non-financial business.

Last Reviewed: 2026-06-02Plain-English reference · not legal advice

Plain-English Summary

An AML (anti-money-laundering) or financial-watchlist hit flags a party associated with financial-crime risk under the U.S. anti-money-laundering framework, which is separate from export controls and OFAC sanctions. Screening engines often aggregate these lists, so reviewers see them alongside sanctions hits. For an export or visitor-management business, such a hit is frequently dispositioned as "reviewed, not relevant" (code 58) — but any AML program obligations your organization may have are a distinct matter.

Why This Matters

AML and sanctions are complementary but legally distinct: anti-money-laundering rules target illicit money flows, while sanctions screening blocks dealings with designated parties. One cannot substitute for the other. Recognizing that a financial-watchlist hit comes from a different regime keeps reviewers from misclassifying it — and signals when a matter belongs with a financial-crime/AML specialist rather than the export desk.

Visual Guide

Explanation Depth

Concept Explanation

Besides sanctions lists, there are watchlists aimed at money laundering and financial crime. These come from a different set of rules (run by FinCEN under the Bank Secrecy Act) than the export and sanctions rules. For a company that is not a bank, an AML hit is usually "reviewed, not relevant." But it is a different topic, so if real money-laundering concerns come up, it goes to the right specialist — not handled like an export issue.

When You'll See This in SecurePoint

In SecurePoint, an AML/financial-watchlist match (code 58) is presented with its source so reviewers can distinguish it from sanctions/export hits. The disposition and rationale are recorded; matters implicating AML program obligations are referred to the responsible program. The platform documents the screening review; it is not a substitute for a Bank Secrecy Act / AML compliance program.

What You Should Do Next

Identify that the hit is an AML/financial-watchlist match rather than a sanctions/export designation. For an export or visitor-management context with no financial-institution role, document the review and, where appropriate, record it as not relevant (code 58). If your organization has its own Bank Secrecy Act / AML obligations, route the matter to that program — do not assume sanctions screening satisfies AML duties.

What Can Go Wrong

Conflating AML with sanctions is the core risk: clearing or escalating a financial-watchlist hit as if it were an OFAC designation (or vice versa) misstates the record. Assuming AML controls satisfy OFAC screening — or that sanctions screening satisfies AML — is a known compliance error. When a matter implicates real money-laundering risk, it needs the appropriate program and possibly counsel, not an ad hoc disposition.

Need structured workflow compliance?

SecurePoint USA builds these checks, watchlists, approvals, and immutable logs directly into your daily operations.

What is an AML / financial-watchlist hit? | Compliance Academy | SecurePoint USA | SecurePoint USA