Umbrella, EOR, domiciliation, intermediary: which model for a non-EU freelancer

Introduction

You've identified the right non-EU tech freelancer, but your firm can't contract them cleanly on its own.

The topic isn't just administrative. It touches on the subcontracting chain, supplier compliance, taxation, intellectual property, GDPR, the permanent-establishment risk and the reclassification risk if the mission looks like staff secondment.

Several models are then considered: umbrella employment, EOR, domiciliation, direct subcontracting or a contracting intermediary. They don't answer the same need. They don't carry the same risks.

The goal of this article is to compare these collaboration models for a French IT services firm that wants to work with a tech freelancer based outside the EU — for example in Dubai, Bali or another third country.

Compliance box This article provides general information. It does not constitute personalised legal, tax or social advice. Any structuring must be validated against the parties' real situation, the freelancer's effective location, the content of the mission and the applicable contracts.

The real problem for the firm: contracting without weakening the value chain

For a firm, the difficulty isn't just to pay a non-EU freelancer.

The difficulty is to integrate them into a compliant B2B contractual chain that's readable for the end client, acceptable to procurement, usable by finance and robust in the event of an inspection.

In practice, the frictions are often the same:

• the freelancer has no French company;
• their entity is located outside the EU;
• procurement refuses a non-European supplier;
• the foreign invoice blocks accounting;
• the VAT or reverse-charge treatment must be understood;
• the confidentiality, intellectual property and security clauses must be aligned;
• the end client asks for transparency on subcontracting;
• the mission is on a day rate, but must legally remain a service;
• the freelancer is independent, but must not be treated as an integrated employee.

The choice of model must therefore not start from commercial convenience. It must start from the real legal framework.

The models to compare

To bring in a non-EU tech freelancer, a firm generally encounters four options.

1. Umbrella employment.
2. EOR.
3. Domiciliation or setting up a local structure.
4. A contracting intermediary in B2B subcontracting.

These models aren't interchangeable.

Umbrella employment and EOR rest on an employment logic. Domiciliation rests on an address or administrative-appearance logic. The contracting intermediary rests on a structured B2B service logic.

It's this distinction that avoids confusion.

Umbrella employment: useful in some cases, but not suited to every non-EU freelancer

Umbrella employment ("portage salarial") is a model governed by the French Labour Code. It involves a tripartite relationship with an employed professional, an umbrella company and a client company.

The professional becomes an employee of the umbrella company. They receive a salary. The umbrella company takes on employer obligations.

This model can be relevant when the consultant accepts employee status and the mission falls within the legal framework for umbrella employment.

But for a firm that wants to contract with an already-independent tech freelancer based outside the EU, umbrella employment can pose several limits.

The limits of umbrella employment for a non-EU freelancer

Umbrella employment involves an employment contract. It isn't a mere administrative wrapper.

It notably assumes:

• a consistent social-security attachment;
• an employment relationship compatible with the place of execution;
• payroll management;
• the application of social-security rules;
• a structuring compliant with labour law.

If the freelancer is already a genuine non-EU tax resident, works remotely from their country of residence and wants to keep their independent activity, umbrella employment isn't necessarily the right model.

It can also create confusion in the contractual chain. The firm often looks for a supplier or a subcontractor, not an employed professional.

Key takeaway Umbrella employment isn't a mere way to "make a foreign freelancer invoiceable". It's an employment model. It should be used when this logic genuinely matches the situation.

EOR: an employment solution, not B2B subcontracting

EOR, or Employer of Record, consists in having a person employed by a third-party entity, often in the country where they're based.

The EOR becomes the administrative employer. It handles the local employment contract, payroll, social-security obligations and certain HR aspects.

This model is useful when a company wants to recruit an employee in a country where it has no local entity.

But that isn't the same need as a firm wanting to subcontract a mission to an independent tech freelancer.

Why EOR may not suit a firm

EOR turns the relationship into an employment logic.

That can be consistent if the goal is to recruit a person as a local employee. But if the goal is to contract a service with deliverables, milestones and outcome responsibility, EOR isn't always the suitable model.

