OFAC screening software for SDN and Non-SDN checks

“OFAC screening” needs a defined scope. Check which SDN and Non-SDN sources your policy requires and which are available for your subject type. Keep each source name with the result. Different lists can lead to different restrictions or follow-up questions.

The API and dashboard use the same screening process. A saved result names the data and rules used at that time. A source that is unavailable or too old cannot quietly disappear from a required check.

Choose an invented person or company, run a supported synthetic check, and open the saved evidence. Ask the reviewer to explain what supports a possible match and what remains unknown. Try an unresolved case and an error too, so your team knows where each goes.

Use case review to record who each match may be and what your team will do. Use the OFAC API guide when your app will submit the checks. Confirm live source access separately from any synthetic demonstration.

Choose ofac-sdn and ofac-non-sdn as your OFAC policy requires. Check both source IDs in source discovery first. If a required feed fails, the check is incomplete. A no-match also leaves any open ownership or trade questions for your team to resolve.

OFAC screening checks names and known details against the lists you choose. Use the API or dashboard to run supported checks. Review matches, export evidence, and set up repeat checks if needed. Check the lists you can use in current coverage first.

OFAC provides SDN and consolidated Non-SDN data through its Sanctions List Service. These lists do not all mean the same thing. Read the authority, list, program details, and original record when you assess a finding.

Imagine a buyer checking Juniper Meridian Components Ltd. This fictional supplier has reference supplier-1042, a known country, and a registration ID of DEMO-58241. Its file includes a verified registry extract. Every name, ID, and possible match in this example is invented. This is not a real OFAC listing or an actual check result.

Suppose the check returns the fictional candidate Juniper Meridian Trading Ltd. The first outcome is potential_match. A reviewer now needs to decide whether the records describe the same company. The similar name alone does not answer that question.

First, check that the IDs use the same identifier type and issuing registry. Read the full records for other names and relevant details. In this invented example, the verified registry evidence supports a finding that these are different companies. The reviewer explains that evidence and gets a second review if required. One conflicting number is not a universal rule for dismissing matches.

Next, finish the separate supplier checks, including the ownership work your policy calls for. The reviewer with the right role can record the business decision. Keep the original potential_match beside that later decision so the reason for review stays clear. Export the case packet while the facts remain saved. Add repeat checks if the ongoing supplier needs them.

If you cannot verify the IDs, leave the identity unresolved. Assign the missing-information task and keep the case open. If a required OFAC source is unavailable, the check is incomplete. It must not become a no-match or a supplier approval.

OFAC’s 50 Percent Rule guidance explains that ownership can block an entity even when its own name is not on the SDN List. SanctionsKit does not discover beneficial owners, calculate ownership chains, or decide whether an authorization applies. Record those outside checks and their evidence in your review process.

OFAC’s possible-match guidance calls for comparing the full record and available known details. SanctionsKit helps you do that. A no_match is limited to the chosen sources, submitted details, time, and matching rules. It is not an OFAC certificate or permission to make a transaction.

Use the synthetic demo to follow a check into review. Include a no-match, a similar name, an identity that is still unclear, and a required check that fails. Ask who will own each next step. The OFAC API guide shows how to connect that flow to an app.

Before using production, confirm choice of lists, error handling, reviewer roles, and retention. Estimate completed checks and rescreens against the shared allowance on pricing. Your wider OFAC procedures still determine which other checks and approvals are needed.