Indemnification and Liability Allocation in EOR Contracts: Who’s Responsible When Something Goes Wrong

Most companies pick an Employer of Record based on price per employee, coverage countries, and time to onboard. Fair enough — those are visible, measurable, and easy to compare.

The problem is that none of them matter when things go sideways. A wrongful termination claim in Minsk, a tax reassessment from local authorities, an IP dispute with a departing developer — the outcome of every one of these is decided by clauses buried in the middle of your Master Services Agreement.

This guide breaks down how liability and indemnification actually work in EOR relationships: where the risks live, how a fair contract splits them, and the red flags to catch before you sign. It’s written for legal, HR, and finance leaders evaluating providers — including in markets like Belarus, where labor law leaves little margin for error.

The core split: legal employer vs. operational employer

To understand liability in an EOR relationship, start with what makes it structurally unusual.

Your EOR is the legal employer. It signs the employment contract, runs payroll under its own tax ID, withholds contributions, and appears on every filing with local authorities. Your company is the operational employer — you assign the work, manage performance, decide who gets promoted, and choose who gets let go.

In contrast to typical vendor arrangements, that separation produces overlapping risk zones. If a payroll tax is filed erroneously, the EOR is obviously at fault. It is obviously your fault if you fire someone via email without giving them any prior warning. But most real-world problems land somewhere in between, and the contract decides who pays.

This is why the indemnification clause matters more than the day rate. A good EOR partner walks you through exactly how the risk allocation works before you sign — not after something breaks. For context on how a specialized Belarus-focused provider structures this, eor.by publishes its approach openly.

Four risk zones where things actually go wrong

EOR-related disputes almost always come from one of four categories. Knowing them is step one.

Employment law violations. Wrongful termination, unpaid overtime, breach of working-time rules, discrimination claims, missed statutory benefits. Belarusian labor law in particular is highly employee-protective, and even routine terminations require careful notice and severance calculations.

Tax and social contribution errors. Wrong FSSN filings, incorrect income tax withholding, missed deadlines, or miscalculated employer contributions. These trigger penalties and interest, sometimes years after the fact.

Worker misclassification. Treating someone as a contractor when they meet the legal definition of an employee — or vice versa. This is one of the largest sources of legal exposure in global hiring; Deel has a useful breakdown of misclassification risk and how it maps to different service models.

IP, confidentiality, and data breaches. A developer leaks source code. An employee walks out with your customer list. A cyber incident exposes personal data governed by local privacy law. Who owns the IP, who enforces it, and who indemnifies losses is decided at contract stage — not when the incident happens.

The standard indemnification framework

Every serious EOR contract splits responsibility along the same conceptual line: the EOR is liable for the mechanics of employment; the client is liable for the substance of the work relationship.

Here’s what a fair, market-standard split looks like.

The EOR indemnifies you for:

• Payroll accuracy and timely payment
• Tax withholding, filings, and social contribution remittance (see how eor.by’s payroll operations are structured for full FZSN and tax authority compliance in Belarus)
• Statutory benefits administration
• Employment contract compliance with local law
• Its own gross negligence, fraud, or willful misconduct
• Failures caused by its own subcontractors or systems

You indemnify the EOR for:

• Directions given to the worker (assignments, workload, working hours)
• IP ownership and any downstream disputes
• Workplace conduct issues that you were aware of and didn’t act on
• Any instruction that causes a labor law violation
• Misrepresentation of the role during onboarding
• Termination decisions initiated by you

That’s the baseline. Anything materially different — one-way indemnities, tiny caps, broad carve-outs — should be interrogated before signing. Some global providers now offer expanded protection: Remote, for example, advertises unlimited indemnity with no caps for EOR customers. Not every provider does that, but the direction of the market is clear: buyers are asking harder questions, and the best partners answer them upfront.

Red flags to catch before you sign

The clauses below are the ones that cause real damage. Any of them should prompt a conversation before contract execution.

One-way indemnities. The contract protects the EOR against your actions but doesn’t protect you against theirs. In a balanced agreement, both sides indemnify each other for the risks they control.

Liability caps set at monthly fees. A €500-per-month cap on a payroll error that triggers a €200,000 tax assessment is a cap in name only. Look for caps expressed as a multiple of annual fees, or ideally tied to the actual harm at issue for high-severity categories like fraud, gross negligence, and IP infringement.

