What Your EOR Actually Does (And Doesn't Do)
The audit that asked questions nobody could answer
Real Compliance, Real Stakes: A Teamed Case Study
Country: Sub-Saharan Africa | Issue Type: EOR Governance and Benefits Compliance | Outcome: Audit resolved, discrimination risk avoided
Based on real client situations, amalgamated for anonymity.
Key takeaways
- An Employer of Record, or EOR, is a company that legally employs your international staff on your behalf. It is a common and legitimate way to hire people in other countries. But if you cannot explain how it works when someone asks, that becomes a serious problem.
- Using an EOR means three parties are involved in every employment relationship: you, the EOR, and the worker. That three-way arrangement needs to be documented, or it creates a gap that an auditor will find.
- A common mistake is putting EOR workers onto the client company's own benefits plan. Because the EOR is the legal employer, not you, this is a compliance error that can carry real legal consequences.
- Neither problem in this case study came from doing something dishonest. Both came from an arrangement that had never been properly written down or checked.
- Teamed's role was advisory throughout: clarifying the structure, drafting the explanation, and guiding the response. That is what thinking ahead looks like in practice.
First, a quick explanation of what an EOR is
If you already know how an EOR works, skip ahead.
An Employer of Record is a third-party company that becomes the legal employer of your workers in a country where you do not have your own registered entity. It issues the employment contract, runs local payroll, handles tax filings, and administers statutory benefits. You pay a monthly fee per employee and continue to manage what the person does day to day. It is the standard way companies hire internationally without setting up their own local entity in every country.
Challenge 1: The audit that exposed the gap
A life sciences company was using an EOR to employ a small team of specialists in two countries. The arrangement had been running without any issues for some time. Payroll was being handled. Workers had contracts. The commercial agreement with the EOR was in place.
Then an external auditor came in.
Auditors reviewing a company's international employment arrangements will ask straightforward questions about who is responsible for what. In this case, those questions were:
Who is the legal employer of your workers in these countries? How are those workers connected to you contractually, given that the contracts are with the EOR and not with you? Who is responsible for their salary, bonuses, benefits, and tax deductions? If there is a legal dispute, who is liable?
These are not trick questions. They are the kind of thing any well-run company should be able to answer.
The company could not answer them.
Not because anything was being done dishonestly. The EOR arrangement was correct. But nobody had ever written down how it worked. There was no document that explained the three-party chain in plain language. The contracts existed. The commercial agreement existed. The bridge between them, a simple explanation of how it all connected, did not.
The question that made the gap most visible was this one: if the contracts are with your EOR provider, how exactly are your workers engaged with you?
There was no good answer ready. And that, in an audit, is itself a problem.
Challenge 2: the wrong benefits plan
Alongside the audit, something else came to light.
One of the EOR-employed workers had been enrolled in the client company's own benefits plan. This had happened because the company's People team managed benefits centrally. When they added this worker to the system, they added them the same way they added everyone else. It felt consistent. It was a mistake.
Here is why. The worker's legal employer was the EOR, not the client company. That matters because benefits, including things like paternity leave and healthcare insurance, are governed by the employment relationship. The legally responsible employer is the one whose rules apply.
By enrolling this worker in the client's plan, the company had created a mismatch. The worker was covered by a plan that had no legal basis to cover them, administered by a company that was not their legal employer.
When questions came up about paternity leave eligibility and healthcare coverage, nobody could give a clear answer. Which employer's rules applied? Which plan would respond if a claim was made?
Under the labour law framework in this jurisdiction, treating workers inconsistently when it comes to employment entitlements carries discrimination risk. Some workers were getting benefits through the correct employer. This one was not. The fact that it happened by accident does not change the legal exposure. Intention is not the test.
What Teamed identified
Looking at both challenges together, the root cause was the same in each case: the EOR arrangement had been set up correctly but had never been properly explained or checked.
On the audit, Teamed identified that the single-contract EOR model was not the problem. The structure was sound. What was missing was a document that translated that structure into plain language an auditor could follow. The chain was real. The explanation was not.
On the benefits issue, Teamed identified a pattern that comes up regularly when companies treat their global workforce as a single group without distinguishing between directly employed staff and EOR-employed staff. The instinct to treat everyone the same is understandable. But statutory benefits obligations attach to the legal employer, not the commercial client. When the EOR is the employer, the EOR's plan governs the worker. Enrolling that worker in the client's plan does not give them more. It gives them a mismatch, and depending on the jurisdiction, a discrimination exposure.
What was at stake
An unresolved audit in a regulated industry is not a minor inconvenience. The inability to show who holds employment obligations can open up questions about permanent establishment risk, which is the risk that a company's activities in another country create unexpected tax and legal obligations there. It can also raise questions about whether workers have been correctly classified and whether statutory deductions are being made by the right entity.
On the benefits side, a discrimination claim under a protective labour law framework is not easily dismissed. The burden of justification sits with the employer. Saying "we didn't know they were on the wrong plan" is not a legal defence. And beyond the formal exposure, there was a practical problem: the worker's actual entitlements were genuinely unclear. If a claim had been made, nobody knew which employer would be responsible or which plan would pay.
Neither issue was at the point of no return. But both had the potential to become significantly more serious if left unaddressed.
What Teamed recommended
The first priority was documentation. Before responding to the auditor, the company needed a plain-language written explanation of how the EOR model worked: who held the employment relationship, who was responsible for payroll and statutory compliance, and what the Master Services Agreement covered. Teamed also advised making the MSA available to the auditor with some framing context. Auditors asking to see contracts are usually looking for accountability, not sensitive commercial detail. Providing it, with explanation, closes the question far faster than declining.
The principle: explain the structure before defending it. A correctly structured arrangement that nobody can explain looks worse than an imperfect one that is clearly owned.
On the benefits issue, the immediate step was to move the worker onto the EOR's plan and confirm it covered the relevant entitlements under local law. The broader recommendation was a cleaner distinction going forward: what the company provides to directly employed staff is governed by employment law, what it wants EOR workers to receive belongs in the commercial agreement with the EOR, not in the client's own benefits system.
You cannot transfer compliance obligations by putting someone on the wrong form.
What an EOR does, and what it does not
A lot of the confusion in situations like this comes from assuming the EOR covers more than it does, or that responsibility sits with the client when it does not. Here is a simple breakdown.
3 questions every company should be able to answer about their EOR arrangement
If you use an EOR right now, these are the three questions an auditor, a regulator, or an acquirer doing due diligence is most likely to ask. If you cannot answer them clearly today, that is worth addressing before someone external asks first.
1. Who is the legal employer of your workers, and how are they connected to you? The answer should explain the three-party chain in plain language: the EOR employs the worker under a local contract, you engage the EOR under a Master Services Agreement, and you direct the worker's day-to-day activity. That explanation should exist in writing, not just in someone's head.
2. Who is responsible for salary, benefits, statutory deductions, and key employment terms? The EOR holds the statutory obligations. But benefits the client wants workers to receive beyond the statutory minimum need to be specified in the commercial agreement with the EOR, not administered informally through the client's own systems. If you cannot trace every element of a worker's compensation and benefits back to either the EOR's obligations or your MSA, there is a gap.
3. If there is a legal dispute involving one of your EOR workers, who is liable and under which jurisdiction? The answer depends on what the dispute is about. Employment claims sit with the EOR as the legal employer. Commercial disputes between you and the EOR sit under your MSA. Understanding which framework applies to which type of issue, and having the documents to back it up, is what audit-ready documentation looks like in practice.
Still got questions? Talk to an Expert.
Over 1,000 companies have worked with Teamed to get their global employment right, across 187+ countries for EOR and 100+ countries for entity formation and management. If you are using an EOR today and not certain you could answer those three questions, that conversation is worth having now.
