The mistakes that derail an IT services firm contract when you are a non-EU freelancer

Your deal can fall through even after the day rate has been accepted, the end client wants you to start, and the IT services firm only has to approve your supplier file.

At that stage, the blockage rarely comes from your technical level. It more often comes from a procurement, compliance or legal doubt. A document is missing. The company is poorly presented. The contract looks too much like individual staff secondment. Your posture gives the impression of a disguised employee.

These contracting mistakes between an IT services firm and a non-EU freelancer are often avoidable. The aim is not to “convince at any cost”. The aim is to make your file readable, verifiable and contractable.

Why an IT services firm hesitates at the last minute

A French IT services firm does not sign only with a skillset. It signs with a supplier.

Even if the commercial discussion is advanced, the IT services firm must be able to justify:

• who its contracting party is;
• who has authority to sign;
• where the entity is registered;
• what service is being purchased;
• what deliverables or outcomes are expected;
• what compliance risks it accepts;
• how it documents its due diligence.

For a tech freelancer based outside the EU, the difficulty often comes from the gap between the commercial reality and the contractual presentation.

Commercially, you are “the freelance developer recommended for the engagement”. Legally, the IT services firm must onboard a foreign company, verify its existence, understand its model, frame a service, then secure the chain with the end client.

The problem is not always that the IT services firm refuses non-EU freelancers. The problem is often that the file arrives in a form the IT services firm does not know how to validate without taking an internal risk.

If your company is based in Dubai, Bali or elsewhere outside the EU, you can read the guide to becoming contractable with a French IT services firm from Dubai. It sets out the general framework. Here, the objective is more operational: identifying the signals that block a signature.

Mistake no. 1: sending an incomplete supplier file

The first warning signal is simple: the IT services firm has to chase several times to obtain the basic documents.

An incomplete file creates two negative impressions. First, your company appears poorly structured. Second, the IT services firm understands that it will have to carry the compliance effort alone.

Documents generally expected

Expectations vary depending on the IT services firm, but some items often recur:

• certificate of incorporation or equivalent document;
• articles of association or extract identifying the entity;
• proof of the company’s address;
• identification of the beneficial owner where available;
• identity document of the signatory or proof of their authority;
• bank details consistent with the contracting entity;
• tax certificate or local equivalent, if requested;
• professional liability insurance, if applicable;
• clear description of the company’s activity;
• references or contextual information on services performed.

The IT services firm is not just looking for PDFs. It is looking for overall consistency.

If your company has one name in the register, a different one in the quote, another one in the email, and the bank account is not in the same name, the file becomes difficult to defend.

To anticipate this level of expectation, use the onboarding checklist an IT services firm expects from a foreign supplier. It helps distinguish basic documents, compliance evidence and items that reassure procurement teams.

The right reflex

Prepare a single, clean and up-to-date supplier file before you even receive the contract.

It must enable the IT services firm to answer three questions quickly:

1. does the entity really exist?
2. does the person signing have authority to bind the entity?
3. does the announced service correspond to the declared activity?

A good file does not guarantee signature. But a vague file is often enough to delay, escalate or kill the deal.

Mistake no. 2: poorly presenting your non-EU company

Many freelancers talk about their company as a simple personal administrative vehicle. That is understandable in an informal discussion. It is risky in an exchange with an IT services firm.

A poorly presented company gives the impression of an empty shell, created only to bypass contracting constraints.

What worries the IT services firm

The following wording can create doubt:

• “it’s just my structure for invoicing”;
• “I’m independent, the company does not really have any activity”;
• “I mainly work with French clients from abroad”;
• “I can sign with any entity if that helps”;
• “the address is administrative, but I am often in France”.

These sentences may seem harmless. Yet they open sensitive topics: reality of the activity, genuine tax residence, permanent establishment risk, consistency of the service model, due diligence.

The point is not to turn your company into an international group. It is to present it for what it must be: a real, identified supplier, with a consistent activity and the capacity to perform a service.

Healthy configuration vs abusive configuration

A healthy configuration is based on an operational reality.

You are genuinely tax-resident outside the EU. You genuinely work remotely. You have no organised presence in France. Your company has a verifiable existence. The contract describes a service, not disguised integration into the teams of the IT services firm or the end client.

Conversely, an abusive configuration consists in using a foreign entity as a front when the activity is in practice organised from France, with regular presence, strong operational dependence and no real substance. This type of arrangement should not be sought.

StelarWork does not sell tax optimisation. If a freelancer is already genuinely tax-resident outside the EU, StelarWork can remove an administrative friction point for the IT services firm by structuring a compliant French supplier relationship. Genuine residence and genuine remote delivery remain prerequisites for consistency.

