KYB for a non-EU freelancer: how to verify who really signs the contract

Your IT services firm can lose a deal simply because the selected freelancer doesn't present a signatory acceptable to your procurement, finance or compliance teams.

The topic isn't only whether the profile is good.

The topic is who signs, in the name of which entity, with which supporting documents, what apparent tax setup, what invoicing capacity and what level of risk for the firm.

That's precisely what KYB for a non-EU freelancer is about: verifying who signs before committing to the mission.

Why KYB becomes critical with a non-EU freelancer

A firm knows how to contract with a French freelancer.

It knows how to check a company registration number, a registration extract, a URSSAF vigilance certificate, professional liability insurance, an invoice with French VAT or a clearly explained exemption.

With a tech freelancer based outside the EU, the situation changes.

The freelancer may reside in Dubai, Bali, Singapore, Mauritius or elsewhere. They may operate through a local company, an independent status, an offshore entity, or sometimes with no clear structure. They may send an invoice in a foreign currency, with no VAT, with a personal address, a registration number that's hard to verify, or documentation not comparable to French standards.

For the firm, the question becomes simple:

The real KYB question Is the signatory a clearly identifiable person or company, legally capable of contracting, tax-consistent, and sufficiently documented to be accepted as a supplier?

If the answer is vague, the risk moves up the chain.

Procurement, finance, legal and operational management can block the file, even if the end client is already waiting for the consultant.

KYB, KYC: don't confuse the two checks

KYC means "Know Your Customer".

It aims to identify a natural person: identity, residence, official documents, sometimes the beneficial owner or source of funds depending on the context.

KYB means "Know Your Business".

It aims to identify a professional entity: company, registration, legal representatives, beneficial owners, address, activity, capacity to issue an invoice, consistency between the contract and the structure that invoices.

In the case of a non-EU freelancer, the two levels can overlap.

You need to understand:

• who the person delivering the service is;
• which entity invoices;
• who owns or controls that entity;
• who has the power to sign;
• where the activity is really carried out;
• whether the documentation provided is consistent with the proposed arrangement.

The risk appears when these elements don't line up.

Example: a person based in France says they invoice through a Dubai company, with no real presence there, no demonstrable local activity, and a mission carried out from France. That's not a sound configuration. It can expose the contractual chain to a tax, social-security or compliance risk.

Conversely, a freelancer genuinely settled outside the EU, working remotely from their country of residence, with a documented structure and no organised presence in France, presents a more consistent situation.

What the firm must verify before signing

KYB for a non-EU freelancer isn't about piling up PDFs.

It's about validating a contractual logic.

1. The identity of the actual provider

The firm must know which person delivers the service.

That generally includes:

• a valid identity document;
• a declared residence address;
• consistency between the professional profile, the location and the contractual information;
• a check of any sanctions, restrictions or compliance alerts according to internal procedures.

This step is more KYC.

It isn't enough.

A freelancer can be personally identified yet invoice through an entity that raises problems.

2. The existence of the entity that invoices

If the freelancer invoices through a foreign company, the firm must understand that entity.

Points to analyse:

• country of registration;
• exact legal name;
• registration number;
• address;
• legal representative;
• beneficial owner where available;
• declared activity;
• capacity to issue invoices;
• consistency between the entity and the service sold.

The sensitive point is often verifiability.

Some jurisdictions provide clear public registers. Others require local documents, sometimes hard for a French team to interpret.

3. The power to sign

The contract must be signed by a person with the authority to bind the entity.

That's often the forgotten point.

A freelancer may send a contract signed in their personal name while the invoice will be issued by a foreign company. Or the reverse. They may also use an entity of which they are neither the legal representative nor a documented agent.

For a firm, this mismatch creates a risk.

The contract, the invoice, the purchase order, the bank statement and the KYB documents must tell the same story.

A weak signal to address immediately If the signatory's name, the invoicing entity's name and the bank-account holder don't match, the file must be clarified before any purchase order is issued.

4. Apparent tax consistency

