A confirmed sanctions match means your screening tool found a real party, and not a lookalike. Most tools then offer two possibilities: false positive, or true positive.
There is a different third case, and it is common. The identity is confirmed, but the match may not require any action from your company. That depends on the list, your jurisdiction, and the dates.
A false positive is quick: the party is not the listed one, you note why, you move on. A confirmed match that does not apply to you has no such button, so it gets cleared like noise or left open for days. And clearing a real match without recording why is where most screening programs are inadequate.
A confirmed match is not a finding of breach
Screening answers one question: is this the listed party? It does not answer the next one: does that listing create an obligation for you? Those are different questions, and tools tend to merge them. A red flag appears, and the unspoken assumption is that a real match means a breach. It does not.
Take a supplier that matches a designated entity on a US list. Your company is in Germany, the goods are EU-origin, and no US person or US dollar is involved. The match is real. The obligation may not reach you. Whether it does is a legal question about which regime applies, not a question the matching engine can settle.
That is the distinction that matters. Identity is settled by the tool. Consequence is settled by a person who reads the regime.
Does the list change what the match means?
An OFAC listing, an EU asset freeze, a place on a US export-control list, a sectoral restriction, an enforcement list: each carries its own obligation. Tools often display them side by side, at the same priority, in the same red colour, but the legal effect is not.
An EU asset freeze is precise about what it forbids. Under the EU's asset-freeze regulation, the funds and economic resources of a listed person are frozen, and no funds or economic resources may be made available to that person, directly or indirectly.
An export-control listing works differently. It restricts what you may ship to that party, not whether you may take their payment. Two real matches, two different actions.
List membership is not the only way an obligation attaches. A party can be caught because a listed person owns or controls it, even when its own name appears nowhere. That ownership test has its own rules, set out in our note on the OFAC 50% rule.
So the first question after a confirmed match is not how serious it looks. It is which list it sits on, and what that list actually requires.
Is the match even yours to act on?
A sanctions obligation has a reach. It applies to certain people, certain goods, and certain transactions, not to everyone everywhere. US rules can follow a US person, a US-origin good, a US-dollar payment, or a re-export of controlled US technology. EU rules apply to EU operators and to conduct inside the Union.
The match tells you the party is listed. It does not tell you whether your transaction falls inside that reach.
Take the same German supplier matched against a US list. If the deal touches no US person, no US-origin goods, and no US-dollar clearing, the US obligation may not attach to it. Change one fact, add US-dollar settlement, and the answer can change with it. The match did not move. Your exposure did.
There is a harder version of this question. Some US measures can expose a non-US company to US action for dealing with a listed party, even with no direct US link. Whether that risk applies sits in the designation text, not in the alert. Read it the wrong way and you lose either a clean deal or an unflagged exposure.
Nexus is not a detail you add later. It decides whether the match is yours at all.
Does the date change the answer?
A confirmed match needs two dates before it can be understood: the date the party was listed, and the date your company did business with them. Without those two dates, the alert has no timeline.
Say your company sold goods to a customer in March. The customer was added to a sanctions list in October. When you screen the customer today, the match is real. But that does not mean the March sale was a sanctions breach. At the time of the sale, the customer was not yet listed.
The question then becomes narrower and more useful: did anything happen after the listing date?
Was there a payment? A delivery? A refund? A credit note? A warranty service? Software access? A new order? If the relationship ended before the listing, the historic match may not require the same action as a live relationship. If something continued after the listing, the case has to be reviewed as a current exposure.
A confirmed match without dates is incomplete. It tells you who the party is, but not whether the relevant activity happened while the restriction applied.
The status your tool does not have
Once you connect the list, nexus, and dates together, another status appears. The match is real. The party is the listed party. But for this company, on this list, with this transaction history, there may be no current action to take.
Many screening tools do not give analysts a clean place to record that. They allow the case to be cleared, escalated, or left open. None of those is quite right.
If the analyst clears it as a false positive, the record says the party was not the listed party. That is untrue. If the analyst escalates it as a true positive, the record may imply a breach or obligation that the facts do not support. If the analyst leaves it open, the same case keeps consuming time even after the decision has already been made.
So teams build the missing status by hand.
One team keeps a separate log for real matches that do not currently require action, with the list, the reason, and the date of review. Another adds a manual watch flag: not relevant today, re-check if a list that matters to us names this party later.
This is not something better matching can fix. Better matching helps remove false positives. It does not tell the analyst what a real match means for this company, under this regime, on these facts.
What does an unrecorded clear cost you later?
Here is the part that turns an annoyance into exposure. When the not-actionable match gets cleared as a false positive, the record now says the party was not the listed one. That is false. You confirmed it was the listed one and decided the obligation did not reach you. The record shows the opposite of what you did.
An auditor or a regulator reading that file later sees a real match marked as a non-match, with no reasoning behind it. The decision may have been correct. The evidence for it is gone. A confirmed match cleared with no recorded reason is a sharper exposure than any false positive. You let a real listed-party match through and cannot show why that was lawful.
This is the same defensibility standard auditors apply across the whole program, set out in what auditors look for in a sanctions program. It is also the mirror image of the actionable case. When a confirmed match does reach you, the duties to freeze, block, and report on a deadline are strict. They are covered in what to do with a true positive hit.
What the record has to contain
A defensible not-actionable decision is not complicated. It just has to be written down. The record needs the matched party and the list it sits on. It needs two dates, when the party was listed and when the business happened. It needs the nexus you assessed, the policy you applied, the decision, the reason, and who signed it.
One more field matters: status. A not-actionable match today can become actionable tomorrow, if the party lands on a list that reaches you. The record should carry a watch state, so the decision is revisited when the facts change, not left to memory. The person who made the call may not be in the role in three years.
This gives you one number to manage. Detection time is the gap between a list change and a seen match. Resolution time is the gap between a seen match and a documented decision. For the not-actionable match, resolution time is often infinite, because the decision is never recorded as a decision at all. So the number to watch: for every confirmed match, how long until a documented decision you could defend?
What a confirmed match really asks of you
Two things decide what a confirmed match means for you. The first is what the law requires, given the list, your nexus, and the dates. The second is whether your records can show the decision you made and why.
One number tracks the second: the time from a confirmed match to a documented, defensible decision, counting the not-actionable ones that today reach no decision at all.
A screening tool can confirm the name. It cannot confirm the consequence, and it cannot write your reasoning down for you. Screening finds the party. Resolution decides what the party means for you, and proves it.