If your blockage specifically comes from your Dubai company, the article why an IT services firm blocks your Dubai company and how to remove the barrier explains this symptom from the IT services firm’s side.

Mistake no. 3: not proving who really signs

An IT services firm cannot rely on a name in an email signature. It must know who binds the company.

This point is often underestimated by non-EU freelancers. Yet it can block a contract at the last minute, especially when documents come from jurisdictions whose incorporation extract formats are less familiar to French procurement teams.

Warning signals

Doubt appears when:

• the signatory is not mentioned in the incorporation documents;
• the director’s name differs across documents;
• the email address used is not linked to the company’s domain;
• another person negotiates although they have no apparent mandate;
• the signature is sent without proof of authority;
• the documents do not allow the beneficial owner to be identified.

This is not an administrative detail. It is the basis of contracting.

If the IT services firm cannot verify that the right person is signing, it exposes its contract to a later challenge. That is rarely acceptable for a procurement or legal department.

The right reflex

Before sending the signed contract, gather the items that demonstrate the signing chain:

• incorporation document;
• document listing directors or managers;
• delegation of authority if the signatory is not a director;
• consistency between company name, address, email, any stamp and bank details;
• readable version, translated if necessary, or accompanied by an explanation.

To go further on this point, read how to secure who really signs the contract before submitting your file. It is one of the easiest checks to anticipate, but also one of the most blocking when it comes too late.

Mistake no. 4: accepting a contract that looks like staff secondment

An IT services firm must purchase a service. Not “an available human being”.

The nuance is essential. The more the contract looks like simple staff secondment, the more it creates risks: reclassification, unlawful labour lending, unlawful labour supply, inconsistency with the end-client contractual chain.

The risk increases if the contract only talks about days, presence, working hours, managerial validation and integration into teams, without describing the expected outcomes.

Wording to watch

Some indicators should alert you:

• no service scope;
• no deliverable or objective defined;
• direct attachment to a client manager;
• working hours imposed as for an employee;
• validation of holiday or absences by the client;
• mandatory internal email address without a framework;
• disciplinary reporting rather than service monitoring;
• clause focused solely on a number of days sold.

None of these formulations is automatically problematic in isolation. Their accumulation is what creates a signal of subordination or staff secondment.

The right reflex

The contract must frame a service agreement.

It may mention a day rate, a duration, monitoring arrangements and project constraints. But it must also specify:

• the scope;
• the expected deliverables or outcomes;
• each party’s responsibilities;
• acceptance or sign-off arrangements;
• prerequisites provided by the IT services firm or the end client;
• the limits of the engagement;
• the conditions for modifying the scope.

In an IT services firm chain, the contract must also remain consistent with the upstream contract. This is the back-to-back principle: what is promised to the end client must be compatible with what is requested from the supplier.

The issue is not to mask the reality of the engagement. The issue is to document a genuine service, with a defensible professional framework.

Mistake no. 5: adopting an employee posture

Even with a well-drafted contract, your behaviour can create the wrong signal.

An IT services firm also observes posture. If you ask to be treated like an internal employee, if you use employee language, or if you accept a direct hierarchical relationship, the file becomes more sensitive.

Behaviours that create tension

Here are frequent signals:

• asking for a “freelance hire”;
• talking about “my manager” rather than a project contact;
• asking for holiday approval like an employee;
• accepting imposed working hours without project justification;
• appearing in the internal organisation chart;
• participating in internal rituals with no link to the service;
• using only the client’s HR tools;
• presenting yourself as a member of the client team on LinkedIn.

These items may seem practical day to day. They can also weaken the classification of the relationship.

To understand this point, read the subordination signals that make a relationship slide towards employment. It helps distinguish project coordination from subordination.

The right reflex

Adopt a supplier posture.

You work on a scope. You report on progress. You participate in meetings necessary for the service. You comply with security and confidentiality constraints. But you do not present yourself as an employee of the IT services firm or of the end client.

The difference is sometimes subtle, but it is important.

An IT services firm will be more comfortable if it can document a supplier-to-client relationship, rather than a disguised hierarchical relationship.

Mistake no. 6: treating compliance as an end-of-process detail

Many blockages appear because compliance comes too late.

The sales contact has approved the day rate. The client manager wants to start. The start date is close. The freelancer then sends their documents in a rush. Procurement discovers a non-EU company, an unclear signature, a contract to adapt and missing information.

This is the classic scenario of a deal slowing down at the last minute.

What the IT services firm sees

From the IT services firm’s perspective, urgency does not reduce risk. It increases it.

A procurement department may wonder:

• why the file was not prepared earlier;
• who approved the supplier;
• whether the end client accepts this contractual link;
• whether the upstream contract allows subcontracting;
• whether the supplier complies with internal requirements;
• whether starting without a signed contract exposes the IT services firm.

