TRADE CONTROLSBRIEF

Authority, evidence, and operating consequence across borders.

Newsroom

Global trade controls intelligence

Reporting on export controls, sanctions, classification, licensing, customs operations, enforcement, and the systems that carry those decisions into transactions.

Sanctions Operations

The CSL and OFAC SLS serve different screening-data jobs

The U.S. Consolidated Screening List combines selected Commerce, State, and Treasury lists for cross-agency screening. OFAC's Sanctions List Service is the direct delivery and search environment for OFAC's SDN and non-SDN data, custom datasets, and list-change archives.

ITAR brokering review follows facilitation—not physical custody

22 CFR Part 129 defines brokering through action on behalf of another that facilitates covered defense trade, including specified financing, transport, solicitation, negotiation, contracting, and arranging activities. The review must capture the actor, relationship, activity, article or service, parties, countries, exclusions, approval, and report even when the actor never ships or physically holds the item.

Prewave scoping needs a regulation-specific supplier population

Prewave says its due-diligence platform automates scoping across CSDDD, LkSG, carbon, and biodiversity criteria before analyzing suppliers, responding to risk events, and reporting. Buyers need a versioned population for each governed program so an inclusion, exclusion, score, alert, or report can be reproduced without turning provider output into a legal applicability decision.

SAP GTS needs user, document, and deployment scope

SAP's current Global Trade Services page lists price-on-request private-edition offers measured by users, a co-deployment prerequisite, and a customs-connection add-on measured by documents per year. Buyers need one commercial schedule that keeps those units, environments, connections, services, and pass-through costs separate.

EAR technology access needs a release-event ledger

EAR Part 734 treats some releases of technology or source code to a foreign person as exports or reexports, while defining bounded activities that are not. The control record therefore needs the technology, person, place, method, access information, encryption state, authority analysis, and actual release event—not only a file location or account flag.

Everstream DDRT inputs need source-to-cell provenance

Everstream says its sub-tier visibility can surface potential UFLPA exposure for an automotive Due Diligence Reporting Template. Each populated assertion still needs the named supplier and site, relationship path, source observation, date, interpretation, reviewer, and unresolved boundary behind that specific report cell.

OFAC's auto-and-rail determination is not an SDN list

OFAC's October 1 action applies Executive Order 13902 to Iran's automotive and rail sectors while separately publishing named designations, record updates, and an amended FAQ. Trade controls must preserve the legal object, program tag, named subject, effective time, and transaction analysis instead of treating the sector determination as a blanket list entry.

Exiger needs separate entity, ecosystem, and item dispositions

Exiger presents entity, ecosystem, and item-level views alongside data covering sanctions, trade embargoes, enforcement, modern slavery, adverse media, and other risks. Those signals can support investigation, but an entity relationship, upstream network flag, and component concern do not establish the same subject, scope, legal rule, transaction facts, or authorized disposition.

Oracle GTM tariff savings need an opportunity-realization ledger

Oracle says Global Trade Management can screen for tariff-savings opportunities, compare savings, assign programs for future imports, and estimate total landed costs. A screened opportunity is not a realized benefit until eligibility, transaction use, filing, authority treatment, accounting, and any later correction reconcile.

EAR de minimis needs a calculation ledger

Calculate EAR de minimis from destination-controlled U.S. content over the foreign item's fair-market value. Check zero-threshold rules and FDP scope separately.

OFAC Part 505 needs a program-specific citation map

OFAC's final rule, effective September 25, 2026, consolidates existing sanctions penalty procedures into new 31 CFR part 505 without making substantive changes to the penalty provisions. Part 505 expressly leaves program-specific prohibitions, definitions, interpretations, licenses, and some additional penalties in the relevant program authorities.

OFAC's 2026 blocked-property report needs June 30 asset state

OFAC's 2026 Annual Report of Blocked Property guidance calls for each discrete block held on June 30, 2026, to be reported by September 30. A current balance, sanctions-screen result, or ORS submission number cannot replace the asset-level historical state and initial Blocked/Rejected Report ID that the guidance asks filers to reconcile.

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 Ethiopia removals need program-and-list transition records

OFAC says the national emergency declared in Executive Order 14046 expired and that it removed persons designated under that authority from the SDN List and removed program FAQs. A screening program must carry the exact authority, deleted list identities and aliases, list-file version, effective observation time, rescreened population, and separate-authority review instead of converting the program change into a universal cleared-party label.

