Key Takeaways
- An Employer of Record becomes the legal employer on record, handling payroll, taxes, and compliance while the client retains day-to-day management of the worker.
- A Contractor of Record manages contractor agreements and payments but does not create an employment relationship—the worker stays independent.
- A COR contract does not eliminate misclassification risk; if the working relationship resembles employment, regulators can reclassify the worker regardless of the label.
- EOR lets companies employ workers in a new country in weeks, without setting up a local legal entity.
- U.S. DOL classification regulations took effect March 11, 2024, and a February 2026 NPRM signals further rule changes—companies using COR arrangements should monitor developments in each jurisdiction.
What Is an Employer of Record (EOR)?
An Employer of Record (EOR) is a third-party company that becomes the legal employer for a worker in a given country. The EOR holds the employment contract, runs payroll, files taxes, administers statutory and supplemental benefits, and owns every compliance obligation in that jurisdiction. The worker's paycheck comes from the EOR, and all regulatory filings go through the EOR. The client pays a monthly fee that bundles salary, payroll taxes, benefits administration, and the provider's compliance work.
The client company is not the legal employer, but it keeps full operational control. Day-to-day management, task direction, and IP ownership all remain with the client. The EOR is the legal employer on paper—not the manager in practice.
The practical consequence is significant: a company can employ someone in a country where it has no registered entity. There is no need to incorporate locally, appoint directors, or open a local bank account before making the hire. EOR onboarding typically takes weeks rather than months, which matters when a strong candidate is already in conversation with other companies.
One boundary worth noting: the EOR does not recruit. The client identifies the candidate through its own process. The EOR steps in once the hiring decision is made to handle everything that follows. Gloroots offers Global Employer of Record (EOR) services for companies running employment across multiple countries. For a detailed walkthrough of how the model works in practice, see how EOR works.
What Is a Contractor of Record (COR)?
A Contractor of Record (COR) is a model where the provider acts as the legal contracting entity for an independent contractor or freelancer. The COR manages service agreements, processes invoices, executes payments, and handles compliance with local freelance regulations. It does not employ the worker.
That distinction matters. The worker remains an independent contractor throughout the engagement. No employment relationship is created, which means the worker does not receive employee benefits—no health insurance, no paid leave, no statutory protections that apply to employees under local labor law. Under the U.S. Fair Labor Standards Act, for example, independent contractors are in business for themselves and are not covered by FLSA minimum wage or overtime requirements.
Because no employment relationship exists, the COR carries less legal responsibility than an EOR. The provider manages the administrative layer—contracts, payments, tax filings—but the compliance obligations that come with employing someone do not apply.
Some vendors market this model as an Agent of Record (AOR). The name differs; the underlying structure is the same.
Why 'Company of Record' Causes Naming Confusion
Some vendors use the phrase Company of Record loosely in their marketing materials, treating it as a synonym for Employer of Record. That usage creates real confusion when a founder searches for a COR comparison and lands on EOR content instead.
Throughout this article, COR means Contractor of Record—a model that keeps the worker as an independent contractor with no employment relationship.
When evaluating a vendor that uses the term Company of Record, ask directly: does this arrangement create an employment relationship, or does the worker remain an independent contractor? The answer determines which compliance obligations apply, what the worker receives, and what liability the company carries. EOR and COR serve different workforce needs and carry distinct compliance responsibilities—the label a vendor chooses does not change that.
EOR vs COR: How the Two Models Compare
| Dimension | EOR (Employer of Record) | COR (Contractor of Record) |
|---|---|---|
| Legal employer status | Provider is the legal employer | Provider is the contracting entity, not the employer |
| Contract held by | Employment contract with the EOR | Service agreement with the COR |
| Payroll and tax filing | EOR runs payroll and files taxes in the worker's country | COR processes invoices and payments; no payroll relationship |
| Benefits administration | EOR administers statutory and supplemental benefits | No employee benefits; worker is not entitled to them |
| Worker rights and protections | Worker covered by local labor law as an employee | Worker not covered by employment law protections |
| Misclassification risk | Lower; employment relationship is properly established | Risk remains if the working relationship is employee-like |
| Speed to onboard | Typically weeks | Generally faster; no employment setup required |
| Cost structure | Monthly per-employee fee bundling salary, payroll taxes, benefits, and compliance | Typically lower per-engagement cost; no benefits overhead |
| Best-fit engagement type | Long-term, integrated roles | Variable, project-based, or skills-specific engagements |
The Legal Mechanics: Worker Classification and Misclassification Risk
Under the U.S. Fair Labor Standards Act (FLSA), worker classification is not determined by what a contract says. It is determined by the economic reality of the working relationship. If a worker is economically dependent on the company for work, the FLSA treats that person as an employee. If the worker genuinely operates as an independent business—serving multiple clients, controlling their own methods, bearing their own financial risk—they are an independent contractor.
The U.S. Department of Labor formalized this multi-factor economic reality analysis in regulations that took effect on March 11, 2024 (29 CFR part 795). On February 26, 2026, the DOL published a Notice of Proposed Rulemaking (91 FR 9932) covering classification under the FLSA, the Family and Medical Leave Act, and the Migrant and Seasonal Agricultural Worker Protection Act. That NPRM signals further regulatory evolution. Companies relying on contractor arrangements should monitor rule changes in each jurisdiction where they engage workers.
A COR contract does not resolve this. If the working relationship looks like employment—exclusive engagement, set hours, company-controlled tools, daily direction from a manager—regulators can reclassify the worker regardless of what the service agreement says. The contract label does not determine status; the economic reality does.
The consequences of misclassification are material: audits, back taxes, fines, and legal disputes. Governments worldwide have intensified enforcement. The cost of getting classification wrong typically exceeds the cost of structuring it correctly from the start.
This section covers U.S. federal law. Classification rules vary by jurisdiction. Seek local legal advice for each country where workers are engaged.
Permanent Establishment and IP Assignment: Two Risks Operators Often Miss
Two compliance risks sit outside the basic EOR/COR definition but affect the hiring decision in ways that matter to a company's tax position and asset ownership.
Permanent establishment (PE) risk. If a worker's activities in a country create a taxable presence for the client company, the company may owe corporate tax in that jurisdiction—even without a registered entity there. EOR providers typically structure engagements to minimize PE exposure. COR arrangements carry their own PE considerations depending on what the contractor does and how they do it. PE rules are jurisdiction-specific and fact-dependent. Verify the implications with local tax counsel before engaging workers in a new country.
IP assignment. Under an EOR arrangement, the client retains IP ownership. The EOR is the legal employer, not the IP owner, and the employment contract is structured accordingly. Under a COR arrangement, IP assignment must be addressed explicitly in the service agreement. Work-for-hire rules vary by country and do not automatically transfer IP to the client. If the service agreement is silent on IP, the contractor may retain rights to work they produced. Review IP assignment terms before any engagement begins, and confirm that local law supports the assignment mechanism used.
Neither of these risks is a reason to avoid international hiring. They are reasons to structure it correctly and verify the details with qualified counsel in each jurisdiction.
When to Use EOR vs COR: A Decision Framework
The right model depends on the nature of the working relationship, not on which option costs less upfront. Use the signals below to assess each engagement.
Use EOR when:
- The role is long-term and integrated into the team's day-to-day work.
- The worker will use company tools, follow company schedules, or report to a manager regularly.
- The country has strong labor protections that require statutory benefits.
- The company wants to offer the worker a career path or convert them to a permanent hire.
- The jurisdiction has a high misclassification enforcement risk and the working relationship could be read as employment.
Use COR when:
- The engagement is project-based or time-limited with a defined deliverable.
- The worker serves multiple clients and genuinely operates as an independent business.
- The company needs a specific skill for a bounded scope of work.
- The engagement is unlikely to become ongoing or exclusive.
When the status is genuinely ambiguous, treat that ambiguity as a signal. If it is not clear whether the relationship is employment or contracting, the cost of misclassification—audits, back taxes, fines, and legal disputes—typically exceeds the cost of structuring the engagement as employment through an EOR. Default to EOR or seek legal advice before proceeding. EOR and COR serve different workforce needs and carry distinct compliance responsibilities; the choice has consequences that extend well beyond the initial contract.
For founders evaluating their first international hire, see EOR for startups for context specific to early-stage companies.
Running EOR and COR Together: The Hybrid Workforce Model
EOR and COR are not mutually exclusive. Many companies run both models simultaneously, and in 2026 that hybrid approach has become a standard way to build global teams with different worker types.
In practice, a hybrid workforce looks like this: a core group of full-time employees managed through EOR in key markets, supported by COR-managed contractors brought in for specific projects or skills gaps. The EOR layer covers roles that are integrated, ongoing, and require statutory benefits. The COR layer covers variable, skills-based engagements where the worker genuinely operates independently.
The model also creates a natural conversion path. When a contractor engagement becomes ongoing, when the worker becomes economically dependent on the company, or when the company wants to offer benefits and a career path, converting to employment through an EOR is the appropriate step. That conversion does not require setting up a local entity—the EOR handles the employment infrastructure—and can typically be completed in weeks rather than months.
Leading providers now offer both EOR and COR services on a single platform. That means a company can manage its full workforce through one vendor and transition workers between models as business needs change, without switching providers or rebuilding compliance processes from scratch.
How to Evaluate a Provider for EOR or COR
Gloroots positions its services around centralized employment governance—giving companies visibility and control across their global workforce from a single platform. When evaluating any provider, apply the criteria below before committing.
Entity ownership. Ask whether the provider owns its legal entities in the countries you need, or relies on third-party partners. Owned entities typically mean faster onboarding, cleaner compliance accountability, and a shorter chain of responsibility when something goes wrong.
Country depth. Coverage count is less useful than depth. Ask about payroll accuracy rates, local legal expertise, and how the provider handles country-specific statutory requirements—termination rules, mandatory benefits, notice periods. A provider that covers 150 countries but handles each one through a subcontractor may offer less protection than one with deep in-country operations in the markets you actually need.
Termination and offboarding support. Ask how the provider manages terminations, severance calculations, and offboarding in each country. Compliance risk concentrates at the end of an employment relationship, not the beginning.
Data privacy and IP assignment. Confirm that the provider's contracts include explicit IP assignment clauses and comply with local data privacy regulations—GDPR in Europe, for example. Do not assume these are standard.
Pricing transparency. Ask for an all-in per-employee cost that includes salary, payroll taxes, benefits administration, and the provider fee. The EOR model bundles these into a monthly fee; hidden additions to that fee are a common source of friction. For a detailed breakdown of what EOR pricing typically includes, see EOR cost explained. For a curated comparison of providers, see top EOR providers.
Compliance Trends to Watch in 2026 and Beyond
Worker classification rules are not static. Companies that set up contractor arrangements and then leave them unchanged are exposed to regulatory shifts that can change the compliance picture mid-engagement.
On February 26, 2026, the U.S. Department of Labor published a Notice of Proposed Rulemaking (91 FR 9932) covering worker classification under the FLSA, the Family and Medical Leave Act, and the Migrant and Seasonal Agricultural Worker Protection Act. The NPRM signals that U.S. classification rules remain under active review. Companies relying on COR arrangements in the U.S. should track the rulemaking and assess whether their contractor engagements remain correctly structured as the rules evolve.
Beyond the U.S., governments worldwide have intensified enforcement of worker classification rules. Misclassification is more costly to resolve than it was in prior years—audits, back taxes, fines, and legal disputes are the documented outcomes.
The practical response is to build a review cadence into workforce governance. Classification rules that applied when a contractor was first engaged may change during the engagement. A periodic review—at least annually, and whenever a jurisdiction signals regulatory activity—reduces the risk of being caught with an arrangement that no longer meets current standards.
Frequently Asked Questions
Is a Contractor of Record the same as an Employer of Record?
No. An EOR creates a full employment relationship—the provider is the legal employer, and the worker receives employee benefits and statutory protections. A COR keeps the worker as an independent contractor; no employment relationship is created and no employee benefits apply. The two models carry different compliance obligations, different cost structures, and different levels of legal responsibility for the provider.
Can a COR fully protect a company from misclassification liability?
No. A COR manages contractor administration—agreements, payments, local filings—but does not eliminate misclassification risk. Under the U.S. FLSA, classification is determined by the economic reality of the working relationship, not the contract label. If the engagement is exclusive, the hours are set by the company, or the tools are company-controlled, regulators can reclassify the worker as an employee regardless of what the service agreement says. Equivalent rules apply in most other jurisdictions.
When should a company convert a contractor to an employee through an EOR?
Convert when the engagement shifts from project-based to ongoing, when the worker becomes economically dependent on the company, or when the company wants to offer benefits and a career path. Conversion through an EOR does not require setting up a local entity and can typically be completed in weeks. Many providers that offer both EOR and COR services support this transition within the same platform.
Does using an EOR create a permanent establishment risk?
EOR providers typically structure engagements to minimize permanent establishment (PE) risk. However, PE exposure depends on the nature of the worker's activities in the country, not solely on the employment model used. Companies should verify PE implications with local tax counsel for each jurisdiction where they employ workers.
What is the difference between an EOR and a PEO?
A Professional Employer Organization (PEO) operates as a co-employer and typically requires the client company to have an existing legal entity in the country. An EOR is the sole legal employer and does not require the client to have a local entity. For international hiring without a local presence, EOR is the appropriate model.
How long does it take to onboard an employee through an EOR?
EOR onboarding typically takes weeks rather than months. The exact timeline depends on the country, the complexity of the role, and how quickly the client completes its own hiring process. The EOR handles compliance, contracts, and payroll setup. The client is responsible for identifying the candidate—the EOR does not recruit.
Can one provider handle both EOR and COR engagements?
Yes. Many providers now offer both EOR and COR services, allowing companies to manage employees and contractors through a single platform. This also supports transitions between models—for example, converting a contractor to an employee through EOR—without switching vendors or rebuilding compliance processes.
Ready to take the first step?
Request a demo now and learn how you can focus on building, without worrying for compliance, ever!
