Employer of Record (EOR)

An Employer of Record (EOR) is a third-party provider that becomes the legal employer of a worker in a country where the hiring company has no entity: it signs the local employment contract, runs payroll and statutory benefits, and carries the compliance liability, while the hiring company directs the day-to-day work.

Key takeaways

Does hiring through an EOR add to your own headcount thresholds?

No — not for a worker based abroad. Workers an EOR employs abroad are the provider’s own common-law employees, not the client’s, under the IRS’s common-law test for who controls the work and how it gets done. Under the IRS rule for combining related employers, aggregation for Applicable Large Employer status reaches only businesses under common or related ownership (IRC §414), so an unrelated EOR vendor never gets folded into the client’s own 50-full-time-equivalent headcount. The IRS’s guidance on the employer mandate makes the same point even more directly: that status counts only employees performing work in the 50 states and D.C., and hours tied to foreign-source income drop out of the full-time count entirely, regardless of who signs the paycheck.

How employer-of-record hiring actually works

Hiring through an EOR follows the same sequence regardless of provider. The client selects the candidate and agrees on compensation; the EOR then signs the local employment contract as the legal employer. From there, the EOR runs payroll, withholds local taxes, administers statutory benefits, and handles the termination when the engagement ends — all under that country’s labor law. The client pays the worker’s salary cost plus the provider’s fee, charged either flat per employee per month or as a percentage of gross salary.

Delivery quality tracks how the EOR actually operates locally. A provider that owns its entity in the country tends to run payroll and benefits directly and consistently. One that routes the hire through a network of local partners is only as reliable as that partner relationship, and service quality can vary from country to country within the same provider’s coverage. Benefits may lag what a strong local employer offers.

Employer of Record vs the neighboring models

Five models often get treated as interchangeable, but they split cleanly on four points: whether you need your own local entity, who signs with the worker, who carries compliance and misclassification liability, and what kind of worker it is.

ModelNeeds your own local entity?Who signs with the workerWho carries compliance/misclassification liabilityWorker type
Employer of RecordNoProvider, as legal employerProviderEmployee
PEOYesYour entity (co-employer)Split (co-employment)Employee
Contractor of RecordNoProvider, as contracting partyPer the indemnity clause — published terms cap or exclude itIndependent contractor
Agent of RecordNoProvider, as agentLimited — check the indemnity clauseIndependent contractor
Own entity (direct)YesYouYouEither

A temp staffing agency looks similar for short-term assignments, but it rarely takes on the same compliance-liability transfer as an EOR. Global payroll software sits outside this table too. It processes payroll inside entities the client already owns and doesn’t employ anyone.

Who an Employer of Record is not for

An EOR is the wrong tool for a genuinely independent contractor, for work that’s built to be short, and for a single country where headcount has already outgrown the model.

The first is the most common mismatch. A worker who sets their own hours, supplies their own tools, and works for other clients is genuinely a contractor. Put that person on an EOR and the relationship becomes full-time employment regardless. Payroll tax withholding and statutory benefits enrollment start on day one, whether the engagement was built for that or not. Contractor of Record, Agent of Record, and contractor management software exist for exactly this worker type — all three handle the paperwork without turning the person into an employee. If the real question is whether that worker should legally be an employee in the first place, that’s a contractor-misclassification issue, and an EOR doesn’t resolve it; it just adds an employment relationship on top of a dispute that was never settled.

Short or project-based work fails for a different reason. Companies commonly assume they can dial back the paperwork for a two-month pilot or a single deliverable; the law doesn’t offer that option. Statutory notice and benefit entitlements attach under local law from the first day of employment in most jurisdictions, at whatever tier applies, regardless of how long the assignment was meant to run — there’s no reduced-obligation version of an EOR for a short engagement.

And an EOR stops making sense once a single country’s headcount grows large enough that setting up a local entity and running payroll directly costs less, indefinitely, than continuing to pay per-head provider fees.

Where EOR arrangements break in practice

Control and termination timing are where EOR arrangements break down, regardless of provider.

Control creep is the first, and it usually starts innocently. A client manages an EOR-employed worker exactly like an in-house hire — same tools, same reporting line, same say over discipline, without registering that the legal significance of that control changes once the worker isn’t on the client’s own payroll. An EOR contract makes the provider the legal employer, but if the client sets the worker’s exact hours, requires them to work exclusively inside the client’s internal systems, and directs discipline or termination without going through the EOR, regulators can find that the client itself is the true or joint employer, whatever the paperwork says. That finding runs on the same subordination indicators used worldwide to test whether an employment relationship exists at all: instruction and control over the work, integration into the client’s organization, fixed hours or a specified workplace, and work that must be performed personally rather than delegated — the indicators the ILO’s Recommendation No. 198 sets out in paragraph 13.

If the finding sticks, the client ends up on the hook for the same statutory obligations the EOR arrangement was meant to shift away from it in the first place. How that plays out mechanically is a co-employment question; the same control pattern can also raise a permanent establishment issue for the client’s home-country tax position, since staff directed and disciplined like employees stop looking like an arm’s-length vendor relationship.

The second break is timing. Statutory termination notice runs on the worker’s country’s calendar, not the client’s, and it scales with tenure. Germany’s §622 BGB runs from two weeks during probation to four weeks in the standard case, rising in stages to seven months once a worker has 20 years of service, and the EOR has to honor whichever tier applies on the timeline the statute sets. A client that plans a reduction around its own fiscal calendar, without checking which tier applies, ends up either delaying the exit past its own timeline or paying out notice it never budgeted for. Switching providers has a related cost. The new provider re-contracts the employees itself, so that transition friction is worth pricing in before committing to an EOR long-term.

The CIS angle: when EOR is the wrong tool for a CIS-based team

For most people based in the Commonwealth of Independent States (CIS) and working for a foreign-run company, an EOR is the wrong default. The underlying engagement usually isn’t employment in the first place. In Russia specifically, the majority of that workforce is structured as self-employed under the NPD regime (самозанятые) or as sole proprietors, and Federal Law No. 422-FZ caps eligible NPD income at ₽2.4 million a year. That status reflects a contractor-style engagement. Wrapping it in EOR employment changes the legal category of the relationship without changing what the work actually is.

Running an EOR for that group turns a self-employed or sole-proprietor engagement into a payroll relationship, full statutory benefits included, that the underlying work never called for and its cost doesn’t justify. Contractor of Record providers fit the large majority of these cases instead. The worker stays a contractor, and the provider manages the engagement without converting it into payroll employment.

An EOR is still the right call when actual employment is the goal — work-permit sponsorship, statutory benefits the worker specifically needs, or a genuine staff role based in Kazakhstan, Armenia, Georgia, or Uzbekistan, where hiring as a direct employee is the intended arrangement.

FAQ

Beyond the fee, what should you check in an EOR provider? Whether the provider has verifiable coverage in the exact country you’re hiring in — broad regional claims often don’t hold up country by country. The employer-of-record ratings compare providers on that basis.

Can a worker hired through an EOR later become a direct hire? Usually, yes — nothing about the underlying relationship requires it to stay routed through the EOR once the client sets up its own entity in that country, and conversion is a standard exit path. Whether it’s free depends on the individual service agreement. Many providers attach a minimum engagement period or a one-off conversion fee, so confirm that term before signing.