Guide collection
AML screening guides: KYC, customer checks, and software scope
Compare AML, KYC, and sanctions screening, then plan customer checks, case review, and software requirements without overstating product coverage.
On this page
Choose the question you need to answer
AML is a broader program context than a sanctions list check. These guides explain where identity verification, customer due diligence, screening, transaction monitoring, and reporting answer different questions. Start with the distinctions before deciding which product capability your team needs.
A useful buying process names the required controls and the evidence each one produces. SanctionsKit supports selected-source screening and its review workflow. It does not claim that purchasing a screening API creates an entire AML program or makes an organization automatically compliant.
Understand the scope and the first decision
What is sanctions screening? A practical business guide. Understand sanctions screening, the difference between matching and identity review, and how source coverage, ownership, and monitoring affect the result.
What is AML screening? Scope, checks, and review workflows. Learn where sanctions and watchlist screening fit into AML, what the checks can establish, and which identity, ownership, and transaction controls remain separate.
OFAC screening vs AML screening: what is the difference?. Compare OFAC sanctions checks with broader AML controls, including identity, beneficial ownership, watchlists, monitoring, and case review.
KYC vs AML vs sanctions screening: a practical comparison. Separate KYC, KYB, CDD, AML, and sanctions screening so your onboarding workflow records what each control actually verifies and leaves unresolved.
Build the review and operating process
AML compliance software: a screening-focused buying checklist. Evaluate AML software by actual scope: sanctions sources, identity controls, case management, monitoring, integrations, retention, and operational costs.
Customer screening: connect onboarding, review, and monitoring. Design customer and counterparty screening around stable identities, selected sources, documented match decisions, and changes across the relationship.
Sanctions screening for small businesses: a workable process. Build a manageable sanctions screening process for a small business, with clear party selection, review ownership, evidence, and escalation boundaries.
Keep the related controls connected
AML case management vs sanctions case management. Learn how sanctions identity investigations differ from broader AML cases, and how to connect findings without losing evidence, access controls, or decision scope.
AML screening API for fintech: a safe integration design. Integrate the sanctions-screening part of an AML workflow with server-side keys, idempotency, review states, monitoring, and retained evidence.
Sanctions monitoring vs transaction monitoring. Compare ongoing name and entity rescreening with transaction-behavior monitoring, and design separate outcomes, evidence, and escalation paths.
Use the guide as part of a defined procedure
These pages explain workflows and product boundaries. They do not establish whether a specific person is a listed identity, replace current official guidance, or decide whether a transaction is authorized. Keep the source comparison, remaining uncertainty, required review, and separate business action in the record.
For product behavior, use the published documentation and current source coverage. For a customer or vendor workflow, start with the actual legal party and preserve the evidence behind the decision.