Customer vs transaction screening
Customer screening checks who the bank banks; transaction screening checks what it moves. Different data, different timing, one obligation.
IN ONE LINE
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.
WHAT IT ACTUALLY IS
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.
HOW IT WORKS
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.
THE WORDS
- Real-time screening
- Screening a payment while it is in flight, so a hit stops the payment before it leaves rather than being found afterwards.
READ FIRST
CONNECTED TO
SOURCES
- Wolfsberg Group Sanctions Screening Guidance — The Wolfsberg Group
- Payments Signal editorial teaching models — Payments Signal
Derived from Customer vs transaction screening. Every claim on this card is sourced on that page.