Payroll

A Taxonomy of EOR, PEO, Global Payroll, and Contractor of Record

I’ve spent over a decade watching companies pick the wrong global hiring model. Not because they don’t care. Because the terminology in this space is a mess. EOR, PEO, global payroll, contractor of record. Vendors use them interchangeably. Advisors mix them up. Even some regulators get it wrong. I wrote this paper to fix that. Here’s what I found.

Four models. Four different things.

These are not variations of the same service. They have different legal structures, different compliance implications, and different use cases. Treating them as the same thing is how companies end up with compliance gaps they don’t know about.

The taxonomy I built uses four dimensions to separate them: who is the legal employer, whether the client needs a local entity, how portable the structure is across jurisdictions, and whether co-employment or shared liability exists. Once you map each model against those four dimensions, the differences become clear.

EOR: the one that actually solves the “no entity” problem

Employer of record is the only model where the intermediary becomes the full legal employer under local law. The EOR issues the employment contract, runs payroll, handles tax, and carries compliance responsibility. The client directs the work but has no direct employment relationship with the worker.

No entity required on the client side works in most countries. This is what most companies mean when they say they want to “hire someone abroad without setting up a company.”

One thing to watch, some countries cap how long you can use an EOR for the same worker. Germany limits it to 18 months. Go beyond that without a review and you risk being treated as the direct employer, with back-liability.

PEO: mostly a US thing, whatever vendors tell you

Professional employer organisation means co-employment. You and the PEO are both employers simultaneously, with responsibilities split by a written agreement. The IRS recognises this in the US. It works cleanly there.

Outside the US, co-employment doesn’t exist as a legal concept in most countries. When a vendor sells you “global PEO,” what they’re almost always selling you is an EOR arrangement. The co-employment structure has no legal standing internationally.

This matters. If you believe you’ve transferred employer liability to a global PEO provider in Germany or Singapore, and co-employment isn’t legally recognised there, you haven’t. You’re still fully exposed.

Global payroll: admin, not employment

Global payroll does not make anyone the employer. The client stays the legal employer in every country. The provider handles payroll calculation, tax remittance, and statutory reporting – the admin layer.

You need a legal entity in every country where you have workers. Global payroll doesn’t solve the “no entity” problem. It handles the paperwork once the entity problem is already solved.

Plenty of companies use EOR and global payroll alongside each other. EOR covers markets where they have no entity. Global payroll handles the ones where they do.

COR: for contractors, not a cheaper version of EOR

Contractor of record is for genuinely independent contractors. No employment relationship. The COR holds the commercial contract, checks classification, processes payments, and keeps the documentation regulators want to see.

The key word is “genuinely.” COR does not fix a misclassified relationship. If you’re directing someone’s daily work, providing their equipment, and they’re working for you exclusively – that looks like employment in most jurisdictions. Putting a COR in the middle doesn’t change that. It just creates a documented record of a misclassified arrangement, which typically makes things worse.

The decision is simpler than it looks

Two questions. That’s it.

First: is this worker an employee or a genuine independent contractor? Classification is based on how the relationship actually works, not what the contract calls it.

If it’s an employee, do you have a legal entity in their country? No entity means use EOR. If entity exists, use global payroll or domestic PEO, depending on what you need.

If it’s a contractor, is the relationship genuinely independent? If yes, COR works. If no, go back to the employee path and use EOR.

Why this matters

The wrong choice has real consequences. A company that signs up for global payroll, expecting it to cover employment liability in a new market, has no legal employer there. A company using “global PEO” internationally, thinking co-employment applies, has not transferred any liability. A company using COR for a relationship that looks like employment has documented its own compliance failure.

This is not academic. These are the mistakes I see companies make regularly. The terminology is the problem. Get that right, and the rest follows.

The full paper is available on Zenodo: https://doi.org/10.5281/zenodo.18861073

About the Author

Robbin Schuchmann is co-founder of Employ Borderless, an independent advisory platform for global hiring solutions, headquartered in Singapore. He runs international business operations and digital marketing, and has spent 10 years working across global hiring, EOR, PEO and payroll. Employ Borderless helps companies find the right global hiring provider through independent research, provider reviews, direct comparisons and one-on-one advisory.