For a firm, several questions arise:

• who actually carries the responsibility for the service?
• who guarantees the compliance of the deliverables?
• who signs the confidentiality and intellectual property commitments?
• who is responsible towards the end client?
• how does the mission fit with the firm's main contract?

EOR answers an HR problem. B2B subcontracting answers a supplier problem.

These are two different logics.

Domiciliation: an address doesn't create economic substance

Domiciliation consists in assigning an administrative address to a business. It can be useful to receive mail, register a structure or have a professional address.

But domiciliation doesn't solve the substance of the topic.

It doesn't automatically create:

• real economic substance;
• robust contractual capacity;
• tax compliance;
• a secure subcontracting relationship;
• risk management for the firm;
• an invoicing chain acceptable to procurement.

For a firm, accepting a company domiciled in France or elsewhere isn't enough. You have to understand who actually works, from where the mission is carried out, where decisions are made, where the effective tax residence is and whether the entity has an operational reality.

The shell-entity risk

Creating or using a front company to mask the real situation is a bad practice.

If the freelancer lives in France, works from France, decides from France, but invoices through a foreign entity with no substance, the configuration can be abusive. It can expose the parties to tax and social-security risks.

Conversely, a sound configuration rests on consistent facts.

The freelancer is a genuine non-EU tax resident. They effectively live in their country of residence. They carry out their activity there remotely. They have no organised presence in France. They don't simulate a foreign base.

Tax box A non-EU freelancer's local tax rate isn't a product sold by an intermediary. It depends on their genuine tax residence, their personal situation and the law applicable in their country. The basic rule remains reality: effective residence, genuine presence, activity carried out remotely, absence of an artificial organisation in France.

Direct subcontracting with the non-EU freelancer: possible, but often blocking for the firm

A firm can sometimes contract directly with a non-EU freelancer or company.

On paper, it's the simplest model. In practice, it's often blocked by internal processes.

The reasons are frequent:

• the supplier is outside the procurement repository;
• KYC or KYB compliance is incomplete;
• sanctions or anti-corruption checks are difficult;
• insurance isn't aligned;
• the intellectual property clauses aren't sufficient;
• the governing law and jurisdiction pose problems;
• the foreign invoice generates specific accounting handling;
• the VAT reverse charge must be correctly handled;
• the end client refuses certain levels of international subcontracting.

Direct subcontracting isn't impossible, then. But it assumes the firm accepts carrying the supplier complexity itself.

For a one-off, low-stakes mission, this can sometimes be acceptable. For a critical, long mission integrated into a demanding end-client contract, the topic becomes more sensitive.

The contracting intermediary: a B2B logic suited to non-EU tech freelancers

The contracting intermediary answers a specific need: letting a French firm contract with a French supplier, while bringing in an independent tech freelancer based outside the EU within a structured B2B framework.

This model doesn't rest on an employment contract. It doesn't rest on domiciliation. It doesn't rest on an EOR. It doesn't consist in representing the freelancer in France.

It rests on a chain of contracts.

The intermediary contracts in its own name with the firm. It invoices the firm. It contracts separately with the non-EU freelancer. It aligns the essential commitments back-to-back where necessary: confidentiality, intellectual property, security, compliance, deliverables, deadlines, payment conditions, liability.

This is the model StelarWork fits into.

StelarWork is a French company (SASU) that steps onto the contract between a French firm and a tech freelancer based outside the EU. It invoices the firm, pays the freelancer, carries the operational compliance of the scheme and aims to reduce the contractual risk for the firm.

StelarWork doesn't employ the freelancer. StelarWork isn't an umbrella company. StelarWork isn't an EOR. StelarWork isn't a domiciliation solution. StelarWork doesn't sign in the freelancer's name. StelarWork contracts in its own name.

Comparison of the collaboration models

