Export license determination

Description

Export-license determination is the per-transaction question that sits in front of every cross-border shipment of goods, software, or technology that touches a controlled list. The logic has three layers: classification (what is the item, and what category does it fall into under the EAR Commerce Control List, the ITAR US Munitions List, or the EU dual-use Annex I), destination (where is it going, and what licensing requirements does that destination trigger under the applicable regime), and end-use plus end-user (does any catch-all under EAR Part 744 or its EU equivalent apply). The output of the workflow is a per-transaction decision: license required, license not required, license-exception claimed (with the specific exception cited and the conditions documented), or transaction refused. The defensibility argument hinges on documentation of how the decision was reached, not just the decision itself; classifications drift as products change, and a classification correct two years ago may be incorrect for the current build. Operators commonly under-budget the dual-use software question, where modest cryptographic or information-security functionality is enough to put an otherwise routine SaaS export inside the EAR perimeter. The license-exception path (EAR ENC for mass-market encryption is the canonical example) reduces the operational cost but raises the documentation burden, since the exception only holds if the conditions were met at export time.

Applicability

Applies when: markets include US.

How predicates are evaluated

Required by (3 regulations)

• US EAR

  15 CFR §736.2 + Country Chart at 15 CFR Part 738 Supp. No. 1 — pair ECCN reasons-for-control with destination-specific licensing requirements; License Exceptions ENC, TSU, APP for software platforms; SNAP-R submission for individual licenses.

  15 CFR §736.2 + Country Chart at 15 CFR Part 738 Supp. No. 1

• EU Dual-Use

  Regulation (EU) 2021/821, Articles 7-12 — Individual Export Authorisations from Member State competent authorities plus EU GEAs (001-008); BAFA ELAN-K2 / DGT / CDIU per Member State.

  Regulation (EU) 2021/821, Articles 7-12

• UK Export Control

  Export Control Order 2008 Articles 3-26 — SIEL/OIEL/OGEL framework; SPIRE submission; OGEL Cryptographic Development the most-used by software platforms.

  Export Control Order 2008 Articles 3-26

Fulfilled by (2)

• descartes · partial · high effort · $$$
• In-house build · high effort

ClearLaunch does not accept payment from vendors. Methodology.

Evidence formats

• license-determination matrix
• license file
• license-exception use log