A trade-finance desk at an international bank receives a documentary credit request. The underlying goods are dual-use items. The beneficiary is a company in a third market. The shipping route passes through a transhipment hub known for diversion risk. Nothing on the face of the transaction triggers an obvious screen hit – but the Export Administration Regulations (the EAR, administered by the Bureau of Industry and Security, or BIS) may prohibit the financing just as directly as any OFAC designation. Does your team know where to look?
Trade-finance sanctions controls under BIS / EAR require banks, freight forwarders, and exporters to screen not just named parties but the goods, the end-use, and the end-user against the Commerce Control List and the Entity List before a letter of credit, documentary collection, or supply-chain finance facility is confirmed. A single mis-classified item or an unscreened intermediate consignee can expose a firm to a significant civil or criminal penalty – with no de-minimis safe harbour for knowing violations.
This guide walks through the procedure step by step, identifies the pitfalls that recur in our practice, and flags where BIS / EAR diverges from the OFAC financial-sanctions regime and from the UK and EU positions – because for a cross-border trade-finance transaction, two or more regimes will typically apply at once.
Step 1: Understand who BIS / EAR reaches in a trade-finance transaction
BIS / EAR jurisdiction extends to any person – wherever located – who causes the export, re-export, or transfer of a US-origin item, or of a foreign-made item that incorporates US-controlled content above the applicable de-minimis threshold. That reach is extraterritorial. A European bank financing a shipment of US-origin goods between two non-US parties is within scope if it causes or facilitates the export.
In practice, "causing" an export is interpreted broadly. Issuing a letter of credit, confirming a documentary collection, or releasing a payment against shipping documents can each constitute facilitation if the underlying transaction is prohibited. This is the starting point that many trade-finance teams miss: they treat BIS as an exporter's problem, not a bank's problem. It is both.
The Entity List (BIS's list of parties subject to licence requirements) and the Denied Persons List (parties barred from receiving US exports) are the primary party-screening lists. But party screening is only the first gate. The goods classification and the end-use statement must be reviewed alongside it. As of mid-2026, BIS has continued to expand both lists and to issue new Foreign Direct Product Rules that extend EAR reach to certain foreign-made goods – verify the current scope before relying on any prior classification.
Step 2: Classify the goods and map them to the Commerce Control List
Every item subject to the EAR has an Export Control Classification Number (ECCN – a five-character alphanumeric code on the Commerce Control List that defines the item's export-control status and the licences required). Before a trade-finance facility is confirmed, the ECCN determines whether a licence exception applies or whether a licence application to BIS is mandatory.
The classification step is where trade-finance teams are most exposed. Letter-of-credit or documentary-collection review processes often focus on whether the buyer is listed – they do not always ask what the goods are and whether the goods can legally reach the stated destination via the stated route. An item with an ECCN in the 3A, 4A, 5A, 6A, or 7A category – broadly, electronics, computing, telecom, lasers, and military-related items – will carry stricter controls than an item classified EAR99 (the catch-all for items not listed on the CCL). And EAR99 is not a free pass: the General Prohibition on exports to parties on the Entity List applies regardless of classification.
In our experience, the classification task should sit with the exporter or seller, supported by the freight forwarder. The bank's role is to request and verify a credible classification before confirming credit. Where the classification is implausible given the item description – a high-specification microprocessor described as "general machinery", for example – the bank has an independent duty to probe. Accepting a false classification is not a defence.
Step 3: Screen all parties across the full transaction chain
Party screening for BIS / EAR purposes covers more counterparties than OFAC screening alone. The EAR requires a review of the ultimate consignee, the intermediate consignee, the end-user, and – critically – the purchaser where that differs from the consignee. In a typical trade-finance structure, all four may be distinct entities.
The BIS Entity List imposes a licence requirement for transactions with listed parties; the Denied Persons List imposes a near-absolute prohibition. Neither list is identical to the OFAC SDN List (OFAC's list of Specially Designated Nationals and blocked persons) or to the EU or UK consolidated lists. A party may appear on one but not another. Screening systems that run only against OFAC and UN lists will miss Entity List hits. Have you configured your screening platform to pull all three US lists, not just the SDN?
The cross-border dimension matters here. For a trade-finance transaction that also touches EU or UK parties, the EU dual-use rules and OFSI's financial-sanctions regime will run in parallel. Where the two sets of obligations diverge – and they increasingly do – the stricter prohibition governs the transaction. A bank incorporated in the UK cannot rely on the fact that BIS has issued a licence if OFSI's own rules prohibit the underlying payment.
Step 4: Evaluate end-use and end-user red flags before confirming credit
BIS's "know your customer" guidance and the General Prohibition on proceeding with a transaction where there are red flags of a prohibited end-use create an affirmative duty to investigate. This is the step that most clearly distinguishes the BIS / EAR regime from a purely list-based OFAC sanctions screen.
Red flags under the EAR include: a buyer who is reluctant to specify the end-use; a shipment routed through a jurisdiction known for transhipment to restricted destinations; a buyer whose business does not obviously match the goods ordered; payment terms that are inconsistent with normal trade; and requests to omit or alter the ECCN on shipping documents. In a trade-finance context, the documentary-credit or collection process surfaces many of these indicators naturally – but only if the reviewing team is trained to recognise them.
In a recent matter, a logistics business involved in a multi-party supply chain was approached to confirm a freight-finance arrangement for goods described as "industrial components". The declared ECCN was EAR99, but the item specification in the accompanying technical sheet matched a classification with specific end-use controls. We advised the client to pause confirmation, request a revised classification from the exporter with supporting documentation, and run a secondary screen on the intermediate consignee. The hold surfaced a potential match on the Entity List that the initial ECCN-only screen had not flagged. The matter was resolved before credit was confirmed.
Step 5: Apply the correct licence or licence exception before release
Where the goods classification, the destination, and the party screen indicate that a transaction requires a licence, trade-finance parties must obtain that licence – or confirm that a licence exception applies – before releasing funds or documents. Common licence exceptions relevant to trade finance include the EAR licence exception for certain low-value shipments and the exception for items moving between the US and close-allied export regimes. Neither is unlimited and both carry conditions.
Where no exception applies, the exporter must apply to BIS for a specific licence. The bank's role is to hold the transaction until the licence is in hand and to review the licence conditions – in particular, any end-use certificate requirement or post-shipment reporting obligation. Confirming credit before licence confirmation is itself a violation if the underlying export requires one.
The procedure under BIS differs from an OFAC specific-licence application in one significant respect: OFAC licences are transaction-specific and address party-based prohibitions, whereas a BIS export licence addresses the goods and the destination as well as the parties. Both can be in play simultaneously on a single transaction. Both have their own timelines, standards, and conditions. Where both are required, we advise clients to run the applications in parallel rather than sequentially to minimise delay.
The position under two or more regimes must be confirmed: a BIS licence does not relieve an EU or UK entity of its obligations under EU dual-use rules or the UK Export Control Order. If the re-export or onward transfer touches a UK or EU person or territory, additional authorisations may be required.
The position above covers the standard procedural case. Your facts – the goods, the route, the parties, the financing structure, and the timing – change the analysis at every step. If you are assessing a transaction now, contact Calder & Vance at info@caldervance.com for a structured review.
Step 6: Document the decision and maintain records
BIS requires exporters and related parties to maintain records of export transactions and the licensing decisions supporting them. The recordkeeping obligation under the EAR runs for a defined period from the date of export; OFAC's equivalent obligation has a parallel duration. Both exceed standard commercial document-retention periods in some jurisdictions. A trade-finance team that has reviewed and cleared a transaction must be able to reconstruct that decision from the file years later.
The document package for each trade-finance transaction should include: the ECCN classification and its supporting basis; the party-screen results across all lists; the end-use statement or end-user certificate where required; evidence of any licence exception relied upon or the licence itself; and a record of any red-flag review and its resolution. Where the decision involved counsel or a compliance sign-off, that opinion should be retained.
Inadequate recordkeeping is an aggravating factor in BIS enforcement. It removes the evidential base for a voluntary self-disclosure mitigation argument and leaves a firm unable to demonstrate a good-faith compliance posture. In our compliance-programme work, we regularly advise clients to build the documentation step into the credit-confirmation workflow rather than treating it as a post-transaction task.
Common pitfalls and risk flags: where trade-finance controls break down
Party-only screening – running OFAC and UN lists but not the BIS Entity List and Denied Persons List – is the most common structural gap we see in trade-finance compliance programmes. The BIS lists are not subsets of OFAC lists. They must be screened independently and on the same cadence.
A second pitfall is accepting a seller's ECCN at face value without a plausibility check. Banks and forfaiters are not BIS classification agents, but they are expected to query obvious mismatches. A dual-use item described in ways that point to a sensitive ECCN cannot plausibly be classified as EAR99 based on the seller's unverified assertion alone.
A third risk area is the intermediate consignee. Trade-finance documentation often focuses on the buyer and the ultimate destination. The intermediate consignee – a freight forwarder, a consolidator, a bonded warehouse – may itself be listed or may be a known transhipment facilitator. Screening must reach all named parties on the shipping documents, not only the buyer.
Finally, voluntary self-disclosure (VSD – a party-initiated report to BIS or OFAC of a potential violation, typically before the agency is aware of it) is available under both BIS and OFAC enforcement schemes and can reduce penalty exposure. But the decision to disclose is not automatic. A VSD that is incomplete, poorly timed, or that discloses violations without also disclosing the remediation plan can complicate rather than assist the enforcement position. If a potential violation has been identified, take legal advice before deciding whether and how to disclose.
If a transaction has already been flagged, a filing refused, or an enforcement inquiry received, an early review of the position can preserve options that narrow significantly with time. Contact us at info@caldervance.com for a confidential assessment.
How BIS / EAR compares with the UK, EU, and other regimes on trade-finance controls
The BIS / EAR regime is goods-and-destination driven as well as party driven. The EU dual-use rules and the UK Export Control Order share this dual focus but operate with different control lists, different licence categories, and different enforcement postures. For a cross-border trade-finance transaction, the three regimes are typically all in play – and the strictest prohibition governs.
One significant divergence is the extraterritorial reach of US controls through Foreign Direct Product Rules. These extend BIS jurisdiction to certain foreign-made goods produced using US technology or equipment. An EU bank financing a shipment of foreign-made semiconductors may be within EAR reach even if neither the goods nor the parties are US. The EU dual-use regime does not contain an equivalent extraterritorial hook of this kind – though the EU has introduced its own tools in different form.
Under OFSI (the UK Office of Financial Sanctions Implementation), the financial-sanctions prohibition is triggered by the status of the party, not primarily by the goods. The ownership-and-control test under OFSI and under EU Council regulations can catch non-listed entities through their relationship to listed persons. BIS's Entity List mechanism is different: it imposes a licence requirement rather than an asset freeze, and the ownership-attribution rules are not identical to the OFSI and EU ownership and control test (the UK and EU test for whether a non-listed entity is caught through a listed person's ownership or control).
Practitioners advising on BIS matters in a multi-regime context note that the compliance architecture for a trade-finance programme must map each regime's trigger, each regime's party lists, and each regime's goods controls separately – and then identify where the overlaps create cumulative obligations. A checklist built for OFAC compliance alone will not satisfy BIS. A BIS-compliant programme will not automatically satisfy EU or UK requirements. The regimes require separate treatment, even where the transaction is single.
For clients operating across jurisdictions, we regularly advise on building a single integrated compliance workflow that addresses all applicable regimes simultaneously, with clear escalation paths for transactions that require licence or authorisation under more than one system.
Related practices
- Sanctions compliance audit and testing – structured testing of screening logic, programme gaps, and documentation standards across regimes
- Trade-finance sanctions controls – Canada (GAC) – a parallel guide for the Canadian regime and its interaction with US and UK controls
- Cross-border trade-finance sanctions controls – multi-regime analysis for transactions spanning US, UK, EU, and other jurisdictions