Model	Main logic	When it's relevant	Points of attention for a firm
Umbrella employment	Employed professional	A consultant accepting employee status within a compatible framework	Not suited to every independent non-EU freelancer; social-security obligations; employment relationship
EOR	Local employment via a third party	Recruiting a person as an employee in a foreign country	Less suited to a B2B service; HR management rather than supplier
Domiciliation	Administrative address	Need for an address or registration	Doesn't create substance; doesn't solve supplier compliance
Direct non-EU subcontracting	Direct contract with the freelancer or their entity	A firm able to manage a foreign supplier, taxation, compliance and risks	Procurement onboarding, VAT, governing law, IP, due diligence, disputes
Contracting intermediary	B2B service via a French supplier	A firm wanting to contract with a French structure while working with a non-EU freelancer	Must remain a service, with deliverables, governance and consistent contracts

The central point: service, deliverables and responsibility

For a firm, the contractual vocabulary isn't a detail.

A mission with a non-EU freelancer must not be structured as staff secondment. It must be conceived as a service.

That implies:

• a purchase order;
• a mission description;
• identifiable deliverables or objectives;
• milestones where relevant;
• service governance;
• validation of the work;
• confidentiality clauses;
• intellectual property clauses;
• suitable contractual liability.

The day rate can be used as an economic term. But it must not obscure the nature of the relationship: a provision of services, not employment integration.

This distinction is important to limit the risks of reclassification, unlawful labour lending or unlawful labour supply.

Social-risk box The risk doesn't come from a freelancer working with a firm. It comes from a poorly structured relationship: absence of deliverables, direct hierarchical integration, total operational dependence, control like an employee, absence of the supplier's own responsibility. The contract and the execution must stay consistent.

The permanent-establishment risk: not creating an artificial presence in France

When a foreign freelancer or company works with a French firm, the permanent-establishment question can arise.

The risk rises if a person or entity in France acts as the foreign freelancer's dependent representative, concludes contracts in their name or creates an organised economic presence in France for them.

It's precisely to avoid this ambiguity that a contracting intermediary must contract in its own name.

In the StelarWork model, StelarWork doesn't act as the freelancer's representative. It doesn't conclude contracts in the freelancer's name. It isn't their dependent agent. It establishes its own contractual relationship with the firm and its own contractual relationship with the freelancer.

This distinction is structuring.

It avoids confusion between:

• a representative who binds the freelancer;
• and a French supplier who buys a service from a foreign freelancer to perform its own contractual commitment.

The non-EU freelancer's taxation: the reality principle

The freelancer's taxation depends first on their genuine tax residence.

A sound configuration assumes the freelancer:

• effectively resides outside the EU;
• spends most of their time in their country of residence;
• genuinely works remotely from that country;
• has no organised presence in France;
• doesn't conceal an activity carried out from France;
• has, where applicable, a structure consistent with their real activity.

The 183-day threshold is often used as an international benchmark, but on its own it isn't enough. Depending on the country, other criteria can matter: home, centre of economic interests, place where the activity is habitually carried out, place of effective management, family or asset ties.

An abusive configuration would be different.

For example: a consultant lives in France, works from France, uses a foreign entity with no substance, invoices as if they were abroad and claims to fall under non-EU taxation. This situation isn't optimisation. It can be fraud.

StelarWork does not sell tax avoidance. StelarWork doesn't transform a tax residence. StelarWork doesn't create a foreign tax rate.

StelarWork steps in when the freelancer is already in a genuine and consistent non-EU situation, and the firm needs a French contractual framework to work with them.

VAT, invoicing and reverse charge: what the firm must look at

Invoicing is often the first operational block.

When a firm buys a service directly from a non-EU supplier, specific rules can apply, notably regarding the VAT reverse charge for services between taxable persons. The treatment depends on the nature of the service, the location of the parties and the applicable rules.

When the firm contracts with a French supplier, the invoicing chain becomes more readable for its internal teams. The French supplier issues an invoice compliant with the framework applicable in France. Accounting departments handle a local supplier, subject to the usual checks.

This doesn't remove the compliance obligations. It makes them more practical to manage.

The important thing is to document the flows:

• who invoices whom;
• which service is invoiced;
• which contract supports the invoice;
• which VAT treatment is applied;
• which proof of execution exists;
• which deliverables or validations justify the payment.

