Who Owns the Code? Intellectual Property When You Hire Through an EOR
Hiring through an EOR means someone else is the legal employer, so your IP passes through two contracts before it reaches you. Here's where that chain breaks and which clauses to check.
Your code passes through a company you don't control
When a developer in Berlin, Bengaluru or São Paulo joins through an employer of record, you aren't their employer. The EOR is. That matters for intellectual property, because in many legal systems the default owner of work an employee creates is the employer, not whoever pays the invoice. So employer of record intellectual property never reaches you directly. It reaches you through a chain of contracts, and the chain is only as strong as its weakest link.
Usually the chain holds. Mainstream EORs draft their employment contracts and master service agreements so that rights end up with the client. But "usually" isn't good enough when the asset is your core product, or when an investor's diligence team asks you to prove chain of title for every engineer who has touched the codebase. This piece covers how the transfer works, where local law interferes, and what to put in front of your lawyer before you sign.
Three handoffs: employee to EOR to client
A clean transfer usually has three parts:
- Employee to EOR. The local employment contract includes an invention assignment clause. The employee assigns (or confirms the EOR owns) everything created in the course of the job. In many countries the law already vests some of this in the employer automatically. Software written by employees is a common example.
- EOR to client. The master service agreement (MSA) says the EOR assigns those rights to you, or holds them on trust for you until it does.
- Confirmation and cooperation. The employee agrees to sign follow-up documents, such as patent filings or registrations, and to waive or not assert personal rights where the law allows.
Some EORs use a direct structure instead, where the employee assigns straight to the client as a named beneficiary. That shortens the chain. But not every jurisdiction treats an assignment to a non-employer as cleanly as one to the employer, so ask which model the EOR uses in each country you hire in. Don't accept an answer about their "standard" contract.
Moral rights: the part you often can't buy
Economic rights (to copy, sell and license) can generally be transferred. Moral rights are different. They include the right to be named as author and to object to distortion of the work, and in many civil-law countries they stay with the individual whatever the contract says.
- Germany and France treat authors' personal rights as inalienable. German law doesn't allow copyright itself to be transferred, only exclusive usage rights, though special rules give employers the usage rights to software written as part of the job.
- Japan lets an employer be treated as the author of certain works made for hire, but an individual author's moral rights can't be assigned. Contracts usually rely on a covenant not to exercise them.
- India protects attribution and integrity rights by statute, and they generally survive assignment.
- The UK and several other common-law countries let authors waive moral rights in writing, which is cleaner.
For most software teams, moral rights rarely cause commercial trouble. They matter more for design, content and anything you'll heavily modify or white-label. Make sure the contract includes a waiver where waivers are valid and a non-assertion covenant where they aren't.
Employee-inventor pay in Germany, Japan and China
Patentable inventions bring a second problem. Several countries require employers to pay inventors something beyond salary, and contracts often can't waive that right in advance. With an EOR, the legal obligation sits with the EOR, but the commercial value sits with you. Your MSA has to say who pays.
| Country | How the employer acquires inventions | Inventor compensation | What to check |
|---|---|---|---|
| Germany | Employer claims the invention after the employee reports it; the claim can be deemed made after a statutory period unless released | Statutory reasonable compensation, often tied to the invention's commercial value | Reporting process, who handles claims, who funds compensation |
| Japan | Work rules can vest service inventions in the employer from the outset | Employee entitled to a "reasonable benefit" (money or other economic benefit) | Whether the EOR's work rules include an invention policy and benefit scheme |
| China | Service inventions generally belong to the employer | Reward on grant plus remuneration once exploited; statutory defaults can apply if no policy or agreement exists | A written reward policy, so you aren't left with the defaults |
If you expect patents, which is common in hardware, biotech and deep tech, raise this before the first hire in these countries. A policy that's missing at the start is harder and more expensive to fix later.
Prior inventions, side projects and open source
Ownership disputes rarely concern work done at the desk on a Tuesday. They concern what the engineer built before joining, on weekends, or in a public repository. Three points need explicit treatment:
- Prior inventions schedule. The employee lists pre-existing IP. Anything they bring into your product should come with a license to you, ideally perpetual and royalty-free.
- Scope of "in the course of employment." Several jurisdictions, including some US states and a number of European countries, limit how far an employer can claim inventions made on personal time without company resources. Clauses that try to grab everything tend to be unenforceable in exactly the cases that matter.
- Open-source contributions. Spell out whether employees may contribute to outside projects and what approval they need. A copyleft license slipped into your codebase is a bigger diligence problem than a missing signature.
Clauses to put in front of counsel
Ask the EOR for the actual local employment contract template for each country, not a summary, along with the MSA. Then have counsel confirm the following:
- Present assignment language ("hereby assigns") rather than a promise to assign later, in both the employment contract and the MSA.
- Coverage of all IP types: copyright, inventions, designs, trade secrets, database rights and know-how.
- Specificity where the law requires it. Some countries, India among them, have default rules that limit the duration or territory of an assignment that doesn't state them. That's a real risk for the EOR-to-client leg, so state scope explicitly (worldwide, for the full term of protection).
- Moral rights waiver or non-assertion covenant, adjusted for each country.
- Inventor compensation: who administers it and who bears the cost.
- Further-assurance and power-of-attorney clauses that survive termination, so you can still get signatures after the person or the EOR relationship is gone.
- Confidentiality and trade-secret protection that runs to you directly, not only to the EOR.
- Exit terms: what happens to rights if you leave the EOR, the EOR becomes insolvent, or you convert the employee to your own entity.
Red flags in an EOR's IP terms
Watch for these during contract review:
- Transfer conditional on payment. Some MSAs pass IP only once all invoices are paid. That's commercially understandable, but a billing dispute could then cloud your title. Negotiate for transfer on creation, with the EOR's remedies limited to money.
- A "standard global template" with no local versions. One contract can't meet German, Japanese and Brazilian requirements at once.
- No mention of inventor compensation in countries where the law requires it.
- A license instead of an assignment. A license leaves ownership with the EOR, and investors will notice.
- Reluctance to share country templates before signature.
Large providers such as Deel, Remote, Oyster, Rippling and Papaya Global all address IP in their contracts, but their drafting and willingness to negotiate differ. Compare the actual documents, not the sales deck.
What a proper review costs
Typical 2026 market ranges, which vary by firm, country and contract, so confirm with providers:
- Local counsel review of one country's EOR employment template: roughly $800–$3,000.
- MSA review for IP and liability terms: roughly $1,500–$5,000.
- Invention policy drafting for Germany, Japan or China: roughly $2,000–$8,000 per country.
- Confirmatory assignments to fix gaps after the fact: cheap per document, but expensive when someone has already left or won't sign.
Here's a hypothetical example. Say a 40-person software company has engineers in five countries through one EOR. A one-time review of five templates plus the MSA might run $6,000–$15,000. That's small next to a delayed funding round or acquisition while lawyers chase signatures from former staff.
A decision rule for your next hire
If the person will write code, designs or anything else that ends up in your product, don't sign the EOR order form until three things are true. Counsel has seen that country's actual employment template. The MSA uses present assignment to you with no payment condition (or one you've accepted knowingly). And in countries with inventor-compensation laws, the contract says who pays.
For patent-heavy roles in Germany, Japan or China, involve local counsel before the offer goes out. For everyone else, run the clause checklist above once per country and keep the signed documents in your own data room, not just the EOR's portal.
Common questions
Does an EOR automatically assign IP to my company?
No. The employee's work usually belongs first to the EOR as the legal employer, and it reaches you only through the master service agreement. Most reputable EORs include this assignment, but confirm it uses present assignment language and isn't conditional on payment.
Can an employee waive moral rights?
It depends on the country. The UK and several other common-law countries allow written waivers, while Germany, France, Japan and others treat moral rights as non-transferable, so contracts there rely on non-assertion covenants instead. Have local counsel confirm what is enforceable for each hire.
Who pays employee-inventor compensation when hiring through an EOR?
The legal obligation usually sits with the EOR as employer, but the MSA should say whether the cost passes through to you. In Germany, Japan and China this compensation often can't be waived in advance, so settle the arrangement before any patentable work begins.
Is it better to have employees assign IP directly to my company?
A direct assignment shortens the chain and can simplify diligence, and some EORs offer it. Whether it's enforceable as cleanly as an assignment to the employer varies by jurisdiction, so treat it as an extra layer of protection, not a replacement for the EOR-to-client assignment.
What happens to IP if I switch EORs or open my own entity?
Rights already assigned to you stay with you, provided the assignments were valid when made. The risk is in anything left unassigned or conditional, so before you transition, get confirmatory assignments and make sure further-assurance clauses survive termination.
Written by the Hire Team Plus editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.