Subcontracting a non-EU freelancer compliantly: the IT services firm guide

Your firm has found the right tech profile, but the freelancer is based outside the EU and your procurement team can't reference them directly.

The problem isn't the technical level. It's contractual, tax-related, documentary and compliance-related. A mission sold to your end client can be blocked because the consultant works from Dubai, Bali, Mauritius or another country outside the European Union, with a local structure that's hard for your procurement, finance or compliance teams to qualify.

Subcontracting a non-EU freelancer compliantly means handling several topics at once: contract, invoicing, VAT, due diligence, deliverables, intellectual property, GDPR, permanent-establishment risk, prevention of undeclared work, and the absence of any artificial arrangement.

StelarWork addresses this exact case: becoming the firm's French supplier, contracting in its own name, invoicing the firm, paying the non-EU freelancer and carrying the documentary framework needed for clean subcontracting.

StelarWork is not umbrella employment, not domiciliation, not an EOR, not a law firm and not a business introducer. StelarWork acts as a French supplier in a B2B subcontracting chain, with a service contract, deliverables and a compliance framework.

Why a non-EU freelancer often becomes "unsignable" for an IT services firm

A non-EU tech freelancer can be perfectly competent, available and already validated operationally by your teams.

Yet they can remain impossible to engage directly.

The reasons are often the same:

• a company registered in a jurisdiction your procurement team doesn't know how to handle;
• the absence of documents equivalent to French standards;
• uncertainty about VAT or the reverse charge;
• difficulty verifying the identity of the actual counterparty;
• risk of non-compliance with your due-diligence obligations;
• no clear framework on deliverables, intellectual property and confidentiality;
• a block from your legal or finance department;
• the end client's refusal to include an indirect non-European supplier in the chain.

The result is frustrating: the profile is good, the client need is real, but the contract doesn't go through.

For an IT services firm, the issue is therefore not just to "find a freelancer". It's to make the subcontracting contractable, traceable and acceptable to your internal processes.

The risks to address before subcontracting a non-EU freelancer

Subcontracting a non-EU freelancer compliantly is not about dropping a foreign invoice into your ERP.

The chain must be secured on several levels.

Contractual risk

The relationship must be structured as a provision of services.

That requires:

• a defined mission scope;
• expected deliverables or results;
• a purchase order or a clear contract;
• confidentiality clauses;
• intellectual property clauses;
• acceptance or validation terms;
• liability rules;
• consistency between your end-client contract and your subcontracting contract.

The key point is the back-to-back contractual set-up.

Your firm must be able to absorb its end client's requirements and pass them down a consistent contractual chain, without creating any grey area.

Risk of reclassification or unlawful labour supply

Subcontracting must remain a service.

It must not be presented as staff secondment. It must not boil down to "a consultant placed at the client's site" with no autonomy, no deliverable and no service liability.

A sound configuration rests on:

• an identified supplier;
• a documented service;
• results or deliverables;
• B2B invoicing;
• the absence of any relationship of subordination;
• an operational organisation consistent with the contract.

A risky configuration appears when the freelancer is integrated as a de facto employee, managed directly like an in-house staffer, with no service framework or supplier liability.

StelarWork is designed to stay on the B2B service side, with a contract, a purchase order and a supplier logic.

Tax risk

A non-EU freelancer may have a genuine tax residence outside France and the European Union.

But that reality must be consistent with the facts.

The principle is simple: tax residence is not declared. It is established.

A sound configuration notably requires:

• a genuine residence in the declared country;
• a consistent physical presence, often assessed against the 183-day threshold under the applicable local rules and treaties;
• an activity actually carried out remotely from abroad;
• no organised, habitual presence in France;
• no office, team or power to conclude contracts in France on the freelancer's behalf;
• no shell entity used to mask an activity carried out elsewhere.

Conversely, a foreign structure with no substance, used while the activity is in reality carried out from France, may constitute an abusive or fraudulent arrangement.

StelarWork does not sell tax optimisation. StelarWork does not create a non-EU tax status. When a freelancer is already a genuine tax resident abroad, StelarWork removes an administrative and contractual friction for the firm.

Permanent-establishment risk

Permanent establishment is a sensitive topic when a foreign activity has ties to France.

To avoid creating a risky situation, you must in particular avoid having someone in France conclude contracts in the foreign freelancer's name or act as their dependent agent.

StelarWork does not sign in the freelancer's name. StelarWork contracts in its own name with the firm, then organises its own subcontracting relationship with the freelancer.

