Rescreen the selected subject
Choose six-hour, daily, or weekly checks. Qualified source updates can also trigger a full rescreen of the saved subject.
Ongoing sanctions monitoring and alert management
Keep checking customers and vendors as lists change. Set a schedule for repeat checks. See what changed in the monitoring inbox, then open the linked case. Each completed check uses one credit from your shared allowance.
Paid plans start at $59/month for 5,000 checks each month. API and review dashboard included. See pricing.
Keep selected subjects in view.
Record the selected coverage
Run a full rescreen
Bring the case back to review
What this helps your team do
Choose six-hour, daily, or weekly checks. Qualified source updates can also trigger a full rescreen of the saved subject.
See new or removed matches, changed evidence, policy changes, failures and recovery events. Compare the saved evidence from before and after.
Open the linked case when an alert needs review. Pause or resume monitors as the relationship changes. Seeing an alert is separate from deciding the case.
A practical use case
Your team reviewed a supplier last month. Today, a source record changes. The old result stays in the history, and a new check gives the reviewer current facts to compare.
Choose the people and companies that need repeat checks. Save the known details and sources needed to screen each one.
The schedule and qualified source updates trigger fresh checks. Each completed rescreen uses the shared allowance. Failed checks need follow-up.
Compare the before-and-after evidence in the monitoring inbox. Acknowledging an event does not decide the case; open the linked case to record your conclusion.
Ongoing sanctions monitoring is useful when a relationship lasts beyond the first screening. Start with the customer, supplier, or other party your policy says to monitor. A company and its owners are separate subjects. If several parties need checks, plan for several monitors.
Choose the sources and a six-hour, daily, or weekly schedule. Include rescreens after qualified source updates in your workload estimate. Each monitor needs the subject’s known details to remain saved. A one-time minimal-retention result cannot provide those details later. Set a clear point at which the monitor should stop.
For example, 40 subjects checked daily use about 1,200 scheduled rescreens in a 30-day month. Add the first checks and any runs caused by source changes. Each completed rescreen uses the shared production allowance. A monitor slot sets how many subjects you can monitor; it does not include unlimited checks. Compare both limits on pricing.
In a fictional supplier review, an operator sees an evidence-change alert and opens its linked case. The reviewer compares the earlier and current facts, then records a new decision if needed. Acknowledging the alert shows that someone saw it. The case still needs its own review. A failed monitoring run also needs attention: failure does not mean the supplier’s result stayed unchanged.
Choose the sources and schedule for repeat checks of a saved customer or supplier. Test a change with made-up records. Check that the alert opens the right result. Your team must be able to tell a failed check from one with no new evidence. Read the monitoring guide and check current coverage before you start.
TRY IT WITH YOUR TEAM
Check your sources, try a free live check and estimate your monthly cost.
Find your required sources, what they cover and when they were refreshed.
Explore coverageUse your free live checks to find possible matches. Compare the evidence and save a decision.
Start with 250 free checksCount new checks, rows in uploaded lists and repeat checks from monitoring.
See workload examples
Evaluate the details
No. Sanctions monitoring checks saved names against lists again. Transaction monitoring looks for patterns in payments and other activity. SanctionsKit does not look for those patterns.
No. Each completed rescreen uses the same production allowance as API calls, dashboard checks, and completed batch rows. Estimate your schedule plus source-change checks. There are no automatic overage charges.
Keep the name, known details, and sources needed for each repeat check. Stop the monitor when you no longer need it. Your records policy sets how long past results are kept.
Assign an operator to review new inbox events and a reviewer to handle linked cases. Compare the changed evidence before making a decision. Keep failed checks assigned too, so a source or request problem does not become an unnoticed gap.
Yes. New evidence, changed subject details, or a policy change may need a fresh review. The earlier decision stays in the history. It does not tell the system to ignore that person or company forever.
You can choose six-hour, daily, or weekly checks. If your team’s policy sets the schedule, the monitor follows it. Pause or resume a monitor as needed. Stopping new checks does not delete past results.
See SanctionsKit in action
Start with 250 free live checks. Use the API or dashboard to review matches and save decisions. Choose a paid plan when you need more checks.