OFAC SDN vs non-SDN lists: choose and review each source

SDN and non-SDN are different coverage choices

OFAC publishes the SDN list and consolidated non-SDN lists through its Sanctions List Service. The entries and rules differ. A check of one list does not show that the other was searched.

In SanctionsKit, the source IDs are ofac-sdn and ofac-non-sdn. Neither means all sanctions lists worldwide. A name check against OFAC sources also leaves other questions open, such as who owns the party and what activity you plan to carry out.

Choose the scope your procedure requires

In New screening, apply the approved policy or select permitted sources. Owners and administrators manage required coverage in Screening policies. Confirm current Production availability for every required source.

If required coverage is unavailable, keep the operation incomplete. Do not quietly drop one list. Use Sandbox and invented subjects to rehearse this behavior; its records are synthetic.

Verify sources before an API request

The example below shows a Production request shape using a fictional company. It is not proof that either source is active for your account. First call GET /api/v1/sources and verify availability and organization support.

POST /api/v1/screenings needs authorization, content type and an idempotency key. Include the approved policy when required, and use one coverage selector. Start with the quickstart if you need a safe synthetic first request.

{
  "subject": {
    "name": "Example Trading Company",
    "entityType": "organization"
  },
  "sources": [
    "ofac-sdn",
    "ofac-non-sdn"
  ],
  "reference": "demo-vendor-1042",
  "retention": "standard"
}

Read the originating list in every candidate

The result saves the source versions used. For each candidate, read matches.record.sourceId, record.list, designations and the authority link. These fields show where the record came from and which rule to review. A non-SDN finding does not automatically become an SDN finding.

Review each candidate. Two sources may copy the same original entry. Those copies do not give you two independent reasons to think it is the same party. Compare the facts behind the name.

Separate identity from the restriction on the activity

For a fictional company, first compare trusted registration details and other facts that identify it. Then have the responsible team assess the relevant restriction and planned activity. Keep the identity finding and business decision separate in the case.

Use the evidence workflow to export the retained record. Link any required ownership or other outside review. If both selected sources return no match, that still answers only the list question; it is not a general clearance certificate.

Frequently asked questions