This distinction matters.

It allows you to reason in terms of a B2B chain of services, rather than representing the foreign freelancer in France.

VAT risk

VAT must be handled according to the nature of the services, the location of the parties and the applicable rules.

In a typical chain:

• the firm receives an invoice from a French supplier;
• French VAT may apply under ordinary rules;
• the relationship with the non-EU provider must be analysed separately;
• some international service flows may involve reverse-charge mechanisms.

The important point for the firm is to receive a usable invoice, issued by a French supplier, in a format compatible with its finance processes.

This reduces the friction of a hard-to-qualify non-European invoice.

Due-diligence risk

IT services firms often have to collect and maintain supplier documents: identity, registration, certificates, social and tax compliance where required, insurance, sanctions, anti-corruption, GDPR.

With a non-EU freelancer, these checks become more complex.

Documents are not always equivalent to French standards. Local registers can be hard to read. Formats don't match procurement's expectations.

By going through a French supplier such as StelarWork, the firm has a local contractual counterpart, with more readable documentation and a better-framed compliance responsibility.

The point is not to make a freelancer "French". The point is to let the firm contract with a French supplier, in a documented subcontracting chain, while the freelancer remains based outside the EU and works remotely within a consistent framework.

What an IT services firm expects before signing

A decision-maker at a firm isn't just looking for an administrative solution.

They must protect their margin, their end client and their internal organisation.

Before approving subcontracting with a non-EU freelancer, the questions are generally the following:

• Who invoices the firm?
• Which contract governs the mission?
• Who carries the supplier liability?
• Will the invoice be accepted by accounting?
• Can the end client audit the chain?
• Are the deliverables defined?
• Are intellectual property rights transferred correctly?
• Are the confidentiality clauses aligned?
• Is personal data handled within a suitable GDPR framework?
• Is the freelancer's tax residence consistent with reality?
• Does the arrangement avoid an organised presence in France?
• Is the reclassification risk reduced by a genuine service framework?

These questions must be handled before the start.

A mission launched too quickly may work operationally for a few weeks, then get blocked at invoicing, client audit or renewal.

The StelarWork model: a single French supplier for the firm

StelarWork steps in to simplify the chain on the firm's side.

The principle is as follows:

1. The firm contracts with StelarWork, a French company.
2. StelarWork invoices the firm as a supplier.
3. StelarWork contracts in its own name with the non-EU freelancer.
4. StelarWork pays the freelancer under the agreed framework.
5. The mission is structured as a service, with scope, deliverables and contractual obligations.
6. Compliance documents are centralised and made usable for the firm.

So the firm doesn't have to reference a hard-to-validate non-EU structure directly.

It works with a single French supplier, within a more readable contractual framework.

StelarWork turns a hard-to-sign subcontracting situation into a French supplier relationship that is documented and usable by an IT services firm. The goal is to reduce compliance, finance and procurement friction, without artificially altering the freelancer's tax or operational reality.

What StelarWork does not do

This clarification is essential.

StelarWork does not become the freelancer's employer. There is no employment contract, no salary and no relationship of subordination.

StelarWork does not domicile the freelancer in France.

StelarWork does not create a non-EU tax residence.

StelarWork does not promise any particular tax rate.

StelarWork does not act as the freelancer's agent to conclude contracts in their name.

StelarWork does not provide personalised legal or tax advice.

StelarWork does not replace the internal analysis of the firm, its legal counsel, its tax adviser or its end client.

Its role is more precise: to provide a French contractual and administrative infrastructure enabling B2B subcontracting with a tech freelancer genuinely based outside the EU.

The conditions for a sound configuration

Subcontracting with a non-EU freelancer is more robust when several conditions are met.

The freelancer is genuinely based outside the EU

The freelancer must work from their country of genuine residence.

The situation must be consistent with:

• their place of living;
• their professional registration;
• their local tax obligations;
• their invoices;
• their work organisation;
• their absence of habitual presence in France.

A freelancer who registers a company in Dubai but actually works from Paris is not in a sound configuration.

The mission is genuinely remote

The model works when the service is delivered remotely.

Occasional travel may exist depending on the case, but it must stay consistent with the contractual framework, immigration rules, tax obligations and the end client's policies.

A regular, organised presence in France can create additional risks.

The contract describes a service

The documentation must speak of service, scope, deliverables, deadlines, acceptance, confidentiality and intellectual property.

It must not create an appearance of subordination.

Wording matters, but it isn't enough. Operational practices must stay consistent with the contract.