StelarWork does not sell tax avoidance.

A freelancer may already be a genuine non-EU tax resident, for example in the United Arab Emirates or Indonesia. In that case, their local tax regime pre-dates the relationship with the firm. The friction for the firm isn't the freelancer's tax rate. The friction is administrative, contractual and compliance-related.

The principle to keep is reality.

A sound configuration notably assumes:

• genuine residence outside the EU;
• a physical presence consistent with that residence;
• a mission genuinely carried out remotely;
• no organised presence in France;
• no foreign entity used as a mere shell;
• documentation consistent across residence, invoicing and execution.

An abusive configuration is different.

It consists, for example, in keeping an activity mainly in France while invoicing through a foreign entity with no substance, for the sole purpose of avoiding French tax or social-security rules. This type of arrangement must be ruled out.

5. VAT treatment and invoicing

International invoicing raises practical points.

Depending on the configuration, the foreign provider's invoice may not include French VAT. The firm must then check the applicable accounting treatment, notably the reverse-charge mechanisms where they're relevant.

But VAT is only part of the topic.

The real operational stake is the ability to integrate the supplier into the firm's systems:

• vendor onboarding;
• purchase order;
• quote or contract;
• compliant invoice;
• verifiable bank details;
• currency;
• supporting documents available in an audit.

If the supplier file doesn't pass internal checks, the mission can be blocked, even if the end client has approved the profile.

The risks for the firm when KYB is insufficient

Incomplete KYB doesn't just create a theoretical risk.

It can produce very concrete effects.

A procurement or finance block

The most frequent case is the administrative block.

The delivery manager wants to move. The end client is waiting. The freelancer is available. But procurement or finance refuses to open the supplier.

Possible reasons:

• an unverifiable foreign entity;
• incomplete documents;
• bank details in a third party's name;
• a non-compliant invoice;
• no identifiable legal representative;
• a country or structure not accepted by internal policy.

The mission then starts late, or not at all.

An inconsistent contractual chain

A firm sells a service to its end client.

It must then secure the relationship with its own supplier.

If the upstream and downstream contracts aren't aligned, the firm can end up exposed.

The back-to-back must notably handle:

• the service scope;
• the deliverables;
• confidentiality;
• intellectual property;
• security;
• liability;
• acceptance terms;
• continuity;
• any subcontracting;
• end-client compliance.

The harder the supplier is to identify, the more fragile this back-to-back becomes.

A poorly controlled reclassification or labour-lending risk

The firm must avoid building a relationship that looks like a mere supply of personnel with no service framework.

The right vocabulary isn't enough.

The contract must reflect a genuine service, with a scope, deliverables, an expected outcome, governance and suitable monitoring terms.

It's not about "placing" a person at the end client's. It's about buying and reselling a framed service.

This distinction matters in a firm's chain, especially when the provider is independent and based outside the EU.

A permanent-establishment risk

Another topic must be handled with caution: permanent establishment.

If a foreign person or company has an organised presence in France, or a dependent agent who habitually concludes contracts in its name, the tax authorities may question whether a permanent establishment exists.

That's why you must avoid arrangements where a French party would act as the foreign freelancer's representative to conclude contracts in their name.

StelarWork doesn't position itself that way.

StelarWork contracts in its own name with the firm, then contractually organises the delivery of the service with the non-EU freelancer. The goal is to give the firm an identifiable French supplier, with a more readable contractual chain, without presenting itself as the freelancer's agent or tax representative.

What a usable KYB file must contain

A usable KYB file must let an internal third party understand the situation quickly.

It must answer five questions.

Who delivers the service?

The person's identity must be clear.

The LinkedIn profile isn't enough. The CV isn't enough. An email address isn't enough.

You need identification consistent with the contract and the mission.

Who invoices?

The invoice must come from the entity named in the contract.

If the invoice comes from a foreign company, that company must be documented.

If the invoice comes from a natural person, their professional status must be understandable.

Who signs?

The person who signs must have authority.

