Withholding tax on a service paid outside the EU: when does it really apply?

Your IT services firm can lose a deal for a very simple reason: the tech freelancer is excellent, but their non-EU invoice raises a tax question that no one wants to carry alone.

The question comes up often.

Should withholding tax be applied to a non-EU service?
Who should check the tax treaty?
Which supporting documents should be kept?
And what happens if the freelancer invoices from Dubai, Bali or another non-European jurisdiction?

For an IT services firm, the issue is not theoretical. It directly affects the signature of the purchase order, supplier compliance, the audit trail and the risk of a tax reassessment.

This article explains the principles to understand before contracting with a tech freelancer established outside the EU.

Disclaimer: this article provides general information for IT services firms. It does not constitute personalised legal, tax or accounting advice. Every situation should be checked with your usual advisers, in particular in light of the country concerned, the applicable tax treaty, the exact nature of the service and the contractual flows.

Withholding tax on a non-EU service: the practical problem for an IT services firm

When a French IT services firm buys a service from a supplier established outside France, the invoice may look simple: a day rate, an assignment, an international payment.

In practice, several questions immediately arise.

Is the supplier genuinely established outside the EU?
Is the service performed remotely or in France?
Is the service provider a company, an individual independent contractor, or an intermediary structure?
Can France tax all or part of the income through withholding tax?
Can a tax treaty limit or eliminate that withholding tax?
Which documents must the IT services firm keep in the event of an audit?

This is often where the deal stalls.

The freelancer is competent. The end client wants to start. But on the IT services firm side, the supplier is considered difficult to sign: international tax, compliance, non-EU payment, incomplete documents, risk of reclassification, risk of incorrectly applied withholding tax.

StelarWork intervenes precisely on this contractual friction: the IT services firm contracts with a French company, which invoices in France, carries the compliance framework and contracts in its own name with the non-EU freelancer under a service-based approach.

What withholding tax is

Withholding tax is a tax mechanism under which the debtor of a payment withholds a portion of the amount due and pays it to the tax authorities.

In an international context, it generally targets income paid by a French entity to a non-resident person or company.

For an IT services firm, the issue arises when the payment leaves France for a foreign service provider.

Three topics should not be confused:

• tax that may be due by the service provider in their country of residence;
• withholding tax that may apply in France;
• VAT, with its own rules, including the reverse charge in certain cases.

Withholding tax is therefore not VAT.
Nor is it a social security contribution.
It is an income taxation mechanism at source, where French domestic law and tax treaties provide for it.

Why non-EU services are sensitive

A non-EU service concentrates several risk factors for an IT services firm.

First, the supplier is not in a legal environment that is harmonised with the European Union. Documentary, tax and social standards vary significantly.

Second, the international payment may involve a bank, a currency, a low-tax jurisdiction or a poorly documented structure.

Finally, the tech assignment is often performed remotely, with daily exchanges with French teams. This can blur the line between an autonomous service and operational integration.

The issue is not to refuse any relationship with non-EU talent.
The issue is to qualify the relationship correctly.

An IT services firm must be able to demonstrate that it is purchasing a service, not staff secondment. It must document the service provider’s residence, the nature of the deliverables, the responsibilities, the invoicing and the tax treatment applied.

The basic principle: French domestic law, then the tax treaty

The analysis of withholding tax on a non-EU service generally follows two steps.

First step: check whether French domestic law provides for withholding tax on the type of income concerned.

Second step: check whether a tax treaty between France and the service provider’s country of residence limits, reduces or eliminates taxation in France.

The tax treaty may override domestic law, provided that the service provider is indeed a tax resident of the relevant State and that the conditions are met.

This is an essential point.

A tax treaty does not apply because an invoice mentions a foreign address. It applies because genuine tax residence has been established and documented.

Tax treaty: the document is not enough without economic reality

For a tax treaty to be enforceable, it must be possible to document the tax residence of the beneficial owner of the income.

In practice, companies often request:

• a recent tax residence certificate;
• the supplier’s identification information;
• the legal classification of the service provider;
• the exact nature of the service;
• any tax forms that may be required;
• consistency between the country of residence, the place of performance and the banking flows.

The tax treaty should not be treated as a simple sales argument.

It is part of a body of evidence.

A freelancer who genuinely lives in Dubai, genuinely works remotely from Dubai, has a consistent local status and has no organised presence in France does not present the same profile as someone who invoices through a foreign entity while physically working from France.

Principle of reality: tax residence cannot be declared into existence

International tax is based on a simple principle: reality prevails over appearance.

