Practical guide
How to run an OFAC check and understand the result
Find OFAC's official search tool, then learn how to run a saved check, review possible matches and keep the evidence in SanctionsKit.
On this page
An OFAC check compares a named party with selected lists
An OFAC check looks for possible matches between a subject and selected OFAC records. SanctionsKit uses the identity details you submit and returns the result of that comparison. It does not verify the person's documents or run a general background check.
For a direct lookup, open OFAC's official search. For a saved check and review record, use SanctionsKit New screening. The steps below explain how to read and retain that result.
Before starting, gather the legal name, subject type and known facts that help distinguish the party. Keep an internal reference so the result can be connected to the correct account or deal.
Create a result your team can find
Open New screening. For a recurring customer, choose Create a saved profile and enter your party reference in External reference. Check the environment and choose the approved, available coverage.
An application can submit the same kind of check through POST /api/v1/screenings. Use a stable reference and standard retention when reviewers need the result in the dashboard. Practice with invented subjects in Sandbox before an authorized Production workflow.
Read the outcome without adding to it
A successful response has data.status set to no_match or potential_match. A no-match describes the completed comparison within its selected sources. A potential match means at least one candidate needs identity review; it does not establish wrongdoing.
Errors use a separate response envelope. A timeout, failed source or malformed response leaves the check incomplete. Do not turn a missing result into a no-match just so an application can move forward.
Separate the name comparison from the business decision
For a fictional company with a similar-name candidate, compare the registration details and jurisdiction in the Review queue. Record each candidate's identity finding and the evidence behind it.
Complete any required external checks and approval before the separate business decision. A no-match can still have a case if policy requires further work. The check did not verify a bank account or research the company's ownership.
Save evidence of this check, then revisit changes
Keep the result ID and use evidence exports while the record is retained. Original documents belong in your approved repository; the case can hold a reference to them.
The result is evidence about one moment and scope, not a permanent certificate. Use Monitoring for continuing relationships or run a new check when policy requires. Follow the search walkthrough for each step.
Sources and references
Authority and technical sources
SanctionsKit documentation
Frequently asked questions
What information do I need for an OFAC check?
Start with the legal name and correct subject type. Add reliable dates and identifiers where you have them, keeping partial dates at their known precision. Use a party reference to connect the result with your own records.
Is an OFAC check the same as a background check?
No. It compares the supplied subject with the selected sanctions records. It does not verify identity documents, check general criminal history, confirm bank account ownership or complete your wider customer review.
Does a potential match mean I must reject the customer?
The label means a candidate needs review. Establish the identity facts, identify the relevant restriction and complete your approved process. Record the business decision separately rather than making it from the name score.
How long is an OFAC check valid?
A result describes the check performed at its recorded time. There is no validity period built into the label. Your policy should define repeat checks based on the relationship, changes and applicable requirements.