Broad carve-outs disguised as boilerplate. Watch for language excluding liability for “regulatory changes,” “third-party actions,” or “acts beyond reasonable control.” Compliance monitoring is the EOR’s core job. Carving it out defeats the point.

No duty to defend. There’s a meaningful difference between an EOR that will defend you in a claim from day one and one that only reimburses you after you’ve paid the lawyers and the settlement. Ask which model applies.

Vague “gross negligence” definitions. If the contract limits EOR liability to “gross negligence” without defining it or giving examples, you may be one step away from arguing the meaning of the term in court.

Missing insurance requirements. Ask for a certificate of insurance covering professional indemnity, employment practices liability, and cyber. Oyster, for instance, publishes that its liability insurance coverage exceeds $8 million — you should know your provider’s number, and it should be in writing.

No clear distinction between EOR and PEO responsibilities. In a co-employment PEO model, liability is shared, not transferred. If you’re comparing structures, understand how each model allocates responsibility differently — the wrong choice can leave you carrying risk you thought you’d offloaded.

Three scenarios that show the clauses in action

Abstract clauses are hard to evaluate. Here’s how the same three problems play out under a tight contract vs. a loose one.

Scenario A: The EOR miscalculates social contributions for eight months. The tax authority issues a reassessment plus penalties. In a well-drafted contract, this is squarely the EOR’s problem — they indemnify for tax filing errors, they defend the reassessment, and their professional indemnity insurance covers the exposure. In a weak contract, the liability cap sits at three months of fees, and you eat most of the loss. Getting cross-border payment flows right is exactly the kind of thing the EOR is being paid to handle correctly.

Scenario B: Your team fires an employee over Slack with no notice. The employee files a wrongful termination claim. In a well-drafted contract, the client indemnifies the EOR — you gave the instruction, you own the outcome. In a weak contract, the responsibility is muddled, and both parties get dragged into litigation while their lawyers argue about who directed what.

Scenario C: A developer walks out with a copy of your source code. In a well-drafted contract, IP ownership was assigned to your company at hire, the employment agreement includes proper confidentiality and post-termination clauses under local law, and the EOR supports the enforcement action. In a weak contract, IP language is generic, local moral rights aren’t waived, and you find yourself litigating ownership in a foreign jurisdiction. Playroll’s Belarus hiring guide is a useful reference on how local employment terms interact with these clauses.

Questions to ask before you sign

Before signing any EOR agreement, get written answers to the following:

1. What is your liability cap, and is it tied to fees or to actual damages?
2. Do you defend claims from day one, or reimburse after judgment?
3. What are the limits of your professional indemnity, EPL, and cyber insurance?
4. How is “gross negligence” defined in this agreement, and can we see examples?
5. Who owns IP created by the employee, and how is that assignment enforced locally?
6. What happens if a regulatory change causes a compliance failure — who carries that risk?
7. Are indemnities mutual, and are they capped symmetrically?
8. In a jurisdiction like Belarus, how do you handle notice periods, severance, and trade union notifications on terminations?

Remote People has a useful summary of Belarus-specific employment mechanics worth reading alongside the contract review.

The bottom line

Choosing an EOR is choosing a legal risk partner, not a payroll vendor. Pricing pages tell you what a hire costs when everything goes right. The indemnification clause tells you what a hire costs when something goes wrong — and over a long enough timeline, something eventually will.

Good EOR partners treat indemnification as a conversation to have upfront, not a clause to hide in an appendix. If a provider can’t walk you through their risk allocation clearly in a first sales call, that’s data. If they can — and they show you their insurance certificates, their sample contracts, and their claims history — that’s also data.

Contact us

If you’re evaluating providers for hiring in Belarus specifically, eor.by is happy to walk through our approach to indemnification and liability allocation in detail before any commitment. Bring your legal team. That’s the conversation worth having.

About the author

John D.

Content Marketing Manager

John D. is the content Marketing Manager at EOR.by. He has a passion for simplifying complex topics. With experience creating content and developing strategies in the local market and abroad, John shares his rich experience to make easier processes in companies striving for their development and scaling.