That's the heart of the keyword: KYB for a non-EU freelancer — verify who signs.

The signature must bind the right party. It must not create ambiguity between the natural person, the foreign company and the bank account.

Where is the service carried out?

The real location matters.

A freelancer genuinely based outside the EU who works remotely doesn't present the same risk profile as a freelancer present in France but invoicing through a foreign entity.

The file must document the consistency, without building an administrative fiction.

How is the service framed?

The contract must concern a service.

It must avoid wordings that reduce the relationship to a person's mere availability.

A sound framework specifies:

• the deliverables;
• the objectives;
• the scope;
• the client constraints;
• the security rules;
• the validation terms;
• the responsibilities;
• the invoicing conditions.

Why firms often block on non-EU freelancers

The block doesn't always come from the real risk.

It often comes from the inability to qualify it.

A firm can accept a foreign supplier if the file is clear. But it will struggle to accept a freelancer whose structure is hard to read, whose documents are incomplete or whose invoicing country triggers internal questions.

Operational teams sometimes underestimate this friction.

They see a rare, available, competitive and recommended expert.

Finance teams see a non-standard supplier, a foreign currency, atypical KYB documentation, an international bank account and tax questions.

Both readings are legitimate.

The solution is to turn an operational opportunity into a clean supplier file.

StelarWork's role in this chain

StelarWork steps in between the French firm and the tech freelancer based outside the EU.

Concretely, StelarWork:

• contracts in its own name with the firm;
• invoices the firm as a French supplier;
• contracts the delivery of the service with the non-EU freelancer;
• pays the freelancer under the agreed framework;
• carries part of the documentary and contractual compliance;
• aims to reduce the KYB friction on the firm's side.

The firm doesn't have to directly onboard a foreign supplier that's hard to document.

It contracts with a French company (SASU), within a framework more familiar to its procurement and finance.

The freelancer remains based outside the EU. Their pre-existing tax status isn't turned into a product. StelarWork removes an administrative and contractual friction to let the firm work with an expert who would otherwise have been hard to sign.

StelarWork's positioning StelarWork acts as a French supplier in a provision of services: the company contracts in its own name with the firm, invoices in France and contractually organises the delivery of the mission with the non-EU freelancer. The freelancer remains independent and keeps their own status; StelarWork doesn't stand in for them and doesn't sign in their name.

The points of attention before using a French intermediary

Not all intermediation solutions are equal.

For a firm, the analysis must focus on the model's robustness.

Useful questions:

• Does the intermediary contract in its own name?
• Is the invoice issued to the firm French and compliant?
• Is the scope worded as a service?
• Are the deliverables and responsibilities documented?
• Is the non-EU freelancer identified and verified?
• Are the genuine residence and the place of execution consistent?
• Does the model avoid making the intermediary the freelancer's representative?
• Is the contractual chain aligned with the end-client contract?
• Are the confidentiality, security and intellectual property obligations replicated back-to-back?

The goal isn't to add a party for comfort.

The goal is to make signable a service that wasn't, within the firm's internal standards.

Sound configuration vs abusive configuration

It's useful to distinguish the situations clearly.

Sound configuration

A tech freelancer genuinely resides outside the EU.

They work remotely from their country of residence. They have no organised presence in France. They have a locally consistent professional status or structure. They work on a defined service, with deliverables and a clear contractual framework.

The firm wants to work with them but can't or won't directly onboard their foreign entity.

In this case, a French supplier such as StelarWork can simplify the contractual and documentary chain, while keeping a compliance logic.

Abusive configuration

A person works mainly from France but invoices through a foreign company with no substance. The structure is used as a shell. The displayed tax residence doesn't match reality. The mission is organised as a continuous presence at a French client's, with no genuine outcome-based service.

This type of situation must be refused or restructured before any commitment.

StelarWork isn't meant to make an artificial configuration acceptable.

KYB checklist for a non-EU freelancer

Before committing to a mission, a firm can use this checklist as a basis for internal discussion.

Non-EU freelancer KYB checklist

