Use case
Customer onboarding sanctions screening workflow
Connect an explicit list check to onboarding while keeping identity review and other required checks in their own decision paths.
On this page
Collect reliable identifying facts
Use the name your process has collected and the correct subject type. Add a known date or reliable identifier when it is appropriate to collect it. Do not manufacture a birth date or infer nationality from a name to fill a form. Those guesses can make a screening look more certain than it is.
Define required sources before making the request. A versioned package can keep your policy consistent across screens, while explicit source IDs make a tailored selection visible. Record the result ID and selected coverage alongside the onboarding record.
Give the application three clear paths
A potential match should enter identity review. A completed no-match result can satisfy the defined list-check step subject to your policy. An unavailable source, invalid request, or processing failure should remain incomplete and follow your approved recovery or escalation path.
None of these paths replaces identity verification, ownership research, PEP checks, or any other due diligence your activity requires. SanctionsKit does not supply those additional integrations. Avoid a single approved badge that hides which steps actually completed.
Decide what happens after onboarding
Retain evidence only as long as your approved policy requires. If an ongoing relationship needs monitoring, disclose and authorize the retained subject data and budget the rescreens. A one-time minimal-retention screen cannot serve as an undeclared perpetual monitor. Keep case notes relevant to the identity comparison and revisit them when new evidence warrants it.