Genuine tax residence requires consistency between several factors:

• the usual place of living;
• the length of presence in the country concerned, often assessed through the 183-day threshold depending on local and treaty rules;
• the centre of personal and economic interests;
• the real place where the service is performed;
• the absence of an organised and habitual presence in France;
• the reality of the resources used abroad.

The 183-day threshold is a common reference point, but it does not summarise the entire analysis. Tax treaties and domestic laws may apply other criteria.

An IT services firm must therefore reason in substance.

Healthy configuration

A tech freelancer is a genuine tax resident outside the EU.
They effectively live and work from that country.
They have a consistent local status.
They perform the service remotely.
They have no office, team, organised presence or habitual intervention in France.
The assignment is described as a service with deliverables and responsibilities.

In this configuration, the tax analysis can be structured, documented and discussed with the IT services firm’s advisers.

Abusive configuration

A person is in reality working from France, but invoices through a foreign entity.
The foreign address is a shell entity.
The stated tax residence does not correspond to the real place of living.
The service looks like integration into internal teams, with no autonomy and no defined deliverables.

This configuration must be avoided.

It can create tax, social security, contractual and criminal risks. It does not correspond to the compliance approach expected of an IT services firm.

The case of low-tax jurisdictions

Certain destinations such as Dubai or Bali attract many international tech freelancers.

The question is not whether the country is tax-attractive.
The question is whether the situation is real, documented and compatible with the IT services firm’s obligations.

StelarWork does not sell ‘0% tax’.
StelarWork does not create tax residence abroad.
StelarWork does not artificially transform a French situation into a non-EU situation.

If a freelancer is already a genuine tax resident outside the EU, with a consistent remote activity, StelarWork can remove administrative and contractual friction for the IT services firm by becoming its French supplier.

Compliance then rests on the pre-existing reality of the situation, not on artificial optimisation.

Non-EU service: frequent mistakes by IT services firms

Paying the foreign invoice without a tax analysis

The first mistake is to pay a non-EU invoice as if it were a standard French invoice.

The fact that the service is tech, intellectual or remote is not enough to eliminate every withholding tax issue.

The income, the country, the service provider, the tax treaty and the supporting documents must be qualified.

Confusing billing address and tax residence

An address in Dubai, Singapore, Hong Kong or Bali is not sufficient proof.

The IT services firm must be able to justify why it treated the service provider as non-French resident and, where applicable, as tax resident of another State.

Applying a tax treaty without supporting evidence

A tax treaty may open the door to favourable treatment. But it requires documentation.

Without a tax residence certificate or consistent supporting documents, the treatment applied becomes fragile.

Ignoring the permanent establishment risk

If the non-resident service provider has a fixed place of business in France, or if a person acts in France to habitually conclude contracts in their name, a permanent establishment issue may arise.

This is a sensitive point.

In the StelarWork model, StelarWork contracts in its own name with the IT services firm. StelarWork does not act as the freelancer’s representative and does not conclude contracts in the freelancer’s name.

This distinction is important to avoid artificially creating a taxable presence in France for the foreign service provider.

Describing the assignment as staff secondment

Contract wording matters.

An assignment worded only in man-days, integrated into the end client’s organisation chart, with no deliverables or specific responsibility, can weaken the analysis.

A compliant approach favours the service: scope, deliverables, expected outcome, acceptance criteria, responsibilities, purchase order and back-to-back clauses where necessary.

Withholding tax and VAT: two separate analyses

An IT services firm must also distinguish the tax treatment of income from the VAT treatment.

For certain international B2B services, VAT may fall under specific mechanisms, including the reverse charge. This does not answer the withholding tax question.

A non-EU invoice may therefore be correct from a VAT perspective, while still raising an international income tax issue.

Conversely, a withholding tax analysis does not remove the need to check VAT.

The two topics must be handled separately in the supplier file.

Which documents should be requested before paying a non-EU service provider?

The documentation depends on the country, the nature of the service provider and the applicable tax treaty.

In a prudent approach, an IT services firm will generally seek to gather:

• the service provider’s full identity;
• their legal status;
• their country of tax residence;
• a tax residence certificate where available;
• the relevant tax forms depending on the country and the income;
• the contract or purchase order describing the service;
• the expected deliverables;
• the validation procedures;
• bank details consistent with the declared situation;
• supplier compliance information;
• checks relating to any sanctions and restrictions;
• VAT documentation where necessary.

This list is not universal. It must be adapted to the case at hand with your advisers.

But it shows one key point: compliance is not limited to receiving an invoice.