Supplier due diligence: why a French supplier can simplify onboarding

Firms often have demanding procurement processes.

Even when the freelancer is excellent, their onboarding can fail if their status doesn't match internal criteria.

The most common sticking points are:

• no usable registration extract;
• foreign documents that are hard to verify;
• non-compliant professional insurance;
• absence of standard clauses;
• international-payment difficulties;
• doubts about tax residence;
• difficulty formalising subcontracting with the end client;
• absence of aligned contractual guarantees.

A French contracting intermediary can simplify this step.

The firm contracts with an identifiable French company, subject to a known legal framework, able to take on the necessary commitments and set up a back-to-back relationship with the freelancer.

This point is often decisive for procurement, finance and the legal department.

The clauses to frame in a contracting-intermediary model

A good model doesn't rest only on a French invoice.

It rests on consistent contracts.

The important clauses notably include:

• the object of the service;
• the expected deliverables;
• the validation terms;
• confidentiality;
• intellectual property;
• IT security;
• GDPR, when personal data is processed;
• anti-corruption;
• international sanctions;
• cooperation obligations;
• payment conditions;
• liability limits;
• termination;
• governing law;
• dispute management.

The back-to-back contract is important.

If the firm imposes obligations on the supplier, the supplier must be able to pass them down consistently to the freelancer who delivers the service. Without that, the contractual chain becomes fragile.

GDPR and security: don't forget the place of execution

A non-EU freelancer can have access to technical environments, code, internal tools or personal data.

The GDPR question must therefore be handled from the framing stage.

You must in particular identify:

• whether personal data is processed;
• what role each party plays;
• whether a transfer outside the EU exists;
• which contractual guarantees are necessary;
• which security measures are required;
• which access is opened;
• how access is revoked at the end of the mission.

Here too, reality prevails.

A freelancer based outside the EU who accesses data from their country of residence can trigger specific obligations. These obligations must be analysed before the mission is carried out.

End client: preserving transparency in the subcontracting chain

A firm often acts within a contract concluded with an end client.

Before adding a non-EU freelancer to the chain, you have to check the rules of the main contract.

Some clauses impose:

• prior subcontracting authorisation;
• informing the end client;
• geographical restrictions;
• security requirements;
• reinforced confidentiality obligations;
• reversibility rules;
• data location;
• supplier approval.

A contracting intermediary must not serve to mask subcontracting. It must allow it to be structured cleanly.

For a firm, transparency is often more protective than opacity.

When to choose which model?

The right model depends on the reality of the collaboration.

Choosing umbrella employment

Umbrella employment can be considered if the professional accepts an employment logic and the mission falls within the applicable legal framework.

It's less natural when the freelancer is already independent, based outside the EU and wants to keep a B2B relationship.

Choosing EOR

EOR is relevant when a company wants to employ someone in a foreign country without creating a local entity.

It's less suited if the goal is to buy an independent service in a B2B subcontracting chain.

Choosing domiciliation

Domiciliation can meet a limited administrative need.

It must not be used to create an artificial appearance of presence or mask the real place of activity.

Choosing direct subcontracting

Direct subcontracting can work if the firm accepts managing a non-EU supplier and has the internal resources to handle the contractual, tax, compliance and operational aspects.

It can be heavy when procurement or the end client requires a French supplier.

Choosing the contracting intermediary

The contracting intermediary is relevant when the firm wants to work with an already-identified non-EU tech freelancer, but wishes to contract with a French supplier.

It's a useful model when the main topic isn't to recruit, domicile or employ, but to make the B2B relationship contractable and compliant.

What StelarWork brings in this framework

StelarWork acts as a French supplier between a French firm and a tech freelancer based outside the EU.

Concretely, StelarWork:

• contracts in its own name with the firm;
• invoices the firm;
• contracts separately with the freelancer;
• pays the freelancer under the agreed conditions;
• structures the relationship as a service;
• aligns the essential contractual obligations;
• eases supplier onboarding on the firm's side;
• helps document the compliance of the relationship.

The freelancer remains independent. The firm has a French supplier. The mission is structured as a service, with a more readable contractual framework.

