EOR vs Contractor

The meeting starts the way these meetings always start. Legal walks in with a spreadsheet of names.

Finance has a column titled “monthly invoice.&#8221 HR has a column titled “tenure.&#8221

Someone, usually the head of People Ops, has the unenviable job of explaining why the person on row seven, who has been billing the same hours every Monday for fourteen months from the same desk in the same Madrid co-working space using a company laptop and a company Slack handle, is technically a contractor.

The room knows the answer before the question lands. That person is an employee in everything but paperwork, and the paperwork is the part that costs you money when a tax authority decides to look.

This article is the working document Sarah Patel keeps open during that meeting.

It is a comparison of what an Employer of Record arrangement actually buys you against what an independent contractor engagement actually exposes you to, with the cost numbers, the legal tests, and the conversion playbook. No abstractions.

No “it depends.” Concrete decisions, country by country.

The employment status question that legal teams keep asking

Every cross-border hiring conversation eventually arrives at the same fork: do you bring this person on as an employee through an Employer of Record, or do you engage them as an independent contractor and pay against an invoice. The choice looks like a procurement decision.

It is not.

It is a tax classification, a labour law classification, and an intellectual property classification rolled into one, and each of the three jurisdictions involved (where the worker sits, where your company is registered, where the work product lands) has its own opinion about which classification is correct.

The cost difference between the two on the surface looks dramatic. A contractor in Lisbon costs roughly what their invoice says.

An EOR-employed person in Lisbon costs the gross salary plus 23.75 percent employer social contributions plus the EOR fee plus statutory holiday pay plus a thirteenth and fourteenth month, which Portuguese law treats as standard.

On a 60,000 EUR base, that is the difference between paying 60,000 a year and paying around 84,000. So why would anyone choose the more expensive route.

The answer is that the contractor figure is only the cheaper number until a tax authority decides the relationship was never really contracting in the first place.

At that point you owe the back social contributions, the back income tax that should have been withheld, the interest, the penalty, and depending on the jurisdiction, the legal notice period and severance you would have owed an employee.

The EOR cost is a known, budgeted, recurring line. The contractor cost is the same recurring line plus a contingent liability that grows every month the misclassification continues. Sarah Patel does not need a definition of either model.

She needs to know where that contingent liability sits on her risk register.

What an independent contractor engagement means legally

An independent contractor is a self-employed individual or a single-member company who invoices you for services on a project, retainer, or hourly basis. There is no employment contract.

There is a services agreement, sometimes called a master services agreement or a statement of work.

The contractor is responsible for their own tax registration, their own social contributions, their own pension, their own equipment, their own insurance, and their own working hours. You pay the invoice gross.

You do not withhold income tax (with rare exceptions like US 1099 reporting thresholds or Indian TDS withholding for non-resident contractors).

The legal relationship is supposed to look like a buyer purchasing a service from a vendor.

The contractor decides when and where they work, brings their own tools, takes on multiple clients, bears business risk if a project goes badly, and can substitute another worker to fulfil the contract.

The more of those tests the relationship fails, the more it starts to look like employment to a tax authority, and the closer you are to a misclassification finding.

The benefits to the company are real and immediate. No employer social contributions, which in France, Germany, and Brazil add 35 to 45 percent on top of gross salary. No statutory holiday pay obligation.

No notice period. No severance. No pension contribution.

No registration with the local labour authority. Termination is the end of a contract period, not a dismissal process. For genuine project-based work or specialist consulting where the relationship is finite and clearly defined, the contractor model is the right tool.

The risk to the company is also real.

If a tax authority later determines the relationship was employment in substance, the company is liable for unpaid employer contributions backdated to day one, employee withholding tax that should have been deducted, interest, fines, and in several jurisdictions, the full notice period and severance the worker would have been entitled to as an employee.

The contractor invoice was always the cheaper number on paper. It was rarely the cheapest number after audit.

IP ownership and confidentiality: differences between employees and contractors

Intellectual property is the second-order issue most companies miss until a senior engineer leaves and takes the codebase architecture with them.

In most common-law jurisdictions, work created by an employee in the course of their employment is owned by the employer by default, with no further paperwork required.

Work created by an independent contractor is owned by the contractor by default, and only transfers to the company through an explicit written assignment in the services agreement.

That sounds like a paperwork problem. It becomes a real problem in three situations.

First, when the contractor agreement was a templated freelance contract pulled off the internet that did not include a present-tense IP assignment clause, leaving a gap that a buyer’s due diligence will find during an acquisition.

Second, when the contractor is in a jurisdiction with moral rights doctrine (France, Germany, Italy, much of continental Europe), where some authorial rights cannot be assigned by contract and require ongoing acknowledgement.

