Tech freelancer abroad: working with France, country by country

Your French project may be approved technically, then blocked at supplier onboarding because your company is in Dubai, Bali, Casablanca, Tbilisi, Montreal or Ho Chi Minh City.

The issue is not always your day rate, your level or your availability.

The issue is often contractual.

A French IT services firm must pay a supplier it can onboard, control, document and defend in the event of an audit. As soon as you are a non-EU tech freelancer, it looks at more than your profile: country of residence, local company, currency, invoicing, tax, sanctions, due diligence, permanent establishment risk, reclassification risk, and the ability to work back-to-back with its own client.

The aim of this guide is to read destinations country by country, without selling an expat dream. What matters here is understanding what reassures or blocks a French IT services firm, and which contracting framework to favour in order to keep working with France cleanly.

What really changes when you are a tech freelancer abroad

For a French IT services firm, a tech freelancer based outside the EU is not just “a remote consultant”.

It is a foreign supplier.

That difference triggers several internal questions:

• can the supplier be created in the ERP?
• is the invoice compliant?
• is the international payment straightforward?
• is the currency under control?
• is the contract enforceable?
• does the country present a tax, banking or compliance risk?
• does the service look like a genuine service provision, or like staff secondment?
• does the freelancer create a permanent establishment risk in France?
• can the IT services firm pass through the end-client commitments back-to-back?

The blockage rarely comes from a single point. It comes from an accumulation.

A country may be clear for you from a tax perspective, but difficult for an IT services firm to onboard. Conversely, a country may be easy to pay, but raise questions about genuine residence or an organised presence in France.

The right question is not: “in which country can I pay less tax?”
The right question is: “in which country can I be genuinely resident, work remotely, invoice cleanly and remain acceptable to a French IT services firm?”

The tax reality principle to keep in mind

Before comparing destinations, we need to set a baseline.

Tax residence is not created simply by having a foreign company. It is assessed according to real criteria: physical presence, home, centre of economic interests, place of work, tax treaties and the actual organisation of the activity.

The 183-day threshold is often mentioned, but it is not the only criterion. It is not always sufficient. It does not automatically protect you if your personal, economic or operational life remains anchored in France.

Healthy configuration

A healthy configuration generally looks like this:

• you genuinely live in the country you declare;
• you have an appropriate residence status there;
• your activity is carried out remotely from that country;
• your local company or status corresponds to a real activity;
• you have no office, team, negotiating authority or organised presence in France;
• your contracts describe a service provision, with deliverables, responsibilities and acceptance procedures.

Abusive configuration

An abusive configuration looks more like this:

• a foreign company created solely for invoicing;
• a façade residence with no real presence;
• activity carried out mainly from France;
• negotiation, signature or structured commercial management in France;
• near-exclusive dependence on a French client with strong operational integration;
• absence of local substance.

This zone should be avoided. It can create tax and contractual risks, particularly around the permanent establishment risk for non-EU freelancers.

StelarWork does not sell tax optimisation. Where the freelancer is already a genuine non-EU tax resident, StelarWork removes an administrative and contractual friction point for the French IT services firm. Residence, personal tax and local compliance remain matters to be validated separately with competent advisers.

Country-by-country reading table

The table below provides an operational reading. It does not replace a local legal or tax analysis. It helps anticipate the reaction of a French IT services firm.

Destination	Typical local status	Perception of a French IT services firm	Points requiring attention	Contracting framework to favour
Dubai / United Arab Emirates	Free zone company, mainland company, self-employed depending on visa and activity	Common destination for tech freelancers, but onboarding can be sensitive	Genuine residence, substance, tax treaty, bank account, “tax optimisation” reputation to clarify	Documented B2B service, deliverables, back-to-back contract. If the IT services firm refuses the UAE entity, a French supplier contracting in its own name
Bali / Indonesia	Suitable visa, local structure or invoicing via a foreign entity depending on the situation	Attractive destination, but sometimes less readable for French procurement teams	Local right to work, genuine residence, international payments, currency, proof of activity outside France	Clear service framework, remote scope, structured invoicing. French supplier if the IT services firm cannot handle Indonesia
Morocco	Auto-entrepreneur, local company, professional status depending on activity	Country generally known to IT services firms, favourable cultural and time-zone proximity	Possible withholdings, tax treaty, proof of residence, economic dependence	Service agreement with local company/status if accepted, or French contracting party if procurement blocks
Georgia	Individual entrepreneur, small business status depending on conditions	Sometimes attractive country, but less familiar to French procurement departments	Substance, bank account, local tax, “low tax” image, applicable treaty or lack of a clear mechanism depending on the case	Strengthened documentation, deliverables, proof of residence. French supplier if direct onboarding is too heavy
Canada	Incorporation, self-employed worker, provincial/federal corporation	Reassuring jurisdiction, but more complex on time zones, contracts and tax	Tax residence, France–Canada treaty, insurance, intellectual property, time-zone difference	Standard B2B contract if the IT services firm accepts the Canadian supplier. Precise back-to-back wording on IP, confidentiality and deliverables
Vietnam	Business visa, local company, foreign structure depending on the case	Less standard destination for a French IT services firm	Local law, residence, payments, supporting documents, currency, tax readability	Highly structured remote service, strengthened supplier documentation. French supplier if Vietnam onboarding blocks

