VAT reverse charge on a service received from a non-EU provider

VAT reverse charge: the point of attention when your firm buys a non-EU service

Your firm has found the right tech freelancer, but their company is based in Dubai, Bali or another country outside the European Union. The day rate is reasonable. The technical level is good. The end client approves the profile.

The block comes next: foreign invoice, no VAT, reverse charge, supplier compliance, due diligence, tax risk, contractual clauses, international payment.

For a French IT services firm, the VAT reverse charge isn't an accounting detail. It's a mechanism that can be perfectly normal in a non-EU service, but that must be understood, documented and correctly handled.

This article explains how the VAT reverse charge works in an international B2B context, the frequent risks for a firm, and the cases where a French contractual intermediary such as StelarWork simplifies the supplier relationship.

This article provides general information on VAT, international invoicing and B2B compliance. It does not constitute personalised legal, tax or accounting advice. Each situation must be validated with your chartered accountant, your tax adviser or your legal department.

What is the VAT reverse charge?

The VAT reverse charge is a mechanism in which the business customer declares the VAT due on a transaction themselves, instead of the supplier charging it.

In a classic B2B relationship between two French companies, the supplier charges French VAT. The customer pays it to the supplier, then deducts it under the applicable rules.

In certain international transactions, notably when a provider is established outside France, the supplier doesn't charge French VAT. The French customer must then reverse-charge the VAT: they declare it as output VAT and, if the deduction conditions are met, deduct it simultaneously.

In practice, for a VAT-registered firm, this can have a neutral financial effect. But the reporting obligation remains real.

The frequent mistake is to consider that the absence of VAT on a foreign invoice means there's no VAT issue. That's rarely the right reasoning.

Why the VAT reverse charge concerns IT services firms

Firms regularly buy intellectual services: software development, DevOps, data engineering, cybersecurity, cloud architecture, QA, product engineering.

When the provider is established outside the EU, the invoice received can be issued by:

• a services company based in the United Arab Emirates;
• a structure registered in Singapore;
• an independent contractor based in Indonesia;
• a foreign company owned by an expat French freelancer;
• a tech provider operating full-remote from a third country.

In this type of scheme, the question isn't only: "is the freelancer good?"

The question is also: "can the firm integrate this supplier into its procurement process without creating a tax, contractual or compliance risk?"

The VAT reverse charge is one of the first checkpoints.

The general principle for a non-EU service

For a B2B provision of services, the general VAT place-of-supply rule often leads to taxing the transaction in the business customer's country.

If a French firm buys a service from a provider established outside the EU, the service can be regarded as located in France for VAT purposes. The foreign supplier doesn't necessarily charge French VAT. The firm must then reverse-charge the VAT in France.

The exact treatment depends on the nature of the service, the place of establishment of the parties, their status as taxable persons and any special rules that apply.

For a classic B2B tech service, the reverse-charge mechanism is frequent.

The foreign provider's invoice should ideally carry consistent statements: identification of the supplier, identification of the customer, description of the service, amount excluding tax, absence of VAT charged, and a statement indicating that VAT is reverse-charged by the customer where applicable.

Without these elements, the risk isn't only tax-related. It also becomes operational: blocked invoice, delayed payment, rejection by supplier accounting, request for correction.

What the firm must check on a non-EU invoice

An invoice issued by a non-EU freelancer or company must be readable for your accounting. It must allow you to justify the nature of the purchase and its VAT treatment.

The points to check include:

• the supplier's full identity;
• their real address of establishment;
• their local registration number where one exists;
• the full identity of the customer firm;
• the service period;
• the precise description of the service;
• the amount invoiced;
• the currency;
• the absence of French VAT charged;
• the reverse-charge statement where the mechanism applies;
• the consistency between invoice, contract and purchase order.

The most sensitive point is often the description of the service.

An invoice stating only "IT services" or "consulting" is weak. It poorly documents the reality of the transaction. A more precise wording, linked to deliverables or an outcome-based service, is preferable.

Examples:

• development of an authentication module;
• fixing of bugs on an API;
• setting up a CI/CD pipeline;
• audit of a cloud configuration;
• delivery of a set of automation scripts;
• contribution to a backlog defined in a purchase order.

For a firm, documentary consistency is essential. The contract, the purchase order, the deliverables, the invoices and the monitoring elements must tell the same story.

VAT reverse charge doesn't mean absence of compliance

The reverse charge answers a VAT question. It doesn't settle everything.

A firm that buys a non-EU service must also ask supplier-compliance questions:

• does the supplier genuinely exist?
• do they have sufficient substance in their country?
• who actually delivers the service?
• does the provider genuinely work from abroad?
• is there an organised presence in France?
• are the contractual flows consistent with the operational flows?
• are the confidentiality, intellectual property and security clauses suitable?
• is the payment made to an account consistent with the contractual supplier?

These questions are especially important when the provider is a French or French-speaking tech freelancer who lives outside the EU.

The fact that a freelancer is based in Dubai, Bali or elsewhere can be perfectly normal. But you must document the reality: effective residence, activity carried out remotely, absence of an organised presence in France, absence of an artificial scheme.

Reality principle: residence, genuine remote work and no organised presence in France

On international tax topics, the sound logic rests on the reality principle.

A sound configuration is one where the freelancer:

• genuinely resides outside France and outside the EU, in the sense of the 183-day threshold generally used for effective tax residence;
• effectively carries out their activity from abroad;
• has a consistent local structure or status;
• doesn't habitually work from France;
• doesn't have an organised presence in France;
• doesn't create confusion between the displayed residence and the operational reality.

Conversely, an abusive configuration would be a non-EU shell entity used while the activity is in reality carried out from France, with no local substance or genuine residence. This type of scheme can be reclassified. It must not be set up.

StelarWork does not sell tax avoidance. The fact that a freelancer is subject to a non-EU local tax regime relates to their pre-existing situation, which must be genuine and documented. StelarWork steps in to remove a contractual, administrative and compliance friction between a French firm and a tech provider who can't be directly integrated into the usual procurement circuits.

The permanent-establishment risk

The permanent-establishment topic must be looked at seriously.

When a foreign provider develops an activity in France in an organised way, or when a person habitually concludes contracts in France in that provider's name, the authorities may question the existence of a permanent establishment.

For a firm, this risk isn't always direct. But it can weaken the supplier relationship, especially if the contractual arrangement is poorly structured.

A key point: a French structure must not be presented as the foreign freelancer's representative signing in their name. This type of language creates dangerous confusion.

StelarWork contracts in its own name with the firm. The firm has a French supplier. In parallel, StelarWork organises its contractual relationship with the non-EU provider within a separate framework, designed to reflect a B2B service, with obligations, deliverables and a consistent documentary chain.

The goal is to reduce grey areas, not to create an artificial representation in France for the freelancer.

The risk of unlawful labour lending: why the service must be framed

In tech services, the line between a provision of services and staff secondment must be controlled.

A firm must avoid schemes where an external party is integrated as a de facto employee, with no autonomy, no deliverables, no real contractual framework, and under direct operational control comparable to a relationship of subordination.

The right angle is that of a service:

• a defined scope;
• deliverables;
• a purchase order;
• supplier responsibility;
• delivery monitoring;
• invoicing consistent with the service;
• back-to-back documentation between the commitments taken on and those subcontracted.

This doesn't mean a tech service can't be monitored regularly. A firm needs visibility. But the relationship must stay structured as a B2B service, and not as an informal secondment of a person.

StelarWork is designed to fit this logic: a French supplier contracts with the firm for a service, then organises delivery with the non-EU freelancer within a separate contractual framework.

What StelarWork changes on the firm's side

When the firm contracts directly with a non-EU freelancer or company, it must handle:

• international invoicing;
• the VAT reverse charge;
• foreign-supplier validation;
• international payments;
• compliance documents;
• contractual consistency;
• intellectual property clauses;
• risks linked to residence and establishment;
• the supplier's acceptability to the procurement or finance department.

