Why Your Legitimate Payees Keep Getting Flagged

Screening flags names. Your payee data decides how fast they clear.

Yesterday's video was about what happens after a sanctions screening hit: where the ticket goes, who owns it, and how fast it moves. This post is about the part before that. Why clean, legitimate payees get flagged in the first place, and what your team controls.

Sanctions screening compares the names on your payouts against government lists, starting with OFAC's Specially Designated Nationals list in the US. It's designed to be cautious, so a close match stops the payment until someone can rule it out. To rule it out, a reviewer compares everything else on the record: date of birth, address, country, entity details. OFAC's own guidance for evaluating a hit works the same way. The more identifiers that don't line up, the less likely it's a true match.

That's where most of the delay lives. Not in the hit. In the missing data behind it.

What Triggers the Hit

Common names

A shared first name or surname is often enough for a partial match. If you pay thousands of people, some of them will share a name with someone on a list. That's expected.

Names spelled more than one way

Names that originate in non-Latin scripts can be romanized several different ways, and list entries carry aliases and variant spellings to account for it. Screening tools use fuzzy matching to catch those variants, which also means they catch more innocent near-matches.

Generic business names

Business payees with common words in their names, like Global, Trading or International, generate partial matches more easily than distinctive names do.

What Slows the Clear

Name-only records

If all you collected is a name and a bank account, the reviewer has nothing to compare against the list entry. The hit can't be ruled out, so it waits.

Names that don't line up

The name in your system doesn't match the name on the bank account or ID. Nicknames, abbreviations, missing middle names, or a business being paid under an individual's name all create mismatches that need a human to sort out.

Data gathered after the fact

When the provider has to request more information, it comes to you. You go to the payee. The payee answers when they get to it. What could have cleared the same day turns into a week, and the payee only sees that they haven't been paid.

What You Control

Collect enough at onboarding. For individuals: full legal name as it appears on their ID and bank account, date of birth, full address and country. For businesses: registered legal name, registration details and country of incorporation.

Keep one source of truth. Payee data that lives in three systems drifts. Pick one, and push changes to your provider when a payee's details change.

Know what your provider needs to clear a hit. Ask what they request most often, and make sure you already have it before the first payout, not after the first hold.

Ask how cleared payees are handled. Some setups remember a payee once a false positive is cleared. Others review the same person again on every payout. If you pay people repeatedly, that difference adds up fast.

The Takeaway

Screening is going to flag names. That part isn't in your control. How quickly a legitimate payee clears is, and it mostly comes down to the data you collected before anyone needed it.