Both Employer of Record and Contractor of Record solve the same surface problem: how to engage workers in a country where your company has no legal entity. The models behind that surface are different in ways that determine which one fits your situation and which one creates problems you did not anticipate. Sunbytes provides both EOR and COR arrangements across multiple markets. This article explains how Employer of Record vs Contractor of Record differ legally and operationally, what each costs, and when to choose one over the other.
TL;DR
- An Employer of Record(EOR) is the legal employer of your permanent hire. It holds the employment contract, registers social insurance, withholds income tax, and runs payroll. You retain full operational control. Use EOR when you want to hire someone permanently in a market where you have no legal entity.
- A Contractor of Record formalises a contractor arrangement through a third-party entity, removing misclassification risk from you without creating employment. The COR holds the service agreement. Use COR when the worker is a genuinely independent specialist engaged on a project basis.
- A Dutch SaaS company used EOR for three permanent product managers and COR for two senior contractors building a payment integration across two markets. Six months later, one COR role converted to EOR as the engagement became ongoing. Both transitions happened without entity setup in either country.
What is an Employer of Record (EOR)?
EOR is the structure that makes permanent employment possible in a market where you have no local entity. The EOR’s entity is already in place. It employs your hire on your behalf, manages all statutory obligations, and lets you retain full operational management of the person’s daily work.
The full onboarding process, including what documents are needed and what causes delays, is covered in the EOR onboarding guide.
How EOR works: legal employer vs functional employer
“An Employer of Record is the legal employer of the worker in the target country. It signs the employment contract, registers social insurance, withholds and remits income tax, and processes payroll. You are the functional employer: you set the role, direct daily work, and manage performance.”
The split between legal and functional employers is what makes EOR useful for international hiring. You keep everything that matters operationally. The EOR keeps everything that requires local legal infrastructure: entity, employment contract, tax registration, and compliance administration.
This is not sub-contracting. The worker is employed by the EOR with full statutory protections: social insurance, paid leave, and labor law rights. From the worker’s perspective, the employment relationship is with the EOR. From your perspective, they are fully integrated into your team.
What the EOR handles vs what the client handles
| EOR handles | Client handles | |
|---|---|---|
| Employment | Employment contract under local labor law | Role definition and job responsibilities |
| Compliance | Social insurance registration and contributions | Performance evaluation and goals |
| Payroll | Monthly payroll processing and PIT withholding | Compensation decisions and salary increments |
| Offboarding | Contract termination, deregistration, final pay | Business decision to end the role |
What is a Contractor of Record (COR)?
Misclassification worker risk is reduced when a Contractor of Record (COR) formalises a contractor engagement through a third-party entity, removing misclassification risk without creating an employment relationship. The COR holds the service agreement with the contractor and the commercial agreement with you. The key difference from a direct service contract is where classification liability sits.
The distinction between contractor and employee status, and the risk that builds when contractor arrangements drift toward employment, is covered in detail in the contractor vs freelancer guide.
How COR works: service agreement vs employment contract
“A Contractor of Record holds the service agreement with the contractor and the commercial agreement with you. It handles payments, tax withholding, and compliance documentation. You direct the contractor’s daily work. The COR absorbs the classification risk.”
The fundamental difference from EOR is the legal instrument. EOR uses a labor contract governed by employment law. COR uses a service agreement governed by civil or commercial law. No employment relationship is created. No statutory employment benefits apply, as explained in the Ultimate Guide to Hire Contractors in Vietnam.
That distinction creates a specific risk. In most markets, if working conditions resemble employment, paid work, managerial control, and regular payment, the arrangement will be treated as employment regardless of the contract label. A COR does not protect an arrangement that is functionally employment. It protects a genuinely independent engagement from the compliance liability that builds as duration and integration increase.
What the COR handles vs direct contractor engagement
| COR engagement | Direct contractor engagement | |
|---|---|---|
| Contract | COR signs service agreement with contractor | Client signs directly with contractor |
| Payment | COR pays contractor and withholds applicable tax | Client pays contractor directly |
| Liability | COR absorbs misclassification liability | Client carries full classification risk |
| Documentation | IP assignment and confidentiality handled by COR | Client must structure these directly |
| Offboarding | Handled through COR, completed within 24 hours | Client manages exit directly |
EOR vs COR: The key differences
The EOR vs COR difference is not primarily a cost decision. It is a classification decision. It begins with whether the worker is, or should be, an employee or a genuinely independent specialist. Everything else follows from that.
Legal framework and contract type
EOR operates under employment law in the target country. The worker is a full employee with all statutory protections. COR operates under civil or commercial contract law. No employment relationship exists. No statutory employment benefits apply.
If an arrangement structured as COR is later found to meet the criteria for employment (paid work, management and supervision, and regular payment) the COR entity bears the reclassification liability rather than the client. That protection only works if the engagement is genuinely independent.
Statutory benefits and employer contributions
| EOR | COR | |
|---|---|---|
| Social insurance | Full employer contributions required | Not applicable (no employment relationship) |
| Annual leave | Statutory entitlements apply | Not applicable |
| Income tax | EOR withholds and remits on behalf of worker | COR withholds applicable tax on contractor payments |
| Severance | Applies under local labor law | Not applicable |
| Notice period | Statutory notice applies | As defined in service agreement |
Cost comparison: EOR fees vs COR service fee
EOR costs more per engagement than COR because it carries more compliance infrastructure: social insurance, payroll, employment contract administration, and ongoing labor law compliance. COR is generally lower cost because the structure is simpler.
The cost comparison should not drive the classification decision. If the worker should be an employee, using COR to avoid EOR costs does not reduce liability. It concentrates on it.
Speed of setup
EOR setup for most markets runs 5 to 14 business days for nationals and 3 to 4 weeks for foreign employees requiring a work permit. COR setup runs 5 to 10 business days from agreement to first working day, with no social insurance registration or payroll cycle to initiate.
How to decide: EOR or COR for your global hire?
Knowing when to use EOR vs COR starts with one question: is the worker functionally an employee or a genuinely independent specialist? The Dutch SaaS company in the opening case chose EOR for its product managers because they were permanent team members integrated into the product function, using company tools, and working exclusively for the company. It chose COR for the two contractors building a payment integration because they had defined scope, milestone-based payment, and visible parallel client work.
When EOR is the right model
Use EOR when: the worker will be a permanent or long-term member of your team; the role involves daily management direction from your company; the worker uses your tools and systems; and the engagement has no defined endpoint. If someone is working as part of your team in every practical sense, they should be employed.
When COR is the right model
Use COR when: the worker is a genuinely independent specialist with a defined scope; the engagement has an expected endpoint; payment is milestone or deliverable-based; and the contractor maintains other client relationships simultaneously. COR is also the right model when engagement duration is uncertain and you want to absorb classification risk while the role’s long-term nature becomes clear.
When you need both (and how to transition between them)
Many international companies use both models simultaneously: EOR for permanent team members, COR for specialist contractors engaged on a project basis. Transitioning from COR to EOR happens when a contractor role becomes ongoing or the client wants to offer a permanent position. When both models are managed through the same provider, the transition is straightforward: the COR agreement ends and the EOR arrangement begins with minimal disruption to the working relationship.
Hiring permanently in a new market or retaining a specialist contractor across borders?
Sunbytes provides both EOR and COR under its own legal entity. No local entity required. Compliant from day one. Both models are available through a single provider across multiple markets.
Explore Accelerate Workforce Solutions
How Sunbytes handles EOR and COR globally
EOR and COR solve different problems. Having both through the same provider means you do not need to restructure vendor relationships when a contractor role converts to permanent employment, or when your hiring mix changes as the team grows.
Sunbytes is a Dutch-founded technology and workforce company founded in 2011, with 300+ client projects across 20+ countries.
- Through Accelerate Workforce Solutions, Sunbytes provides both EOR and COR arrangements through its own legal entities. Employment contracts issued within 48 hours. Payroll on time every cycle. COR service agreements include IP assignment and confidentiality clauses.
- For companies whose EOR or COR need is in engineering or technical roles, Digital Transformation Solutions sources candidates through active networks. The employment or contracting structure is matched to the role once the candidate is identified.
Employment and contractor documents move between client and provider entities across jurisdictions. CyberSecurity Solutions embeds applicable data protection requirements into both EOR and COR engagement processes from the first document exchange.
FAQs
An EOR creates an employment relationship. The worker is a full employee with all statutory protections including social insurance, paid leave, and notice entitlements. A COR creates a service relationship. The contractor is engaged under a civil service agreement. No employment relationship exists and no statutory benefits apply.
Using COR for a worker who is functionally permanent does not eliminate employment liability. It puts the liability in the wrong place.
No. Both EOR and COR are designed specifically for companies without a local entity in the target market. The EOR holds the employment relationship. The COR holds the service agreement. In both models, the client has no direct employment or contracting relationship with the worker.
COR is typically cheaper per engagement because it carries less compliance infrastructure. EOR includes social insurance, payroll, and ongoing labor law compliance management, which costs more. The cost comparison matters less than the classification question. If the worker should be employed, using COR to reduce cost creates liability that exceeds the saving.
Yes, and this is a common transition. When a contractor role becomes ongoing, when the contractor becomes integrated into the team, or when the client wants to offer a permanent position, the COR agreement ends and EOR employment begins. When both models are managed through the same provider, Sunbytes handles the transition without a gap in the working arrangement.
It depends on the nature of the role. For permanent team members, EOR is the right structure. For specialist contractors engaged on a defined project, COR is appropriate. When duration is uncertain and working conditions may evolve toward employment, beginning with COR and transitioning to EOR at the three-month review is the most defensible approach.
Let’s start with Sunbytes
Let us know your requirements for the team and we will contact you right away.
