Turkey: tech freelancer in Istanbul and French engagements, the playbook

You have passed the technical interview, the end client wants to start, but the French IT services firm blocks when it comes to creating your supplier account because you are a tech freelancer in Turkey, based in Istanbul.

This blockage comes late. Often after several positive discussions. The problem is not your technical level. The problem is how readable your file is: who contracts, who invoices, which VAT treatment applies, what compliance risk the IT services firm agrees to carry, and how it can justify the relationship to its procurement or legal teams.

For a Turkey Istanbul tech freelancer working on French engagements, the central question is therefore not only “how do I find an engagement?”. It is: how do I become contractually signable by a French IT services firm?

Istanbul is a strong tech talent pool, but that is not enough for a French IT services firm

Istanbul has a concentration of strong profiles in backend development, data, DevOps, cybersecurity, mobile, cloud and product engineering. The time difference with France remains reasonable. Remote work is operationally realistic. English is common in tech environments, and some profiles already work with European clients.

On paper, the market is attractive for a French IT services firm looking for a rare profile.

But from a procurement perspective, this technical logic is not enough. An IT services firm does not only sell expertise. It resells a service to its end client. It must therefore secure its own contractual chain.

If your file appears unclear, the IT services firm may prefer a less rare profile that is easier to contract with.

The point is not to “convince” the IT services firm that Turkey is a good tech country. The point is to give it a contractual, documentary and invoicing chain that it can accept without creating an internal risk.

To put Turkey into a broader view of non-EU freelancers working with French clients, you can also read the country-by-country guide to working with France.

What really blocks a French IT services firm with a non-EU freelancer

A French IT services firm may be interested in your profile and still refuse to sign directly with you. The reasons are rarely explained in detail. They often fall under internal compliance.

A foreign invoice that is difficult to integrate

If you invoice from Turkey, the IT services firm has to process international invoicing. This can raise several questions:

• what is your exact status;
• which tax number or registration number should be used;
• which VAT wording should be applied;
• which currency should be accepted;
• which bank account should be validated;
• which accounting treatment should apply;
• which supporting document should be requested in the event of an audit.

In many IT services firms, procurement teams are organised to handle French or European suppliers. A non-EU invoice can fall outside the standard process.

That does not necessarily make it impossible. But it is slower, more controlled, and sometimes rejected as a matter of principle.

The issue is very similar to what is seen in other non-EU countries, as explained in how a freelancer can invoice a French IT services firm compliantly from Thailand.

A contractual chain that is too short or too ambiguous

An IT services firm wants to know exactly who carries the service.

It avoids situations where the relationship looks like simply making an individual available, with no framework for deliverables, liability, intellectual property and confidentiality.

Your contract must therefore read like a B2B service. It must specify:

• the scope of the engagement;
• the expected deliverables or outcomes;
• the validation arrangements;
• the day rate or agreed price;
• confidentiality rules;
• ownership of deliverables;
• the respective liabilities;
• invoicing and payment terms.

An IT services firm may accept a long engagement. But it must be able to explain it as a structured service, not as an unframed individual relationship.

Fear of tax or social security risk

As soon as a non-EU freelancer works with a French company, some legal departments ask questions:

• is the freelancer genuinely tax-resident outside France;
• does the freelancer genuinely work from Istanbul;
• does the freelancer regularly come to work on premises in France;
• is there an organised presence in France;
• does anyone conclude contracts in France on the freelancer’s behalf;
• is the foreign structure real or merely declarative.

These questions do not mean that working from Istanbul is problematic. They mean that the operational reality must be consistent with the documents.

Healthy configuration: you genuinely live and work from Turkey, you have a coherent local status, the engagement is performed remotely, with no organised presence in France, and the contractual chain reflects that reality.

Abusive configuration: a foreign entity with no substance is used only to conceal an activity carried out in France or to artificially avoid tax or social security obligations. This configuration should not be pursued.

StelarWork does not sell tax optimisation. If a freelancer is already genuinely tax-resident outside the EU, StelarWork can remove administrative and contractual friction for the IT services firm. Genuine residence, substance and the consistency of the situation remain decisive.

The file expected by a French IT services firm’s procurement team

To maximise your chances, prepare a clear supplier file before the contracting phase even begins. This reduces the risk of a blockage at the critical moment.

The basic information to make immediately readable

Your file must allow the IT services firm to understand who you are and how you operate.

In particular, prepare:

• your professional identity;
• your real business address in Istanbul;
• your working status in Turkey;
• your local registration details, if applicable;
• your tax number or professional identifier;
• your professional bank details;
• a short presentation of your activity;
• your up-to-date CV or technical profile;
• anonymised professional references if necessary;
• a professional liability insurance certificate if you have one.

The aim is not to drown the IT services firm in documents. The aim is to avoid making it guess.

