UK post-Brexit: is a British freelancer “non-EU” for an IT services firm?

Your procurement team is blocking the purchase order because the freelancer is in the United Kingdom, while the project team still treats them as an “almost European” profile.

Since Brexit, that reflex is no longer enough. For a French IT services firm, a British freelancer must be analysed as a provider established in a third country outside the European Union, with immediate consequences for VAT, supplier due diligence, contractual clauses and the documentation to collect.

The issue is not geographical. London is still close to Paris. The issue is legal: the United Kingdom is no longer in the European Union.

Is a British freelancer non-EU since Brexit?

Yes. For a French IT services firm, a British freelancer is a non-EU freelancer.

Since the United Kingdom effectively left the European Union, a provider established in the UK no longer falls under the standard intra-EU framework. They must be treated as a supplier located in a third country, in the same way as a freelancer based in Dubai, Bali, Vietnam or any other jurisdiction that is not a member of the European Union.

This does not mean the United Kingdom is inherently a “risky” destination. It means your procurement, finance and compliance processes cannot use the same automatic checks as for a freelancer established in France, Belgium, Spain or Germany.

The right reflex for an IT services firm: do not ask “Is the United Kingdom close to the EU?”, but “Is this supplier established in the EU in the legal and tax sense?”. Since Brexit, the answer is no.

To place the UK case within a broader framework, you can read the country-by-country guide to contracting with France. The United Kingdom follows the same analysis logic as any other third country, even if its administrative environment is more familiar to many French IT services firms.

Why the confusion persists within IT services firms

The confusion comes from three habits.

First, many British freelancers were already working with French clients before Brexit. Operational teams have sometimes kept the same reflexes: day rate in euros, communication in English, remote engagement, smooth project workflow.

Second, the United Kingdom is still perceived as a reliable, structured and nearby market. That commercial proximity does not change the legal classification.

Finally, some procurement tools or ERPs still have overly simplistic internal categories: “Europe”, “international”, “intragroup”, “freelance”. Compliance, however, is not managed through a commercial region. It is managed according to the supplier’s genuine establishment, status, country of registration, VAT regime and the obligations applicable on the client side.

Consequence no. 1: VAT is no longer treated as an intra-EU transaction

For a B2B service between a British freelancer and a French IT services firm, the VAT position must be checked as a service performed by a supplier established outside the EU.

In practice, the IT services firm must in particular look at:

• the country of establishment of the freelancer or their company;
• the tax number or VAT number available;
• the exact nature of the service;
• the place where the service is economically consumed;
• the wording expected on the invoice;
• the possible reverse charge mechanism on the French client side.

The point is not to “find a VAT trick”. The point is to avoid an invoice that accounts payable cannot process, a rejection by procurement or an urgent correction at month-end.

A post-Brexit British invoice is not checked like an intra-EU invoice. The IT services firm must ensure that the VAT treatment genuinely matches a cross-border service with a supplier established in a third country.

The Dubai or Bali cases are different, but they reveal the same friction points: VAT, non-European supplier, supporting documents, procurement compliance. To explore this operational logic further, see what blocks an invoice to a French IT services firm from Dubai or Bali.

Consequence no. 2: supplier due diligence changes in nature

A French IT services firm cannot simply rely on a LinkedIn profile, a day rate and bank details.

Even for a remote engagement, the British supplier must be correctly identified. Depending on the structure used, this may be:

• an individual freelancer;
• a UK limited company;
• a consulting structure;
• a more complex setup involving an entity outside the United Kingdom.

Due diligence must cover the supplier’s real existence, registration, beneficial owner, the consistency between the declared country and the genuine activity, as well as the provider’s ability to issue a compliant invoice.

For an IT services firm, this point is particularly sensitive because the freelancer often works within a subcontracting chain. The end client may require clear traceability of all contributors and all suppliers involved in the service.

What the IT services firm must avoid

The IT services firm must avoid situations where the supplier is legally unclear.

Typical examples:

• the freelancer says they are based in the United Kingdom, but invoices through a company in another jurisdiction without a coherent explanation;
• the company issuing the invoice has no clear link with the person performing the service;
• the contract refers to one person, while the invoice comes from another entity;
• the billing address, bank details, tax status and operational reality do not tell the same story.

