Table of Contents
You ran a check and something came back. Now you need to escalate a screening hit the right way. A hit is not proof of a problem. It is a signal that a name, address, or company in your deal looks like an entry on a sanctions or restricted party list. What you do next matters. Rush it, and you may block a good customer or miss a real risk.
This guide gives you a clear escalation path. You will learn who to tell, how to investigate, when to hold the deal, when to call a lawyer, and how to record every step. If you are new to the topic, start with our overview of denied party screening.
What a screening hit actually means
A hit means your tool matched something in your transaction to a list entry. It could be a strong match or a weak one. Many hits are false alarms. A common name, a shared city, or a partial spelling can all trigger a match. Before you panic, remember that most hits clear once you look closer. Our guide to false positives in denied party screening explains why this happens.
The goal of escalation is simple. Decide if the hit is a false positive or a true match. Do it fast, but do it with care.
Who to notify first
Do not sit on a hit and hope it goes away. Tell the right people quickly. Who you notify depends on your size and setup.
- Your compliance officer or the person who owns screening decisions.
- Your manager, so the deal timeline is understood.
- The sales or operations person handling the order, so nothing ships by mistake.
- Senior management, if the match looks serious or involves a big customer.
If you are a small team, one person may wear all these hats. That is fine. The key point is that a decision maker knows about the hit and owns the outcome.
How to investigate the hit
Now compare your data to the list entry. Work through the details side by side. You are looking for real overlap, not just a shared word.
Check the identifiers
- Full name and any known aliases.
- Address, city, and country.
- Date of birth for a person, or registration details for a company.
- Any ID numbers, like a passport or company number.
If your customer is in one country and the list entry is in another, that is a strong sign of a false positive. If the name, address, and other details all line up, treat it as a likely true match. Also check which list fired. Learn to read entries on the OFAC SDN list and the BIS Entity List. Each list carries different rules.
Do not forget ownership
A party can be blocked even if it is not named directly. If a listed person owns a large share of a company, that company may be off limits too. This is the reason to understand the 50 percent rule. Ownership can turn a clean name into a real problem.
When to hold the deal
While you investigate, pause anything that moves goods, money, or data. This protects you if the hit turns out to be real. Use the table below as a simple guide.
| Situation | Action |
|---|---|
| Weak match, details clearly differ | Clear it, record why, proceed |
| Some details match, unsure | Hold the deal, keep investigating |
| Strong match on key identifiers | Hold, escalate to senior level |
| Signs of evasion or hidden ownership | Hold, get legal advice now |
When in doubt, hold. It is easier to release a held order than to unwind a shipment that should never have gone. Watch for sanctions evasion red flags during this stage.
When to get legal advice
Some hits are above your pay grade. That is not a failure. It is good judgment. Get legal advice when any of these apply.
- The match looks like a true match on a sanctions list.
- You may have already shipped or paid before the hit was found.
- The deal involves complex ownership you cannot untangle.
- You think you may need to file a report or seek a licence.
Getting a listed party wrong carries real cost. The penalties for dealing with a denied party can be steep, and they can hit both the company and the people involved. A lawyer helps you act correctly and on time.
How to document every step
Write down what you did and why. Good records protect you later. If a regulator or auditor asks, your notes tell the story. This is part of a solid audit trail.
- Save the original hit, with the date and the tool used.
- Record the list entry you compared it against.
- Note each identifier you checked and the result.
- State your decision: false positive or true match.
- Name the person who made the call and when.
- Store the file so it can be found again.
Do this for cleared hits too, not only for true matches. A clear record of why you released a deal is just as valuable. For the full workflow, see our step by step guide on how to do denied party screening and follow the wider screening best practices.
Build a repeatable escalation path
Do not treat each hit as a surprise. Write down your steps once, then follow them every time. A simple path means anyone on the team can act the same way. It also cuts delay, because people know their role. Review the path now and then, and update it when lists or rules change. To go deeper on the whole process, revisit our main guide to denied party screening.
Frequently Asked Questions
How fast should I escalate a hit?
Start the same day the hit appears. Notify the decision maker and hold anything that could move. Speed protects you, but the review itself should still be careful and complete.
Can I clear a hit myself?
Yes, if it is clearly a false positive and your role allows it. Record your reasons. If the match is strong or you are unsure, pass it up the chain and seek legal advice.
Do I report every hit to a regulator?
No. Most hits are false positives and need no report. Reporting may apply only when you find a true match or a blocked transaction. A lawyer can tell you what your rules require.
Key Takeaways
A screening hit is a signal, not a verdict. Notify the right person, compare the details, and hold the deal while you check. Clear false positives with a clean record, and escalate true matches to senior staff and legal help. Document every step, even the ones you release. A written escalation path keeps your team calm and consistent. If you want help setting one up, contact our team.