A company wants to hire a senior engineer in the Netherlands. They have no Dutch entity. They get two proposals: one from an EOR, one from a global payroll provider, and both lists of features look similar enough that the decision gets pushed to HR, then to legal, then back again without resolution.
It is easy to see why teams mix the two up. EOR and global payroll both deal with employee payments, and both often involve an outside provider. But the real difference is the employment setup behind the payroll. When that setup is wrong, the issue is not just extra admin work. It can create legal, tax, and compliance exposure.
This is the distinction worth understanding before the proposals land on your desk.
What Payrolling Actually Means
Payrolling is a service where a third party places a worker on its payroll and handles salary payments, tax withholding, deductions, and basic filings. The client company still manages the worker’s day-to-day tasks and direction. It is not a software category. It is not a synonym for global payroll. It is a service model with a specific scope.
The term originates in staffing. A staffing agency "payrolls" a worker when it processes that worker's compensation through its own payroll infrastructure, often because the client company either cannot or does not want to add that person directly to its books. In most cases, the client company still carries responsibility for how the worker is engaged, managed, and classified.
This mix-up happens a lot in cross-border hiring. Teams see “payrolling” and think it covers the full employment setup. In reality, it only covers part of the process. It can help with payments, deductions, filings, and payroll administration, but it does not make the worker legally employed in that country.
That distinction drives the whole decision: payroll can support an employment setup, but it does not always create one.
What an EOR Does That Payrolling Does Not
An employer of record does more than run payroll. It becomes the legal employer in that country. The EOR signs the employment contract, files taxes and social contributions through its own registration, and provides statutory benefits based on local law.
That is the main difference from payrolling. If an employment dispute comes up, the EOR is the formal employer in that country. The client still needs to manage the relationship carefully, but the legal employment structure sits with the EOR. This is not a small legal detail. It is the reason the model exists.
This matters most when a company wants to hire in a country where it has no local entity. Without one, the company usually cannot employ workers directly under local law. A payroll provider can process payments, but it cannot create a valid employment relationship on its own.
The difference becomes clear when there is a complaint, a termination, a severance obligation, or a tax audit. At that point, the question is not which system processed payroll. The question is who is responsible for the employment relationship. Under an EOR setup, the EOR holds the formal employer role.
This is also where finance teams can misunderstand the model. EOR does not simply sit on top of the client’s employment relationship as extra protection. It replaces that relationship in the country where the worker is hired, which can reduce the client company’s direct employment exposure there.
When Payrolling Is the Right Choice
Payrolling can be the right model when the company already has a legal entity in the country. In that case, the employment structure is already in place. The company may only need help with payroll administration, such as salary calculations, tax remittance, statutory deductions, and payslip generation.
For example, a company with a subsidiary in Canada and three full-time employees does not need an EOR just to pay them. It needs a payroll provider that can process wages correctly and keep payments and filings on schedule. That is usually cheaper than paying EOR fees for each employee.
Payrolling can also work for short-term or contingent roles, as long as the company has already reviewed the worker’s classification. Staffing agencies often use this model when the worker relationship is defined, time-bound, and properly classified.
The key point is simple: payrolling works when the legal foundation already exists. It runs on top of that structure. It does not create it.
When You Need an EOR, Not Just Payroll
Payrolling is not enough when a company has no legal entity in the worker’s country. A payroll provider can process payments, deductions, and payslips, but it cannot create a local employment relationship by itself. If there is no registered employer in that country, the company may still have a gap in the employment structure.
The risk becomes clear if local authorities review the relationship. A worker may be treated as an employee if the company controls their work, pays them regularly, and includes them in daily operations. If that happens, the risk usually falls on the company directing the work, not the provider running payroll.
There can also be tax exposure. Local workers may create permanent establishment risk when they sell, negotiate, represent the business, or help build a steady presence in the country. Payrolling does not solve that problem.
EOR is built for this situation. The EOR provides the local entity, issues the employment contract, handles employer obligations, and becomes the legal employer. The client manages the work, while the EOR holds the employment relationship.
EOR is often the right model in situations such as:
- Hiring a first employee in a country where the company has no entity
- Expanding into a new market before setting up an entity
- Bringing on international talent while entity registration is still pending
- Hiring in a jurisdiction with complex employment rules or frequent regulatory updates
- Reclassifying a contractor as an employee without first establishing a local entity
The distinction comes down to a handful of dimensions. Here is how the two models compare side by side:
How Payroll Works Under EOR
Under an EOR, the company is not running payroll through its own entity overseas. The employee sits under the EOR’s local entity, so the payslip, payroll filings, taxes, and required contributions are handled there instead.
The client still approves what should be paid for that cycle. That includes salary, bonuses, commissions, and any other variable pay. Once that is confirmed, the EOR runs the local payroll, calculates the required deductions, pays the employee, and sends employer contributions to the relevant authorities.
For the client, the result is usually one invoice. It includes the worker’s full employment cost and the EOR fee. That makes the payroll easier to review, especially when the company is hiring in countries where the finance team does not know every local tax rule or filing requirement.
The funding setup is worth asking about early. Some EOR providers want the salary amount transferred before payroll goes out. Others release payroll first and invoice afterward. When a company is paying people across different countries and currencies, that timing can make a real difference to cash flow.
The EOR-to-Entity Transition: When Payroll Takes Over from EOR
EOR can be a good way to enter a new country, but it is not always the setup a company keeps long term. A company may start with one EOR employee, add more people in the same market, and eventually review whether the per-employee fee still makes sense. At a certain point, running a local entity may become more cost-effective than paying EOR fees for every employee.
That point is not the same everywhere. In a country where entity setup is fairly simple and ongoing compliance work is manageable, it may be worth reviewing the switch once headcount reaches a point where EOR fees begin to outweigh entity costs. In markets with heavier registration, tax, or employment requirements, the calculation usually changes later.
There are also non-cost triggers for the transition:
- Sales functions: Certain revenue-generating activities performed by local workers can create permanent establishment risk that EOR does not fully neutralize. When sales personnel are authorized to negotiate or conclude contracts on behalf of the company, some tax authorities may determine that a taxable presence exists regardless of the EOR structure.
- M&A activity: EOR employment relationships may need special handling during an acquisition because the employees are formally employed by the EOR, not the client company. Companies being acquired or acquiring others need entity structures that can hold employment cleanly.
- Long-term market commitment: At the point where a market is clearly strategic and headcount is growing, entity ownership gives the company direct control over employment terms, benefits design, and local HR operations.
The handover takes time. Employees have to be moved from the EOR setup to the company’s own local entity, payroll needs to switch over, and contracts and benefits are usually reissued under the new registration.
EOR vs Payroll: A Practical Decision Framework
The easiest way to choose between EOR and payroll is to start with the legal setup, not the price. These three questions usually make the answer clear.
1. Do you have a legal entity in the country where you want to hire?
If yes: payrolling and global payroll are on the table. You have the legal foundation. What you need is administrative payroll support.
If no: EOR is usually the safer structure for a full-time or ongoing employment relationship. Payrolling should not be treated as a substitute for a local employer.
2. Will this worker be employed on an ongoing basis, directed by your team, and integrated into your operations?
If yes, regardless of what the contract says: the engagement has the characteristics of employment. Using a payrolling service in a country where you have no entity creates the structural gap described above. An EOR resolves it.
If no, and the engagement is genuinely project-bounded with an independent worker: you may not need EOR or payrolling. Contractor management may be the appropriate structure, and the distinction between contractor and employee is worth assessing under local law before structuring anything.
3. What is the intended duration and trajectory of this hire?
Short-term, defined-scope work through an established entity may fit payrolling. Ongoing employment in a new country usually points to EOR until the entity math changes. For a market the company expects to grow in over the next few years, EOR can support the first hires while the company plans the entity transition.
The decision is not primarily about cost at the point of first hire. It is about which structure correctly holds the employment relationship for the specific context.
A Note on the EOR-PEO Distinction
A common source of confusion, particularly in North American HR contexts: EOR and PEO are not the same model.
A Professional Employer Organization (PEO) operates through co-employment. The PEO and the client company share employer status; the client remains a co-employer and retains legal exposure for employment matters. PEOs are primarily used within the United States, where co-employment is a recognized legal structure.
An EOR is the formal legal employer in the jurisdiction where it operates. Unlike a PEO structure, the client company is not usually treated as a co-employer under the EOR model. This is one reason the EOR model is commonly used for international hiring. Co-employment rules vary by country, and many markets do not treat PEO-style arrangements the same way the U.S. does.
Using these terms interchangeably leads to incorrect assumptions about liability allocation. In an EOR arrangement, the EOR carries the formal employer responsibilities in the foreign country. In a PEO arrangement, the client company remains part of the employer relationship.
How Borderless AI Handles Both
The right model can change by country. A company may need EOR in one market and entity-based payroll in another. Borderless AI helps teams manage both from one system. If a company wants to hire in a country where it has no local entity, Borderless AI can act as the employer of record through its own legal entities across 170+ countries. Because the worker is employed through Borderless AI directly, companies get a clearer employment setup, cleaner contracts, and more consistent payroll and compliance processes.
For companies that already have entities abroad, Borderless AI can also run global payroll under the client’s own entity structure. The platform manages the full payroll cycle, including tax calculations, statutory contributions, multi-currency payments, and payslip generation. There is no salary pre-funding requirement, and both EOR and entity-based payroll can be managed in the same system. This is useful for companies hiring across several countries where the employment setup is not the same everywhere.
Conclusion
EOR and payroll are not two versions of the same service. Payroll is for a country where the company already has a legal way to employ the worker. EOR is for a country where it does not.
So the decision starts with the worker’s location, the company’s entity status there, and whether the company can legally act as the employer in that market.
