- Read the liability clause first, not the price: an EOR contract that caps the provider's liability at a few months of fees leaves you carrying the exposure it was bought to remove.
- Silence is the worst red flag: a contract that never says who is liable for a misclassification finding, a tax penalty or an unlawful dismissal has not allocated that risk to the provider.
- Check whether they employ or subcontract: if the provider uses a third-party partner in the country, your worker's legal employer is a company you never assessed and cannot hold to your terms.
- IP assignment must chain all the way to you: the employee assigns to the legal employer, so without an onward assignment clause the work product stops at the EOR rather than reaching your company.
Want a second pair of eyes on the red flags in an EOR contract before you sign? Talk with our team today!
Discover how Wisemonk creates impactful and reliable content.
Most EOR contracts are reviewed for price and turnaround time. The clauses that decide what happens when something goes wrong sit further down, they are rarely negotiated, and they are the reason a company that outsourced its employment risk discovers it still owns most of it. The gap is usually not a bad clause. It is an absent one.
We are an employer of record, so we sign these agreements from the other side and we know which clauses buyers push back on and which they never reach. This guide walks the contract in the order risk actually lands: liability first, then indemnity, IP, termination, pricing, and the question of who your worker is legally employed by at all.
What should an EOR contract actually cover?
Seven things, and a contract missing any of them is incomplete rather than merely brief: who legally employs the worker, who carries which liability, what is indemnified and by whom, how intellectual property reaches you, how either side exits, what the price includes, and what happens to data. Everything else is commercial detail.
If the mechanics are still unfamiliar, it helps to be clear on how an EOR works before reading its contract, because the risk allocation only makes sense against the structure.
This article is about diligence before signature. For managing the agreement across its life once signed, check out our guide on EOR Contract Management: A Guide to Global Agreements 2026.
What are the biggest red flags in an EOR contract?
Nine recur often enough to check for by name. Read them as a checklist against the draft in front of you, and treat a missing clause as seriously as an unfavourable one, because silence defaults the risk to whoever is left holding it.
| Red flag | Why it matters | What to ask for |
|---|---|---|
| Liability capped at a small multiple of fees | The cap can be far below a single statutory penalty | A carve-out from the cap for compliance and statutory failures |
| No compliance indemnity from the provider | Their filing or payroll error becomes your cost | An express indemnity for their own statutory errors |
| Indemnity running one way only | You cover them, nobody covers you | Mutual indemnities, each scoped to what that party controls |
| Silence on subcontracting | An unassessed third party may become the legal employer | The employing entity named, and consent required to change it |
| No onward IP assignment | Work product stops at the EOR instead of reaching you | Assignment from employee to EOR, and EOR to you |
| Long service notice with no employee-level exit | You cannot right-size without paying for headcount you removed | Separate notice for the service and for individual employees |
| Severance responsibility left undefined | A dismissal cost lands unexpectedly, sometimes months later | Explicit allocation of severance and dismissal cost |
| Transfer or conversion penalties | Moving staff to your own entity becomes expensive by design | A defined transfer right with no punitive fee |
| Fees quoted without stating exclusions | Statutory costs, deposits and FX appear after signature | A full inclusions and exclusions schedule |
Rows one and two travel together and are the pair we would fix before any other. A liability cap is reasonable in principle, but a cap with no carve-out for statutory failures means the provider's worst case is smaller than your worst case for the same event, which inverts the entire point of the arrangement.
For the wider risk picture these clauses are allocating, check out our guide on EOR Risk Management: Mitigating Global Hiring Risks 2026.
Who is liable if an EOR gets compliance wrong?
Whoever the contract says, and in most contracts more of it sits with you than buyers assume. The EOR is the legal employer, so it is the entity the authority pursues. That is genuine protection and it is what you are buying. But nearly every agreement also gives the provider a right to recover its costs from you, so the economic liability flows back unless a clause expressly stops it.
Separating those two ideas is the single most useful thing you can do when reading an EOR contract. Being shielded from the authority is not the same as being shielded from the cost, and a provider can be perfectly willing to stand in front of a regulator while sending you the bill afterwards.
The three layers of liability, and why only one of them transfers cleanly
Any compliance failure produces three separate exposures, and they do not travel together:
- Legal liability to the authority: sits with the legal employer, which is the EOR. This is the layer that genuinely transfers.
- Economic liability for the cost: sits wherever the contract puts it, and the default in most drafts is you.
- Operational and reputational cost: never transfers at all. The employee whose pay was wrong works for your team, and the disruption is yours.
So the honest summary is that an EOR transfers one layer outright, negotiates the second, and cannot touch the third. A provider claiming to remove all your employment risk is describing the first layer and quietly leaving out the other two.
How liability should be allocated by cause
The fair principle is that each party carries what it controls, and a well-drafted contract allocates by cause rather than by a blanket rule. Check the draft in front of you against this:
| What went wrong | Who caused it | Who should bear the cost | Clause to look for |
|---|---|---|---|
| Payroll miscalculated, wrong statutory rate applied | The EOR | The EOR | Provider indemnity for its own statutory errors |
| Filing or remittance late | The EOR | The EOR, including interest and penalties | Penalties expressly inside the indemnity |
| Employment contract non-compliant with local law | The EOR, as drafter | The EOR | Warranty that local agreements are compliant |
| Role misclassified as contractor on your instruction | You | You | Client indemnity, scoped to your instructions only |
| Dismissal instructed without lawful grounds | You | You, but the EOR must warn you first | A duty to advise before executing an instruction |
| Wrong employee data supplied | You | You | Data accuracy obligation on the client |
| Permanent establishment exposure from how the work is directed | Usually both | Shared, and defined in advance | Express PE risk allocation, not silence |
Row five is the one buyers most often miss and the one that protects you most cheaply. A provider who executes an unlawful instruction without telling you it is unlawful has added nothing over a payroll bureau, and a duty to advise costs them nothing to accept if they know their market.
Row seven is the one most contracts leave silent, and silence is not neutral. Permanent establishment risk arises from how you direct the work, so it genuinely is shared, and an agreement that says nothing about it has effectively left it with you.
One structural point underpins all of this. In an EOR arrangement there is one legal employer, and it is the EOR. Any contract or marketing language that describes the relationship as shared employment should be questioned, because it muddies exactly the boundary that makes the liability allocation above workable.
For the full set of duties a provider is taking on and the risks attached to each, read our article on Employer of record compliance: responsibilities and risks.
Row four turns entirely on worker classification, which is the one area where a client instruction can create liability no provider can absorb.
Ask us the liability questions before you ask them of anyone else
We will walk you through how our own agreement allocates compliance risk, clause by clause, so you have a benchmark to compare against.
What indemnity and insurance terms should you insist on?
Mutual indemnities, each scoped to what that party actually controls, and a liability cap that carves out statutory and compliance failures. A one-way indemnity protecting only the provider is the clearest signal in the document that the risk allocation has not been negotiated by anyone before you.
Four specifics are worth pushing on, and none of them is unusual to ask for:
- Penalties and interest inside the indemnity: an indemnity covering only the underpaid amount leaves you the penalty, which is usually the larger number.
- A carve-out from the liability cap: otherwise the indemnity is worth no more than the cap, however broadly it is drafted.
- Employment practices liability cover: ask what insurance actually stands behind the indemnity, and for evidence of it.
- Survival after termination: tax and employment claims surface years later, so the indemnity must outlive the service period.
The last of those is the one that gets dropped in a fast signature. An indemnity that expires with the contract is close to worthless for statutory exposure, because the assessment window in most jurisdictions is longer than the average EOR relationship.
An indemnity is a promise to pay later, so it is worth pairing with the right to run a compliance audit and catch problems while they are still small.
Does the contract assign IP and confidentiality correctly?
Check for a two-step chain, because one step is not enough. The employee assigns their work product to their legal employer, which is the EOR, not to you. Without an express onward assignment from the EOR to your company, the intellectual property your team is producing stops one company short of the business that paid for it.
This is the red flag with the longest fuse. Nothing goes wrong while the relationship is healthy, and it surfaces during a funding round, an acquisition or a dispute, when someone asks to see the chain of title for code or designs and finds it broken in the middle.
Ask to see the employment agreement template, not just the service agreement. The assignment has to be valid under the employee's own law, and some jurisdictions restrict how broadly future inventions can be assigned or require specific formalities to make it effective.
Confidentiality needs the same treatment. A confidentiality obligation running only between you and the EOR does not bind the employee who actually handles your data, so look for a direct obligation in the employment agreement and a right for you to enforce it.
Data protection sits alongside this and is a separate diligence exercise, so check out our guide on EOR Data Security: A Global Compliance & Protection Guide.
What do the termination and offboarding clauses commit you to?
More than most buyers read for, and this is where negotiating leverage disappears the moment you sign. Two separate notice periods matter, not one: notice to end the whole service, and notice to remove a single employee. A contract with only the first leaves you paying for people you have already released.
| Term | What to check | The red flag version |
|---|---|---|
| Service notice | How long to exit the whole agreement | Auto-renewal with a long notice window |
| Employee-level notice | How quickly one person can come off | No separate mechanism at all |
| Severance responsibility | Who funds statutory and contractual severance | Undefined, or left to the provider's discretion |
| Dismissal decision rights | Who decides, and whether they must advise you first | Provider may refuse without stated grounds |
| Transfer to your own entity | Whether you may convert employees later | A conversion fee, or an outright prohibition |
| Transfer to another provider | Whether you may move without penalty | Non-solicit language that traps the employee |
| Records on exit | What you receive, in what format, by when | No obligation to hand back payroll records |
The last two rows are the ones that quietly determine whether you have a partner or a dependency. If moving an employee to your own entity triggers a fee, and moving them to another provider is restricted, then the switching cost has been engineered into the agreement rather than earned by the service.
For how dismissals actually run under an EOR and who does what, check out our guide on EOR Employee Termination: What Global Employers Must Know.
Read the exit terms as though you were already switching providers, because that is the moment they will be used.
A conversion right matters most if you expect to open your own entity once headcount in the market justifies it.
How is the pricing structured, and where do costs appear later?
Judge the fee against a full inclusions and exclusions schedule, not against another provider's headline number. A low monthly fee is not a red flag on its own, but a fee quoted without a written statement of what it excludes always is, because every exclusion becomes an invoice you did not model.
| Cost | The question to ask |
|---|---|
| Statutory employer contributions | Are these passed through at cost, or marked up? |
| Currency conversion | What rate is used, and is a margin added to it? |
| Security deposits | How much is held, for how long, and is it returned? |
| Onboarding and offboarding fees | Are these per employee, and are they charged on exit too? |
| Severance funding | Is severance pre-funded, invoiced later, or accrued monthly? |
| Benefits administration | Is plan administration inside the fee or billed separately? |
| Expenses and equipment | Is there a handling percentage on reimbursements? |
The deposit question is the one that changes cash flow rather than cost. A provider holding several months of payroll as security is not doing anything improper, but it is working capital sitting outside your business, and it belongs in the comparison alongside the fee.
For a full breakdown of how these agreements are priced and what the real total looks like, check out our guide on Employer of Record Pricing in 2026: Real Cost Breakdown.
Who legally employs your worker, and does the contract say so?
The contract should name the employing entity, and you should be able to verify it exists. Some providers own entities in the countries they sell; others use local partners and act as an aggregator. Neither model is wrong, but only one of them means the company you assessed is the company employing your worker.
The red flag is not the aggregator model. It is silence about it. If the agreement permits subcontracting without naming the partner or requiring your consent, then the entity carrying your employment relationship can change without your knowledge, and your negotiated terms may not reach it.
Four questions settle this quickly, and a provider who cannot answer them in writing has told you something:
- Which entity will employ this person? Ask for its legal name and registration details.
- Do you own it, or is it a partner? Both answers are acceptable; an evasive one is not.
- Can it change without telling me? Look for a consent requirement rather than a general right to subcontract.
- Do my terms flow through to the partner? Indemnities and confidentiality are worth little if they stop at the intermediary.
Question four is the one that matters most in practice, because an indemnity from a provider that does not control the employing entity is an indemnity backed by a contract you have never seen.
For a full comparison of the two structures and what each means for you, read our article on Owned-entity vs aggregator EOR: a 2026 buyer's guide.
Every question above belongs in your evaluation before contract stage, so check out our guide on EOR Vendor Selection: How to Choose Your Provider (2026).
The contract is only the start: keeping global compliance consistent afterwards is what decides whether the terms you negotiated ever get used.
Agree the implementation plan before signature too, since a vague start date is how a first payroll gets missed.
How does Wisemonk help global companies handle EOR contracts?
Wisemonk is a leading Employer of Record (EOR) in India that helps global companies hire, pay, and manage employees, without setting up a local entity. We simplify complex HR operations so you can focus on strategy, not administration.
Here's how we help businesses manage EOR contracts more effectively:
- Legal employer of record: we act as your legal employer and manage payroll, taxes, and compliance under local employment laws.
- Clear risk allocation: our agreement states who carries which liability, so the answer is on paper before anything goes wrong.
- Benefits administration: health insurance, retirement contributions and paid leave handled so employees stay satisfied and compliant.
- End-to-end HR management: from onboarding and documentation to day-to-day employee support.
- Fast, compliant onboarding: hire and onboard top talent in under a week, fully compliant with local labor and tax laws.
Currently we are strongest in India, and we are planning to expand into future markets such as the US and the UK. With Wisemonk, you get a reliable partner for your global hiring and payroll journey.
Bring us the contract you are about to sign
We will show you how our agreement allocates liability, indemnity and exit rights, so you have a real benchmark rather than a checklist.
What our clients say
Companies from the US, UK, and Europe trust us to build their teams compliantly and fast. Here's what our clients say:
"I'm very happy that I discovered Wisemonk. They have been a pure pleasure to work with, and their attention to detail is impressive. They helped us understand their pricing model, find top-qualified individuals, interview them, and then onboard them. I gave them criteria for the type of people we sought, and they delivered. The individuals they were able to find have been some of the best engineers I have ever worked with. I recommend Wisemonk to anyone who is in need of staffing assistance."
- Dan Sampson, Head of Engineering at Cobu
Frequently asked questions
What is the biggest red flag in an EOR contract?
A liability cap set at a small multiple of monthly fees, combined with no compliance indemnity. That pairing means the provider carries almost none of the employment risk you engaged them to absorb, and the gap only becomes visible when something has already gone wrong.
Who is liable if an EOR gets compliance wrong?
Whoever the contract says, and by default more of it sits with you than most buyers expect. The EOR is the legal employer and answers to the authority, but it will usually recover from you unless the agreement expressly makes compliance failures its own risk.
Should an EOR contract include an indemnity?
Yes, and it should run in both directions. You indemnify them for your instructions and your data; they indemnify you for their payroll, filing and statutory errors. A one-way indemnity that only protects the provider is a straightforward red flag.
Does an EOR own the intellectual property my worker creates?
It can, by default. The employee assigns work product to their legal employer, which is the EOR. Your contract needs an express onward assignment from the EOR to you, plus confirmation that the employment agreement itself contains a valid assignment clause.
What termination terms should I check in an EOR contract?
Notice period for the service, notice for individual employees, who decides and who pays for a dismissal, severance responsibility, and whether you can transfer employees to your own entity or another provider without penalty. Exit terms are where leverage disappears.
Is a low EOR price a red flag?
Not by itself, but it should prompt questions. Ask what the fee excludes, whether statutory costs are passed through at cost, what deposits are held, and how currency conversion is priced. Cheap headline pricing often reflects costs relocated rather than removed.
How do I know if the EOR actually owns an entity in the country?
Ask them to name the employing entity and show its registration, then check the contract permits or prohibits subcontracting. An aggregator model is not automatically wrong, but you should know it, assess the partner, and have your terms flow through to them.
Ready to build your India team?
Tell us who you're looking to hire. We'll walk you through exactly how the setup works for your company, your timeline, and your budget.