Repacked prescriptions need origin-marking continuity

CBP's fact sheet explains that certain foreign-origin capsules, pills, tablets, lozenges, and troches are excepted from individual marking under the J-List, while the outermost container that ordinarily reaches the ultimate purchaser must show origin. When an in-scope medication is repacked for retail sale, the control question is whether that already-determined origin survives the exact container handoff with the required importer certification and downstream notice.

An Interos Section 889 flag needs covered-equipment evidence

Interos says its compliance-risk product can identify prohibited companies for Section 889 work across a supplier network. A company or network flag can direct diligence, but the federal-procurement decision still needs the exact entity, equipment or service, use, representation, contract clause, and applicable rule recorded together.

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.

ComplyAdvantage joint cases need risk-by-risk disposition

ComplyAdvantage says one payment case can present alerts involving parties, reference text, and bank identifiers in a joint analyst view. A release or rejection remains defensible only when every consequential risk is tied to its message field, source profile, evidence, reviewer disposition, and payment-level decision.

Sayari evidence packages need claim-level source timestamps

Sayari says its supply-chain risk platform combines trade, corporate, ownership, facility, and watchlist evidence and can produce source-cited packages. A compiled package is useful only when each consequential claim retains its own source, observation date, entity match, relationship basis, and legal-decision boundary.

Moody's association flags need separate control tests

Moody's describes sanctions data spanning lists, ownership and control, and cautionary associations below ownership thresholds. Those signals can support review, but an association must remain distinct from a designation, ownership finding, legal control conclusion, or transaction prohibition in the applicable jurisdiction.

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.

Dow Jones securities screening needs two decision records

Dow Jones describes sanctions data and screening for securities and related ownership risk. A defensible control keeps the pre-trade authorization separate from the post-trade monitoring and disposition record, with the exact instrument, issuer, ownership link, authority version, account, transaction, reviewer, and action preserved at each point.

Facctum customer and payment screens need separate dispositions

Facctum presents customer screening and payment screening as distinct capabilities alongside continuous watchlist updates. A standing relationship review and a time-sensitive payment decision may share identity data, but they require different populations, messages, clocks, evidence, authorities, and retained outcomes.

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.

CAS special procedures need stock-to-declaration proof

Customs4trade says CAS supports declarations, Special Procedures, excise, and stock administration for customs warehousing, inward and outward processing, and tax warehouses. That operating coverage becomes defensible when every receipt, transfer, use, adjustment, conversion, and dispatch reconciles to the applicable authorization, declaration, remaining balance, duty state, and discharge record.

An Altana product-network link is not a transaction-specific trade decision

Altana describes a product-level global supply-chain network used to connect suppliers, products, and shipments for compliance work. Network context can focus investigation, but an observed or inferred edge still needs provenance, confidence, time, and entity resolution before a qualified owner applies the controlling jurisdiction, list, authorization, end-use, and transaction facts.

A World-Check adverse-media match is not a sanctions restriction

LSEG presents World-Check data for sanctions, politically exposed persons, regulatory and law-enforcement lists, adverse media, and related screening uses. A shared screening environment can organize those signals, but an adverse-media match, a watchlist record, and a legal restriction have different sources, meanings, review tests, and transaction consequences.

Treasury's August 28 actions need separate control clocks

Treasury announced two different August 28 actions: OFAC added Reza Mohammad Taeedi and Kameng Trading Limited to the SDN List, while FinCEN proposed a special measure concerning Banque Misr UAE. The designations create current sanctions consequences; the FinCEN measure remains a proposal with its own comment and rulemaking clock.

An Oracle GTM license assignment needs reservation and usage reconciliation

Oracle positions Global Trade Management for license determination and management alongside transaction controls. Assigning a license to a line can document a proposed authorization path, but release and remaining authority depend on the licensed scope, quantities or values, reservations, actual use, corrections, and authority conditions staying reconciled.

An e2open broker handoff needs filing acceptance and correction lineage

e2open presents a global trade suite spanning due-diligence screening, export and import management, customs self-filing, classification, trade agreements, and duty programs. Platform preparation and transmission can support a controlled filing process, but the importer still needs broker authority, message identity, customs acceptance, rejection, amendment, and release evidence for the specific transaction.

A Trademo shipment record does not qualify a supplier for a controlled purchase

