Explain the scope of the check
Keep chosen sources, original references, and dataset, engine, and policy versions with the result. You can see which data and rules were used.
Sanctions screening evidence and audit trail
Keep the facts behind a screening with the review that followed. Export a saved result as JSON or a case packet as PDF or JSON. The record shows what was checked, what was found, and why your team chose the next step.
Paid plans start at $59/month for 5,000 checks each month. API and review dashboard included. See pricing.
A result with its context
Export retained evidence as structured JSON.
What this helps your team do
Keep chosen sources, original references, and dataset, engine, and policy versions with the result. You can see which data and rules were used.
Read the first outcome beside later notes and decisions. Source download time stays separate from the date the authority published a record.
Export while evidence is still available. Store the downloaded file under your own access and retention rules. Holds can preserve eligible evidence before it expires.
A practical use case
A colleague needs to understand a supplier check months after the first review. The case should show the source evidence, the comparison, and the reason for the decision.
Open the saved result and inspect the lists, source records, matched facts, and versions used for that check.
Read the reviewer’s decision alongside the first outcome. Check the dates; downloading a source is different from the authority publishing it.
Download a JSON result or a PDF or JSON case packet. Keep the exported copy in your approved records system.
A sanctions screening audit trail should answer five questions: who was checked, which lists were used, when the check ran, what it found, and what your team decided. The original result stays separate from the later review. That lets another person see how the team reached its conclusion.
For a fictional supplier, a reviewer should be able to follow a possible match back to the source record. The case note should explain the names or IDs compared, any missing facts, and why the identity was confirmed, dismissed, or left unresolved. A score by itself cannot explain that decision.
Use a result’s JSON export for its saved facts behind the check. Use a PDF or JSON case packet for the available review history, notes, and decisions. Use the screening register for a list of checks in a date range. Original PDFs and identity images stay in your document service. A case packet includes their saved links rather than the files themselves.
Before relying on an export, try one with invented data. Check who can open it, when the retention period starts, and where your team will store copies. Reports flag evidence nearing expiry so an authorized person can act in time. Exporting later cannot bring back evidence that has already expired or details that were never saved.
Export a completed case with made-up details. Open the file and check its source dates, possible matches and saved decisions. Store it where your team keeps review records. Check how long those records must be kept. The evidence reference lists the saved fields. An old export does not prove that a source is still current today.
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
It includes the saved result, lists checked, source links, and versions of the data and rules used. A case packet also includes saved decisions, notes, and text files. You can export only the facts that are still saved when you download it.
No. Keep original PDFs, images, and passport scans in your team’s document service. SanctionsKit does not store those original files. It saves their links in the case packet. Your own service controls who can open those files and how long they are kept.
No. A hash can help compare a file with a trusted copy, but a hash and ordinary storage do not make an archive tamper-proof. Once downloaded, the file is outside the app’s access controls. Store it under your own records policy.
No. Retrieval time tells you when the data was downloaded. Publication time tells you when the authority published it. If a genuine publication date is unavailable, SanctionsKit leaves it unknown.
New paid workspaces start with 10 calendar years of standard retention. Existing workspaces keep their saved policy. Open standard-review cases preserve available evidence. The policy may start the retention period when review ends or at a recorded relationship-end or business event; if both apply, the later event starts it. Eligible minimal-retention API checks omit the saved subject, keep a reduced result for 24 hours, and create no case.
Yes. Authorized administrators can place a timed hold or one that lasts until released on eligible standard-retention evidence. Each hold has a reason and release record. Apply it while the evidence still exists. A hold cannot recover expired records or details omitted by minimal retention.
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.