Sanctioned party screening: what each role knows and where the gaps bite

Compliance knows how to judge a potential match. The payments desk knows what is about to leave the bank, and procurement or sales know who the counterparty really is. Trouble starts when one role assumes another has already screened, or clears a hit without context that someone else holds.

What compliance sees

The compliance analyst understands the lists. They know which regimes apply, how ownership rules extend a designation to subsidiaries, and why a common surname on a watchlist is usually noise. They can read a fuzzy match and decide whether it deserves a second look.

What they rarely see is the commercial picture. A hit arrives as a name, an address and a score. The analyst does not know whether the supplier has been paid for years without incident, whether the customer was introduced through an agent, or whether the shipment is already on the water. They decide in isolation, and the record of why they decided often lives in a free text box that nobody else reads.

What the payments desk sees

Accounts payable and treasury see money in motion. They know which vendor bank details changed last week, which payment is going to a country the vendor has never used before, and which beneficiary name on the wire differs slightly from the name in the vendor master. That last detail matters. Screening run at onboarding checks the legal entity. The payment may be going to someone else entirely.

Payments staff also feel the deadline. When a screening hit holds a payment that fails validation, they are the ones fielding calls from the supplier and from the business owner who promised the money would arrive. Under that pressure, the temptation is to release and sort it out later. Most payment teams have no authority to judge a match, yet they are often the people best placed to spot that something has shifted.

Foreign payments add another layer. The intermediary bank, the currency route and the beneficiary bank can each carry their own exposure, and the bank may reject or freeze a transfer that internal screening passed.

What procurement and sales see

The people who own the relationship know things no system captures. They know the distributor is really a front for a larger group. They heard that the new parent company is based somewhere sensitive. They know the end user named on the order is not the party who will actually use the goods.

They also know when a counterparty is about to change. Mergers, new trading names and relocated offices reach the buyer or account manager long before anyone updates the master data. If that knowledge never reaches compliance, the screening runs against a stale picture and returns a clean result that means nothing.

This group is also the most likely to see screening as an obstacle. A held order is a lost quarter to them, so they may be slow to volunteer anything that could cause another hold.

Where the gaps cause harm

The most common failure is the handoff assumption. Procurement believes compliance screened the vendor at setup. Compliance believes payments rescreens before release. Payments believes the vendor master is only populated with cleared parties. Each belief is reasonable, and together they leave nobody checking the party who actually receives the funds.

False positive fatigue is the next problem. When analysts clear hundreds of weak matches, they build a whitelist. That list is rarely reviewed when lists update, so a party cleared under old designations stays cleared after it is added.

Ownership changes slip through. A supplier screened clean can become majority owned by a designated person, and only the relationship owner may hear about it.

Finally, overrides go unrecorded. A payment released by a senior manager to meet a deadline may leave no trace that explains who judged the hit and on what basis. That gap is what an auditor or regulator will find first.

Questions to ask the people who run it

• When a payment is held for a screening hit, who actually decides to release it, and where is that decision written down?
• Is the beneficiary on the outgoing payment screened, or only the vendor record?
• What happens when a vendor changes bank details or trading name? Does anything trigger a rescreen?
• How do account managers report a change in a customer's ownership, and has anyone ever done it?
• Which matches get cleared automatically, and when was that list last reviewed against the current designations?
• Has the bank ever rejected a transfer that internal screening passed? What changed afterwards?
• Who is allowed to override a hold, and has that ever happened under deadline pressure?
• If an analyst is unsure, who do they call for commercial context?

Expect the answers to differ from the procedure document. The workarounds people describe are where the real control sits.

Before changing anything

Map where each piece of knowledge enters and where it stops. A better matching engine will not help if the relationship owner's knowledge never reaches the analyst. Give compliance a simple way to ask the business for context, and give the business a reason to offer it. Put screening at the point of payment release as well as at onboarding, and make every override leave a record that names the person and the reason.

APQC's Process Classification Framework® (PCF) is an open standard developed by APQC, a nonprofit that promotes benchmarking and best practices worldwide. To download the full PCF or to view definitions and measures, please visit www.apqc.org/pcf.