• Freelancer's identity verified.
• Real country of residence consistent with the mission's execution.
• No organised presence in France.
• Invoicing entity identified and documented.
• Power to sign verified.
• Bank-account holder consistent with the invoicing entity.
• Contract aligned with the invoice and the purchase order.
• Service described by scope, deliverables and outcome.
• Confidentiality, security and intellectual property clauses handled.
• VAT and accounting treatment validated by the competent teams.
• Permanent-establishment risk identified and avoided in the structuring.
• Supplier file acceptable to procurement, finance and compliance.

This checklist doesn't replace a legal or tax analysis.

It helps spot the vague areas before they block the mission.

The right reflex for a firm

The right reflex isn't to ask the non-EU freelancer to "find a solution" in a hurry.

That's often how inconsistent arrangements are born: an entity created too fast, an invoice issued by a third party, an unstable address, incomplete documents, a misaligned signature.

The right reflex is to handle the topic from the commercial qualification stage.

As soon as a non-EU profile is considered, the firm should ask three questions:

1. Who signs?
2. Who invoices?
3. Where is the service really carried out?

If the answers are sharp, the file can move forward.

If they're vague, they must be clarified before the purchase order.

StelarWork steps in precisely at this stage: structuring a readable contractual relationship between the French firm and a non-EU tech freelancer, when directly onboarding the freelancer isn't suited to the firm's internal requirements.

FAQ

What is KYB for a non-EU freelancer?

KYB consists in verifying the professional entity that invoices and signs: legal existence, legal representative, beneficial owner where available, address, invoicing capacity, consistency with the service and the bank account.

In the case of a non-EU freelancer, this check often needs to be completed with KYC on the person actually delivering the mission.

What's the difference between KYB and KYC?

KYC identifies a natural person.

KYB identifies a professional entity.

For a firm, both are useful: you need to know who delivers the service, but also who invoices, who signs and which structure carries the contractual commitment.

Why is verifying who signs so important?

Because the signature binds a contractual party.

If the person who signs doesn't have the power to bind the invoicing entity, the contract can become hard to defend or to enforce. The firm can also end up with a contract, an invoice and a payment that don't correspond to the same legal reality.

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

It's possible in some configurations, if the supplier is documented, verifiable, tax-consistent and accepted by the firm's internal procedures.

In practice, many firms block on vendor onboarding, invoicing, compliance, VAT, the currency or the KYB documentation.

Does StelarWork replace the freelancer in the relationship?

StelarWork contracts in its own name with the firm and then organises the delivery of the service with the non-EU freelancer.

The goal is to give the firm an identifiable French supplier and a more readable contractual chain. StelarWork doesn't sign in the freelancer's name and doesn't present itself as their representative in France.

Is the non-EU freelancer's tax status optimised by StelarWork?

No.

If a freelancer is already a genuine non-EU tax resident, their local regime pre-dates the relationship with the firm. StelarWork doesn't sell a tax rate or tax avoidance. StelarWork removes an administrative, documentary and contractual friction for the firm.

The residence must correspond to a reality: effective presence outside the EU, a mission carried out remotely, no organised presence in France, no shell entity.

What are the main red flags?

The most frequent red flags are:

• an invoice issued by an entity different from the one that signs;
• a bank account in a third party's name;
• a foreign company that can't be verified;
• a declared residence inconsistent with the actual execution;
• a regular presence in France despite non-EU invoicing;
• a contract centred on a person's availability rather than on a service;
• missing tax or legal documentation.

Is a foreign invoice without VAT necessarily a problem?

No, not necessarily.

But the treatment must be understood and validated by the competent teams, notably on reverse-charge topics where they apply. The central point remains the overall consistency of the supplier, the invoice, the contract and the actual delivery of the service.

Does StelarWork provide personalised legal or tax advice?

No.

The elements presented here are general information for decision-makers at IT services firms. They do not constitute personalised legal, tax or social advice. Each situation must be analysed with the firm's competent advisers, according to the facts, the countries involved and the available documents.