Building a file that reassures an IT services firm's procurement team: documents to provide

Your profile has been approved by the operational team, but the IT services firm's procurement team is blocking because your company is outside the EU, your documents are not in the right format, or no one clearly understands who signs, who invoices and who carries the risk.

An IT services firm procurement file for a non-EU freelancer must follow a simple logic: enable the buyer to onboard you as a supplier without creating any grey area.
Not just prove that you can deliver. You also need to reassure them about the provider’s identity, legal existence, tax position, bank details, insurance and contracting setup.

The objective is not to send “more documents”.
The objective is to send the right documents, in the right order, with the right wording.

What procurement wants to verify before approving a non-EU freelancer

For an IT services firm, the supplier file is used to answer four questions.

1. Who signs the contract?
2. Who invoices the service?
3. Who carries the contractual commitments?
4. Who is the operational and administrative contact?

If these answers are unclear, the file will go back and forth.
If they are contradictory, it may be rejected.

This is often the case when the freelancer presents a company in Dubai, Bali, Hong Kong or elsewhere outside the EU, but the IT services firm does not know how to integrate it into its French procurement processes. To understand this friction from the outset, you can read why an IT services firm sometimes refuses a Dubai company.

A good procurement file does not try to “convince” through explanations. It makes the supplier readable, verifiable and contractable.

To frame the topic as a whole, the starting point remains the guide to becoming contractable for an IT services firm. The checklist below focuses specifically on the documents to provide and the order in which to present them.

The logic of a supplier file ready to sign

A file that is ready to sign is not a complete archive of your company.
It is a decision file for procurement.

It must be short, consistent and organised.
Each document must answer a possible objection.

The reading order for procurement

Present your documents in this order:

1. Identification of the provider
2. Signing authority
3. Legal documents
4. Tax documents
5. Bank details
6. Professional insurance
7. Description of the service
8. Useful contacts

This order avoids a common confusion: starting with the day rate, CV or purchase order when procurement has not yet correctly identified the supplier.

The minimum expected content

An IT services firm procurement file for a non-EU freelancer should generally include:

• a clear supplier information sheet;
• a company registration extract or local equivalent;
• articles of association or incorporation documents if requested;
• proof of the signatory’s authority;
• proof of identity for the beneficial owner or director, depending on the KYB procedure;
• a relevant tax certificate or tax information;
• professional bank details or a bank statement;
• a professional liability insurance certificate if available;
• a description of the service and deliverables;
• an administrative contact for contractual exchanges.

The file must show a logical continuity: the same entity signs, invoices, receives payments and assumes responsibility for the service.

1. Identity and identification documents

The first step is to identify the provider unambiguously.

For a non-EU company, procurement may not recognise local formats. You therefore need to make the documents readable for a French team.

Documents to provide

Generally prepare:

• the full legal name of the company;
• the official address;
• the local registration number;
• the relevant register;
• the incorporation date;
• the name of the director or authorised representative;
• the beneficial owners if requested as part of KYB;
• a copy of the signatory’s identity document if the procedure requires it.

If the local document is not in French or English, attach an informal translation. It does not always replace a certified translation, but it helps procurement understand the file quickly.

Watch point: the signatory

The signatory must have authority to bind the entity.

If the signatory’s name does not appear clearly in the registration documents, add a resolution, delegation of authority or any equivalent document.

This step is often underestimated. Yet it is central. To go further, read how to verify who really signs the contract.

2. Legal documents to prepare

Legal documents are used to prove that the entity exists, is active and can provide a service to a French IT services firm.

Essential documents

Depending on the country and legal form, prepare:

• certificate of incorporation or register extract;
• commercial licence if applicable;
• articles of association or memorandum/articles of association if requested;
• proof of the company’s address;
• document naming the directors or managers;
• document naming shareholders or beneficial owners if required.

These documents feed into the supplier file and KYB procedure.
They must not contradict one another.

Documents that remove objections

Some supporting documents are not always mandatory, but can speed up approval:

• certificate of good standing or equivalent;
• recent extract from the local register;
• certificate of activity;
• simple organisation chart if several entities are involved;
• short note explaining the role of each entity.

The simpler the contractual chain, the easier the file is to approve. An IT services firm wants to avoid signing with an entity that does not match the one that invoices or actually performs the service.

3. Tax documents: stay factual and consistent

Tax documents are not there to promise optimisation.
They are there to show where the provider is really located and to avoid an inconsistent qualification.

