Compliance & Screening
Seven deterministic, rule-table-driven engines — restricted/denied party, country embargo, UFLPA forced labor, end-use, end-user, anti-boycott, military end-use — run on every shipment and every party. Qubere keeps re-screening what it already cleared when the party or the watchlist changes, and every hit is immutable evidence.
The problem
What a trade-compliance team will tell you:
"We screen against OFAC at onboarding. We do not re-screen when OFAC updates the SDN list — which is basically weekly."
Stale clearances
"A name match in our old tool is treated as a legal-identity match. Analysts waste days clearing false positives with no way to record why."
False positives
"When we clear a party, that's a status field someone can overwrite. There's no immutable record of the hit that was there before."
No audit trail
How Qubere addresses it
Restricted / denied-party screening
Every party is screened against SDN, Consolidated non-SDN, DPL, ISN, SSI, FSE, PLC, NS-MBS, DOW JONES — exact, raw-word, and a phonetic shortlist feeding a fuzzy scorer, plus an independent red-flag keyword check. Results are immutable; the disposition is separate.
RDPS · continuous / reverse screening
A delta-impact dispatcher reacts to a specific reference-data change within minutes; a full-population dispatcher re-screens the whole account on a schedule. Every outcome records whether the result worsened and a deterministic transition type.
| Party | Before | After | Transition |
|---|---|---|---|
| Severstroy OOO | CLEAR | HIT | NEW_HIT |
| Baltic Marine Ltd | POTENTIAL | HIT | ESCALATED |
RPS · matcher quality
Every reviewed HIT-tier disposition on file — confirmed match or false positive — feeds a precision / false-positive-rate readout, plus a threshold sweep showing what recall and precision would have been at every other nameThreshold cutoff. Same ground truth an analyst already produced by doing their job; nothing new to label.
| Threshold | Surfaced | Precision | Recall |
|---|---|---|---|
| 0.70 | 488 | 81.2% | 97.4% |
| 0.80 current | 312 | 88.1% | 91.0% |
| 0.90 | 201 | 94.5% | 76.6% |
Community screening · batch
Submit a batch (manual or file upload); Qubere runs the canonical RPS and embargo engines against every row — it orchestrates, it never re-implements matching. A denied-party match and a red-flag keyword hit stay independent findings.
| # | Party | RPS | Red flag | Category |
|---|---|---|---|---|
| 0007 | Nanjing Optics Import Export | MATCH | — | CONFIRMED_MATCH |
| 0114 | Dalian Hengli Group Co. | 0.78 | — | POTENTIAL_DENIED_PARTY |
| 0233 | Meridian Defense Systems LLC | NO_MATCH | "military end use" | RED_FLAG_ONLY |
| 0341 | Hansa Components GmbH | — | — | PRE_APPROVED_REUSE |
Network & ownership intelligence
Qubere persists Dow Jones' relationship rows (director/officer/associate/family/beneficial-owner) as a bounded graph and evaluates two things off every direct match: an ownership-attribution rule (OFAC's 50% rule, up the chain, never fabricated when a source lacks a percentage) and a relationship review signal — a director/officer/associate of a sanctioned entity, worded and colored as a review flag, never a hit.
License determination
A deterministic engine (never an LLM) runs classification-format validation, tri-state end-use / end-user handling, and license-exception evaluation as pure functions — now with real jurisdiction-specific evaluators (US country-group, EU, UK/E1, RPL, plus a generic rule-graph fallback covering every other country in the reference table). US control-list data, EU classification flags, and EU license-exception pairing are loaded and published today — real verdicts, not just the fail-safe. For any capability whose reference dataset still isn't published, it never fabricates a LICENSE_REQUIRED / NO_LICENSE_REQUIRED outcome.
No control-rule dataset → the engine will not output a licensing verdict. This is fail-safe by design.
Audit, notifications & the partner API
Compliance events queue durable notifications through an outbox/dispatcher (never sent inline, so a mail outage can't lose a hit alert). Every action writes an immutable AuditLog entry. External systems hit the same read/rescreen behavior by API key.
| Time | Action | Entity | Actor | Src |
|---|---|---|---|---|
| 12:41:07 | RPS_RESCREEN | PTY-4471 | J. Kessler | UI |
| 12:39:55 | EMBARGO_SCREEN | SHP-2026-000188 | system | PIPE |
| 11:22:03 | RESTRICTED_PARTY_SCREEN | PTY-8890 | api-key: acme-prod | API |
| 09:15:40 | COMPLIANCE_FORMAL_OVERRIDE_CREATE | RES-11902 | D. Osei | UI |
What's real today
Sell what's there: the denied-party, embargo, forced-labor, and network/relationship coverage is real and continuous, spanning the US, UN, and fifteen additional national/multilateral sanctions and exclusion sources. Say plainly where it stops.
Objection handling
| "Is this an AI making sanctions calls?" | No. Every screening verdict is a rule table and a scorer you can inspect. The AI in the platform does analysis inside stages — it never decides a hit. |
| "Do you do PEP / beneficial ownership?" | No standalone PEP list or corporate-registry lookup — still a known gap. But ownership-attribution off a direct hit is real: OFAC's 50% rule, evaluated up the chain, plus a director/officer review signal from the relationship graph. Honestly scoped — Dow Jones doesn't send an ownership percentage today, so most cases surface as "ownership data incomplete," not a computed number, and an incomplete/conflicted/unresolved finding auto-opens an EDD case for an analyst. Sell what's there: denied-party, embargo, forced-labor, and network/relationship coverage is real and continuous. |
| "License determination sounds like it does nothing." | Not anymore — US control-list data and EU classification/license-exception data are loaded and published, so it returns real verdicts there today. For everything else it's still the honest thing: it refuses to output a fake control-list answer when the data to back it isn't loaded. "REVIEW_REQUIRED, here's what I checked" is worth more than a guess. |
The close
Immutable results, separate dispositions, continuous re-screening. Continuous assurance, not a onboarding checkbox.
Next step: send us an anonymized slice of your party master. We'll run it live — RPS, embargo, UFLPA — and walk the findings with your compliance lead.
Full feature list and talk track: docs/apps/customs/sales/compliance-and-screening.md