Every party screened.
In milliseconds.
Stable Denied Party Screening checks suppliers, consignees, manufacturers, and carriers against OFAC, BIS, UNSC, and EU lists in real time, with match scores, fuzzy name matching, and a compliance review queue built for your team.
Real-time screening,
built for compliance teams.
Every capability is production-hardened for importers, customs brokers, and freight forwarders. Not a checkbox feature bolted onto a filing system.
Screen every party before the shipment moves.
Suppliers, consignees, manufacturers, carriers, banks, and beneficial owners: screened against 40+ lists the moment they're added to a shipment. No overnight batch. No manual lookup. Sub-200ms, every time.
Find matches that exact-string search misses.
We use phonetic, transliteration, and edit-distance matching to catch name variants, alternative spellings, and transliteration differences across scripts. OFAC uses aliases and alternate names for a reason, and so do we.
Every major sanctions and restricted party list in one API.
OFAC SDN, BIS Entity List, UNSC Consolidated, EU Consolidated, UK HMT, DFAT Australia, and 30+ additional country and multilateral lists: updated within minutes of publication, versioned, and searchable.
Your compliance team focuses on real matches, not false positives.
Matches below your confidence threshold go into a review queue. Reviewers see the match score, the matched list entry, the reason for the flag, and a documentation field, so every decision is logged with the reviewer's reasoning.
Every screening decision documented and exportable.
Screening date, list version, match score, reviewer decision, and reviewer ID: logged for every party, every shipment. Pull a screening history for any party in seconds. Export in formats regulators accept.
Screen where the data is. Not as an afterthought.
REST API for embedding screening into your ERP, TMS, or entry workflow. Webhooks for real-time callbacks. Batch screening for historical records. We integrate into the places where parties are first entered, not at the end of the process.
From party submitted
to decision logged.
Every screening runs the same four steps, in under 200 milliseconds, with a complete audit record regardless of the outcome.
Screen a party with one API call or from the portal UI.
POST a party name, country, and type (supplier, consignee, etc.) via the API or enter it in the portal. The screening engine runs across all relevant lists within 200 milliseconds.
Fuzzy matching, transliteration, and alias expansion. Not just exact strings.
The engine checks exact name, aliases, AKAs, and transliterated variants. It applies fuzzy matching for typos and variants. Match scores are returned for every potential hit.
Auto-clear below threshold. Review queue above.
Parties that score below your auto-clear threshold are cleared automatically and logged. Parties that score above are queued for compliance review with the full match context.
Every decision logged with reviewer reasoning.
Compliance reviewer sees the match, documents their decision, and marks as cleared or denied. The decision, timestamp, reviewer ID, and list version are all stored in the audit trail, ready for export if a regulator asks.
The audit trail regulators actually ask for.
OFAC and BIS examiners look for documentation of the screening date, the exact list version used, the match score, the reviewer decision, and the reviewer identity, for every party, every time. Stable DPS logs all of it by default, retains it for five years, and exports it in the format examiners accept.