For a non-EU freelancer, the reality principle is essential: genuine tax residence, effective presence outside France, consistent remote activity, no organised presence in France.

A foreign company used as a mere shell entity, with no substance, while the activity is managed from France, creates an abusive setup that must be avoided. It can expose you to tax, social security and contractual risks.

Useful tax documents

Depending on your situation, prepare:

• local tax number or equivalent;
• tax residence certificate if available;
• tax registration certificate;
• information required for supplier processing;
• simple statement on your real place of activity;
• clarification that there is no permanent establishment in France, if relevant and verifiable.

The aim is not to provide a full tax analysis.
The aim is to avoid a visible inconsistency.

What to avoid

Avoid wording such as:

• “I am based in Dubai but spend most of my time in France”;
• “the company invoices from abroad but everything is managed from Paris”;
• “the foreign address is only administrative”;
• “the client does not need to know where I actually work”.

These statements create an immediate risk for procurement.

A sound setup is based on an operational reality: genuine residence outside the EU, genuine remote service, no permanent organisation in France. An artificial setup may be analysed as abusive.

4. Bank details: consistency and traceability

The bank details must match the contractual supplier.

If the company signs, the bank account must be in the company’s name.
A personal account can trigger a block, even if the bank accepts it locally.

Documents to provide

Prepare:

• bank account details or a bank letter;
• the exact name of the account holder;
• IBAN if available;
• SWIFT/BIC;
• the bank’s address;
• the account currency;
• any intermediary bank details.

Check that the account holder’s name matches the company’s legal name exactly.
Differences in punctuation or abbreviations may be enough to slow down onboarding.

Beware of payment accounts

Some IT services firms accept professional payment accounts. Others reject them or request additional checks.

The issue is not only banking-related. It also touches on internal compliance, fraud prevention and payment traceability.

5. Professional insurance: a signal of seriousness

Professional liability insurance is not always available in the same formats depending on the country. But when it exists, it strongly reassures procurement.

It shows that the provider has anticipated the risks linked to the service.

Expected details

The certificate should ideally mention:

• the name of the insured entity;
• the validity period;
• the covered activities;
• the coverage limits;
• the geographical area covered;
• the insurer;
• any major exclusions if mentioned.

If your insurance does not cover French or European clients, do not hide it.
It is better to clarify this before signature than to discover it during supplier onboarding.

6. The service sheet: connecting the procurement file to the IT services firm’s need

A supplier file should not be purely administrative.
It should also make the service being sold understandable.

To avoid ambiguity, present the engagement as a B2B service with objectives, scope and deliverables. Not as an informal integration into the client’s teams.

Useful information

Add a short sheet with:

• service title;
• context;
• scope;
• expected deliverables;
• follow-up arrangements;
• day rate or expected amount if already approved;
• estimated dates;
• project contacts;
• place of performance, especially if the service is delivered remotely.

This sheet helps qualify the relationship. It supports an outcome-based service logic, or at least a structured service, rather than a simple available resource with no defined scope.

Risk to avoid

Avoid wording that gives the impression that the IT services firm “places” a person with a client without a service framework.

Vocabulary matters.
Talk about supplier, service, deliverables, purchase order, contractual liability and delivery follow-up.

7. Supporting documents that reassure procurement

Beyond the essential documents, some elements reduce friction.

A supplier information sheet in French

Even if your legal documents are in English, a supplier information sheet in French helps a lot.

It can include:

• legal name;
• country;
• legal form;
• registration number;
• address;
• director;
• signatory;
• administrative contact;
• finance contact;
• operational contact;
• currency;
• bank details;
• insurance;
• brief description of the activity.

This sheet does not replace official documents.
It serves as a reading guide.

A short compliance note

One page may be enough to explain:

• where the company is registered;
• where the activity is actually carried out;
• who signs;
• who invoices;
• who performs the service;
• how exchanges are tracked;
• who to contact in case of procurement or finance questions.

This note must remain factual.
It must not promise the absence of risk or provide legal advice.

Consistency between CV, company and contract

If your CV says Paris, your company says Dubai and your engagement says remote from Bali, procurement will ask questions.

This is not necessarily blocking if the reality is clear.
But it must be explained properly.

8. Mistakes that waste time

A file may be rejected for very simple reasons.

Common mistakes

The most common are:

• sending an expired or illegible register extract;
• providing a trading name instead of the legal name;
• using a personal bank account;
• having an unauthorised person sign;
• stating an inconsistent tax address;
• failing to distinguish between the company and the individual;
• mixing several entities without explaining their role;
• presenting a sample invoice before the supplier has been approved;
• responding to procurement with undocumented oral explanations;
• promising a tax position without supporting evidence.