A supplier is not problematic simply because they are outside the EU. It is the inconsistency between operational reality and documentation that creates the risk.

The due diligence reflexes observed with Dubai freezone companies illustrate this logic well. A structure may be perfectly legal locally, but difficult for French procurement teams to accept if the documentation does not meet their standards. On this point, see why a Dubai freezone company often blocks French procurement teams.

Consequence no. 3: the contract must be designed as international subcontracting

A non-EU British freelancer must not be contractually integrated as a simple informal reinforcement.

For an IT services firm, the right framework is a service agreement, with an identified supplier, a purchase order, a scope, deliverables, deadlines, confidentiality requirements and, where necessary, back-to-back clauses aligned with the end client’s obligations.

The contract must in particular clarify:

• the nature of the service;
• the expected deliverables;
• the acceptance criteria;
• the acceptance testing process;
• confidentiality rules;
• intellectual property;
• security obligations;
• any subcontracting;
• data protection;
• the consequences of a breach.

The aim is to avoid a relationship that is too close to an integrated-staff logic without a proper service framework. For the IT services firm, the engagement must remain structured around an outcome or deliverables, not around simple operational presence without contractual autonomy.

The more closely the freelancer is integrated into the end client’s teams, the cleaner the contract must be: scope, deliverables, responsibilities, supervision, acceptance. Operational proximity must not erase the contractual reality of subcontracting.

Consequence no. 4: genuine residence remains central

Brexit does not remove the need to verify the reality of the freelancer’s situation.

A non-EU British freelancer must be analysed according to their genuine establishment, genuine tax residence and actual working arrangements. If they genuinely live and work in the United Kingdom, with remote activity from the United Kingdom, the reasoning is coherent.

By contrast, a setup becomes fragile if the documents declare a situation that does not match reality.

Healthy setup

A healthy setup looks like this:

• the freelancer genuinely lives in the United Kingdom;
• they work remotely from the United Kingdom;
• their structure or status matches that reality;
• they do not have an organised presence in France;
• they do not have a team, office or fixed installation in France for this activity;
• the invoice, contract and bank details are consistent.

This setup does not remove the checks, but it gives the IT services firm a clear basis.

Abusive setup

An abusive setup looks more like this:

• a foreign company is used as a mere shell entity;
• the freelancer is in reality habitually working from France;
• the foreign address does not correspond to the genuine place of activity;
• the arrangement aims to conceal an organised presence in France;
• the documentation contradicts the facts.

This type of arrangement should be ruled out. It may create tax, social security, contractual and reputational risks for the parties.

The reality principle prevails: genuine residence, genuine place of performance, absence of an organised presence in France. A foreign entity without substance does not secure a relationship. On the contrary, it may expose it.

This principle applies to the United Kingdom as it does to other third countries. The case of a freelancer in Vietnam follows a comparable logic: a different country, but the same questions around residence, invoice, contract and compliance. See how a freelancer in Vietnam invoices a French IT services firm while remaining compliant.

Personal data: the United Kingdom is no longer in the EU, but remains a special case

For tech engagements, the freelancer may access environments, tickets, test databases, logs, credentials or client data.

Since Brexit, the United Kingdom is no longer in the European Union. You must therefore reason in terms of a transfer to a third country under the GDPR.

However, the United Kingdom benefits from a specific framework recognised by the European Union at the time of writing. This simplifies some situations compared with other third countries, but it does not exempt the IT services firm from documenting access, purposes, security measures and contractual commitments.

The IT services firm must remain attentive to three points:

• does the freelancer access personal data?
• is the data only viewed, or is it also extracted?
• does the end client impose geographical or contractual restrictions?

The answer must be aligned with the main contract between the IT services firm and its end client.

Permanent establishment risk: do not create an artificial French presence

The permanent establishment issue mainly concerns situations where a foreign entity in practice carries out a structured activity in France.

For a British freelancer, the risk increases if the relationship gives the impression that they have an organised presence in France, a representative who commits their business, or local commercial capacity acting on their behalf.

