Customer vs transaction screening
Customer screening checks who the bank banks; transaction screening checks what it moves. Different data, different timing, one obligation.
L0 Explain simply
An everyday analogy: a secure building runs two checks against the same set of banned-person posters. At the membership desk, every new member is checked before they get a badge, and the whole membership register is re-checked whenever new posters arrive. At the parcel gate, every package passing through is checked for banned names anywhere on the label — sender, receiver, or anyone mentioned in the notes. The desk catches a banned person trying to join; the gate catches a banned name inside traffic that merely passes through, even when neither end is a member. A bank needs both checks for the same reason the building does: the people it knows and the payments it carries are different populations.
L1 Core concepts
Financial institutions deploy two main screening controls. Customer screening (also called name screening) compares customer reference data — names, beneficial owners, connected parties — against sanctions lists at onboarding, when customer data changes, and when the lists change. Transaction screening compares payment messages in flight, before processing continues, so that a payment involving a listed party can be stopped before a potential violation occurs. The two differ in reach: customer screening only sees parties the bank has a relationship with, while transaction screening sees every name in every message — including third parties the bank will never onboard. In a correspondent chain, an intermediary bank may be the only institution positioned to spot a listed name at all.
L2 Practitioner view
The practical differences drive design. Customer data is structured, owned by the bank, and improvable: a missing birthdate can be requested, a garbled name corrected, and the record screened again calmly before an account opens. Payment data arrives from elsewhere, on a clock — it can be truncated, abbreviated, or crammed into free text, and the bank cannot fix it, only decide. That is why customer screening decisions are usually more confident and transaction alerts more time-pressured. Neither control substitutes for the other: transaction screening alone never sees beneficial owners who are absent from messages; customer screening alone never sees the third-party traffic flowing through accounts. Institutions vary on whether one engine serves both or each has its own, but the coverage logic is the same everywhere.
L3 Technical details
Configuration questions practitioners actually face: which customer attributes are screened — names only, or also addresses, countries, and identifying documents — and whether connected parties such as directors and beneficial owners are in scope, both documented risk decisions. When lists update, customer rescreening can re-run the full base or screen only the delta of changed entries; when customer data changes, that change should itself trigger rescreening. On the transaction side, scope covers party fields, agent identifiers, and free text, and repeated alerts on recurring payments raise the question of previously-adjudicated-match handling — suppressing a known-innocent match is efficient but needs governance, review dates, and an owner, because yesterday's innocent namesake can be tomorrow's designation.
Sources & standards1
- Market practice
Wolfsberg Group Sanctions Screening Guidance ↗ — The Wolfsberg Group · Reference data/customer screening and transactions/message screening sections
Wolfsberg guidance is industry market practice, not law; institutions vary in how they apply it.
Sources for this topic2
- Market practice
Wolfsberg Group Sanctions Screening Guidance ↗ — The Wolfsberg Group · The two main screening controls: customer/name screening and transaction screening
Wolfsberg guidance is industry market practice, not law; institutions vary in how they apply it.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
What this simplifies: The membership-desk/parcel-gate analogy presents the two controls as cleanly separate; real institutions blur them — some screen customers transactionally and some enrich transaction screening with customer data. Organisational splits vary widely between banks.
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.
Deepest material on this page: L3 — Technical details. Where a topic stops short of implementation depth, that is a deliberate coverage decision, not an oversight — see coverage.