The contractual chain is consistent

The firm often has a contract with its end client.

Subcontracting must remain compatible with that contract: subcontracting authorisation, confidentiality, security, reversibility, GDPR, intellectual property, insurance, audit.

StelarWork helps structure this supplier chain to avoid obvious contradictions between commitments.

The documents are usable

Compliant subcontracting is also documented subcontracting.

You must be able to produce the elements needed by procurement, finance, compliance or the end client.

Depending on the case, this may include:

• identification documents;
• registration information;
• the service contract;
• the purchase order;
• invoices;
• available certificates or equivalents;
• KYC/KYB elements;
• confidentiality clauses;
• GDPR commitments;
• items relating to sanctions and restriction lists;
• proof of residence or substance where required.

Example of a firm case

A French IT services firm wins a cloud development mission for a large account.

The best profile identified is a senior freelancer based in Dubai. They have a local structure, genuinely work from the United Arab Emirates and have no organised presence in France.

The end client accepts subcontracting but refuses a supplier chain with an unreferenced non-European company.

The firm can't integrate the freelancer into its procurement system directly.

In this case, StelarWork can step in as the firm's French supplier.

The firm signs with StelarWork. StelarWork issues invoices to the firm. StelarWork frames its relationship with the non-EU freelancer. The mission remains an outcome-based service, with a defined scope and deliverables.

The situation becomes more readable for the firm: a French supplier, a contract, a usable invoice, centralised documentation.

The points to check before starting

Before launching a mission with a non-EU freelancer, a firm should check several things.

1. Does the end client authorise subcontracting?

Some client contracts require prior authorisation.

Others prohibit certain countries, certain subcontracting chains or certain data transfers.

This must be checked before presenting the profile.

2. Does the freelancer genuinely work from abroad?

Consistency between declared residence and operational reality is central.

A sound situation does not rest on a mailbox, a shell company or a fictitious residence.

3. Is the scope contractable as a service?

A day rate can exist in the commercial negotiation.

But the contract must remain structured around a service, not the secondment of a person.

The right reflex is to document the scope, the deliverables, the responsibilities and the validation terms.

4. Are GDPR obligations handled?

If the freelancer accesses personal data, the GDPR framework must be examined.

You must in particular identify:

• the accessible data;
• the role of the parties;
• the security measures;
• any transfers outside the EU;
• the necessary contractual clauses;
• the end client's requirements.

5. Is intellectual property transferred correctly?

For a development, architecture, cybersecurity or data mission, intellectual property is a major topic.

The firm must be able to transfer to its end client the rights it has committed to transfer.

The contractual chain must therefore avoid breaks in the chain of rights.

6. Is invoicing compatible with your finance processes?

A foreign invoice can trigger checks, ERP blocks or additional requests.

A French supplier invoice can make processing easier, subject to the firm's internal rules.

7. Does the model avoid signals of subordination?

The operational reality must stay consistent with the service.

You must avoid indicators of disguised employment: hierarchical integration, lack of autonomy, disciplinary control, unjustified exclusivity, absence of supplier liability.

Why the single supplier makes the firm's life easier

The single-supplier model is especially suited to firms working with rare profiles.

It preserves the agility of international sourcing without making the firm bear the complexity of direct non-EU referencing.

For the firm, the concrete benefits are:

• a French counterparty;
• a local supplier invoice;
• a service contract;
• documentation that is simpler to audit;
• a counterpart responsible for the administrative chain;
• better readability for procurement and finance;
• reduced friction linked to international payment;
• a clearer framework for the end client.

This model doesn't remove all risk analysis.

It aims to make the risk identifiable, documented and better allocated contractually.

Common mistakes to avoid

Signing a foreign structure directly without verification

A non-EU registration is not enough.

You need to understand who is contracting, where the service is delivered, how invoicing works and which documents can be produced.

Confusing tax residence with a company address

A freelancer may have a company in one country and genuinely reside in another.

This point must be clarified.

Genuine tax residence depends on the facts, not just on commercial documents.

Treating the mission as plain staffing

Even when the price is expressed as a day rate, subcontracting must be framed as a service.

The day rate is an economic calculation method. It must not make the deliverables, liability and autonomy of the provider disappear.

Ignoring the end-client contract

Some firms discover too late that their end client requires prior validation of any subcontractor.

This can block the mission when the freelancer has already started.

Promising tax optimisation

This is a mistake.

A freelancer genuinely resident outside the EU may have a specific local tax regime. But that isn't a contractual product to sell to the firm.

