Screening execution
Customer versus transaction screening, the screening lifecycle, name matching, secondary identifiers, message screening, and system architecture.
- 019 MINCustomer vs transaction screeningCustomer screening checks who the bank banks; transaction screening checks what it moves. Different data, different timing, one obligation.AFTER: Sanctions screening vs AML vs fraud
- 029 MINThe screening lifecycleFrom data in to decision out: how a screened record passes clean, or becomes an alert, a held payment, and finally a documented disposition.AFTER: Customer vs transaction screening
- 0312 MINName matching and fuzzy logicListed names never arrive spelled the same way twice. Fuzzy matching is how the control catches variation — at the price of innocent lookalikes.AFTER: The screening lifecycle · Anatomy of a sanctions list
- 048 MINSecondary identifiers and confidenceA name similarity opens a question; birthdates, documents, and addresses are what close it — in either direction, with evidence.AFTER: Name matching and fuzzy logic · Identifiers and data quality
- 0510 MINScreening payment messagesPayments are screened in flight: party fields, agent identifiers, and free text — and how the message is structured decides how well that works.AFTER: The screening lifecycle · The pacs family: interbank messages
- 0610 MINScreening system architectureOne filter, many callers: how watchlist feeds, matching engines, hold queues, and case management fit into the bank's payment estate.AFTER: The screening lifecycle · Aggregation and provenance
- 0713 MINPayment transparency and the travel ruleComplete, unaltered sender and receiver information must travel with a payment so every bank can screen it — the travel rule, and how controls catch wire stripping.AFTER: Screening payment messages