The right question for an IT services firm: can I sign this supplier properly?

The problem is not only tax-related.

For an IT services firm, signing a non-EU freelancer raises a set of questions:

• international tax;
• withholding tax;
• tax treaty;
• supplier compliance;
• due diligence where applicable;
• international payment;
• back-to-back contracting;
• liability towards the end client;
• risk of reclassification of the relationship;
• permanent establishment risk;
• proof of the service delivered.

This accumulation is what makes some freelancers ‘unsignable’ directly, even when they are technically excellent.

The IT services firm does not always have the time, resources or risk appetite to open an exotic supplier, analyse withholding tax, secure supporting documents and carry the uncertainty.

How StelarWork reduces friction for the IT services firm

StelarWork sits in the contract chain between the French IT services firm and the tech freelancer based outside the EU.

In practical terms, the IT services firm contracts with StelarWork, a French company.
StelarWork invoices the IT services firm.
StelarWork contracts in its own name with the non-EU freelancer.
StelarWork pays the freelancer within the agreed framework.
StelarWork carries the compliance framework, checks and supplier risk management.

The IT services firm therefore does not directly sign a non-EU service provider who is difficult to integrate into its processes.

It works with a French supplier, within a clearer contractual framework designed to reduce compliance friction.

This approach does not exempt the IT services firm from its own internal obligations. It does, however, help structure the relationship and limit the grey areas that often block signature.

What StelarWork does not do

To be clear, StelarWork is not a tax avoidance scheme.

StelarWork does not create foreign tax residence.
StelarWork does not promise the absence of tax.
StelarWork does not allow a French situation to be disguised as a non-EU situation.
StelarWork does not conclude contracts in the freelancer’s name.
StelarWork does not provide staff secondment.
StelarWork does not turn the relationship into an employment contract.

The model is based on a service relationship between professionals, with deliverables, a contractual framework and compliance documentation.

The objective is to make a freelancer who is genuinely established outside the EU contractable where the situation is healthy, documented and compatible with the IT services firm’s requirements.

Withholding tax: what the IT services firm must validate before deciding

Before signing a non-EU service provider directly, an IT services firm must, at a minimum, have several points validated.

The nature of the service

Is it a development, architecture, cybersecurity, consulting, support, licence, transfer of know-how or another type of income?

The classification may change the tax treatment.

The place of use and performance

Is the service performed remotely?
Is it used by a French entity?
Does the service provider physically intervene in France?
Is there a habitual or organised presence in France?

These elements may weigh in the analysis.

The service provider’s tax residence

Is the service provider genuinely tax resident in the country they indicate?
Can they provide a certificate?
Is the personal and professional situation consistent?

The applicable tax treaty

Is there a tax treaty between France and the State concerned?
What does it provide for this type of income?
What documentary conditions are required?

The permanent establishment risk

Does the service provider have a fixed place of business in France?
Does a person conclude contracts in France in their name?
Does the contractual organisation create a taxable presence?

The documentation retained

Can the IT services firm justify its decision in the event of an audit?
Are the documents available and consistent?
Is the supplier file complete?

Anonymised example: a freelancer in Dubai

An IT services firm identifies a cloud architect based in Dubai for a remote assignment with a French end client.

The consultant has a rare profile. The end client wants to start quickly. But the IT services firm hesitates to onboard the consultant directly.

Questions quickly arise:

• what tax treatment should be applied to the invoice?
• which tax treaty should be analysed?
• which supporting documents should be requested?
• how should genuine residence be documented?
• how can the assignment wording avoid looking like staff secondment?
• who carries the risk if the documentation is incomplete?

With a direct signature, the IT services firm must absorb the entire non-EU supplier issue.

With StelarWork, the IT services firm contracts with a French company. The relationship is structured as a service. StelarWork manages the contractual relationship with the non-EU freelancer in its own name, within a documented framework.

The benefit for the IT services firm is not tax artificiality. The benefit is operational and compliance-related: turning a difficult-to-sign relationship into a clearer French supplier relationship.

Anonymised example: a situation to refuse

A developer refers to a company registered outside the EU, but explains that they live mainly in France and work from their French home.

They want to invoice through this foreign structure to ‘simplify’ matters or reduce taxation.

This configuration is problematic.

The contractual appearance does not match reality. The foreign tax residence may be challenged. The tax treaty may not be applicable as presented. The risk for the IT services firm can become significant.

Such a situation should not be treated as a simple non-EU service.

The right approach is to refuse artificial arrangements and return to a classification that reflects reality.