An IT services firm must therefore avoid arrangements where an intermediary is presented as the freelancer’s French representative or as a person concluding contracts in their name.

StelarWork does not act as the freelancer’s representative. StelarWork contracts in its own name within a service chain. It invoices the IT services firm, carries its own contractual framework and pays the provider according to the agreed relationship. The aim is to make the relationship legible for French procurement teams, without artificially creating a French presence for the freelancer.

Where StelarWork fits into this type of situation

An IT services firm’s problem is not always finding the right freelancer. Often, the freelancer has already been identified, technically approved and aligned on the day rate.

The blockage comes next:

• accounts payable does not know how to process the invoice;
• procurement refuses a non-EU supplier;
• the end client asks for a cleaner subcontracting chain;
• the contract proposed by the freelancer does not meet internal standards;
• the documents collected are not sufficient to open the supplier account.

StelarWork then sits between the French IT services firm and the tech freelancer based outside the EU. It contracts in its own name with the IT services firm, invoices the IT services firm, pays the freelancer and carries a compliance framework designed to reduce procurement, finance and contractual friction.

This model is useful when the freelancer is competent, but difficult for the IT services firm to onboard as a direct supplier.

It is not about transforming the freelancer’s tax situation. If the freelancer is already genuinely resident outside the EU, with activity genuinely carried out outside France, StelarWork removes administrative and contractual friction on the IT services firm side. It does not sell tax optimisation and does not create an artificial foreign residence.

The case of a freelance developer in Dubai clearly shows this type of blockage: the operational need exists, but the French IT services firm does not want to, or cannot, contract directly with a foreign structure. See how to work with French IT services firms from Dubai as a freelance developer.

Operational checklist for a French IT services firm

Before contracting with a non-EU British freelancer, the IT services firm can check a few simple points.

Supplier qualification

Is the supplier clearly identified?

You need to distinguish the person performing the service, the entity issuing the invoice and the country of establishment. These three elements must be consistent.

VAT and invoicing

Has the VAT treatment been validated by finance?

The invoice must be usable by the French IT services firm. The reverse charge mechanism, the wording and the country of establishment must not be improvised at the time of payment.

Contract and deliverables

Is the relationship formalised as a service?

The purchase order must describe a scope, deliverables, responsibilities and acceptance conditions. A simple logic of operational availability is not sufficient.

Data and security

Does the freelancer access sensitive or personal data?

If so, the access must be documented. The confidentiality, security and data protection clauses must be aligned with the end-client contract.

Reality of the situation

Does the freelancer genuinely work from the United Kingdom?

The genuine residence, actual place of performance and absence of an organised presence in France must be consistent with the contract and invoice.

FAQ

Is a British freelancer considered non-EU since Brexit?

Yes. Since Brexit, a freelancer established in the United Kingdom must be treated as a provider located in a third country outside the European Union. For a French IT services firm, this affects in particular VAT, supplier due diligence, the subcontracting agreement and document checks.

Can a French IT services firm work with a British freelancer?

Yes, but the relationship must be framed correctly. The IT services firm must identify the supplier, validate the VAT treatment, formalise a service with deliverables and verify the consistency between the country of establishment, the invoice and the reality of performance.

Is the United Kingdom treated like Dubai or Bali?

On the “non-EU” principle, yes: the United Kingdom has been a third country since Brexit. However, local rules, available documents, the banking context, tax and the personal data framework may differ. You must therefore apply a third-country framework, without mechanically copying the treatment of another jurisdiction.

Does StelarWork become the French representative of the British freelancer?

No. StelarWork does not represent the freelancer and does not enter into contracts in their name. StelarWork contracts in its own name with the IT services firm, within a service framework, in order to make the relationship more legible for procurement, finance and compliance.

Disclaimer

This article provides general information for French IT services firms. It does not constitute personalised legal, tax, social security or accounting advice. The applicable rules depend in particular on the freelancer’s structure, their country of genuine residence, the actual place of performance, the end-client contract, the nature of the services and the data flows. Before making any binding decision, have your situation validated by your usual advisers.