OFAC vs BIS in the USA (2026): Which License Do You Need, OFAC, EAR (BIS), or Both?

OFAC vs BIS USA is the first fork in the road for any compliance officer, in-house counsel, banker, or exporter staring at a cross-border transaction that touches a sanctioned party or a controlled item. In 2026, with visible interagency coordination and a steady stream of enforcement actions, more deals than ever trip both regimes at once, and getting the wrong license, or only one of two required licenses, is now a material enforcement risk. This guide gives you a clear decision rule, a side-by-side comparison table, step-by-step application checklists, and coordination guidance for when both agencies claim jurisdiction.

It takes a position: do not treat this as an either/or academic exercise, screen for both, and when both apply, file both in parallel.

Executive summary and quick decision flow

The one-sentence rule of thumb: if your problem is who you are dealing with, a designated person, a blocked entity, or a comprehensively sanctioned jurisdiction, start with OFAC; if your problem is what you are moving, a controlled item, technology, software, or technical data, start with BIS. When both are true, both licenses are required, and neither one relieves you of the other.

OFAC (the Treasury Department’s Office of Foreign Assets Control) administers targeted financial sanctions and authorizes otherwise-prohibited dealings with designated persons and jurisdictions. BIS (the Commerce Department’s Bureau of Industry and Security) administers the Export Administration Regulations (EAR), which control exports, reexports, and transfers of dual-use items, technology, and software. The two regimes overlap constantly in 2026 because dual-use goods and technical assistance are frequently destined for parties who are also sanctioned or listed.

Your three possible outcomes are: apply to OFAC (a designated party or sanctioned jurisdiction is the barrier), apply to BIS/EAR (a controlled item, technology, or deemed export is the barrier), or apply to both (a controlled item is going to, or through, a sanctioned party). The rest of this guide shows you how to reach one of those three answers quickly and defensibly, and how to build applications that stand the best chance of approval.

Quick comparison: legal basis, scope, and practical differences

The clearest way to internalize the OFAC vs BIS USA distinction is to see the two regimes side by side. OFAC’s authority flows in large part from the International Emergency Economic Powers Act (IEEPA, 50 U.S.C. § 1701 et seq.), along with other statutes underlying particular sanctions programs, and is implemented in 31 C.F.R. Chapter V. BIS’s authority flows from the Export Control Reform Act of 2018 (ECRA) and is implemented in the EAR at 15 C.F.R. Parts 730–774. The table below maps every dimension a compliance team needs.

Key takeaways for compliance teams

• Person-based vs item-based. An OFAC license is about who; a BIS license is about what.
• No preemption. Satisfying one regime never excuses the other, screen for both on every transaction.
• Different documentation. OFAC wants party identity, routing, and policy arguments; BIS wants ECCN classification, technical specs, and diversion controls.
• Different enforcers, shared criminal exposure. Both regimes carry civil penalties and can produce DOJ criminal referrals for willful conduct.

Decision framework, when to apply to OFAC, BIS (EAR), both, or pursue mitigation

The heart of any OFAC vs BIS USA analysis is a disciplined, repeatable screening sequence. Do not guess and do not assume that clearing one agency clears the other. Work the three steps below in order for every transaction that touches a foreign party, a listed country, or a technical product.

Step 1, Identify the transaction element

Break the transaction into its components and ask what is actually crossing a border or changing hands: a physical item, software, technology or technical data, a service, or a financial flow. A wire payment to a foreign counterparty is a financial-service element that points toward OFAC. A shipment of an encryption product or an item on the Commerce Control List points toward BIS. Many deals contain several elements at once, for example, a piece of controlled hardware (BIS) sold to a buyer connected to a designated person (OFAC). Cataloguing each element prevents tunnel vision on a single regime.

Step 2, Identify the legal trigger (SDN list vs CCL / Entity List)

Once you know the elements, identify what actually prohibits the activity. For OFAC, the trigger is a sanctions nexus: a party on the Specially Designated Nationals (SDN) List or a program-specific restriction, or a comprehensively sanctioned jurisdiction. For BIS, the trigger is a control classification: an item captured by an Export Control Classification Number (ECCN) on the Commerce Control List, or a party on the BIS Entity List, which imposes license requirements on exports and reexports to the listed party. Note that the Entity List is a BIS instrument even though it, like the SDN List, is party-based, this is exactly where the two regimes blur.

Screen against both OFAC’s lists and BIS’s lists; a hit on either changes your filing obligations.

Step 3, Apply the jurisdictional tests

Confirm that U. S. jurisdiction attaches before assuming a license is even required. OFAC generally reaches U. S. persons, transactions within the United States, and dealings that use the U. S. financial system, and it blocks property of designated parties that is in the United States or in the possession or control of a U. S. person. The EAR reaches items “subject to the EAR,” including U. S. -origin items wherever they travel, certain U. S. persons’ activities, reexports, and certain foreign-produced items containing controlled U. S. -origin content or made with controlled U. S. technology; it also captures “deemed exports”, the release of controlled technology or source code to a foreign national inside the United States.