StelarWork doesn't replace the parties' legal, tax or social analysis. The model aims to reduce friction and frame the relationship, without masking the reality of the mission.

Mistakes to avoid

Several mistakes come up often when a firm wants to bring in a non-EU tech freelancer.

Believing an address is enough

Domiciliation doesn't solve tax residence, economic substance, supplier compliance or contractual obligations.

Confusing employment and service

Umbrella employment and EOR are employment models. They must not be used as mere wrappers of a B2B relationship if reality doesn't match.

Treating the freelancer as an internal employee

Even with a day rate, the relationship must stay structured around a service. Deliverables, governance and the supplier's responsibility are essential.

Masking the real location

If the freelancer works from abroad, that must be owned and handled. If the freelancer actually works from France, you must not build a foreign fiction.

Forgetting the end-client contract

The firm must check its obligations towards the end client before integrating a subcontractor into the chain.

Neglecting intellectual property

On tech missions, the transfer or licensing of rights over the code, documentation, developments and deliverables must be clear.

Summary: the right model depends on the reality of the relationship

The choice between umbrella employment, EOR, domiciliation, direct subcontracting and an intermediary must not be made on a criterion of apparent simplicity.

It must be made from the real relationship.

If you want to employ a person, EOR or umbrella employment can be studied. If you only need an address, domiciliation can meet a limited need. If you can manage a non-EU supplier, direct subcontracting can work. If you want to work with a non-EU tech freelancer while contracting with a French supplier, the contracting intermediary is often the most consistent model.

StelarWork fits this last logic.

The goal isn't to artificially transform the freelancer's situation. The goal is to remove a contractual and administrative friction for the firm, when the non-EU freelancer's real situation is sound, documentable and compatible with a B2B service.

FAQ

Is StelarWork umbrella employment?

No. StelarWork isn't an umbrella company.

There is no employment contract between StelarWork and the freelancer. There is no salary. There is no employed-professional status.

StelarWork acts as a French supplier in a B2B service chain.

What's the difference between StelarWork and an EOR?

An EOR employs a person locally on a company's behalf. It's an HR and employment logic.

StelarWork doesn't employ the freelancer. StelarWork contracts in its own name with the firm and separately with the independent freelancer. The framework is that of a B2B service.

Is domiciliation enough to make a non-EU freelancer acceptable to a firm?

No. An address isn't enough.

Domiciliation doesn't create economic substance, doesn't solve tax residence, doesn't secure intellectual property and doesn't replace a consistent service contract.

Does StelarWork let a freelancer pay 0% tax?

No. StelarWork doesn't sell tax optimisation and doesn't transform a freelancer's tax residence.

If a freelancer is already a genuine tax resident in a non-EU country, their taxation depends on their personal situation and the applicable local law. StelarWork only steps in to remove a contractual and administrative friction on the firm's side, in a genuine and documentable configuration.

Can a freelancer based in Dubai or Bali work for a French firm?

Yes, subject to a consistent framework.

You must in particular check the freelancer's genuine residence, the place of execution of the mission, the end-client contract's obligations, the applicable taxation, GDPR, intellectual property and the structuring of the service.

Can the firm impose its clauses on the freelancer?

The necessary clauses can be aligned back-to-back where relevant.

This notably concerns confidentiality, intellectual property, security, GDPR, end-client requirements and certain compliance obligations.

Is the day rate compatible with a B2B service?

Yes, the day rate can be an economic term.

But the relationship must stay structured as a service: clear object, deliverables, governance, validation, the supplier's responsibility. The day rate must not lead to treating the freelancer as an integrated employee.

Does StelarWork act as the freelancer's representative in France?

No. StelarWork doesn't sign in the freelancer's name and doesn't act as their dependent agent.

StelarWork contracts in its own name with the firm and separately with the freelancer.

Does the model remove all risks?

No. No serious model removes all risks.

A well-structured contracting intermediary aims to reduce friction and frame the relationship. Compliance also depends on the actual execution of the mission, the contracts, the freelancer's effective location and the end client's obligations.