OFAC non-SDN lists: scope and screening evidence

Read the name of the original list

OFAC publishes its non-SDN lists in a consolidated set of files. SanctionsKit reads the XML feed through ofac-non-sdn. Combining the files makes them easier to retrieve; it does not make every entry subject to the same conditions.

A possible match retains the original list name, program labels, and available restriction wording. Start with those details when you review it. The reason a record appears on one non-SDN list may differ from the reason for another.

Keep non-SDN and SDN results distinct

A package can include both direct OFAC sources. The result shows that selected coverage, and a non-SDN record keeps its non-SDN identity. It is not relabeled as an SDN designation.

CSL may carry a copy of the same OFAC record. SanctionsKit can remove that duplicate copy when both entries have the same official OFAC entity number. This avoids counting one listing twice while keeping the original record and the CSL reference.

Use the record to guide the legal review

The non-SDN source profile shows records and refresh information. Follow the original list reference to the current rules for the activity you plan to carry out. SanctionsKit supplies the list evidence; your review must assess the legal conditions.

An unknown list identity needs investigation. It is not assigned a guessed legal category. Keeping that uncertainty visible is more useful than giving a reviewer a simple status that the source does not support.

Move from a company name to the underlying measure

When researching a named company, open its entry in the non-SDN directory and compare legal names, aliases and available identifiers. Keep the component list with the record before assessing the activity. A general non-SDN description cannot establish which measure applies to that company, and a separate SDN check may still be required.