IP Protection Through EOR: How to Secure Your Intellectual Property

Your Code Belongs to a Company You Don’t Control. Unless You Fix the Contracts.

Here’s the default EOR IP chain: your engineer in Berlin writes code. That code belongs to their employer — the EOR’s German GmbH. That GmbH is supposed to assign the IP to your company. Two hops. Two contracts. Two opportunities for the chain to break.

Most of the time, this works fine. The EOR’s employment contract includes an IP assignment clause. The service agreement between you and the EOR includes another. Code gets written, IP flows through the chain, nobody thinks about it until a funding round or acquisition.

The problem: “most of the time” isn’t good enough when your entire product was built by engineers employed through EOR entities. If an acquirer’s lawyers find a gap in the IP chain, the deal slows down, the valuation drops, or the acquisition falls apart. I’ve seen this happen over a single missing clause in an Indian employment contract.

The Two-Hop IP Chain, Explained

Hop 1: Employee → EOR Entity. The employment contract between your worker and the EOR’s local entity must include a clause assigning all work-related intellectual property to the EOR entity. This covers code, inventions, designs, documentation, and any other creative output produced during the course of employment.

Hop 2: EOR Entity → Your Company. The service agreement between you and the EOR provider must include a clause assigning (not licensing) all IP from the EOR entity to your company. This is the handoff that gives you ownership.

Critical distinction: assignment vs. license. An assignment transfers ownership. A license grants permission to use. Some EOR templates default to licensing — “EOR grants Client a perpetual, worldwide license to use work product created by employees.” That’s not ownership. If you need to enforce IP rights, sue for infringement, or prove ownership during M&A, a license is insufficient. Insist on assignment language.

The correct clause structure:

1. Employee assigns all IP to EOR entity (in the employment contract)
2. EOR entity assigns all IP to your company (in the service agreement)
3. Both clauses should include present-tense assignment (“hereby assigns”) not future promises (“agrees to assign”)
4. Both should cover all forms of IP: copyright, patents, trade secrets, designs, trademarks created during employment

Country-Specific IP Law That Overrides Your Contract

Default IP assignment clauses work in most common-law jurisdictions (US, UK, Singapore, Australia). Civil law countries and countries with specific employee IP legislation create complications.

Germany: The Employee Inventions Act (Arbeitnehmererfindungsgesetz)

Germany’s Arbeitnehmererfindungsgesetz is the most significant IP law override for EOR employment. Under this law:

• Employees must report inventions to their employer in writing (Erfindungsmeldung)
• The employer has 4 months to claim the invention (unbeschränkte Inanspruchnahme)
• If the employer doesn’t claim within 4 months, the rights revert to the employee
• The employee is entitled to “reasonable compensation” (angemessene Vergütung) for claimed inventions, calculated based on the invention’s commercial value

This applies to the EOR entity, not to your company. If your engineer in Germany invents a patentable algorithm, the EOR entity must follow the Arbeitnehmererfindungsgesetz process: receive the report, claim the invention within 4 months, and pay compensation. Then the EOR assigns the invention to you under the service agreement.

What goes wrong: The EOR entity doesn’t have a process for handling invention reports. The 4-month window passes. The employee retains the patent rights. Your engineer now owns the algorithm your product depends on.

Fix: Ask your EOR provider specifically about their Arbeitnehmererfindungsgesetz compliance process. Do they have a procedure for receiving and claiming inventions? Who monitors the 4-month deadline? Is invention compensation included in the employment cost or billed separately?

India: Patents Act, 1970 and Copyright Act, 1957

India’s IP framework creates two separate issues:

Patents: Under Section 53(1) of the Patents Act, patent rights for inventions made “in the course of the employee’s duties” belong to the employer. But “in the course of duties” is interpreted narrowly. An engineer hired to develop software who invents a hardware innovation may retain patent rights if hardware development wasn’t part of their defined job responsibilities.

Copyright: Section 17 of the Copyright Act assigns copyright of works created during employment to the employer — but only if the work was created “in the course of employment.” Freelance or contractor work defaults to the creator. For EOR employees, the employment contract should explicitly define the scope of work broadly enough to capture all relevant creative output.