Dubai: a common destination, but watch the signal it sends

Dubai is one of the destinations most often mentioned by non-EU tech freelancers who want to continue selling French projects.

From the freelancer’s perspective, the appeal is often stability, the international ecosystem, a time zone compatible with France and the possibility of creating a local structure. From the IT services firm’s perspective, the country may trigger a more in-depth review.

The blockage is not necessarily rational. It may come from procurement policy, the bank, compliance or a lack of familiarity with the UAE framework.

The IT services firm will mainly try to understand:

• whether your residence in the UAE is genuine;
• whether your company has a coherent existence;
• whether the service is actually performed outside France;
• whether the international payment is under control;
• whether the contract can be aligned with the end-client commitments;
• whether the arrangement creates no permanent establishment or abusive tax risk.

For a deeper look at tax, residence and double taxation, the guide on what the France–UAE tax treaty changes for a tech freelancer in Dubai sets out the main principles without reducing the topic to a simple tax rate.

Contractually, Dubai is also a good example of the distinction between “technically strong freelancer” and “supplier acceptable to an IT services firm”. The dedicated guide on how to work with French IT services firms from Dubai explains this logic in detail.

The framework to favour for Dubai

If the IT services firm accepts your UAE company, the contract must remain a B2B service: scope, deliverables, responsibilities, confidentiality, intellectual property, acceptance procedures and invoicing.

If the IT services firm refuses to onboard your company, the issue becomes operational: it does not necessarily want to reject your profile, but it cannot or does not want to onboard your supplier. This is precisely the situation analysed in why an IT services firm refuses to contract with a Dubai company.

In that case, StelarWork can enter the contract as the French supplier of the IT services firm, in its own name. StelarWork invoices the IT services firm, contracts the service, carries the compliance framework and pays the non-EU freelancer according to the agreed documents.

This does not turn the freelancer into an employee. It does not create an employment contract. It does not make StelarWork the freelancer’s representative in France.

Bali / Indonesia: appealing for remote work, less readable for procurement

Bali is a well-known remote-work destination. For a French IT services firm, that is precisely what can create additional scrutiny.

The country is sometimes associated with a lifestyle narrative. But an IT services firm does not approve a project based on a narrative. It approves a supplier, an invoice, a contract, a risk and an ability to deliver.

The sensitive points are often:

• residence status and the right to carry out an activity;
• consistency between genuine residence and invoicing;
• the structure issuing the invoice;
• international payments;
• bank fees and currencies;
• continuity of service despite the time-zone difference;
• the ability to produce documented deliverables.

For payments, the destination matters a great deal. International transfers, currencies, fees and delays can become a concrete friction point. The guide on paying a freelancer in Dubai or Bali without friction explains these issues from the financial execution side.

The framework to favour for Bali

The framework must be particularly clear about remote execution.

Any ambiguity suggesting that the freelancer is “placed” with the end client or integrated as an internal resource should be avoided. The project must be described as a service: objectives, backlog or work packages, deliverables, reporting, acceptance and responsibilities.

If the IT services firm has no process for onboarding an Indonesian structure or a complex international situation, it may prefer a French supplier. StelarWork can then carry the contractual relationship with the IT services firm in its own name, while structuring the relationship with the non-EU freelancer.

Morocco: a more familiar destination, but not automatic

Morocco is often better understood by French IT services firms than other non-EU destinations.

Geographical, linguistic and time-zone proximity is reassuring. Many French players already work with Moroccan providers, particularly in IT.

That does not mean everything is simple.

The IT services firm may request:

• proof that the activity exists;
• tax information;
• bank documents;
• robust intellectual property clauses;
• clarification on VAT or possible withholdings;
• proof that the service is not performed from France.

The main risk is not always the country. It may come from the way the project is organised.

If you work every day under the operational orders of the end client, with no defined deliverables, with regular presence in France and strong dependence, the “non-EU freelance service” structure becomes fragile.

The framework to favour for Morocco

Where the IT services firm accepts the Moroccan supplier, a standard B2B contract may work.