The signals that reassure legal and compliance teams

A good file is not limited to an invoice and a CV. It shows that the relationship can be audited.

Positive signals include:

• an address consistent with your genuine residence;
• a bank account in the name of the professional or structure issuing the invoice;
• correctly numbered and dated invoices;
• contractual wording consistent with a B2B service;
• the ability to explain your VAT regime without approximation;
• no artificial arrangement between several countries without justification;
• clear traceability between contract, purchase order, invoice and payment.

Conversely, some signals create friction:

• an invoice issued by an entity that the freelancer cannot explain;
• a bank account in a country with no link to the activity;
• a contradictory residence address;
• no clear local status;
• a contract signed by a person who is not the real supplier;
• a “zero tax” promise presented as a commercial argument;
• refusal to provide minimum KYC information.

These points are not specific to Istanbul. They appear in several non-EU jurisdictions. The procurement obstacles are similar to those described in what blocks invoicing a French IT services firm from Dubai or Bali.

International invoicing: what the IT services firm wants to avoid

Invoicing is often the breaking point. An IT services firm may like your profile, but not want to manage a direct international invoice.

VAT must be handled properly

In an international B2B relationship, VAT depends on the nature of the service, where the parties are established and the applicable rules. A French IT services firm expects an understandable invoice with the correct wording.

Where the supplier is outside the EU, some cases involve a reverse charge mechanism on the French client side. But this treatment must be properly documented. If the invoice is ambiguous, procurement or accounting may block it.

With a French supplier contractually interposed in its own name, the invoice received by the IT services firm fits more easily into its usual processes. The IT services firm then deals with a French supplier, with a more familiar documentary framework.

Payment must follow a clear chain

An international payment can trigger additional checks:

• verification of the beneficial owner;
• consistency between the bank beneficiary and the supplier;
• compliance screening;
• bank fees;
• currency;
• processing times;
• supporting documents to archive.

These points are administrative, but they can cost you an engagement if the IT services firm does not want to manage them.

For a freelancer based in Istanbul, the challenge is therefore to present a payment chain that is simple, consistent and documented. The right payment is the one that matches the right contract and the right invoice.

Contracting: what an IT services firm wants to read in the chain

A French IT services firm wants to avoid an imprecise relationship. It wants a sufficiently clear back-to-back contractual chain between what it sells to its end client and what it buys from its supplier.

The contract must talk about a service, not only time spent

Day rates are common in tech engagements. But they must not erase the notion of a service.

Even with a day rate, the contract must frame:

• the functional or technical scope;
• the expected deliverables;
• follow-up and validation arrangements;
• liabilities;
• confidentiality rules;
• intellectual property;
• acceptance procedures, if any;
• end-of-engagement arrangements.

This allows the IT services firm to present the engagement as an outcome-based service, even if it takes place in an agile environment or in collaboration with a client team.

The purchase order must match reality

The purchase order must not be a decorative document. It must be consistent with:

• the contract;
• the quote or commercial agreement;
• the service period;
• the day rate or price;
• the deliverables;
• the invoice.

Inconsistencies between these documents are a weak signal for a procurement department. They slow down validation.

Due diligence must be anticipated

Depending on the case, the IT services firm may need to document its supplier relationship as part of its internal or regulatory obligations. Even where no specific formal obligation applies, large accounts often impose their own checks.

A non-EU freelancer should therefore expect more complete KYC requests than a local supplier. This is not abnormal. It is a consequence of the perceived risk.

The specific case of Istanbul: what can reassure a French IT services firm

Istanbul can be reassuring if your presentation is structured.

The time-zone proximity makes meetings with French teams easier. The depth of the tech talent pool gives credibility to sourcing. Remote work from Istanbul can be compatible with the project rituals of a French IT services firm.

But these advantages must come with a clean administrative framework.

A good presentation could fit into a few lines:

• you are a tech freelancer based in Istanbul;
• you work remotely from Turkey;
• you have a coherent local status;
• you invoice within a documented professional framework;
• you are not asking the IT services firm to manage a grey area;
• you accept a structured contractual setup around deliverables and a purchase order.

This positioning is more reassuring than a pitch focused only on price or flexibility.

A French IT services firm is not only looking for a good developer. It is looking for a supplier that does not weaken its own relationship with its end client.

For comparison with another non-EU setup followed by French IT services firms, the case of freelancers in Tunisia: contracting cleanly from Tunis helps show how the same contracting issues appear in another market.

Where StelarWork fits into the chain

StelarWork intervenes when the French IT services firm wants to work with a non-EU tech freelancer, but does not want to sign directly with them or manage complex international invoicing.

The model is simple:

• StelarWork contracts in its own name with the French IT services firm;
• StelarWork frames the service with the freelancer based outside the EU;
• the IT services firm receives a French supplier invoice;
• the freelancer is paid within the agreed framework;
• the contractual chain is documented and more readable for procurement.