Even if everything can be regularised, the timing alone can be enough to block the deal.

The right reflex

Treat contracting as a commercial step in its own right.

As soon as the IT services firm shows serious interest, prepare:

• your supplier pack;
• your company presentation;
• proof of the signatory’s authority;
• your service scope;
• your availability limits;
• contractual points to clarify;
• any constraints linked to the end client.

Do not let the topic appear at the signing stage. An IT services firm would rather discover a controlled complexity early than a vague complexity late.

How StelarWork intervenes when the foreign supplier becomes difficult to sign

In some cases, the problem does not come from your file in isolation. It comes from the fact that the IT services firm does not want to, or cannot, contract directly with a non-EU company.

StelarWork then fits into the contract between the French IT services firm and the tech freelancer based outside the EU.

Concretely, StelarWork contracts in its own name with the IT services firm, invoices the IT services firm, contracts with the freelancer, carries the compliance associated with this chain and turns a supplier that is difficult to onboard into a French supplier that is more readable for the IT services firm.

This does not change the underlying reality: the engagement must remain a service. The freelancer must remain genuinely based outside the EU if that is the foundation of their situation. The relationship must not become disguised subordination. The contract must remain consistent with the end client’s requirements.

StelarWork does not replace legal or tax analysis specific to each situation. Its role is to reduce contracting friction for the IT services firm by providing a structured and documented French supplier framework.

This approach is particularly useful when the need has been approved, but the IT services firm cannot finalise its foreign supplier onboarding within the required timeframe or under its internal rules.

Anti-rejection checklist before sending your file to the IT services firm

Before submitting your file, check the following points.

Supplier file

• The company’s legal name is identical everywhere.
• The registration number is visible.
• The address is consistent with the official documents.
• The bank account corresponds to the contracting entity.
• The documents are readable and recent.
• The beneficial owner or director is identifiable.
• The signatory has demonstrable authority.

Company presentation

• The declared activity corresponds to the service.
• The company is not presented as a simple shell.
• Your residence and way of working are consistent.
• You do not suggest an organised presence in France if that is not the reality.
• You explain simply how the service will be performed remotely.

Contract and scope

• The contract describes a service, not personal availability.
• The deliverables or outcomes are identified.
• The scope is sufficiently clear.
• Confidentiality and security obligations are consistent.
• The contractual chain is compatible with the end client.
• The terms used avoid a logic of subordination.

Relationship posture

• You present yourself as a supplier.
• You distinguish between project contact and hierarchical manager.
• You avoid employee wording.
• You document progress on the service.
• You do not ask to be integrated as an internal employee.

This checklist does not automatically turn a file into a signed contract. Above all, it reduces the simple reasons for rejection.

FAQ

What are the most frequent mistakes in an IT services firm contract with a non-EU freelancer?

Frequent mistakes include an incomplete supplier file, a poorly presented foreign company, insufficient proof of signature, a contract too close to individual staff secondment and a posture that resembles employment.

These mistakes create doubts for procurement, legal or compliance teams. They can delay signature, trigger an internal review or kill the deal.

Can an IT services firm refuse to sign solely because my company is outside the EU?

Yes, an IT services firm may decide not to onboard a non-EU supplier directly, depending on its internal policy, client constraints or level of risk tolerance.

The issue is not always tax or technical. It may be purely procurement-related: supplier database, due diligence, legal approval, security, insurance, or difficulty verifying foreign documents.

Should I change my foreign company to reassure an IT services firm?

Not necessarily. The first reflex is to clarify and document what already exists: entity identity, signatory authority, real activity, effective residence, service delivery model and contractual consistency.

Creating or changing a structure without operational reality can create risks. A foreign entity must correspond to a reality: residence, activity, management, delivery and substance.

Can StelarWork help if the IT services firm does not want to sign directly with my non-EU company?

Yes, when the blockage concerns direct contracting with a non-EU supplier, StelarWork can intervene as the IT services firm’s French supplier, contracting in its own name with the IT services firm and with the freelancer.

The objective is to make the contractual chain more readable and compliant for the IT services firm, without turning the relationship into employment and without promising any particular tax treatment.

Disclaimer

This article provides general information on contracting between French IT services firms and non-EU tech freelancers. It does not constitute personalised legal, tax or employment advice.

Every situation must be assessed according to the real facts: effective tax residence, place where the engagement is performed, presence or absence in France, company substance, exact role of the parties, upstream contract with the end client and operational practices. A healthy configuration is based on an economic and operational reality. A foreign entity used as a shell without reality can create significant risks and should not be sought.

For any binding decision, have your situation validated by a qualified adviser.