Why this issue mostly blocks IT services firms

An IT services firm is caught between three constraints.

First, it must respond quickly to the end client’s need.

Second, it must secure its margin, its contract and its commercial relationship.

Finally, it must comply with its internal processes: supplier onboarding, compliance, tax, payment and contractual liability.

The non-EU freelancer often brings high technical value, but low administrative compatibility with the standards of a French IT services firm.

This mismatch creates friction.

International tax, withholding tax and the tax treaty then become go / no-go issues.

The right reflex: document before contracting

The treatment of withholding tax should never be improvised at the time of payment.

It must be anticipated before signature.

An IT services firm must in particular avoid discovering after the event:

• that it does not have a tax residence certificate;
• that the tax treaty does not cover the income as expected;
• that the service was performed in France;
• that the invoice comes from an inconsistent entity;
• that the contract describes no deliverables;
• that the relationship looks like operational staff secondment;
• that the payment should have been subject to a specific tax treatment.

Compliance is built upstream.

What changes when a French supplier is contractually inserted

When the IT services firm signs a non-EU freelancer directly, it becomes the direct debtor of the international payment.

It must therefore manage the foreign supplier, its tax treatment, its supporting documents and the associated risks.

When the IT services firm signs StelarWork, it signs with a French company (SASU). The supplier relationship is French on the IT services firm side. The invoice is issued by StelarWork. The contract is structured within a clear B2B framework.

StelarWork then handles the contracting with the non-EU freelancer in its own name.

This model aims to reduce administrative, tax and contractual friction for the IT services firm, without creating an artificial arrangement.

It does not replace personalised legal or tax analysis. It provides an operational framework designed for situations where the freelancer is genuinely established outside the EU and works remotely under a service-based approach.

FAQ

Must a French IT services firm always apply withholding tax to a non-EU service?

No, not always.

The treatment depends on French domestic law, the nature of the income, the service provider’s country of residence, the applicable tax treaty and the supporting documents available.

The case must be analysed before payment. A tax treaty may limit or eliminate withholding tax in certain configurations, but only if the conditions are met and documented.

Is an invoice issued from Dubai enough to avoid withholding tax?

No.

A billing address is not enough. The service provider’s genuine tax residence, the nature of the service, the place of performance, the applicable tax treaty and the available documentation must be checked.

Economic reality prevails over administrative appearance.

Is the 183-day threshold enough to prove tax residence outside France?

No.

The 183-day threshold is a common indicator, but tax residence also depends on other criteria: home, centre of economic interests, place of activity, local rules and the tax treaty.

A full analysis remains necessary.

Does a tax treaty always make it possible to avoid withholding tax?

No.

A tax treaty may limit taxation in France, but its application depends on the type of income, the beneficiary’s genuine tax residence and the conditions set out in the text.

It must be checked and documented.

Does StelarWork make it possible to pay less tax?

No.

StelarWork is not a tax avoidance tool. The freelancer’s tax status must pre-exist and reflect reality. If the freelancer is genuinely tax resident outside the EU, StelarWork can remove contractual and administrative friction for the IT services firm.

StelarWork does not create foreign tax residence and does not validate artificial arrangements.

Does StelarWork sign in the freelancer’s name?

No.

StelarWork contracts in its own name with the IT services firm. StelarWork does not present itself as the freelancer’s representative in France and does not conclude contracts in the freelancer’s name.

This distinction is important in the analysis of permanent establishment risk.

Does StelarWork provide a consultant to the IT services firm as staff secondment?

No.

The relationship is structured as a B2B service, with a scope, deliverables, an expected outcome and a purchase order.

The objective is to avoid grey areas linked to simple operational integration without a service framework.

What should an IT services firm check before signing a non-EU freelancer?

It must check, at a minimum, genuine tax residence, the nature of the service, the applicable tax treaty, the supporting documents available, payment terms, supplier compliance obligations, contract wording and permanent establishment risk.

These checks must be adapted with the IT services firm’s legal and tax advisers.

Conclusion

Withholding tax on a non-EU service is not an administrative detail. For an IT services firm, it is a matter of compliance, documentation and supplier liability.

The right treatment always depends on reality: genuine tax residence, effective remote service, absence of an organised presence in France, applicable tax treaty and a consistent supporting file.

Healthy configurations can be structured. Artificial arrangements must be set aside.

StelarWork helps IT services firms contract with tech freelancers genuinely established outside the EU by turning a difficult-to-sign relationship into a French supplier relationship, documented and designed to reduce compliance friction.