Third, when the contractor used pre-existing tools, libraries, or templates of their own and embedded them in your product, creating a licensing chain you cannot easily extract.

An EOR-employed worker in most jurisdictions creates IP that vests in the EOR (as legal employer), which the EOR-client agreement assigns onward to your company. The chain is clean and tested.

A contractor’s IP transfer is only as clean as the assignment clause in the agreement they signed, the jurisdiction they sit in, and the diligence of whoever drafted that contract three years ago.

Confidentiality is the same story. Employees are bound by implied duties of fidelity and confidentiality during employment, plus whatever survives contractually after termination. Contractors are bound only by the express terms of the services agreement.

If your standard contractor template has a six-month confidentiality clause and the engagement runs for four years, you have a hole.

When contractors are appropriate, and what signals you have crossed the line

The contractor model is the right tool for genuine vendor relationships.

The signals it is the right call: the worker has multiple active clients, sets their own working hours, uses their own equipment, invoices through a registered business entity, takes on real financial risk if the project fails, and is engaged for a defined deliverable rather than ongoing operational work.

The signals that the engagement has crossed the line into employment in substance:

• Time and pattern. The contractor has billed the same hours every week for more than nine months from the same client.
• Integration. The contractor is on the company org chart, attends all-hands, has a company email address, and is listed as a team member externally.
• Control. The company sets working hours, requires presence at specific meetings, and assigns day-to-day tasks rather than reviewing milestone deliverables.
• Equipment and access. The contractor uses a company laptop, company accounts, and company-issued tools and credentials.
• Economic dependence. The client represents more than 70 percent of the contractor’s income, and especially if it represents 100 percent.
• Exclusivity. The contractor is contractually or practically prevented from taking on other clients.
• Personal performance. The contractor cannot send a substitute to do the work without the client’s specific approval.
• Tenure. The relationship has run for more than eighteen months without a clear deliverable boundary.

Three or more of those signals on a single contractor is the threshold at which most cautious legal teams recommend conversion. Five or more is the threshold at which a tax authority would almost certainly find misclassification on audit.

The decision is not whether to convert, but how quickly and with what backdating exposure.

Frequently asked questions

Is an EOR the same as a staffing agency or PEO?

No. A PEO co-employs workers in a country where you already have an entity (US-only model in practice). A staffing agency typically supplies workers on temporary assignment with a different commercial structure.

An EOR is the sole legal employer in a country where you do not have an entity, and the engagement is meant to be ongoing rather than temporary.

Can we use a contractor for the first six months and then convert to EOR?

Only if the first six months is genuinely project-shaped work with a clear scope and deliverables. If it is full-time operational work from day one, the contractor period creates the misclassification evidence you are trying to avoid. The cleaner approach for an open-ended hire is EOR from day one.

Does the worker prefer EOR or contractor?

It varies by country and worker preference. Workers in jurisdictions with strong employment protection (France, Brazil, Germany) often prefer EOR for the security and benefits.

Workers in lighter-touch jurisdictions and senior consultants who optimise for tax efficiency often prefer contractor. Worker preference is not the deciding factor for the company. The legal classification is.

What happens if our contractor incorporates a limited company and invoices through that?

It does not change the misclassification analysis in most jurisdictions. The UK’s IR35 regime explicitly looks through personal service companies. France, Germany, and Brazil all assess the substance of the relationship, not its legal wrapper.

A PSC adds a procurement-friendly layer but does not solve the underlying classification question.

How long does EOR onboarding take compared to contractor?

Contractor signing: same day, once the services agreement is reviewed.

EOR onboarding: typically 5 to 10 business days for standard markets, longer in jurisdictions with mandatory pre-employment medicals (Brazil, parts of Latin America) or work-permit elements (UAE, Saudi Arabia, Singapore for non-residents).

Who carries the misclassification liability if we use an EOR?

The EOR is the legal employer. They carry the employment classification risk for the EOR-employee relationship. Your company carries the risk for any contractor relationships you maintain directly.

An EOR does not retroactively cure misclassification of existing contractors.

It only fixes the going-forward arrangement for workers you move onto it.

What is the conversion timeline if we move ten contractors to EOR across five countries?

Plan for eight to twelve weeks. Two weeks for population review and exposure modelling. Two weeks for EOR vendor selection and contracting.

Three to six weeks for staggered onboarding across jurisdictions, with the longer markets (Brazil, India, Spain) at the back of the queue.

The transition is best run with one project owner, weekly status calls, and a single tracker keeping every worker’s effective date, contract status, and first payroll cycle visible.