Trademo presents global trade data, supplier discovery, screening, and compliance workflows for sourcing teams. Evidence that an entity has shipped a product can inform diligence, but it does not establish legal identity, capability, origin, classification, sanctions status, end-use fit, or approval for the buyer's specific controlled transaction.

An EAR antiboycott request needs separate action and reporting

BIS's electronic Export Administration Regulations resource includes Part 760's prohibitions, exceptions, evasion rule, reporting requirements, and interpretations. A boycott-related term cannot be governed as one generic document flag: the exact request, recipient role, response, action, exception analysis, and reporting disposition need separate, traceable records.

AEB's end-use questionnaire should outlive its risk color

AEB describes digital questionnaires for end-use and red-flag information, configurable green-yellow-red results, transaction blocks, and a questionnaire audit trail. The color can route work, but a trade decision needs the submitted facts, source context, rule version, reviewer, legal basis, and release authority.

What a QAD trade-compliance dashboard can—and cannot—decide

QAD describes Global Trade Compliance Analytics as on-demand dashboard views of compliance statistics, metrics, and trends alongside import, export, screening, and trade-program modules. Portfolio visibility can direct attention, but a chart cannot establish the lawful disposition of a specific order or shipment.

MIC calculates origin and preference—but a preference result is not supplier-origin evidence

MIC's official product page describes collecting supplier declarations and calculating preferential origin from bills of materials across free-trade agreements, with archived calculations and certificates. A favorable result can support a claim only when the underlying declarations, product structure, rule version, dates, and authorized review remain traceable and valid for the transaction.

ONESOURCE joins screening and customs data—but an HS code is not an export-control classification

Thomson Reuters presents ONESOURCE Global Trade as worldwide import-export compliance software with maintained regulatory information, customs tools, screening, and analytics. Reusing product data can reduce duplicate work, but a customs tariff code does not determine an export-control classification, license requirement, end-use restriction, or release decision.

Zonos Landed Cost prices checkout; customs release remains separate

Zonos documents duty, tax, and carrier-fee calculations for cross-border checkout, plus separate classification, shipping, customs-document, restriction, and denied-party functions. A displayed or guaranteed landed cost can support the commercial offer without proving that the goods are correctly classified, unrestricted, admissible, documented, or released by an authority.

Infor LN keeps licenses separate from compliance-check results

Infor's documentation distinguishes configured trade controls, maintained export licenses, document-level data, internal or external checks, and result history. A passed check is therefore a time-bound workflow result—not the licence record or a legal authorization by itself.

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.

Customs status under the UCC is not export authorization

The Union Customs Code governs customs status, representation, decisions, valuation, origin, declarations, procedures, debt, and records. That customs record does not answer a separate export-control authorization question.

Wassenaar control lists do not authorize a transaction

The Arrangement publishes a current dual-use and munitions reference, but says implementation and entry into effect vary by participating state—leaving classification, jurisdiction, end use, parties, and authorization to the applicable national process.

UK export guidance keeps end-use review outside the control list

The Export Control Joint Unit says listed military and dual-use items require classification, while catch-all controls can require a licence for non-listed items because of the intended end use or end user.

EU dual-use rules keep non-listed items inside export review

Regulation (EU) 2021/821 starts with Annex I controls but also creates authorization and notification paths for certain non-listed items, so list classification cannot close every export decision.

OFAC makes screening one control inside a five-part program

The agency's compliance framework gives buyers a broader test than list matching: risk assessment, controls, testing, training, and management commitment must work as one system.

OFAC's July 23 actions join list changes with license context

OFAC's dated action combines additions, a deletion, and three Cuba general licenses. A screening update is incomplete if the workflow captures names but loses the authorization context released with them.

The EU's media FAQ update shows why source status matters

The Commission updated implementation guidance on July 17. Buyers need systems that can use official guidance without presenting it as if it were the binding Council Regulation.

BIS recasts the UAE's country-group treatment under the EAR

The announced shift from Country Groups D:3 and D:4 to A:5 changes destination logic and potential authorization paths, but the implementing Federal Register rule—not the press release—controls transaction decisions.

HMRC data broadens the UK sanctions-control test

Fifty-eight seizures, a £1.16 million compound settlement, and 22 ongoing criminal investigations show why UK trade-sanctions controls extend beyond name screening.

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.