Submit the work once
Use an inline batch for up to 100 subjects or a private JSONL file up to 25 MB and 10,000 subjects. Accepted batches continue in bounded chunks without keeping your connection open.
Bulk sanctions and portfolio screening
Screen your customer or supplier list. Track each row’s result.
Submit a customer, seller, or supplier list and follow each subject through screening. Review completed results, investigate potential matches, and correct failed rows without losing track of the rest of the file.
API and compliance dashboard included in every plan.
SanctionsKitIllustrative workflow
A file. Individual outcomes.
SubjectNext step
PersonReview match
OrganizationView result
Incomplete rowCorrect input
Failed rows stay visible.
Correct an exception without resubmitting the whole file.
What this helps your team do
Turn a list of subjects into work your team can review.
Keep exceptions visible
Completed and failed rows appear separately. A failed input or unavailable check stays an exception to resolve; it never becomes an implied no-match result.
Follow the individual result
Each completed subject has its own screening reference and retained evidence. Potential matches connect to the same review workflow as individual checks.
A practical use case
An existing supplier portfolio needs a sanctions check.
A few exceptions should not force your team to reconstruct the entire run. Keep the accepted job and each row’s outcome visible.
- 01
Prepare subjects and coverage
Map the identities your organization actually holds to the subject format and select the sources required by your policy.
- 02
Track accepted work
Follow progress as the worker processes bounded chunks. Open completed results and distinguish pending, completed, and failed rows.
- 03
Resolve the remaining exceptions
Correct failed subjects and submit those rows as a new request. Avoid resubmitting completed rows simply because part of a file failed.
For the people behind the process
One capability. Useful to the whole team.
Operations
A portfolio run with visible progress
See which rows completed, which need attention, and how much accepted work remains.
Explore your workflowCompliance teams
The same case workflow at larger volume
Review a potential match with its own evidence rather than treating a whole file as a single outcome.
Explore your workflowDevelopers
Submit and retrieve through the API
Build portfolio checks into your system without holding a request open for the whole run.
Explore your workflowEvaluate the details
Batch screening: practical questions.
What happens when some rows fail?
The job reports completed and failed rows separately. Failed rows are not no-match results and do not consume completed-screening units. Correct the exceptions and submit those subjects in a new request.
Can I cancel a batch after it starts?
Cancellation stops pending work between processing chunks. Completed work remains part of usage, and reserved allowance is released for cancelled rows that were not completed.
Do batch screenings use a separate allowance?
No. Completed batch subjects share the production screening allowance with individual API requests, dashboard screens, and monitoring rescreens. There are no automatic overages.
See SanctionsKit in action
Explore how a portfolio becomes individual reviewable results.
Try the interactive demo with synthetic examples. Compare plans for your team’s screening volume.