Run each element against both jurisdictional frameworks. If jurisdiction attaches and a listing or control applies with no available exception, you need a license, and if both frameworks bite, you need two.

How OFAC licensing works, what they ask and how decisions are made

Understanding the OFAC vs BIS USA choice requires knowing how each agency actually processes applications. OFAC’s licensing regime is discretionary and policy-driven, run through its licensing pages and program-specific guidance.

Types of OFAC licenses (general vs specific)

OFAC uses two instruments. A general license is a programmatic authorization published in the regulations that permits a defined category of transactions without an individual application, for example, certain humanitarian, telecommunications, or wind-down activities. A specific license is a case-by-case written authorization you must apply for when no general license covers your facts. Always check for an applicable general license first; if one exists and you fit its terms, you may proceed without filing, though careful recordkeeping remains essential.

Decision standard and typical timeline

OFAC evaluates specific license applications against the foreign policy and national security objectives of the relevant sanctions program, weighing humanitarian considerations and U.S. government interests. Because the standard is discretionary rather than mechanical, framing matters. Processing time varies widely: straightforward matters may resolve in weeks, while sensitive or interagency-referred matters can take many months. Build this uncertainty into your commercial timeline and consider interim measures while you wait.

Common approval arguments and red flags

Applications succeed when they align with the program’s policy goals and present a complete, credible record. Persuasive themes include humanitarian purpose, alignment with U.S. foreign policy objectives, orderly wind-down of pre-existing obligations, and narrowly drawn carve-outs with concrete safeguards. Red flags that undermine an application include vague party identification, unexplained payment routing, indications of possible diversion, and any suggestion the transaction benefits a blocked party beyond the scope requested. Anticipate the reviewer’s concerns and address them proactively with supporting documentation.

How BIS (EAR) licensing works, what they ask and how decisions are made

On the other side of the OFAC vs BIS USA divide, BIS runs a more technical, classification-driven process governed by the EAR. Its licensing and policy pages guide applicants through classification, exceptions, and formal applications.

EAR license types and exceptions

Before filing a full application, determine whether a License Exception authorizes your transaction. The EAR contains numerous exceptions, for example, exceptions covering certain repair and replacement parts, temporary exports, and certain government or other end users, that permit exports without an individual license when specific conditions are met. If no exception applies, you file a specific BIS export license application. The type of application and the level of scrutiny depend on the item’s ECCN, the destination, the end use, and the end user.

Decision standard and timeline

BIS decisions turn on a technical evaluation: the ECCN’s reasons for control, the destination country, and the bona fides of the end use and end user, with national security and foreign policy considerations layered on for sensitive items. Many applications are referred to other agencies, commonly State, Defense, and Energy, for interagency review, which extends timelines. As with OFAC, routine matters can clear in weeks while complex or referred matters run for months. Accurate, complete filings move faster than incomplete ones that trigger follow-up requests.

Commodity classification (ECCN) and technical data tips

Correct ECCN classification is the single most important step in a BIS filing. Misclassification either produces an unnecessary license burden or, far worse, an unlicensed controlled export. Assemble accurate technical specifications, datasheets, and performance parameters, and map them precisely to the Commerce Control List. Remember that technical data and software are controlled alongside hardware, and that releasing controlled technology to a foreign national, including an employee inside the United States, can be a deemed export that may itself require a license. Document your classification reasoning so it can withstand later scrutiny.

OFAC vs BIS USA overlap: priority and coordination when both regimes apply

The hardest OFAC vs BIS USA scenarios are the ones where both agencies claim jurisdiction, and in 2026 these are common. Picture dual-use technology or technical assistance destined for a party that appears on both the SDN List and the Entity List, or a controlled item sold into a comprehensively sanctioned jurisdiction. Here the governing principle is unambiguous: there is no preemption. An OFAC authorization does not cure an EAR violation, and a BIS license does not cure a sanctions violation. You must satisfy both regimes, and failing either exposes you to enforcement even if you were fully licensed under the other.

The practical response is to run both tracks in parallel rather than sequentially. Do not wait for OFAC to decide before approaching BIS, or you will double your timeline. Instead, prepare both applications together so your factual record and legal arguments are consistent. National security and public interest points that support your OFAC filing often reinforce your BIS end-use case, and vice versa, coordinate them so the two agencies see a coherent story rather than two disconnected narratives.

Practical coordination checklist for simultaneous filings

• Screen against all lists. Confirm the party’s status on OFAC’s SDN List and the BIS Entity List before deciding which filings are needed.
• Classify early. Complete the ECCN classification at the outset so the BIS track can begin immediately.
• Engage OFAC early. If a designated party is involved, open the OFAC track in parallel and document humanitarian or exemption arguments.
• Cross-reference the record. Use consistent party identities, transaction descriptions, and end-use statements across both applications.
• Align the arguments. Coordinate national security and public interest points so both agencies receive a unified rationale.

How to prepare a strong OFAC or BIS license application, documentation checklist and sample arguments

Whichever side of the OFAC vs BIS USA line your transaction falls on, approval turns on a complete, credible, agency-tailored record. The two agencies want different things, so build two distinct evidentiary packages.

