Which status for a French freelancer expatriated outside the EU: micro-entreprise, local company or another setup

Your IT services firm approves your day rate, the need is open, then the file gets stuck when the supplier has to be created.

The problem is not only your country of expatriation. It is the status you present to procurement, finance and sometimes legal at the IT services firm.

For a French tech freelancer based outside the EU, the right status is not the one that looks most advantageous on paper. It is the one that remains understandable, invoiceable and defensible for a French IT services firm.

The question of non-EU expatriate freelancer status must therefore be assessed against three simple criteria:

• how understandable the supplier file is;
• the level of tax and social security risk perceived by the IT services firm;
• how simple contracting and invoicing are.

The aim is not to look for a theoretical setup. The aim is to keep selling engagements to French IT services firms without creating an administrative blockage at the last minute.

What the IT services firm really checks before contracting

An IT services firm does not assess only your technical skills. It must also verify that it can onboard you as a supplier without exposing its own client, finance department or procurement team.

In practice, three questions keep coming up.

Is the supplier identifiable and consistent?

The IT services firm wants to understand who is invoicing.

A French SIRET number, a foreign company, a local free zone company, a non-resident individual or a French intermediary do not all provide the same level of comfort.

The file must be understandable:

• supplier identity;
• country of registration;
• beneficial owner;
• bank account;
• consistency between genuine residence, place of activity and invoicing entity;
• available administrative documents;
• ability to issue invoices that accounting can accept.

A status may be legal in your country of residence while still being difficult to integrate into a French IT services firm’s supplier process.

Is the tax and social security risk acceptable?

The IT services firm is trying to avoid ambiguous situations.

In particular, it will consider:

• the risk of reclassification;
• the risk of a permanent establishment in France;
• consistency between expatriation and the activity actually carried out;
• due diligence;
• economic dependence;
• the reality of an outcome-based service rather than staff secondment.

Important point: expatriation is not just an address abroad. In tax and social security matters, reality prevails. Genuine residence, effective presence outside France, genuine remote activity, no organised presence in France and consistent documentation are structuring factors.

A sound configuration can be understood and documented. An artificial configuration, with a shell entity that has no economic reality, creates a high level of risk and may be treated as fraud. It should be ruled out.

Is invoicing simple to process?

Even if legal accepts the principle, accounting may block it.

A French IT services firm generally prefers a supplier:

• already compatible with its ERP;
• able to issue a clear invoice;
• whose bank details do not trigger excessive alerts;
• whose apparent tax position does not require lengthy analysis;
• whose contract can be aligned with the client purchase order.

On an urgent engagement, the simplicity of the file can make the difference between a smooth start and a lost opportunity.

To put the choice of status in the context of your destination, you can also read the practical guide to remaining contractable when you settle abroad.

Option 1: keeping a French micro-entreprise

The French micro-entreprise is often the first reflex for a French freelancer who moves outside the EU.

It has an obvious advantage: French IT services firms know it. The SIRET number, invoices and administrative documents are familiar.

But this surface-level readability is not always enough.

What the IT services firm appreciates

For the IT services firm, a micro-entreprise is easy to create in the supplier database. It looks like a classic French supplier.

Procurement quickly understands:

• the SIRET number;
• the provider’s identity;
• the invoice format;
• the contractual relationship;
• the French administrative attachment.

In the short term, this can reduce friction.

What may cause concern

The difficulty appears when your personal situation no longer matches the administrative appearance.

If you are genuinely expatriated outside the EU, tax resident outside France, and you continue to invoice through a French micro-entreprise, the IT services firm may ask for explanations.

The concerns relate in particular to:

• consistency between non-EU residence and the French social security regime;
• the reality of the activity carried out from abroad;
• reporting obligations;
• the administrative address;
• the risk that the French structure is being used out of habit rather than consistency.

This does not mean that a micro-entreprise automatically becomes impossible as soon as you expatriate. It means it must be consistent with your real and documented situation.

The micro-entreprise reassures through its French simplicity, but it can become fragile if it no longer reflects the reality of your residence, your activity and your obligations.

When the micro-entreprise becomes hard to defend

The file becomes more sensitive when you live outside France on a lasting basis, work entirely remotely, no longer have your centre of economic interests in France, but continue to present a French structure as if nothing had changed.

For the IT services firm, this may raise a simple question: why is a freelancer genuinely based outside the EU still invoicing like a local French independent contractor?

If that question arises late in the process, it can slow down or block supplier onboarding.

Option 2: creating a local company in the country of expatriation

A local company often appears more consistent with genuine expatriation.

You live in Dubai, Bali or elsewhere outside the EU. You create a local entity. You invoice from your new country of residence.

From the point of view of personal consistency, this option may seem natural. From the IT services firm’s point of view, it may be more difficult.

What the IT services firm understands

A local company can be understandable if it corresponds to a clear economic reality:

• you actually reside in the country;
• you carry out your activity there;
• your company is registered there;
• invoicing is issued by that entity;
• documents are available;
• the contract describes an outcome-based service.