With StelarWork, the firm contracts with a French company (SASU).

This changes the operational treatment: the firm receives a French supplier invoice from StelarWork, under the rules applicable to a French company. In most cases of French B2B services, this means an invoice with French VAT, save for any special regime that applies.

The firm therefore no longer has to integrate a non-EU supplier directly into its procurement process. It works with a French supplier — identified, contractual, and designed to carry the administrative and compliance layer linked to the foreign provider.

StelarWork invoices the firm. StelarWork pays the non-EU freelancer. StelarWork carries the contractual, documentary and operational framework between the two relationships.

VAT reverse charge: before and after interposing a French supplier

Here's the essential distinction.

If the firm buys directly from a non-EU provider, it may have to reverse-charge French VAT on the service received.

If the firm buys from StelarWork, a French company, it receives a French invoice. The reverse charge linked to the direct non-EU purchase is no longer the firm's issue in this relationship. The topic is handled in the contractual chain carried by StelarWork, under the rules applicable to its own purchases and sales.

This point matters for finance departments. It's not about making VAT disappear. It's about moving the complexity to the right contractual level, with a French supplier that structures the relationship.

The firm keeps its own accounting and tax obligations on the invoices it receives. But it avoids directly managing a hard-to-validate foreign supplier.

Simplified example

A French firm wants to bring in a backend developer based in Dubai.

Situation 1: direct contract with the freelancer's company

The freelancer invoices from their local structure.

The firm receives a non-EU invoice with no French VAT. It must analyse the VAT treatment, probably reverse-charge the VAT if the service falls within the applicable scope, and document the supplier's compliance.

It must also handle the international contractual clauses, the payment, intellectual property, confidentiality and the supplier's acceptance by procurement.

This scheme can work. But it requires administrative and accounting maturity.

Situation 2: contract with StelarWork

The firm issues a purchase order to StelarWork for a defined service.

StelarWork invoices the firm as a French supplier. StelarWork organises delivery contractually with the non-EU freelancer, in its own name, in a service-and-deliverables logic.

The firm doesn't have to bring the Dubai structure directly into its supplier repository. It benefits from a French contractual counterpart and a more readable framework for its finance, procurement and compliance teams.

Common mistakes to avoid

Believing an invoice without VAT is always correct

A foreign invoice without VAT can be normal. But it must be handled. The reverse charge must be analysed and correctly declared when the conditions are met.

Confusing the freelancer's tax status with the firm's VAT treatment

The fact that a freelancer is a genuine non-EU tax resident doesn't exempt the firm from its VAT obligations in France when it buys the service directly.

These are two different topics.

Accepting a foreign entity with no substance

A non-EU company must correspond to a reality. If the entity is a shell with no real activity, used to mask an activity carried out from France, the risk rises sharply.

Leaving the transaction without a precise purchase order

A vague purchase order weakens the relationship. You must document the service, the scope, the deliverables, the dates, the responsibilities and the validation conditions.

Treating the relationship as a mere individual presence

A tech service must remain a service. The contractual and operational vocabulary matters: supplier, service, deliverables, outcome, responsibility, invoicing.

Firm checklist before buying a non-EU service

Before validating a non-EU tech supplier, your firm can check the following points:

• Is the supplier clearly identified?
• Is their country of establishment consistent with the reality of the activity?
• Is the service delivered remotely from abroad?
• Is there an organised presence in France?
• Does the invoice correctly indicate the absence of VAT and the applicable mechanism?
• Has the VAT reverse charge been validated by accounting?
• Does the contract provide for intellectual property?
• Are the confidentiality and security clauses suitable?
• Is the scope described as a service with deliverables?
• Is the payment consistent with the contractual supplier?
• Does the end client accept this supplier scheme?
• Can internal procurement reference this provider?
• Is the risk of operational dependence controlled?
• Would the supplier file be defensible in the event of an inspection?

If several answers are uncertain, the direct non-EU contract can become too heavy for the firm.

When StelarWork is relevant

StelarWork is relevant when the firm has identified a non-EU tech freelancer, but the direct contract with their structure isn't acceptable or is too risky for internal processes.