What goes wrong: The employment contract with the EOR’s Indian entity defines the employee’s role narrowly (“Software Developer — Backend Services”). The employee creates a machine learning model outside their defined scope but using company data and during work hours. Ownership is ambiguous.

Fix: Draft the role description and IP assignment clause broadly. “All intellectual property created during the course of employment, related to the employer’s business or using the employer’s resources, is assigned to the employer.” Have your IP counsel review the specific language.

France: Intellectual Property Code (Code de la Propriété Intellectuelle)

French IP law has a useful provision for software: Article L113-9 of the Code de la Propriété Intellectuelle assigns economic rights for software created by employees to the employer automatically. No special clause needed for software copyright.

But this only covers software. Other types of IP — inventions, designs, artistic works — follow different rules. Employee inventions must be reported and the employer must claim them (similar to Germany, but the French system uses a different classification: “mission inventions” vs. “off-mission inventions”). Compensation may be owed.

Fix: Don’t rely on the statutory default. Include explicit IP assignment clauses covering all IP types, not just software copyright. The statutory default is a floor, not a ceiling.

Other Countries With Notable IP Rules

Owned Entity vs. Partner Entity: IP Implications

The entity model affects IP security.

Owned entity (e.g., Remote). The EOR provider controls the entity that employs your worker. The IP assignment chain is: Employee → Remote’s entity → Your company. Two parties. Clean chain. If you need to enforce IP rights or prove ownership, you deal with one provider who controls the entire flow.

Partner entity (e.g., Deel in some markets). The chain becomes: Employee → Local partner entity → Deel → Your company. Three parties. The local partner’s employment contract assigns IP to the partner. The partner’s agreement with Deel assigns IP to Deel (or directly to you, depending on the contract structure). Deel’s agreement with you assigns it to you. More links in the chain means more potential failure points.

What goes wrong with partner entities: The local partner’s employment contract template doesn’t include IP assignment language specific to your company. Or the assignment runs to the partner entity, not through to you. During M&A due diligence, the acquirer’s lawyers trace the IP chain and find a gap. The fix requires getting the local partner entity to execute an amendment — which requires the EOR provider to coordinate with a third party.

Fix: For any market where you have engineers or other IP-creating roles, request a copy of the actual employment contract and verify the IP assignment clause. Don’t accept “our standard template covers it.” Read the template.

Best Practices for Engineering Teams Through EOR

1. Review every employment contract before the employee signs. Don’t delegate IP review to the EOR’s legal team alone. Have your IP counsel review the assignment clauses. This takes 30 minutes per contract and prevents problems that cost months to fix.

2. Use present-tense assignment language. “Employee hereby assigns” is stronger than “Employee agrees to assign.” The former creates an immediate transfer. The latter creates a promise that must be enforced separately if breached.

3. Define scope broadly. The IP assignment should cover all work product created during employment that relates to the employer’s business, uses the employer’s resources, or results from the employer’s confidential information. Narrow scope definitions create gaps.

4. Include moral rights waivers where permitted. In some jurisdictions (France, Germany, much of continental Europe), employees have “moral rights” to their creative work — the right to be attributed, the right to prevent modification. These can’t always be waived, but where they can, include the waiver.

5. Address pre-existing IP. The employment contract should require the employee to disclose any pre-existing IP they’ll use in their work and exclude it from the assignment. This prevents disputes about what the employee brought to the role vs. what they created during it.

6. Implement invention disclosure procedures. For teams in Germany, Japan, and South Korea, establish a formal process for employees to report inventions and for the EOR entity to claim them within the statutory deadline.

7. Get the service agreement right. The service agreement between you and the EOR should include:

• Full IP assignment (not license) from EOR to your company
• Representation that the EOR’s employment contracts include proper IP assignment
• Obligation to assist with IP registration (patents, trademarks)
• Survival clause ensuring IP assignment survives termination of the service agreement

8. Maintain an IP register. Track which employees created which IP, which EOR entity employed them, and which contracts govern the assignment. This is the document an acquirer’s lawyers will ask for.

