Denied party screening,
every match explained.
Denied Party Screening from Stable Software checks suppliers, consignees, manufacturers, and carriers against OFAC, BIS, UN, EU, and UK lists on demand, with match scores, fuzzy name and alias matching, and a reviewer queue that logs every decision.
Restricted party screening,
built for compliance teams.
Every capability is built 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, and banks: screened from the portal against every live list in one search, with each match scored and kept on record. No tab-switching between government sites.
Find matches that exact-string search misses.
We use trigram similarity on every primary name and every listed alias, so alternate spellings and typos still surface. OFAC uses aliases and alternate names for a reason, and so do we.
The core sanctions and restricted party lists in one search.
OFAC SDN and non-SDN lists; BIS Entity, Denied Persons, and Unverified lists; State/DDTC; the UN, EU, and UK sanctions lists; Australia DFAT; Canada SEMA; and FBI Most Wanted: refreshed daily, with each list's record count and last sync shown.
Your compliance team reviews matches, not every name.
Every match above the similarity floor opens an alert in the review queue. Reviewers see the match score, the matched list entry, why it matched, and a required reason field, so every decision is logged with the reviewer's reasoning.
Every screening and every decision documented.
Screening date, query, match score, matched list entry, reviewer decision, written reason, and reviewer: logged for every screening and every alert, with the full disposition history in the audit log.
Screen once. Stay covered.
Put a cleared or escalated party under monitoring and it is re-screened after every list refresh. New matches open fresh alerts; matches you already decided stay decided.
From party submitted
to decision logged.
Every screening runs the same four steps, with a complete record regardless of the outcome.
Screen a party from the portal.
Enter a name with its country and address, and screen it as an entity, individual, or address. The engine checks it against every live list in one search.
Fuzzy name and alias matching. Not just exact strings.
The engine checks the primary name and every listed alias, applies trigram fuzzy matching for typos and variants, and returns a score for every potential hit.
Clean results logged. Matches queued.
A name with no match above the similarity floor is logged as clean. Every match is queued for compliance review with the full match context.
Every decision logged with reviewer reasoning.
The compliance reviewer sees the match, documents their reasoning, and clears or escalates it. The decision, timestamp, and reviewer are stored in the audit log, and the party can go under ongoing monitoring.
The audit trail regulators actually ask for.
OFAC and BIS examiners look for documentation of the screening date, the match, the reviewer decision, and the reviewer identity, for every party. Stable DPS logs all of it by default, with the reviewer’s written reason on every decision.