Practical guide
How to handle a possible OFAC match
Review an OFAC match by comparing identity facts, recording missing evidence and separating the match finding from the business decision.
On this page
Confirm which result and source you are reviewing
Open the SanctionsKit Review queue in the correct organization and environment. Confirm the subject and the result that triggered the case. Retained API and dashboard checks use the same review workflow.
Read the source and original list before deciding what the candidate means. OFAC lists can carry different restrictions. A candidate label by itself does not establish that funds are blocked or that every activity is prohibited.
Compare facts that identify the party
Read the complete entry, including aliases, dates and typed identifiers. Compare an identifier only when its type and issuer make it meaningful. A missing field is unknown; it is not a contradiction.
Consider a fictional customer with a common name. A reliable date or identifier may help resolve the candidate, but the reviewer must explain why it belongs to the subject. Keep original proof in the approved document repository and link its reference in the case.
Record a conclusion for every candidate
Enter the identity finding and reason for each candidate. If evidence is insufficient, keep that question open and escalate it through the approved review process. Do not turn uncertainty into a dismissal to finish the queue.
If the input identity was wrong, run a corrected check and link it to the earlier case. Preserve the original result and explain the change so a later reviewer can follow the sequence.
Complete the checks behind the business decision
Ownership, the planned activity and any authorization may need separate assessment. Record the required external check and its evidence reference, or explain why it is not applicable. Then record the business decision separately from the identity finding.
OFAC FAQ 5 distinguishes steps in assessing an apparent match. Blocking and rejecting are different actions. SanctionsKit records your review; it does not block funds, reject a payment or file a report for you.
Finish approval and retain the trail
Where required, obtain approval from a different authorized person. A changed fact may require a fresh decision and approval. Use neutral terms such as possible match while the identity remains unresolved.
Retrieve the retained case evidence through the evidence workflow. For an ongoing relationship, connect later monitoring events to the review so new information reaches the responsible team.
Sources and references
Authority and technical sources
SanctionsKit documentation
Frequently asked questions
What is the first thing to do with an OFAC match alert?
Confirm the subject, environment and source entry, then compare the full identity details. Keep the business activity at its approved checkpoint while required evidence or review is outstanding. A similarity score alone is not a decision.
Can I dismiss a match because the list has less information?
Less information means less certainty, not a conflict. Record what is missing and look for other reliable facts about the party. Leave the question unresolved when the available evidence cannot support a reasoned conclusion.
How do I correct the customer details during a match review?
Correct the underlying identity and run a new check. Link the new result to the earlier case and explain why the input changed. Preserve both so another reviewer can understand the original alert and the correction.
Does closing a match case execute a block or rejection?
No. Case decisions record the review and business disposition. Any required payment action, blocking, rejection or reporting belongs to your authorized operational process and must be handled by the responsible team.