What Happens During M&A Due Diligence

Acquirers and investors scrutinize the IP chain. Here’s what they look for:

1. Complete chain of title. Can you trace ownership from the individual creator through to your company, with signed documents at every step?
2. Assignment, not license. Licenses are revocable (sometimes). Assignments are permanent.
3. Country-specific compliance. Did you follow Germany’s invention reporting process? Did India’s employment contracts address patent vs. copyright separately?
4. No gaps or ambiguities. A missing IP clause in one employment contract affecting one engineer’s work on one feature can delay or derail a deal.

The cost of getting this right upfront: a few hours of IP counsel time per contract. The cost of getting it wrong: weeks of deal delay, significant legal fees, and a potential valuation haircut.

When Not to Use This Approach

Your EOR provides a template IP clause without country-specific legal review. Template IP assignment provisions are a starting point. In Germany, the Netherlands, and Canada, statutory employee IP rights differ from what a standard US-style assignment clause assumes. A clause that works in Singapore fails in Munich without local counsel input.

You’re in a jurisdiction where moral rights exist and can’t be fully waived. In most EU countries, authors retain moral rights (right of attribution, right of integrity) over creative works even after assigning economic rights. IP assignment clauses don’t transfer moral rights — this matters for software, design, and creative content created by EOR employees.

Work product includes inventions developed before or outside the employment scope. Most EOR contracts assign IP created in the course of employment. Pre-hire inventions, side projects, and work done outside working hours create ambiguity that template clauses don’t resolve. You need country-specific agreements that clearly carve out what was brought in and what’s being created for you.

You’re in China or India with employees working on trade secrets. IP protection in these markets requires more than assignment clauses — it requires actively maintained trade secret protocols, additional NDAs reviewed by local counsel, and often non-solicitation provisions that must comply with local enforceability standards. EOR standard contracts are insufficient without supplemental agreements.

Frequently Asked Questions

Does the EOR have any claim to my company’s IP?

Not if the contracts are structured correctly. The EOR entity temporarily holds IP rights (via the employment contract) and immediately assigns them to you (via the service agreement). The EOR has no commercial interest in your IP. But if the service agreement uses licensing language instead of assignment, the EOR entity technically retains ownership and grants you a license. Fix this if you find it.

What happens to IP rights when I switch EOR providers?

The IP created during the previous EOR engagement should already be assigned to you. When you switch providers, the new employment contract with the new EOR entity covers IP going forward. There shouldn’t be a gap — but verify that the old service agreement’s IP assignment clause survives termination.

Can an EOR employee file a patent without my knowledge?

Yes, in any jurisdiction. An employee can file a patent application. The question is who owns it. If the employment contract properly assigns inventions to the EOR entity, and the service agreement assigns them to you, you have a claim to ownership. But you’ll need to enforce it — which is easier if you discovered it early. Implement invention disclosure procedures.

Should I have a separate IP agreement with each EOR employee?

In addition to the IP clauses in the employment contract, some companies require employees to sign a separate IP assignment agreement directly with the client company. This creates a direct IP relationship, bypassing the two-hop chain. It’s belt-and-suspenders — not legally required in most cases, but it provides an extra layer of protection that acquirers appreciate.

To connect this guidance with live hiring demand, see hiring your first international employee and remote jobs by country.

Further Reading

• EOR Compliance Risks — Broader compliance risks including IP
• How Does an EOR Work? — Understanding the legal structure
• EOR for Startups — IP considerations during fundraising
• EOR vs. Setting Up Your Own Entity — Entity control over IP vs. EOR chain
• Hiring in Europe Guide — European IP and employment law context
• Compare EOR providers
• Top EOR reviews
• Hiring your first international employee

Anchal Katyal · Founder, eorHQ

Anchal has spent over a decade in product strategy and market expansion across Asia and the Middle East. She evaluates EOR providers on compliance depth, entity ownership, payroll accuracy, and in-country support quality.

Was this page helpful?

Tell us or send a correction.

Yes No Request a correction