Compliance Screening Agent: Every Counterparty Screened Against the Current Restricted Party List
All counterparties screened against current restricted party lists from OFAC, BIS, EU, UN, and country-specific authorities at every transaction. Matches and near-matches held for review. Every decision documented. Freehand's Compliance Screening Agent closes the onboarding-to-execution gap.
Sanctions Lists Change. One-Time Onboarding Screens Do Not Protect the Transactions That Follow.
Restricted party screening is a regulatory requirement but it is often done once at vendor onboarding and forgotten. Sanctions lists change. Entities are added without notice. A single transaction with a restricted party can trigger penalties that dwarf the value of the trade.
Onboarding Screening Leaves Ongoing Exposure
A counterparty that cleared screening at onboarding may be added to a sanctions list months or years later. Without continuous monitoring, every transaction after the list change is a potential violation. The compliance program has a structural gap between onboarding and execution.
Sanctions List Changes Are Frequent and Unannounced
OFAC, BIS, EU, UN, and country-specific authorities add entities to restricted party lists without advance notice. Organizations that rely on annual rescreening are exposed for up to 12 months after a designation is made.
Near-Match Risk Not Managed
Exact name matching misses near-match risk parties with similar names, transliteration variants, and affiliated entities. Without fuzzy matching and structured review workflows, genuine compliance risk passes undetected.
Counterparty Population Is Larger Than Managed
Compliance screening is often applied to direct suppliers and customers only. Carriers, consignees, freight forwarders, and intermediary banks are counterparties who may not be in the standard screening population creating coverage gaps.
Screening Documentation Incomplete for Audit
When a regulatory authority audits trade compliance, documentation of screening decisions must be available for every relevant transaction. Incomplete screening records create audit risk independent of whether a violation occurred.
Transaction-Level Hold Workflow Not Systematic
When a potential match is detected, the decision about whether to hold, escalate, or clear the transaction is often made informally. Without a structured review workflow, determination quality depends on individual judgment.
Screen Every Transaction. Hold Matches. Document Everything.
Screens all counterparties against current restricted party lists from OFAC, BIS, EU, UN, and country-specific authorities at every transaction. Near-matches flagged and held for review. Cleared transactions proceed. Every decision documented for compliance audit.
Transaction-Level Screening
Every transaction screened against current restricted party lists at the moment of execution. A counterparty newly designated between transactions is caught before the next transaction clears.
Full Counterparty Population Coverage
Screening applied to the full counterparty population: customers, suppliers, carriers, consignees, freight forwarders, intermediary banks, and beneficial owners. No category of trading party is excluded from the screening population.
Near-Match Detection and Review Workflow
Fuzzy matching logic identifies near-matches name variants, transliterations, affiliated entities alongside exact matches. Potential matches routed to a structured review workflow with match details and supporting documentation assembled.
Current List Feed Integration
Transactions where a match or near-match is detected are automatically held pending compliance review. Escalation workflows route high-confidence matches to senior review. Held transactions tracked until reviewed and resolved.
Transaction Hold and Escalation
Transactions where a match or near-match is detected are automatically held pending compliance review. Escalation workflows route high-confidence matches to senior compliance review. Cleared transactions proceed. Held transactions are tracked until reviewed and resolved.
Complete Compliance Documentation
Every screening decision logged with the counterparty screened, the list version used, the result, the reviewer identity if a review was triggered, and the final determination. Complete audit trail available for regulatory authority review for every transaction.
From Trade Documents to Screened, Cleared Transactions
Receives trade document and classification data from upstream agents. Delivers screening results and compliance documentation downstream. Triggers the Alerting Agent on confirmed matches.
Receives from
- Product HS classifications and trade document data from the HS Classification Agent used to enrich screening records with product context for export control cross-referencing alongside counterparty screening.
Alerting Agent
- FTA qualification determinations and certificate of origin records from the FTA Qualification Agent used to verify trade document completeness as part of the compliance screening record.
Broker Audit Agent
- Audited customs entry records from the Broker Audit Agent used to cross-reference counterparty identities in broker-filed entries against the screening population.
This Agent
Compliance Screening Agent
- Screens every counterparty against current restricted party lists at every transaction. Flags matches and near-matches for review. Holds transactions pending clearance. Documents every screening decision for compliance audit.
Triggers
- Confirmed matches, high-confidence near-matches, and screening threshold breach notifications routed through the Alerting Agent to trade compliance, legal, and finance leadership immediately.
What Changes When Compliance Screening Runs on the Agent
The restricted party lists do not change. The frequency and coverage of how your transactions are checked against them does.
.svg)
Results from Live Deployments
Outcomes measured from life sciences, industrial, consumer goods, and logistics service provider deployments across global trade operations.
Every transaction screened at execution. Newly designated counterparties caught before the next transaction.
Full counterparty population covered including carriers, consignees, and forwarders.
Near-match detection with fuzzy matching. Potential matches held for structured review.
Every screening decision documented for audit. Complete trail for every transaction.
Connects to OFAC, BIS, EU, UN, Descartes, Dow Jones, Thomson Reuters, ERP, and TMS on day one.
Scales with transaction volume and counterparty count. No incremental compliance headcount.
Works Where Your Counterparty and Transaction Data Already Lives
Reads from restricted party list feeds, ERP, and TMS. Holds flagged transactions and logs every screening decision to compliance archives natively.
Descartes · Dow Jones · Thomson Reuters · OFAC · BIS
OFAC SDN and non-SDN lists, BIS Entity and Denied Parties lists, EU consolidated list, and UN Security Council lists consumed via Descartes, Dow Jones, and Thomson Reuters REST API feeds with continuous updates.
SAP S/4HANA · Oracle Fusion · Dynamics 365
Counterparty master data customers, suppliers, beneficial owners consumed from ERP via BAPI and REST for the primary screening population.
SAP TM · Blue Yonder
Carrier, consignee, and freight forwarder identity data from TMS used to extend the screening population beyond ERP-managed counterparties.
ERP · Freehand Trade Records
Transaction-level order, shipment, and payment data from ERP and Freehand used to trigger screening at the moment of execution.
MuleSoft · Dell Boomi · Seeburger BIS
Transaction and counterparty data flowing through your integration layer accessed without compliance screening pipeline disruption.
Coupa · SAP Ariba
Supplier and procurement transaction data from P2P platforms consumed for screening at purchase order and payment execution.
Screening Result Log per Transaction
Every screening decision logged in Freehand with counterparty, list version, result, match confidence, and reviewer identity for complete audit trail.
Transaction Hold Workflow
Transactions where a match or near-match is detected held in Freehand and ERP pending compliance review and determination.
SharePoint / OneDrive
Screening records and compliance documentation archived in SharePoint via Graph API for regulatory authority review and internal compliance reporting.
MS Teams / Slack / ServiceNow
Match alerts and high-confidence near-match notifications delivered to trade compliance and legal leadership via webhook and REST immediately.
Snowflake / Databricks
Screening records and compliance analytics written to your data lake for enterprise compliance reporting and audit documentation.
ACE Customs Records
Screening records cross-referenced with broker-filed customs entries for counterparty identity verification in ACE records.
3,400 Counterparties. 7 Near-Matches. 2 Transaction Holds. 90 Days.
Real outcomes from enterprises running the Compliance Screening Agent in production.
Powered by the Freehand Context Graph
The Context Graph connects counterparty master data from ERP, carrier and forwarder identity from TMS, transaction records, and restricted party list feeds from Descartes, Dow Jones, and Thomson Reuters into the unified screening context. Every transaction is screened against the current list at the moment it executes.
Built on the Freehand Logistics Language Model, trained on restricted party screening frameworks, sanctions list structures, fuzzy matching methodologies, and compliance documentation requirements across OFAC, BIS, EU, and UN programs. It understands near-match risk and the difference between a genuine compliance concern and a common name coincidence.
- Every screening decision is fully documented. The counterparty screened, the list version, the match confidence score, the reviewer identity, and the final determination are all logged at the moment of execution. Complete compliance audit trail for every transaction.
- The Context Graph learns from review outcomes. Near-match determinations that were cleared or held update the matching sensitivity for similar future patterns. Accuracy improves as the agent builds familiarity with the organization's counterparty base.
- Compliance screening intelligence connects to every agent that interacts with counterparties. The Alerting Agent receives confirmed match notifications immediately. Broker audit records cross-referenced for counterparty identity verification in ACE entries.
Compliance Screening: Questions Trade and Legal Leaders Ask
Straight answers to what trade compliance and legal leaders ask before deploying the Compliance Screening Agent.
OFAC SDN and non-SDN lists, BIS Entity and Denied Parties lists, EU consolidated list, UN Security Council list, and country-specific lists via Descartes, Dow Jones, and Thomson Reuters. Lists updated continuously every screening decision runs against the current version.
Fuzzy matching logic detects name variants, transliterations, and affiliated entity connections alongside exact matches. Near-matches above a configured confidence threshold are held pending review. The reviewer receives the match details, list context, and supporting documentation.
All counterparties in the trading relationship: customers, suppliers, carriers, consignees, freight forwarders, intermediary banks, and beneficial owners. The screening population extends beyond ERP-managed entities to include TMS carrier and forwarder records.
Transaction held in Freehand and ERP pending compliance review. Escalation workflow triggered based on match confidence level. Reviewer receives full context for determination. Decision and rationale logged. Transaction cleared or blocked based on the determination.
Receives trade document and HS classification data from the HS Classification Agent, FTA qualification records from the FTA Qualification Agent, and audited entry data from the Broker Audit Agent. Triggers the Alerting Agent immediately on confirmed or high-confidence matches.
Deployable in days via pre-built connectors to restricted party list feeds, ERP counterparty data, and TMS carrier records. Most enterprises have transaction-level screening running across the full counterparty population within the first week of deployment.
Deploy the Compliance Screening Agent Across Your Trade Operations
Every transaction screened. Every near-match reviewed. Every decision documented. Deployable in days.
Built on Freehand Studio · freehand.ai