OFAC-specific documentation checklist

• Full transaction details, including dates, amounts, and the commercial purpose.
• Complete identity of every party, with beneficial ownership where relevant.
• Remittance and payment routing, including intermediary banks.
• A clear legal justification anchored to the applicable sanctions program’s policy objectives.
• Risk-mitigation measures and any humanitarian or humanitarian-excepted use.

BIS/EAR documentation checklist

• The correct ECCN with supporting classification reasoning.
• Technical specifications, datasheets, and performance parameters.
• End-use and end-user statements from the ultimate consignee.
• Shipper and freight-forwarder details for the full logistics chain.
• Diversion controls, screening procedures, and post-shipment monitoring commitments.

Sample persuasive arguments

For OFAC, the strongest themes are humanitarian purpose, alignment with U.S. government-supported or U.S. foreign policy objectives, orderly wind-down of pre-existing commitments, and a demonstrated record of compliance. For BIS, the strongest themes are a low-risk ECCN, minimal or tightly bounded technical assistance, robust end-use controls, and a mature export-compliance program with documented denial screening. In both cases, specificity beats generality: concrete safeguards and verifiable facts persuade reviewers far more than boilerplate assurances. Have counsel review any sample language before submission.

Timelines, costs, and enforcement risk comparison

Both regimes process routine matters in weeks and complex or interagency-referred matters in months, so plan for delay and consider interim measures, contractual pauses, escrow, or phased performance, while an application is pending. The largest costs are often non-monetary: missed delivery windows, breached contracts, and reputational exposure. On the enforcement side, OFAC’s civil penalties can be substantial and are adjusted periodically under applicable law, and willful violations can draw DOJ criminal referral; BIS can impose civil fines and denial orders and pursue criminal enforcement for willful export violations. Where you discover a potential violation, weigh voluntary self-disclosure against the risks of non-disclosure with counsel, well-executed disclosures and remediation frequently reduce exposure, but they must be handled carefully and factually.

Practical templates and next steps

Standardize your OFAC vs BIS USA workflow so every transaction is screened the same way. Maintain a written decision tree that walks through transaction elements, legal triggers, and jurisdictional tests; keep an OFAC application checklist and a BIS/EAR application checklist; and retain sample argument language, cleared by counsel, that your team can adapt. Documenting the process is itself a compliance asset, it demonstrates a good-faith, systematic program if your decisions are ever reviewed.

When to consult counsel, red flags checklist

• Any hit against the SDN List, the Entity List, or a comprehensively sanctioned jurisdiction.
• A controlled item or technology destined for, or transiting through, a sanctioned party.
• Uncertain or contested ECCN classification.
• Signs of possible diversion, opaque ownership, or unusual payment routing.
• A potential past violation that may warrant voluntary self-disclosure.

Case examples and enforcement vignettes

OFAC-only scenario. A U.S. company plans a wire payment to settle a legacy obligation with a counterparty later added to the SDN List. No controlled item is involved, so BIS does not bite, but the payment is generally prohibited or blocked absent OFAC authorization. The company files for a specific license framed as an orderly wind-down of a pre-existing contract, supported by full routing detail and party identification, and seeks authorization for the limited settlement. Lesson: person-based barriers with no item component are pure OFAC matters, and wind-down framing is often decisive.

BIS-only scenario. A manufacturer exports controlled technical data to an overseas engineering affiliate in a non-sanctioned country. No designated party is involved, so OFAC does not bite, but the ECCN requires a license to that destination. The manufacturer classifies the data, secures an end-use statement, documents diversion controls, and obtains a BIS license. Lesson: item- and technology-based barriers, including deemed exports, are BIS matters and rise or fall on classification quality.

Overlap scenario. A dual-use component is sold to a buyer on both the SDN List and the Entity List. Both regimes apply. The exporter files parallel OFAC and BIS applications with a consistent factual record and coordinated national security arguments. Lesson: when both regimes bite, parallel filings with a unified narrative are the correct approach, and satisfying only one would still be a violation.

How Global Law Experts can help

Getting the OFAC vs BIS USA decision right, and executing coordinated filings when both apply, is where experienced counsel adds the most value. Explore the International Trade, USA practice area page or find an International Trade lawyer in the USA to arrange a case review before you file.

Sources

1. U.S. Department of the Treasury, OFAC: Sanctions Programs & Country Information
2. U.S. Department of the Treasury, OFAC: Licensing
3. Electronic Code of Federal Regulations, 31 C.F.R. Chapter V (OFAC regulations)
4. U.S. Department of Commerce, Bureau of Industry and Security (BIS)
5. Electronic Code of Federal Regulations, 15 C.F.R. Parts 730–774 (EAR)
6. Legal Information Institute (Cornell), IEEPA (50 U.S.C. § 1701 et seq.)
7. U.S. Department of Commerce, Entity List (BIS)
8. OFAC, Civil Penalties and Enforcement Information
9. BIS, Enforcement
10. Export Control Reform Act of 2018 (ECRA), enacted as part of Pub. L. 115-232, Congress.gov