This consistency is a positive point.

It avoids the impression that a French status has been kept only to make selling easier.

What may block procurement

The blockage rarely comes from a single factor. It often comes from accumulation.

A non-EU company may trigger internal requests about:

• supplier compliance;
• anti-money laundering;
• the beneficial owner;
• the country of registration;
• the bank account;
• applicable taxation;
• contractual clauses;
• the ability to pay a supplier located outside the EU;
• acceptance by the IT services firm’s end client.

Some IT services firms know how to process this type of supplier. Others refuse it as a matter of internal policy.

The issue is especially common with certain jurisdictions heavily used by expatriate freelancers. For a concrete example, see why a company in the Emirates may block French procurement.

The specific case of the foreign company that is “clean but not signable”

This is a common situation.

Your local company exists. Your residence is genuine. Your engagement is remote. Your day rate is accepted. But the IT services firm does not want to create your company as a supplier.

The refusal does not necessarily mean your structure is illegal. It means the IT services firm does not want, or is not able, to support this supplier in its internal workflow.

In that case, the problem is no longer your personal status. The problem becomes the contracting chain.

You can explore this case further with what happens when your IT services firm refuses your Dubai company.

Option 3: going through a French supplier that contracts in its own name

Between the French micro-entreprise kept by inertia and the local company refused by procurement, there is another approach: involving a French supplier in the contractual relationship.

The principle is not to conceal your situation. It is to make the relationship acceptable for the IT services firm while keeping a consistent documentation chain.

StelarWork operates in this framework: a French company (SASU) that contracts in its own name with the IT services firm, invoices the IT services firm, then contracts with the freelancer or their foreign structure to perform the service.

StelarWork does not act as your representative in France and does not sign on behalf of the freelancer. The company carries its own contractual relationship with the IT services firm.

What this changes for the IT services firm

For the IT services firm, the supplier becomes a French company.

This simplifies several points:

• supplier creation;
• invoicing;
• documentation;
• contractual compliance;
• exchanges with procurement;
• alignment between purchase order, deliverables and service.

The IT services firm does not contract directly with a non-EU company that it does not know how to onboard. It deals with a French supplier, which then organises the relationship with the non-EU freelancer under a separate contractual framework.

What this does not change

This approach does not turn an abusive situation into an acceptable one.

If the freelancer claims to live outside France but in reality maintains an organised presence in France, the tax and social security issue remains.

If the foreign company is a mere shell with no reality, the risk remains.

If the engagement is structured as staff secondment without deliverables, the contractual risk remains.

A French supplier can reduce contracting friction. It does not replace the reality of your expatriation, the consistency of your status or the need for a structured service.

The central point: service, deliverables and back-to-back

To remain defensible, the model must be built around a service.

The contract must avoid a “staff secondment” logic and favour:

• an engagement scope;
• deliverables;
• responsibilities;
• an outcome-based service;
• a consistent purchase order;
• back-to-back terms with the expectations of the IT services firm and its end client.

This is what distinguishes a structured supplier chain from a fragile setup.

To compare the models if you do not want either to keep a micro-entreprise or to have your local company accepted directly, you can read smoothing the choice of status with the right collaboration model.

Operational comparison of statuses for a French IT services firm

The choice should not be assessed only according to your personal comfort. It should be assessed according to what the IT services firm can accept.

French micro-entreprise

Supplier readability: high.

This is the most familiar status for a French IT services firm. The administrative file is easy to understand.

Perceived tax and social security risk: variable.

It remains moderate if the situation is consistent. It increases if you are expatriated outside the EU on a lasting basis but continue to invoice as if your activity remained anchored in France.

Invoicing simplicity: high.

A French invoice is generally easy for the IT services firm to process.

Practical reading: useful if it still matches your real situation. More fragile if it is used only to avoid presenting your expatriation.

Local non-EU company

Supplier readability: medium to low depending on the country and the IT services firm.

The structure may be perfectly consistent for you, but difficult for the IT services firm to onboard.

Perceived tax and social security risk: variable.

It may be manageable if residence, activity and company are aligned. It becomes high if the entity appears artificial or if the real presence remains in France.

Invoicing simplicity: variable.

Some IT services firms know how to pay a non-EU supplier. Others refuse or impose a lengthy process.

Practical reading: consistent with genuine expatriation, but not always contractable with a French IT services firm.

French intermediary supplier in its own name

Supplier readability: high for the IT services firm.

The IT services firm deals with a French company, identified and compatible with its usual workflows.

Perceived tax and social security risk: reduced on the IT services firm–supplier relationship, subject to a consistent contractual structure.

The model must remain built around a service, not staff secondment. The freelancer must also maintain a genuine and documented personal situation.

Invoicing simplicity: high.

The IT services firm receives an invoice from a French supplier. Internal processing is generally simpler than with a non-EU entity.

Practical reading: relevant when the freelancer is competent, genuinely expatriated, but difficult for the IT services firm to sign directly.