StelarWork's role is to remove an administrative and contractual friction, not to organise tax avoidance.

How StelarWork fits into the firm's cycle

StelarWork usually steps in when the firm has already identified a non-EU tech freelancer or wants to secure a pool of international profiles.

The process can be structured as follows:

1. Qualification of the firm's need.
2. Verification of the mission context and the end client.
3. Documentary analysis of the freelancer and their structure.
4. Structuring of the service contract between the firm and StelarWork.
5. Alignment of the key clauses: confidentiality, IP, GDPR, deliverables, liability.
6. Separate contracting between StelarWork and the non-EU freelancer.
7. Invoicing of the firm by StelarWork.
8. Payment of the freelancer by StelarWork under the agreed framework.

Each step aims to make the relationship more readable for procurement, finance and compliance teams.

When this model is relevant

The StelarWork model is relevant when:

• the firm wants to work with a non-EU tech freelancer;
• the freelancer is genuinely based outside the EU;
• the mission can be delivered remotely;
• the end client accepts the principle of subcontracting;
• the firm wants to avoid direct non-European referencing;
• the service can be framed with deliverables;
• compliance stakes must be documented.

It is especially useful for rare profiles: cloud, data, AI, cybersecurity, backend, DevOps, software architecture, product engineering.

When this model is not suitable

The model is not suitable if the situation rests on a fictitious residence.

It is not suitable if the freelancer actually works from France while invoicing through a foreign structure with no substance.

It is not suitable if the real need is staff secondment under the client's direct control, with no identifiable service.

It is not suitable if the end client prohibits any subcontracting.

It is not suitable if the mission requires a regular physical presence in France without an appropriate tax, social and immigration framework.

In those cases, the structure of the relationship must be reviewed with competent advisers.

Legal and tax disclaimer

This article provides general information for decision-makers at IT services firms.

It does not constitute personalised legal, tax, social or accounting advice. The applicable rules depend on the facts, the countries involved, the tax treaties, the end-client contract, the nature of the mission and the actual operational organisation.

Before setting up an international subcontracting chain, we recommend consulting your usual advisers: lawyer, tax adviser, chartered accountant, legal department or compliance department.

FAQ

Can a French IT services firm subcontract to a non-EU freelancer?

Yes, in principle a firm can subcontract a service to a non-EU freelancer.

But it must handle the contractual, tax, VAT, compliance, GDPR, intellectual property and due-diligence topics. The mission must remain a genuine B2B service, with a consistent documentary framework.

Why go through a French supplier rather than sign the freelancer directly?

A French supplier often simplifies procurement, finance and compliance processing.

The firm receives a local invoice, signs a contract with a French company and avoids directly referencing a non-European structure that can be hard to qualify.

Does StelarWork employ the freelancer?

No.

StelarWork does not employ the freelancer. There is no employment contract, no salary and no relationship of subordination.

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

Does StelarWork sign in the freelancer's name?

No.

StelarWork contracts in its own name with the firm. StelarWork does not present itself as the freelancer's agent in France and does not conclude contracts in the freelancer's name.

Does the non-EU freelancer necessarily pay less tax?

That's not the point.

A freelancer genuinely resident outside the EU may fall under the tax regime of their country of residence. But that situation must be real, documented and consistent with the facts.

StelarWork does not create a foreign tax residence and does not sell tax optimisation.

What happens if the freelancer actually works from France?

The situation becomes risky.

If the freelancer claims to be based outside the EU but habitually works from France, the tax, social and contractual consistency can be called into question.

A foreign entity with no substance, used to mask an activity carried out in France, may be abusive or fraudulent.

Can we work on a day-rate basis?

Yes, the day rate can serve as an economic basis.

But the contract must remain structured as a service: scope, deliverables, responsibilities, validation terms and the absence of subordination.

Should the end client be informed?

That depends on the contract between the firm and its end client.

Many contracts require prior authorisation or a declaration of subcontractors. This must be checked before starting.

Does StelarWork guarantee the absence of risk?

No.

No serious player can guarantee the total absence of risk. StelarWork is designed to reduce friction and structure a subcontracting chain that is more readable, documented and compliant with the usual B2B requirements.

How do you get started with StelarWork?

The firm can present the mission context, the freelancer's country, the structure used, the end client's constraints and the internal procurement or finance requirements.

StelarWork then analyses whether the scheme can be framed as B2B subcontracting with a French supplier, in a sound and documented configuration.