However, the back-to-back structure must be documented: what the IT services firm owes its end client must be compatible with what the freelancer undertakes to produce. This concerns, in particular, deadlines, confidentiality, security, reversibility, intellectual property and liability.

If the IT services firm cannot handle the Moroccan supplier in its supplier database, using a French contracting party may reduce administrative friction. The key point remains the same: this is a service provision, not staff secondment.

Georgia: attractive tax, but substance is needed

Georgia attracts some tech freelancers because of its perceived administrative simplicity and certain advantageous local regimes.

That is precisely what may raise questions for a French IT services firm.

A buyer or compliance team may wonder whether the relocation is genuine, whether the local status is appropriate, whether the activity is stable and whether the country is being used merely as an invoicing façade.

The answer should not be marketing. It should be documentary.

You must be able to demonstrate a coherent situation:

• genuine residence;
• suitable local status;
• professional bank account or coherent payment arrangement;
• contracts aligned with the activity;
• no organised presence in France;
• genuine remote execution.

A favourable local tax regime is not a problem in itself.
The problem appears when the foreign structure does not correspond to a personal and operational reality.

The framework to favour for Georgia

For a French IT services firm, Georgia may be less standard than Dubai, Morocco or Canada.

Contractual uncertainty must therefore be reduced. The contract must be very readable: who does what, from where, with which deliverables, under which acceptance conditions, and with which confidentiality and security obligations.

If the procurement department does not know how to handle Georgia, StelarWork can act as the French supplier of the IT services firm, in its own name, and structure the relationship with the Georgian freelancer or the freelancer based in Georgia. The aim is to turn a supplier that is difficult to onboard into a more readable B2B relationship for the IT services firm.

Canada: reassuring jurisdiction, but the contract must be handled carefully

Canada is generally perceived as a serious jurisdiction by French IT services firms.

The country is known, contractual practices are close on certain points, banks are readable, and tax treaties are better identified by finance teams.

That does not remove the points requiring attention.

The main points are:

• the time zone;
• genuine tax residence;
• the applicable tax treaty;
• intellectual property;
• confidentiality;
• insurance;
• governing law and dispute resolution;
• the ability to meet service commitments with a French team.

Canada may seem “easy” because it is reassuring. But a poorly contracted project remains a fragile project.

The framework to favour for Canada

If the IT services firm accepts your corporation or Canadian status, a direct contract may be an option.

The contract must be precise on intellectual property, especially for software development, architecture, data or cybersecurity projects. It must also clarify coordination hours, response times and security rules.

If the IT services firm requires a French supplier for supplier onboarding, invoicing or client back-to-back reasons, StelarWork can provide that framework without presenting itself as the freelancer’s employer, agent or representative.

Vietnam: viable destination, but more demanding on documentation

Vietnam may suit some experienced tech freelancers, particularly for asynchronous projects or where the organisation is well established.

For a French IT services firm, Vietnam is often less standard.

Questions may concern:

• the local right to carry out an activity;
• the type of structure used;
• proof of residence;
• the currency;
• payment;
• data protection;
• management of the time-zone difference;
• the tax and accounting documentation available.

The country is not necessarily a problem. Opacity is.

The less familiar the destination is for an IT services firm, the simpler the file must be to read. A vague contract, an unclear invoice or a lack of supporting documents can be enough to block a project.

The framework to favour for Vietnam

The recommended model is a highly structured remote service.

Pure time-and-materials staffing should be avoided. Deliverables, milestones, responsibilities, validation procedures and a management method compatible with distance must be documented.

If the IT services firm cannot process the Vietnamese supplier, a French supplier such as StelarWork may be more acceptable to it. StelarWork contracts with the IT services firm in its own name, invoices the IT services firm and organises payment of the freelancer according to a coherent documentary framework.

What reassures a French IT services firm, whatever the destination

Even though each country has its own specifics, French IT services firms often look for the same guarantees.

An identifiable supplier

The IT services firm must know who it is paying.

This implies:

• a clear entity or status;
• existence documents;
• consistent contact details;
• a bank account in the expected name;
• a compliant invoice;
• no obvious risk signal.

A service, not staff secondment

The boundary is important.

An acceptable project must be described as a service provision. It must be based on a scope, objectives, deliverables, timelines, governance and acceptance procedures.

Conversely, an organisation where the freelancer is simply integrated into the client’s team, managed day to day like an employee and invoiced without deliverables increases contractual risk.

StelarWork structures projects on the service side. The aim is to remain on the supplier, purchase order, deliverables and outcome side.

A back-to-back contractual chain

The IT services firm often sells a service to an end client. It must therefore align its commitments with those of its own subcontractors.

Important clauses often cover:

• confidentiality;
• security;
• intellectual property;
• data protection;
• deadlines;
• reversibility;
• liability;
• audit;
• non-solicitation;
• anti-corruption and sanctions compliance.

If your local contract does not allow the IT services firm to secure this chain, it may refuse even if it wants to work with you.

An understandable tax risk

An IT services firm does not need to know all of your personal tax position. But it must avoid participating in a manifestly fragile arrangement.

It will be more reassured if your situation shows:

• genuine residence outside France;
• an activity carried out remotely;
• no permanent establishment in France;
• a coherent local company or activity;
• invoicing aligned with reality;
• documents available in the event of an audit.

An IT services firm does not only buy your expertise.
It also buys an ability to fit your service into its risk framework.

When StelarWork becomes useful in the relationship with the IT services firm

StelarWork intervenes when the IT services firm wants to work with the freelancer, but cannot or does not want to contract directly with their non-EU entity.

The typical case:

1. the tech freelancer is identified for a French project;
2. the IT services firm approves the profile and day rate;
3. the blockage appears at contract or supplier onboarding stage;
4. the foreign entity is refused or considered too complex;
5. the project risks collapsing for an administrative reason.

StelarWork then enters the contract as a French company.

In practice:

• StelarWork contracts with the IT services firm in its own name;
• StelarWork invoices the IT services firm;
• StelarWork frames a service with the non-EU freelancer;
• StelarWork pays the freelancer;
• StelarWork carries the documentary, contractual and compliance framework of the relationship.

This model aims to make the relationship acceptable to the IT services firm, without making the freelancer an employee and without presenting itself as their representative in France.

It does not replace genuine tax residence. It does not turn a façade structure into a compliant situation. It does not solve a problem of organised presence in France.

It removes one friction point: the IT services firm works with a clean, documented French supplier rather than with a foreign entity it does not know how to handle.

How to choose the right framework depending on your country

The right approach starts with three questions.

Is your residence genuine and defensible?

If you say you are based in Dubai, Bali, Morocco, Georgia, Canada or Vietnam, your situation must be coherent.

This means that your presence, documents, activity and organisation must tell the same story.

If they do not, the issue is not contractual. It is tax and legal.

Is your local entity acceptable to the IT services firm?

Some IT services firms accept foreign suppliers. Others do not.

Some accept Canada or Morocco, but refuse the UAE or Indonesia. Others refuse any non-EU entity as a matter of internal policy.

You therefore need to distinguish between:

• what is legally possible;
• what is tax-coherent;
• what is acceptable to the IT services firm’s procurement team;
• what is compatible with the end-client contract.

Is the project structured as a service?

This is often the most underestimated point.

A clean contract is not enough if execution looks like employment integration or staff secondment.

The project must remain outcome-oriented: deliverables, milestones, validation, autonomy of execution and professional reporting.

The freelancer must be able to demonstrate that they provide a service, not that they occupy a remote position.

FAQ

Can I work with a French IT services firm if I am a non-EU freelancer?

Yes, it is possible, but it is not automatic. The IT services firm must be able to onboard your supplier, pay correctly, document the relationship and secure its contract with the end client. If your non-EU entity is refused, a French company such as StelarWork can contract with the IT services firm in its own name and frame the service.

Which country is the easiest for selling French projects from abroad?

There is no universal answer. Canada and Morocco are often more familiar to French IT services firms. Dubai is common but can trigger compliance questions. Bali, Georgia or Vietnam can work, but often require more documentation. The right country is the one where your residence is genuine, your activity is coherent and your contractual framework is acceptable to the IT services firm.

Can an IT services firm refuse my foreign company even if it is perfectly legal?

Yes. A foreign company may be legal in its country, but refused by an IT services firm for internal reasons: procurement policy, bank, compliance, tax, currency, insurance, due diligence or end-client constraints. The refusal is not always aimed at your profile. It often concerns the supplier to be onboarded.

Does StelarWork handle my expat tax position?

No. StelarWork does not provide personalised tax advice and does not sell a tax status. Tax depends on your genuine residence, your personal situation, your country of relocation, the applicable treaties and the concrete execution of the activity. StelarWork intervenes on the contractual friction between the French IT services firm and the non-EU tech freelancer.

Legal and tax disclaimer

This article provides general information for non-EU tech freelancers and future expatriates wishing to work with French IT services firms. It does not constitute personalised legal, tax, social security or accounting advice.

Rules on tax residence, tax treaties, local law, VAT, withholding tax, permanent establishment and compliance vary by country and individual situation. A professional analysis should be carried out before any decision to relocate, create a structure or enter into international contracts.

StelarWork is not a legal, tax or accounting firm. StelarWork acts as a French contracting party in its own name with the IT services firm, within a documented B2B service provision framework.