1. Define the Transaction before Drafting the Agreement
A workable agreement starts with a practical question: what will actually cross the border? The answer determines which rights must be granted, which controls must remain in place, and which regulatory reviews may be required.
Identify the Technology and Every Form of Access
The parties should list the patents, software, source code, technical data, processes, and know-how included in the deal. A schedule should also identify excluded and third-party materials. This foundation makes the broader technology transfer terms easier to administer and reduces disputes over permitted use.
Separate Assignments, Licenses, and Services
An assignment transfers ownership, while a license grants defined permission to use an asset. Joint development, implementation, training, and support create different duties and should not be hidden inside a broad license grant. Separate provisions can address acceptance, service levels, access, and ownership of work product.
Map the Countries, Users, and Delivery Methods
Compliance analysis depends on where the technology will go, who can access it, and how it will be delivered. The map should cover affiliates, subcontractors, cloud locations, remote engineers, and sublicensees. A lawful initial transfer does not automatically authorize every reexport or downstream use.
2. Complete Regulatory Screening before Granting Access
Federal controls can apply even when New York law governs the contract. The timing matters: data-room access, source-code review, and technical demonstrations may themselves release controlled information.
Determine Whether Cfius Review Is Relevant
A stand-alone commercial license is not automatically subject to review by the Committee on Foreign Investment in the United States. CFIUS analysis becomes more important when the arrangement accompanies foreign equity, control, governance rights, an acquisition, or specified access to a qualifying U.S. .usiness. Certain covered investments involving critical technology may require a declaration, so the parties should assess the structure before closing.
Classify the Technology under the Ear or Itar
Under the Export Administration Regulations, license requirements can depend on classification, destination, end user, and end use. Releasing controlled technology or source code to a foreign person in the United States can be a deemed export. Defense articles, defense services, or technical data on the U.S. Munitions List may require separate authorization under the International Traffic in Arms Regulations. An export controls review should precede access.
Screen Sanctions, Ownership, and Payment Routes
OFAC screening should cover the contracting party, beneficial owners, banks, intermediaries, and relevant jurisdictions. An entity owned 50 percent or more in the aggregate by blocked persons is considered blocked even if it is not separately listed. The agreement should permit suspension or termination when performance would violate sanctions, but this clause does not replace current screening.
| Regime | Primary Trigger | Contract and Closing Response |
|---|---|---|
| CFIUS | Covered foreign investment involving control, information, governance, or decision-making rights | Assess filing risk, conditions, and access limits before closing |
| EAR | Export, reexport, transfer, or release of controlled technology | Classify the technology and restrict destinations, users, and uses |
| ITAR | Defense articles, defense services, or controlled technical data | Confirm authorization before a foreign person receives access |
| OFAC | Blocked parties, comprehensively sanctioned jurisdictions, or prohibited dealings | Screen ownership and payment chains throughout the relationship |
CFIUS
- Primary TriggerCovered foreign investment involving control, information, governance, or decision-making rights
- Contract and Closing ResponseAssess filing risk, conditions, and access limits before closing
EAR
- Primary TriggerExport, reexport, transfer, or release of controlled technology
- Contract and Closing ResponseClassify the technology and restrict destinations, users, and uses
ITAR
- Primary TriggerDefense articles, defense services, or controlled technical data
- Contract and Closing ResponseConfirm authorization before a foreign person receives access
OFAC
- Primary TriggerBlocked parties, comprehensively sanctioned jurisdictions, or prohibited dealings
- Contract and Closing ResponseScreen ownership and payment chains throughout the relationship
3. Draft Rights That Match the Commercial Plan
The license grant should reflect how the business expects to use, improve, and monetize the technology. Broad language may create unintended rights, while language that is too narrow can prevent an otherwise sensible product launch or distribution plan.
Set Ownership, License Scope, and Sublicensing Rules
The agreement should state whether rights are exclusive or nonexclusive and define the territory, field of use, term, users, products, and channels. It should address affiliates, contractors, change of control, and sublicensing. Well-structured technology licensing and IP transactions also distinguish ownership from possession of copies, equipment, or documentation.
Allocate Improvements and Derivative Works
Disputes often arise after the recipient adapts code, improves a process, or combines technology with its own platform. The agreement should define improvements, derivative works, feedback, and jointly developed results. It should allocate ownership, license-back rights, filing authority, costs, and disclosure duties.
Protect Confidential Information and Trade Secrets
Confidentiality terms should match the information and the way teams will work. Practical trade secret protection may include access controls, purpose limits, security standards, incident notice, return or destruction duties, and tailored audit rights. These safeguards help show that the owner treated the information as secret.
4. Plan Payments, Liability, and Cross-Border Enforcement
A technology agreement must continue to work after the launch, when payments, performance questions, and legal changes become real. Commercial terms should therefore connect pricing, compliance, remedies, and exit rights instead of treating them as separate boilerplate sections.
Align Royalties, Taxes, and Payment Mechanics
Royalty terms should define the revenue base, deductions, exchange rates, reports, records, and audit process. Cross-border payments may raise withholding, treaty, and transfer-pricing issues. Related-party transactions should follow applicable arm's-length rules, with tax professionals addressing valuation, benchmarking, documentation, gross-up terms, and local filings.
Allocate Warranties, Indemnities, and Liability
Representations concerning authority, ownership, noninfringement, performance, compliance, and security should fit the diligence record. Indemnities should identify covered claims, defense control, notice, settlement authority, and exclusions. Liability limits should address whether confidentiality breaches, IP misuse, sanctions violations, fraud, or willful misconduct receive different treatment.
Choose Governing Law and Build an Update Process
New York General Obligations Law Section 5-1401 allows parties to select New York law in qualifying transactions of at least $250,000, subject to statutory exceptions. Section 5-1402 separately permits certain actions against nonresidents and foreign entities when the transaction involves at least $1 million, selects New York law, and includes submission to New York jurisdiction. The agreement should still address foreign enforceability, new-user screening, classification updates, legal changes, and secure termination.
5. Frequently Asked Questions
Can sharing source code with a foreign engineer count as an export?
Yes. The EAR may treat the release of controlled source code or technology to a foreign person as an export to the person's relevant country or countries. Classification, access, and authorization should be reviewed before disclosure.
Does every international technology license require a CFIUS filing?
No. A conventional license alone does not automatically require a CFIUS filing. Review may become relevant when it forms part of a covered foreign investment, acquisition, control transaction, or specified access arrangement.
Who owns improvements created by a foreign licensee?
Ownership depends on the agreement, the nature of the work, and applicable law. The parties should not rely on a general ownership clause. They should expressly allocate improvements, derivative works, feedback, joint development, filing rights, and license-back rights.
Can parties choose New York law when neither party is based in New York?
Potentially. New York permits a choice-of-law clause in qualifying transactions that meet the statutory threshold, even without another reasonable relationship to the state. Governing law and forum selection remain distinct issues.
6. Structure the Transfer before Technology Changes Hands
SJKP's attorneys help businesses define technology rights, evaluate cross-border restrictions, negotiate commercial protections, and prepare workable compliance procedures. Contact SJKP before granting technical access or signing the agreement to assess the transaction structure, regulatory triggers, ownership terms, payment mechanics, and enforcement strategy.
14 Aug, 2026
