Export Controls.
Continuous screening across every transaction.
Leah continuously screens transactions, technology transfers, and personnel changes against US EAR, ITAR, UK ECJU, EU dual-use, and entity lists. Re-export risk surfaced, escalations routed, audit trail ready.
Most enterprises learn about trade violations from regulators, not their own systems.
Re-export risk discovered after the fact
Goods that cleared a primary export move through distributors, integrators, and end users. Re-export and in-country transfer rules apply at every hop, but most enterprises only learn about a violation when a regulator opens a file.
Deemed export rules inconsistently applied
Foreign nationals in US labs, on engineering teams, or in joint ventures trigger deemed export controls. HR, legal, and engineering each hold a piece of the picture, and the controls only fire when somebody happens to remember to check.
Technology transfer agreements not screened
TTAs, licensing deals, and joint development agreements move controlled technology, source code, and know-how across borders. Standard contract review rarely flags the export classification implications until a deal is already signed.
Entity list changes lag operations
OFAC, BIS, EU, UK, and sectoral lists update on no fixed cadence. Sales, procurement, and shipping keep moving while the compliance team manually reconciles new designations against an ever growing customer and vendor base.
Foreign person diligence done as a one-time gate
End user and end use diligence happens at onboarding. Roles change, ownership shifts, and downstream parties enter the chain, but the original screen is never refreshed. The compliance posture decays silently.
Audit prep is manual and reactive
When a regulator or internal auditor asks for the trail, teams spend weeks pulling export licenses, screening logs, and decision rationales out of inboxes and shared drives. The record exists, just not in a defensible form.
Every transaction screened against every list, in real time
Leah connects to ERP, CRM, logistics, and trade systems and screens every shipment, sales order, and procurement transaction against US EAR, ITAR, OFAC, UK ECJU, EU dual-use, and sectoral entity lists. Screening runs continuously, not just at order entry, so re-export and in-country transfer risk is caught before the goods move.
“We were screening at order entry and calling it continuous. Leah showed us how many shipments were moving between two list refreshes. That was the gap we did not know we had.”
Head of Trade Compliance, Industrial Equipment Manufacturer
Five steps to continuous trade compliance
Leah integrates with the systems you already run. No rip and replace. Screening becomes a continuous control rather than a workflow step.
Connect
Leah integrates with your ERP, CRM, HRIS, CLM, logistics, and trade systems. Transactions, agreements, and personnel records flow into a single trade compliance intelligence layer without replacing any of your existing systems.
Screen Transactions
Every shipment, sales order, procurement transaction, and payment is screened against US EAR, ITAR, OFAC, UK, EU, and sectoral lists. License coverage is validated and re-export risk is modeled before goods move.
Monitor Lists
Sanctions and entity list updates are ingested as they publish. The active customer and vendor base is re-screened against every new designation, with ownership and aggregation logic applied.
Route Escalations
Holds and matches are classified by risk type and routed to the right owner with full context. Trade compliance, legal, sanctions counsel, and business owners each see only the work they own.
Maintain Records
Every clear, hold, license decision, and override is captured with rationale and timestamp. EAR and ITAR recordkeeping requirements are satisfied automatically and audit responses resolve from a query.
Got Questions? Get Answers.
Most denied party tools screen at order entry and stop there. Leah treats screening as a continuous control: transactions are re-screened on every list update, ownership and aggregation logic is applied, and re-export and in-country transfer risk is modeled past the first hop. It also unifies transaction screening, technology transfer review, deemed export tracking, and recordkeeping into a single layer rather than four disconnected tools.
US EAR (BIS Entity List, Unverified List, Military End User), ITAR (DDTC), OFAC (SDN, sectoral, regional), EU dual-use (Annex I) and consolidated sanctions, UK ECJU strategic export controls and OFSI sanctions, plus relevant national lists for major trading jurisdictions. Sectoral and emerging-tech designations are tracked as they publish.
No. Leah operates on top of the systems you already run. Transactions, agreements, and personnel records continue to live where they live today. Leah reads from those systems, runs the screening and monitoring layer, and writes back holds, decisions, and audit records. There is no rip and replace.
Foreign nationals on controlled programs are mapped to the access rights they actually have, with deemed export licenses tracked against real exposure. End user, end use, and ownership diligence is refreshed on every role change, ownership shift, and downstream party addition, so the screen does not decay between annual reviews.
Every clear, hold, license decision, override, and approval is captured with timestamp, owner, and rationale at the moment it happens. The record satisfies EAR Part 762 and ITAR recordkeeping requirements out of the box. Regulator and internal auditor requests resolve from a query, with the underlying transactions, screenings, and decisions linked together.
Leah is deployed by aerospace, defense, semiconductor, and industrial customers with strict data security and export control requirements. Customer data is encrypted in transit and at rest. SOC 2 Type II, ISO 27001 aligned, with private instance deployment available for customers that require strict data isolation. Controlled technical data is segregated according to ITAR and EAR handling rules.
