TRADE CONTROLSBRIEF

Authority, evidence, and operating consequence across borders.

Coverage desk

Work-List Operations

Source-backed reporting and analysis connected to the companies, capabilities, authorities, and operating domains it affects.

BIS Part 758 keeps EEI filing separate from export authority

EAR Part 758 describes Electronic Export Information filed through the Automated Export System as a statement to the U.S. government about an export transaction, including item and authority fields when required. A filed or accepted EEI record needs to reconcile to the actual shipment and license basis; the filing itself does not grant export authority.

OFAC's August 28 two-record action needs separate match decisions

OFAC's August 28, 2026 action names one individual with two program tags and a link to Bank Melli Iran, plus a separately named trading company under a different tag. A list update needs two identity and transaction dispositions; shared release date, geography, or headline cannot merge the records or supply an unstated ownership finding.

LexisNexis screening data needs use-purpose controls

LexisNexis Risk Solutions describes watchlist coverage spanning sanctions, politically exposed persons, adverse media, enforcement actions, and registration data. The same page also states that named services are not consumer reports and may not be used for covered eligibility purposes, making dataset, purpose, jurisdiction, and decision authority part of every screening receipt.

SAP GTS work lists need function-specific state lineage

SAP says Global Trade Services supports sanctioned-party screening across sales, finance, human resources, procurement, and distribution, with blocked documents collected in work lists. The operational question is whether every work-list entry preserves its originating business function, document identity, version, state, and later change without collapsing unlike records into one generic case.

Castellum alias matching needs field-level identity evidence

Castellum.AI describes sanctions and politically exposed person screening across many issuer lists, languages, aliases, and enriched identifiers. A potential match still needs a reproducible record of the screened subject, list record, field transformations, score, analyst reasoning, and applicable legal review.

Hurricane modular DDP needs provider-by-provider receipts

Hurricane Commerce presents its Global Trade Ecosystem as an integrated, modular Delivered Duty Paid service that can retain a customer's transport, payment, clearance, IOSS, broker, and other providers. Each selected service still needs a named responsibility, handoff, evidence state, exception route, and execution receipt for every consignment.

Avalara restriction checks need product-context proof

Avalara presents tariff classification, landed-cost calculation, and trade-restrictions management within its cross-border offering. A restriction result is only defensible when the exact product, destination, parties, use, rule source, effective version, exception, and shipment decision remain reconstructable.

The EU Sanctions Map is orientation—not a legal decision record

The map organizes regimes, measures, lists, guidance, court rulings, and legal-act links for quick access. Its own disclaimer says the information is not a basis for decisions with legal implications and that only acts published in the EU Official Journal are authentic and produce legal effects.

OFAC program pages organize authorities—not one global sanctions rule

OFAC administers multiple sanctions programs that can be comprehensive or selective. A country label, list hit, or program-page link is a starting point for scoped review—not a universal statement about every transaction.

OFAC modernization makes de-listings an operating control

Treasury removed 76 outdated SDN entries and framed the action as a sanctions-modernization effort. The operational question is what happens to past matches when official status changes.