A trading company receives a denial order from BIS. Within days, counsel is engaged and a retainer is needed. The problem: assets connected to the matter may be caught by export-control restrictions, and the legal team cannot simply draw on a blocked account without authority. This scenario plays out more often than practitioners expect – and the steps a business takes in the first week frequently determine whether representation can be funded at all.
Funding legal representation from restricted or blocked assets under the Export Administration Regulations ("EAR", administered by the Bureau of Industry and Security, "BIS") requires a specific licence or a qualifying exception authorised under the applicable regime. The process is distinct from OFAC's economic-sanctions licensing track, involves different procedural rules, and can catch both US and non-US persons where US-origin items or US-person involvement triggers the rules. As of June 2026, the EAR legal-fees licensing route remains an active tool – but one that requires careful preparation before any funds move.
This guide walks through the process in sequence: what triggers the need for a licence, how the application is built and submitted, where cross-border complications arise, and what risk flags demand early attention.
Step 1 – Identify whether a BIS / EAR restriction actually applies to the funds
The first question is not how to obtain a licence – it is whether you need one at all. BIS restrictions under the EAR apply to exports, re-exports, and in-country transfers of items on the Commerce Control List ("CCL"), and to transactions involving persons on the Entity List (entities subject to a licence requirement for virtually all EAR items), the Denied Persons List, the Unverified List, and equivalent BIS restricted-party lists. A legal-fees licensing question arises when a client or their assets are caught by one of these controls – or when the transaction that funds the legal engagement itself involves a restricted item or a restricted person.
In our experience, the most common trigger is a denial order or an Entity List designation affecting the client entity, where the retainer payment route touches a US financial institution, a US person, or a US-origin item. The threshold question is whether the funds transfer, in its own right, constitutes an export or re-export of an EAR-controlled item – or whether it falls outside the EAR entirely. Fees denominated in currency, paid from a non-EAR asset, to counsel outside a restricted channel, may not require a BIS licence at all. Get that classification wrong in either direction and the consequences are serious: unnecessary delay if you seek a licence that is not needed, or an unlicensed prohibited transaction if you proceed without one that is.
This is not a question to answer on a reading of the statute alone. The interplay between the EAR's scope rules, the relevant CCL entries, and the specific payment mechanic requires a structured review. It is also where the OFAC and BIS tracks first diverge: OFAC's economic-sanctions rules rest on different statutory authority (principally IEEPA) and reach a different class of transactions. A client may simultaneously face OFAC and BIS restrictions – and the two regimes do not share a licence.
Step 2 – Determine the correct BIS licensing mechanism
Once you have confirmed that a BIS / EAR authority is genuinely required, the next step is to identify which licensing mechanism applies. BIS operates two main routes: a licence exception (a standing category of transactions that the EAR permits without a case-by-case application) and a specific licence (a case-by-case authorisation granted by BIS for a defined transaction or class of transactions). A third route – the advisory-opinion process – can provide non-binding guidance on whether a proposed transaction requires a licence, though it does not itself authorise the transaction.
For legal-fees situations, the critical question is whether a licence exception covers the payment or whether a specific licence must be applied for. Licence exceptions under the EAR are written to the item and end-use, not to the purpose of the funds transfer. An exception that covers a particular category of technology or software will not automatically carve out a legal-fees payment. Where a qualifying exception exists, it must be documented precisely at the time of the transaction – after-the-fact reliance is not available.
Where no exception fits, the specific-licence route applies. BIS processes specific-licence applications through its SNAP-R electronic system. The application requires identification of the items (or, in a legal-fees context, the relevant transaction), the parties, the end-use, and a detailed statement of the purpose. Applications are reviewed internally at BIS, and may be referred to other agencies – including the Departments of State, Defense, or Energy – depending on the classification and sensitivity of the items involved. Processing times are not guaranteed and vary depending on the complexity and the interagency referral posture.
The position above covers the standard case. Your facts – the counterparty, the funds source, the payment route, and the specific BIS list entry – change the analysis materially. If you are at this stage and have not yet mapped the transaction fully, now is the time.
Related practices
- Frozen account management under BIS / EAR – practical steps for managing restricted accounts pending authorisation
- Legal-fees licences under the Canadian regime – a parallel guide on the GAC licensing track for comparison
Step 3 – Build the licence application: evidence, structure, and common gaps
A well-structured specific-licence application is the difference between a prompt grant and a prolonged interagency referral. BIS evaluates applications against the licensing policies set out in the EAR – which differ by the type of item, the destination, and the end-use – and against internal guidance on consistent treatment. For legal-fees licences specifically, the application must make the purpose transparent and must avoid any ambiguity that could read as a request to authorise a broader transfer than is actually needed.
The core components of the application are: a precise identification of the items or, in a monetary-transfer context, the transaction being authorised; a description of the parties (applicant, recipient, intermediary financial institutions if any); a clear statement of the end-use (payment of legal fees in connection with a specifically identified proceeding or engagement); and supporting documentation demonstrating the scope of the legal engagement, the fee arrangement, and the basis for the representation. BIS may request additional information or clarification; a failure to respond promptly extends the timeline.
In our cross-border practice, the most common gap in first-draft applications is an underspecified description of the transaction mechanics. Applicants describe the purpose clearly but fail to trace the payment route – which financial institution, in which jurisdiction, with what correspondent arrangement – in sufficient detail for BIS to evaluate the full transaction. Where a non-US financial institution is in the payment chain, additional information on that institution's standing against BIS and OFAC restricted-party lists is advisable.
A second common gap is incomplete identification of the underlying legal proceeding. BIS is more likely to grant a narrowly scoped licence – for defined proceedings, defined counsel, and a defined fee cap or period – than an open-ended authorisation. Counsel preparing the application should structure the request accordingly, even if that means anticipating the need for a later amendment.
Do you have the full payment chain documented before submitting? If a US correspondent bank is in the route, that institution's own compliance requirements will also apply – and their approval is not a substitute for the BIS licence.
Step 4 – Manage the interagency review and timeline
BIS specific-licence applications do not always stay within BIS. The EAR's licensing policy framework provides for referral to other US government agencies when the item, end-use, or party raises national-security, foreign-policy, or other concerns within those agencies' statutory remits. In a legal-fees matter, referral is less common than for hardware or technology export applications – but it is not impossible, particularly where the underlying enforcement matter involves sensitive goods or dual-use technology.
During the review period, no payment can be made under the requested authorisation. This creates a practical problem for counsel who need the retainer before investing significant resource in the representation. Practitioners regularly advise clients at this stage to consider whether: (a) a parallel source of funds – one not caught by the BIS restriction – can sustain the engagement during the review period; (b) a narrowed or emergency application can be prioritised; or (c) the advisory-opinion process can provide interim clarity, even though it is non-binding.
We have acted for businesses in exactly this position – where the gap between filing and grant was extended by an interagency referral and the client needed to manage counsel's expectations and workload in parallel. The lesson is consistent: build as much of the substantive legal work as possible in the period before the application is submitted, and file the application early – before the enforcement timeline compresses the options.
If a transaction has already been flagged or a filing has been refused, an early review can preserve options that narrow with time. For a confidential review of your position, contact Calder & Vance at info@caldervance.com.
Step 5 – Cross-border complications: what changes when non-US parties are involved?
The EAR's extraterritorial reach means that a legal-fees licensing question under BIS / EAR does not stay neatly within US borders. Three scenarios are particularly common in cross-border practice and each requires a different approach.
First, where the client is a non-US company subject to a BIS denial order or Entity List designation, the restrictions apply to any US person – including US-licensed counsel – who provides services in connection with a restricted transaction. US counsel therefore faces their own BIS exposure, not just the client's. The legal-fees licence must address both the client's need to pay and the counsel's ability to receive payment without violating the rules.
Second, where the client's funds are held in a non-US jurisdiction, the payment route may itself constitute a re-export or in-country transfer subject to EAR jurisdiction. This depends on whether the funds originate in or pass through an EAR-controlled item or a transaction that BIS would characterise as subject to its rules. Practitioners advising on multi-currency or multi-jurisdiction retainer structures need to map each step in the payment against the applicable EAR jurisdictional tests before any funds move.
Third – and critically – the BIS / EAR licensing track operates entirely separately from OFAC's economic-sanctions licensing regime. A client facing both an OFAC designation and a BIS restriction (or denial order) must pursue licences from both agencies independently. The OFAC track follows different statutory authority, different application procedures, and may have different licensing policies for legal-fees payments. An OFAC licence does not authorise a transaction that also requires a BIS licence, and vice versa. In our cross-border practice, we regularly advise clients who have obtained one licence and assumed the other was covered – a mistake that can trigger a separate violation.
The UK and EU regimes add further complexity for multinationals. OFSI (the UK's Office of Financial Sanctions Implementation) operates its own licensing regime under the applicable thematic sanctions regulations. The EU licensing regime operates through member-state competent authorities. Neither automatically mirrors the BIS / EAR position. Where a client faces restrictions under multiple regimes, the strictest prohibition governs each leg of the transaction, and a parallel licensing strategy is required.
Step 6 – Record-keeping, compliance, and post-grant obligations
Receiving a BIS specific licence is not the end of the compliance obligation – it is the start of a defined post-grant regime. The EAR imposes record-keeping requirements on licence holders, covering the application, the authorisation, all transactions conducted under the licence, and related correspondence. These records must be maintained for a period set by the applicable regime; verify the current requirement before relying on any stated figure, as it is subject to change.
Beyond the retention obligation, the licence will typically be written with conditions: a defined scope of transactions, a named recipient of funds, a stated legal proceeding, and sometimes a cap on the total amount or a time limit. Transactions outside the scope of the licence are not authorised by it. If the legal engagement expands – if new proceedings are added, if additional counsel are engaged, or if the fee arrangement changes materially – an amendment application or a new licence application may be required before funds are moved under the revised arrangement.
Compliance counsel within the client entity should maintain a licence register that tracks the scope conditions, the transactions completed under each licence, and the dates of the authorised activity. Any apparent variation from the licence terms should be assessed before the next payment is made, not after. BIS has enforcement authority and can consider the adequacy of a licensee's post-grant compliance record in subsequent licensing decisions. A voluntary self-disclosure ("VSD", a proactive report to the regulator of a potential violation made before enforcement action) is available where a post-grant breach is identified – but acting on it promptly is essential, as delay can affect how BIS treats the disclosure.
Myth, misread, and the question practitioners get wrong most often
A persistent myth in cross-border practice is that a legal-fees payment is inherently protected by due-process principles – that regulators will always find a route to allow an accused party to fund its own defence, and that no serious licensing obstacle will stand between a business and its counsel. This is wrong in the BIS / EAR context.
The EAR is an export-control statute, not an economic-sanctions statute. Its licensing regime is built around items and transactions, not around the purpose of a payment. There is no general-purpose carve-out for legal fees equivalent to those that appear in some OFAC general licences. The legal-fees licensing route under BIS / EAR is available, but it requires a specific licence in most cases where a genuine restriction applies – and that licence takes time to obtain, has conditions attached, and can be refused or narrowed.
A second misread is that US counsel's professional-responsibility obligations to accept or continue a representation override BIS restrictions. They do not. US-licensed counsel who transact in violation of the EAR face their own potential liability, separate from the client's. The correct approach is for counsel and client to address the licensing question jointly, at the outset of the engagement, before any funds move.
A third misread – particularly common in cross-border matters – is that obtaining a licence from one regime clears the path under all others. It does not. The BIS licence covers BIS-regulated obligations. OFAC, OFSI, EU competent authorities, and other regulators each have their own licensing tracks. We regularly advise on the sequencing of parallel applications to ensure that authorisation is complete across all applicable regimes before a payment is processed.