Purchasing guide

Sanctions screening software comparison: an evaluation checklist

Use this checklist to compare manual lookup, an internal build and SanctionsKit on source coverage, match review, evidence and operating cost.

On this page

Compare the process from search to decision

Manual official searches, an internal system and a product that connects the steps can each support sanctions screening. They put different work on your team. Compare required sources, check frequency, integration, review handoffs and saved evidence before choosing an approach.

This is a comparison of approaches, not a vendor ranking. The product column describes SanctionsKit. An internal build's capabilities depend on what your team implements and maintains, so evaluate the actual design rather than an ideal version of it.

Use the same customer or supplier scenario for all three. List the subjects and sources, who investigates candidates, which actions need approval and how another reviewer will retrieve the evidence later.

For an OFAC workflow, start with the OFAC screening software overview. For an application integration, inspect the screening API. Then compare plan prices and included capacity against the workflow you tested.

Compare responsibilities side by side

OFAC's Sanctions List Search supports name searches across its SDN and consolidated non-SDN lists. That does not establish coverage of other authorities or every sanctions risk. Evaluate each additional required source for all three approaches.

Use the table to identify which tasks are supplied and which your team must organize. Then test those tasks with the same scenario. A feature label is less useful than evidence that the required workflow can be completed.

Scroll horizontally to compare every column.

Sanctions screening approaches compared by responsibility
RequirementManual official lookupInternal developmentSanctionsKit
CoverageThe operator selects the official tools and lists required by the process.The team acquires and maintains each source it includes.Select eligible sources or a versioned package; confirm current availability.
Application integrationStaff transfer subjects and results between their systems and the search tool.The team designs and maintains the connection.The screening API returns a reference and outcome for your backend to handle.
Potential-match reviewStaff investigate and record decisions in the organization’s chosen process.The team builds or connects its own review workflow.Retained results connect to candidate evidence and the dashboard review queue.
Repeat checksStaff schedule and document repeat searches.The team operates rescreening jobs and handles failures.Configured monitoring supports scheduled and qualified source-triggered rescreening.
Evidence and retentionThe organization records scope, search details, findings, and reasoning.The team implements historical evidence and retention controls.Retained results, case history, and exports follow the applicable retention policy.
Cost inputsStaff time, process controls, recordkeeping, and any separate tooling.Engineering, source maintenance, hosting, security, review, and operations.Subscription, integration, vendor evaluation, review, and internal operations.
Business responsibilityYour organization owns identity findings and business decisions.Your organization owns identity findings and business decisions.Your organization owns identity findings and business decisions.

When occasional manual searches may fit

Manual official searches may fit a team that checks names now and then, with trained staff and no need for an app to start each search. They also help a reviewer inspect an authority's current entry. Decide where staff will save the subject, list, search time, findings and decision.

Try the process with your actual workload. Can staff check every required source, keep clear records and notice when another search is due? No single subject count makes manual work unsuitable for every business. How often you search, the evidence needed and the staff available all matter.

A score cannot decide who the party is. OFAC's match guidance calls for review of the full entry and identifying facts. The process must also name the underlying list and assess the rule that applies.

When an internal system may fit

An internal build may fit unusual needs and a team that wants direct control. Name who will maintain each part: sources, matching, the reviewer interface, saved evidence, security and incident response. Even a small first version needs those owners.

A working file-import and search prototype shows the idea can work. Before Production, test source changes, matching, access controls, failure recovery and past evidence. The build-versus-buy guide helps you map the ongoing work and cost.

When an integrated product may fit

Evaluate a product when results must move from an app or portfolio into a shared review process. SanctionsKit connects its API, dashboard, batch screening, case review and saved evidence. Analysts can work with API results in the included dashboard.

Confirm the sources and types of subjects you need. Investigate a candidate, test an unavailable source, retrieve a result and inspect an export. Review pricing and retention terms. A described source is not proof that it is eligible for your Production request.

Your team still supplies the coverage policy, authorized identity details and reviewers. The product does not discover the complete ownership chain, verify identity documents or decide whether a transaction is legally permitted.

Test each approach with the same fictional supplier

Imagine Cedar Vale Components, a fictional supplier. The buying team has its legal name and checked its company number. A similar-name candidate appears, but the source has incomplete company details. That missing data is unknown, so the reviewer needs more evidence.

For manual searches, record the sources, search details and candidate reference in the chosen case file. For a build, check whether those facts survive the handoff. In SanctionsKit, verify that the retained result opens in case review and keeps the open question and required approval visible.

Assess the business action separately. Owners, other parties, goods, destinations, end use or licenses may need further work. This example explains a review problem; it is not a real listing or a claim about measured product performance.

Estimate cost on equal terms

Use the same subjects, sources, planned repeat checks, retention period and reviewer duties in each estimate. Separate initial setup from recurring checks. Add the labor, tools, infrastructure, subscription and maintenance that each approach needs.

A fictional month with 300 new suppliers and 200 existing suppliers checked once plans 500 subject screenings before extra work. A case adds review effort, but that effort does not have a universal fixed cost. Measure your own process.

Check SanctionsKit pricing for current allowances. API, dashboard, batch and monitoring share the Production screening allowance. The API cost guide explains the difference between requests, subjects and cases.

Make the decision from recorded acceptance checks

Agree a short test plan with engineering and compliance. Record what passed, what needs configuration and what remains unverified. Test the interface, the request and the actual Production coverage. Passing one does not prove the others passed.

Use the interactive demo for a tour with made-up records, or create a workspace for 250 free lifetime live screenings. Share those checks across the API and dashboard, with no monthly reset or credit card needed. The optional sandbox quickstart uses made-up records for integration testing.

  • Every required source and subject type is explicitly available for the intended production workflow.
  • Potential matches reach the responsible reviewer with their original evidence and screening reference.
  • No-match and incomplete operations remain distinguishable from customer or supplier approval.
  • Required review, retention, export, security, and recovery behavior have been checked.
  • The cost estimate includes repeat screenings and the team’s continuing work.

Sources and references

Frequently asked questions

Is this sanctions screening comparison a ranking of vendors?

No. It compares manual official lookup, internal development and a product that connects the steps workflow. SanctionsKit is the product example. Use your own source, review and evidence requirements to evaluate specific vendors or internal designs.

Is there a customer count where manual screening always stops working?

No universal count determines that. Check frequency, number of sources, staffing and evidence needs all affect the workload. Test whether operators can complete and document every required check within your actual process.

What is a useful shared test for manual, build and buy options?

Use one fictional party with a candidate that needs more evidence. Follow the source comparison, reviewer handoff, open question and approval, then retrieve the record. Apply the same acceptance criteria to each approach.

What should I verify before choosing screening software?

Verify required source eligibility, supported subjects, candidate review, failure handling, evidence retrieval, retention and workload costs. Record unverified items explicitly. A successful sample request alone does not establish that the full Production workflow is ready.