Typical cases:

• a freelancer based in Dubai with a local company;
• a senior developer based in Bali;
• a cloud expert living outside the EU on a lasting basis;
• a rare profile validated by the end client, but an unreferenceable supplier;
• a procurement department that refuses a non-EU invoice;
• a finance department that doesn't want to handle the reverse charge and international documentation;
• a need for a French supplier on the contract.

StelarWork turns a hard-to-sign relationship into a more readable French supplier relationship, without presenting the freelancer as an employee, without representing the freelancer in France, and without promising an artificial tax advantage.

The goal is simple: to let the firm buy a compliant, documented tech service that's usable within its B2B processes.

When StelarWork isn't the right answer

StelarWork isn't intended to cover artificial schemes.

The model isn't suitable if:

• the freelancer actually lives in France while displaying a non-EU structure;
• the foreign entity has no substance;
• the service is conceived as an individual presence with no deliverables;
• the client is mainly seeking an artificial tax advantage;
• the operational framework creates a de facto subordination;
• the parties want to circumvent the applicable rules.

In these cases, the right reflex isn't to add an intermediary. The right reflex is to review the scheme.

Compliance rests on reality, not on wording.

Key takeaways

The VAT reverse charge is a normal mechanism in many non-EU B2B services. For a firm, it isn't necessarily costly in cash terms, but it requires rigorous accounting and documentary treatment.

The real topic goes beyond VAT. It touches on supplier compliance, the provider's genuine residence, international invoicing, intellectual property, the permanent-establishment risk and the framing of the service.

When the direct contract with the non-EU freelancer is too complex, StelarWork lets the firm work with a French supplier that carries the contractual and administrative relationship with the foreign provider.

This isn't a tax promise. It's a B2B structuring solution to make a non-EU tech service more acceptable, more readable and better documented on the firm's side.

FAQ

Does the VAT reverse charge always apply to non-EU services?

No. It depends on the nature of the service, the status of the parties and the applicable place-of-supply rules. For a B2B tech service bought by a French firm from a non-EU provider, the reverse charge is frequent, but it must be validated by accounting or the tax adviser.

Is a non-EU invoice without VAT correct?

It can be. But the absence of VAT charged doesn't mean there's no obligation on the customer's side. The firm may have to reverse-charge the VAT in France and keep consistent documentation.

Does the VAT reverse charge cost the firm anything?

When the firm is VAT-registered and has a full right of deduction, the effect can be neutral: the VAT is declared as output and deductible. But it remains a reporting obligation. A treatment error can create a risk of reassessment or correction.

Does StelarWork replace the VAT reverse charge for the firm?

When the firm contracts with StelarWork, it receives an invoice from a French supplier. It therefore doesn't handle the direct invoice from the non-EU freelancer. The VAT topic is then that of a relationship with a French company, under the rules applicable to that relationship.

Does StelarWork offer a tax advantage?

No. StelarWork doesn't sell tax avoidance. If a freelancer is a genuine non-EU tax resident, with an activity genuinely carried out remotely from that country, that's a pre-existing situation that must be documented. StelarWork removes a contractual and administrative friction for the firm, without creating an artificial residence or a shell entity.

Can a firm contract directly with a freelancer based in Dubai or Bali?

Yes, if the supplier is genuine, documented, accepted by procurement, correctly invoiced and compliant with internal requirements. But this scheme requires managing international invoicing, the VAT reverse charge, payment, compliance and contractual clauses. Many firms prefer a French supplier to secure their procurement process.

What's the main risk of a bad non-EU scheme?

The main risk is the contradiction between the documentation and reality. For example: a company displayed as non-EU while the freelancer actually works from France, with no local substance, or a service described as independent while it operates as a permanent individual integration. These schemes must be avoided.

What should a purchase order contain for a non-EU tech service?

It must describe the service, the scope, the deliverables, the period, the validation conditions, the responsibilities and the invoicing terms. The more precise the document, the more it supports the reality of a structured B2B service.