The mistakes that turn a good status into a bad file

A status may be viable on paper and poorly presented in practice.

It is often the supplier file, more than the status itself, that triggers the blockage.

Presenting expatriation without evidence of reality

A non-EU address is not enough.

The IT services firm may ask for consistent elements:

• effective residence;
• entity used;
• place where the engagement is performed;
• bank account;
• registration documents;
• available certificates;
• a clear explanation of the invoicing flow.

This is not excessive curiosity. It is a risk management requirement.

Confusing personal optimisation with B2B acceptability

A status may reduce your charges in your country of residence without being acceptable to a French IT services firm.

The paying client looks at compliance, traceability and risk.

It is therefore not enough to say: “my company is legal in my country”. The IT services firm must also be able to onboard it and justify the contract.

StelarWork does not sell tax exemption or tax optimisation. If a freelancer is already genuinely tax resident outside the EU, with an activity actually carried out outside France, StelarWork can remove administrative friction on the IT services firm contracting side. The tax situation pre-exists the collaboration model.

Waiting until the last minute to handle the file

The worst time to discover a supplier blockage is after the day rate has been approved.

At that stage, the IT services firm has sold the profile, the end client is waiting for the start, and procurement discovers a foreign company or an inconsistent status.

The result is often the same: request for documents, internal arbitration, delay, and sometimes refusal.

To anticipate these points, see how to avoid the file mistakes that derail a contract.

How to choose without thinking only about tax

The right reasoning starts with the engagement and the IT services firm.

Ask the questions in this order.

Is your non-EU residence genuine and stable?

This is the foundation.

A sound configuration assumes genuine residence, effective presence outside France, consistent remote activity and no organised presence in France.

Conversely, an abusive configuration consists of displaying a foreign residence or company with no reality while continuing to operate as if the activity remained in France. This type of scheme must be avoided.

Does the IT services firm accept your direct supplier?

If you keep a micro-entreprise, does the IT services firm accept this situation despite your expatriation?

If you have a local company, does the IT services firm agree to onboard it?

If the answer is no, you need to address the contracting blockage, not simply change status in a rush.

Does the contract describe an outcome-based service?

Status is not enough.

An IT services firm will be more comfortable with a supplier that commits to a scope, deliverables and responsibility for a service.

It will be much less comfortable with a relationship that looks like integrating personnel into its teams, without real autonomy or identifiable deliverables.

The issue is not theoretical. It relates to the risk of reclassification, the risk of unlawful labour lending and the compliance of the contractual chain.

The right status is the one the IT services firm can sign

For a non-EU freelancer, the choice of status cannot be separated from contracting with the IT services firm.

The micro-entreprise reassures through familiarity, but it must remain consistent with your genuine residence.

The local company often better reflects effective expatriation, but it may be refused by French procurement teams.

A French supplier that contracts in its own name can reduce friction when the IT services firm cannot sign a non-EU structure directly, provided the relationship is structured as a compliant service.

The question is therefore not: “which status is the most advantageous?”

The question is: “which status allows me to sell an engagement to a French IT services firm without creating disproportionate supplier risk?”

FAQ

Can I keep my French micro-entreprise if I move outside the EU?

It is possible in some configurations, but it is neither automatic nor neutral.

The central question is consistency between your genuine residence, your activity, your tax and social security obligations, and the entity that invoices. If you are settled outside the EU on a lasting basis, the IT services firm may ask why you continue to invoice through a French structure.

You should avoid keeping a micro-entreprise solely to give an appearance of simplicity if it no longer matches your real situation.

Is a local non-EU company always refused by French IT services firms?

No.

Some IT services firms agree to contract with non-EU companies. Others refuse because of internal policy or because they do not have a suitable supplier workflow.

The refusal depends on the country, the documentation available, the end client, procurement and the perceived level of risk.

A local company may be consistent with your expatriation while still being difficult for the IT services firm to sign.

Does StelarWork replace my tax status abroad?

No.

StelarWork does not create non-EU tax residence and does not artificially transform your situation.

If you are already genuinely tax resident outside the EU, with an activity actually carried out remotely from abroad, StelarWork can help remove administrative and contractual friction on the French IT services firm side.

The reality of your residence and obligations remains a separate matter.

What is the best status for a non-EU expatriate tech freelancer?

There is no single answer.

The best status is the one that combines three elements: consistency with your real situation, acceptability for the French IT services firm and invoicing simplicity.

For some freelancers, the micro-entreprise remains understandable. For others, the local company is more consistent. When the IT services firm refuses to sign a non-EU structure directly, a French supplier contracting in its own name may be an option to consider.

Disclaimer

This article provides general information about status, contracting and compliance issues for tech freelancers expatriated outside the EU. It does not constitute personalised legal, tax, social security or accounting advice.

Each situation depends in particular on your genuine residence, your country of settlement, your effective presence in France or abroad, your structure, your contracts and the IT services firm’s internal rules. Before choosing or changing a status, have your situation validated by a competent professional.