StelarWork does not sign on behalf of the freelancer. StelarWork is not the freelancer’s representative in France. StelarWork does not create an artificial French presence for them. The relationship is structured around a service, deliverables, a purchase order and coherent invoicing.

This positioning is designed to reduce administrative friction for the IT services firm, without transforming the freelancer’s tax or operational reality.

What this changes for the freelancer based in Istanbul

For you, the benefit is concrete: you can be presented as a technically relevant profile without making the IT services firm carry all the complexity of a non-EU supplier.

This can help when:

• the IT services firm refuses non-European suppliers;
• procurement does not know how to onboard a Turkish freelancer;
• accounting blocks the invoice;
• legal asks for a cleaner contractual chain;
• the end client imposes supplier requirements;
• the engagement is ready to start but the internal process slows it down.

StelarWork does not replace your commercial skills or your operational seriousness. Its usefulness lies in contracting, invoicing and compliance.

What this does not change

StelarWork does not make an inconsistent situation acceptable.

If you claim to be based in Istanbul but in reality work in an organised way from France, the problem does not disappear. If your structure is a shell entity with no economic reality, the risk remains. If you cannot explain your residence, status or invoicing, the IT services firm will remain exposed to questions.

The principle remains the same: genuine residence, genuine activity, coherent documents, and an engagement performed within a compliant framework.

The objections observed with some foreign companies without substance are close to those explained in why a Dubai free zone company blocks French IT services firms. The country changes, but the compliance logic remains similar.

Prepare your approach before speaking to a French IT services firm

A tech freelancer based in Istanbul saves time by anticipating questions before they are asked.

Clarify your presentation sentence

Avoid vague wording.

Prefer a professional sentence:

“I am a tech freelancer based in Istanbul. I work remotely on backend development services, with a documented B2B invoicing and contracting framework.”

This sentence says three useful things:

• you are outside the EU;
• you work remotely;
• you have anticipated the contractual topic.

Separate the technical from the contractual

In the first discussions, the IT services firm assesses your expertise. But as soon as the engagement becomes real, the supplier topic arrives.

So prepare two files:

• a technical file: CV, stack, references, availability, day rate;
• an administrative file: status, invoicing, residence, bank, insurance, KYC documents.

This avoids mixing topics and creates an impression of control.

Do not sell a tax advantage

An aggressive tax argument worries a French IT services firm. It can give the impression that the engagement relies on a grey area.

If you are genuinely tax-resident in Turkey, present it as a fact of your situation, not as a product. The IT services firm wants to know whether the relationship is compliant. It is not looking to buy a promise of optimisation.

Accept that the IT services firm thinks in terms of risk

A freelancer often thinks in terms of expertise, availability and day rate. An IT services firm also thinks in terms of audit, liability, end client, invoicing, VAT and due diligence.

Your objective is to answer both logics.

A strong technical profile with a poor administrative file can be rejected. A well-documented profile is more reassuring for procurement and legal.

FAQ

Can a tech freelancer based in Istanbul work with a French IT services firm?

Yes, it is possible if the engagement, residence, invoicing and contracting are consistent. The sensitive point is often supplier onboarding. A French IT services firm may refuse to sign directly with a non-EU freelancer if it does not know how to handle the compliance risk or international invoice.

Why does a French IT services firm block an invoice from Turkey?

The blockage generally comes from international invoicing, VAT treatment, KYC checks, the bank account, the supplier’s status or the difficulty of documenting the contractual chain. Even if the service is technically clear, procurement may refuse a supplier it cannot integrate into its process.

Does StelarWork sign on behalf of the freelancer based in Turkey?

No. StelarWork contracts in its own name with the French IT services firm and separately structures the service relationship with the freelancer. StelarWork does not act as the freelancer’s representative in France and does not conclude contracts on behalf of the freelancer.

Is being tax-resident outside the EU enough to reassure a French IT services firm?

No. Genuine tax residence is important, but it is not enough. The IT services firm also looks at the reality of remote work, the absence of any organised presence in France, the consistency of the local status, the quality of the documents, the invoice, the payment and the contractual chain. A genuine and documented situation is more reassuring than a simple declaration.

Legal and tax disclaimer

This article provides general information for tech freelancers and French IT services firms. It does not constitute personalised legal, tax, social security or accounting advice.

The applicable rules depend on the freelancer’s genuine residence, their local status, the nature of the service, the countries concerned, the applicable tax treaties, any presence in France, the contractual structure and the IT services firm’s practices.

Before signing an engagement or changing your organisation, it is recommended that you consult qualified professionals in the relevant jurisdictions. StelarWork does not offer tax arrangements, does not promise tax savings and is not intended to validate a personal situation without a dedicated analysis.