Export Compliance Requirements

Export compliance encompasses the federal regulatory framework governing the shipment of goods, technology, software, and services from the United States to foreign destinations. Administered primarily by the Bureau of Industry and Security (BIS), the Directorate of Defense Trade Controls (DDTC), and the Office of Foreign Assets Control (OFAC), the system imposes licensing, screening, classification, and recordkeeping obligations on exporters across virtually every industry sector. Non-compliance carries civil penalties reaching into the millions of dollars per violation and, in aggravated cases, criminal prosecution. This page covers the definitional scope, structural mechanics, causal drivers, classification logic, and operational steps of the U.S. export compliance framework.


Definition and Scope

Export compliance refers to the set of legal obligations that apply when U.S.-origin goods, technology, software, or services cross into foreign jurisdictions — physically, electronically, or verbally. The scope extends beyond physical shipments. Under the Export Administration Regulations (EAR) administered by BIS (15 C.F.R. Parts 730–774), a "deemed export" occurs when controlled technology is released to a foreign national inside the United States, making the release equivalent to an export to that individual's home country. This dramatically expands the compliance perimeter for universities, research laboratories, and manufacturers employing foreign nationals.

The International Traffic in Arms Regulations (ITAR), codified at 22 C.F.R. Parts 120–130 and administered by DDTC under the Department of State, covers defense articles and defense services enumerated on the United States Munitions List (USML). Any commodity, technical data, or service that falls on the USML requires a State Department license before export or transfer to a foreign person, with narrow exceptions. For more on deemed export obligations specifically, see Deemed Exports Compliance.

OFAC administers sanctions programs — currently numbering over 30 active programs targeting countries, entities, and individuals — that operate independently of commodity classification. A shipment that clears BIS licensing requirements can still be prohibited under an OFAC sanctions program if the end-user or destination country is designated. The intersection of EAR, ITAR, and OFAC obligations defines the full scope of U.S. export compliance.


Core Mechanics or Structure

The U.S. export control system operates through a classification-then-licensing logic:

Step 1 — Jurisdiction Determination. The first question is whether a product or technology is subject to EAR or ITAR. Jurisdiction follows the nature of the item: EAR covers dual-use goods and technology; ITAR covers inherently military or defense-specific items. Some items are EAR99 — not controlled under the Commerce Control List (CCL) — but may still face OFAC restrictions.

Step 2 — Export Control Classification Number (ECCN) Assignment. Under EAR, each controlled item carries an ECCN from the Commerce Control List. The ECCN drives the applicable licensing policy based on reasons for control (e.g., national security "NS", nuclear nonproliferation "NP", missile technology "MT").

Step 3 — License Requirement Analysis. License requirements depend on the interaction of ECCN, destination country, end-user, and end-use. BIS publishes the Country Chart (Supplement No. 1 to Part 738 of the EAR), which maps ECCN reason-for-control columns against destination countries to determine whether a license is required.

Step 4 — License Exception Evaluation. If a license is required, exporters evaluate whether a License Exception applies. Commonly used exceptions include ENC (encryption items), TMP (temporary exports), and TSR (technology and software under restriction). Each exception carries specific eligibility criteria and recordkeeping obligations.

Step 5 — Denied Party Screening. Before any export, shippers must screen against consolidated screening lists, including BIS's Entity List, Denied Persons List, and Unverified List; OFAC's Specially Designated Nationals (SDN) List; and the State Department's Debarred List. For a detailed treatment of this step, see Denied Party Screening.

Step 6 — Documentation and Filing. Shipments above $2,500 in value (or any value requiring a license) must be filed in the Automated Export System (AES) via the Electronic Export Information (EEI) submission, as required under the Foreign Trade Regulations (FTR) at 15 C.F.R. Part 30.


Causal Relationships or Drivers

Export control regimes do not emerge arbitrarily. Four primary drivers shape the structure and intensity of U.S. export controls:

National Security and Foreign Policy Objectives. The EAR explicitly states that its purpose is to protect national security, foreign policy, and the short supply of commodities (15 C.F.R. § 730.1). Geopolitical developments — such as the expanded Entity List additions targeting Chinese semiconductor entities beginning in 2022 — directly alter which transactions require licensing.

Multilateral Control Regimes. U.S. controls are partially harmonized with four multilateral export control arrangements: the Wassenaar Arrangement (conventional arms and dual-use), the Nuclear Suppliers Group, the Australia Group (biological and chemical weapons), and the Missile Technology Control Regime (MTCR). U.S. commitments under these arrangements drive the specific technical parameters in ECCN entries.

Technology Evolution. As dual-use technologies advance — particularly in semiconductors, artificial intelligence, and biotechnology — BIS publishes new rules expanding or modifying ECCN coverage. The 2022 advanced computing rule (87 Fed. Reg. 62186) added performance thresholds for integrated circuits that triggered new license requirements across the semiconductor supply chain.

Enforcement Outcomes. High-profile enforcement actions feed back into compliance program design. BIS's settlement with Seagate Technology in 2023 — resulting in a $300 million civil penalty (BIS Press Release, April 2023) — signaled heightened scrutiny of exports to entities on the Entity List, prompting broader industry review of supply chain controls.


Classification Boundaries

The boundary between EAR and ITAR jurisdiction is the single most consequential classification decision in U.S. export compliance:

The 2013–2016 Export Control Reform (ECR) initiative transferred hundreds of items from the USML to the CCL, creating a new "600 series" of ECCNs for items with military applications that do not warrant ITAR-level control. Misidentifying a 600 series item as EAR99 remains a documented compliance failure mode.


Tradeoffs and Tensions

Speed vs. Diligence. License applications to BIS average approximately 54 days for processing (per BIS Annual Report to Congress), while DDTC license processing has averaged longer in complex cases. Export velocity requirements in commercial contracts create direct pressure to shortcut classification and screening steps.

Global Business vs. Extraterritorial Reach. The EAR's de minimis rule and the foreign direct product rule (FDPR) extend U.S. jurisdiction to foreign-made items that incorporate more than a threshold percentage of U.S.-controlled content or are produced using U.S.-origin technology. The 2020 FDPR expansion targeting Huawei, and the 2022 expansion targeting Russia and Belarus, demonstrated that foreign subsidiaries of U.S. companies face U.S. compliance obligations even for transactions that never touch U.S. soil.

Voluntary Disclosure vs. Exposure. BIS and DDTC both operate voluntary self-disclosure programs. A complete and timely voluntary self-disclosure can reduce penalties substantially, but the disclosure itself creates a record that regulators retain. The decision to disclose requires legal analysis that balances penalty mitigation against disclosure risk. See Voluntary Self-Disclosure Trade for the framework structure.


Common Misconceptions

Misconception 1: "My product has no military application, so ITAR doesn't apply."
ITAR jurisdiction follows USML classification, not the exporter's intent or primary market. A commercial fastener manufactured to a military specification on the USML is ITAR-controlled regardless of where it is sold.

Misconception 2: "EAR99 items can be exported anywhere without restriction."
EAR99 designation eliminates the need for a license in most scenarios but does not override OFAC sanctions, end-user controls, or the antiboycott provisions at 15 C.F.R. Part 760. Shipping EAR99 items to an SDN-designated party is an OFAC violation.

Misconception 3: "Electronic transmissions of information are not exports."
Under both EAR and ITAR, electronic transmission — including email, cloud sharing, and remote access — of controlled technology or technical data to a foreign national constitutes an export. The EAR addresses this at 15 C.F.R. § 734.13.

Misconception 4: "A freight forwarder handles compliance."
Freight forwarders are responsible for their own filings, but the exporter of record retains primary liability for export classification, licensing, and EEI accuracy. BIS enforcement actions name the exporter, not the logistics provider, in the majority of penalty cases.


Checklist or Steps

The following sequence reflects the standard export compliance workflow as structured by BIS and DDTC guidance documents:

  1. Identify the item — product, technology, software, or service — and document its technical specifications.
  2. Determine jurisdiction — assess whether the item is subject to EAR (BIS) or ITAR (DDTC) based on USML and CCL criteria.
  3. Assign ECCN or USML category — conduct classification using published CCL entries or USML category descriptions; retain classification documentation.
  4. Identify the destination, end-user, and end-use — collect supporting documentation including end-user statements where required.
  5. Screen all parties — run the exporter, consignees, end-users, and intermediaries against BIS, OFAC, and State Department consolidated screening lists before transaction approval.
  6. Determine license requirement — apply the Country Chart (EAR) or USML licensing policy (ITAR) to determine if a license or DDTC authorization is required.
  7. Evaluate license exceptions or exemptions — document the applicable exception and confirm all eligibility conditions are met.
  8. Obtain license if required — submit application via SNAP-R (BIS) or D-Trade (DDTC) and retain the authorization number.
  9. File Electronic Export Information — submit EEI in AES via the Automated Commercial Environment (ACE) portal for shipments meeting FTR thresholds.
  10. Retain records — maintain all export records for a minimum of 5 years from the date of export under EAR (15 C.F.R. § 762.6); ITAR requires 5 years from the expiration of the authorization.

Reference Table or Matrix

Regulatory Framework Administering Agency Governing Regulation Controlled Item Scope License Authority Recordkeeping Period
Export Administration Regulations (EAR) Bureau of Industry and Security (BIS), Dept. of Commerce 15 C.F.R. Parts 730–774 Dual-use goods, technology, software (CCL + EAR99) BIS via SNAP-R 5 years from export date
International Traffic in Arms Regulations (ITAR) Directorate of Defense Trade Controls (DDTC), Dept. of State 22 C.F.R. Parts 120–130 Defense articles and services (USML) DDTC via D-Trade 5 years from authorization expiration
OFAC Sanctions Programs Office of Foreign Assets Control, Dept. of Treasury 31 C.F.R. Parts 500–599 All transactions involving designated parties or countries OFAC-specific licenses 5 years from transaction date
Foreign Trade Regulations (FTR) U.S. Census Bureau, Dept. of Commerce 15 C.F.R. Part 30 AES/EEI filing obligations for all U.S. exports N/A (reporting, not licensing) 5 years from shipment date
Antiboycott Regulations BIS (Office of Antiboycott Compliance) 15 C.F.R. Part 760 Compliance with unsanctioned foreign boycotts Reporting obligations apply 5 years

References

📜 6 regulatory citations referenced  ·  🔍 Monitored by ANA Regulatory Watch  ·  View update log

📜 6 regulatory citations referenced  ·  🔍 Monitored by ANA Regulatory Watch  ·  View update log