These mistakes generate back-and-forth exchanges.
They can also push the file into legal or compliance review.

To complete this section, read the mistakes that derail an IT services firm contract when you are a non-EU freelancer.

The posture mistake

A non-EU tech freelancer sometimes thinks the topic is purely administrative.
For the IT services firm, it is a supplier risk topic.

The right posture is to provide a clear file without downplaying the questions.
Procurement is not trying to block your engagement. They must document their decision.

To see the topic from a procurement team’s perspective, you can also read the procurement checklist for onboarding a foreign supplier.

When StelarWork is involved in the file

Some profiles are technically strong, but difficult for a French IT services firm to sign directly.
The issue is not the freelancer’s level. It is the foreign supplier’s ability to fit into a French procurement framework.

StelarWork can step in as the IT services firm’s supplier, contracting in its own name with the IT services firm and then relying on a separate framework with the non-EU freelancer for performance of the service.

The freelancer does not become an employee.
StelarWork does not act as the freelancer’s representative in France.
The relationship is structured around a service, deliverables and a clear contractual framework.

What this changes for procurement

For the IT services firm, this makes it possible to deal with a French supplier, with consistent documents, French supplier invoicing and an identified contractual counterparty.

The freelancer, for their part, avoids carrying all the friction of non-EU supplier onboarding alone.

This does not turn an artificial situation into a sound one.
If the tax or operational reality is inconsistent, it must be clarified before any contracting takes place.

Final checklist: your IT services firm procurement file as a non-EU freelancer

Before sending your file, check each point.

Identity

• Full legal name of the company
• Registration number
• Official address
• Identified director
• Identified signatory
• Beneficial owner if requested
• Readable and recent documents

Legal status

• Register extract or equivalent
• Commercial licence if applicable
• Articles of association or incorporation document if requested
• Proof of the signatory’s authority
• Consistency between legal name, address and country

Tax

• Tax number or equivalent
• Tax certificate if available
• Genuine residence consistent with the activity
• No organised presence in France if that is the case
• Factual explanation of the remote delivery model

Bank

• Professional account
• Account holder matching the supplier
• IBAN or local bank details
• SWIFT/BIC
• Currency
• Intermediary bank if necessary

Insurance

• Professional liability insurance certificate if available
• Name of the insured entity
• Validity period
• Geographical area covered
• Activities covered

Service

• Clear scope
• Identified deliverables
• Follow-up arrangements
• Day rate or amount consistent with the purchase order
• Operational contact
• Administrative contact

If a document creates ambiguity, add a short explanatory note. Do not leave procurement to guess.

FAQ

Which documents are essential for an IT services firm procurement file for a non-EU freelancer?

The most important documents are the registration extract or local equivalent, proof of the signatory’s identity, proof of their signing authority, professional bank details, basic tax information and, if available, the professional liability insurance certificate.

The exact list depends on the IT services firm, the country of registration and the level of KYB control applied.

Can a non-EU freelancer be rejected even with a strong technical profile?

Yes. The rejection may come from procurement, finance or compliance, even if the operational team wants to work with you.

Common causes include an entity that is difficult to onboard, incomplete documentation, a signatory who cannot be verified, inconsistent bank details or a tax position that is not sufficiently clear.

Should foreign legal documents be translated?

It is not always mandatory, but it is often useful.
An informal translation into French or English can speed up procurement’s review of the file.

For some sensitive documents, the IT services firm may request a certified translation. In that case, follow its internal procedure.

Does StelarWork replace my foreign supplier file?

StelarWork can reduce friction for the IT services firm by becoming the IT services firm’s contractual French supplier, with a separate relationship with the non-EU freelancer for the service.

This does not remove the need for consistent documents on the freelancer side. StelarWork must also understand who performs the service, within what framework and with what supporting documents.

Legal and tax disclaimer

This article provides general information for non-EU tech freelancers and B2B stakeholders. It does not constitute personalised legal, tax, social security or accounting advice.

International situations must be analysed based on the actual facts: effective residence, length of presence, place of performance, substance of the entity, organisation of the activity, absence or existence of a permanent establishment, and the rules applicable in each country.

A sound setup is based on an operational reality that can be documented. An artificial foreign entity or one used as a mere façade can create significant risks and must be avoided. For any binding decision, consult a qualified professional in the relevant jurisdictions.