Use case

Supplier sanctions screening: bulk checks and review

Screen supplier records in batches, investigate aliases and registration details, and monitor selected ongoing relationships.

On this page

Prepare the file around actual entities

Supplier files often contain trading names, repeated subsidiaries, and incomplete registration information. Keep the legal entity you intend to assess distinguishable from a brand, contact person, or payment reference. Use organization subjects and include reliable identifiers with their issuing authority when available.

A batch row is one intended screening subject. SanctionsKit does not silently decide that similarly named suppliers are the same entity. Conservative source-record links also do not establish corporate ownership. Your supplier master data needs its own identity and relationship controls.

Review the exceptions at row level

Each row can carry a selected source package. The batch reports completed results and failures separately, so a malformed row or unavailable source does not disappear inside a single successful-file label. Correct failed rows and resubmit them with new operation identities.

Investigate potential matches with the available name, identifier, address, and restriction details. Where export-control lists matter, retain the original list identity and assess the relevant activity separately. A supplier name search cannot classify goods, resolve end use, or establish licensing requirements.

Keep ongoing review proportionate

Monitor suppliers that need repeated checks under your policy. Every completed rescreen consumes a subject, and the retained monitor input has a separate privacy purpose from a one-time batch. Stop monitors for relationships that no longer justify retention. Preserve completed results and analyst reasoning only within the approved evidence period.