TRADE CONTROLSBRIEF

Authority, evidence, and operating consequence across borders.

Coverage desk

Defense Trade Brokering

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

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.

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.

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.

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.

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.

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.

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.

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.