Tech freelancer in Brazil: invoicing a French IT services firm despite the time difference

Your engagement has been approved by the business team, but the French IT services firm blocks when creating your supplier record because you are a freelancer in Brazil, outside the EU, with a contract, tax residence and international payment to clarify.

The issue is not simply “issuing an invoice”.
For a French IT services firm, the real risk lies elsewhere: contracting properly, justifying non-EU subcontracting, paying without banking friction, and defending the file in the event of a procurement, tax or compliance review.

If you are a tech freelancer based in Brazil and want to work with a French IT services firm, your challenge is therefore simple: make the collaboration clear, documented and acceptable for the IT services firm.

Why a French IT services firm hesitates to contract with a freelancer in Brazil

A French IT services firm may need your expertise quickly.
But its procurement department, finance team or legal team may refuse to sign directly with you.

This refusal is not necessarily linked to your technical profile.
It often comes from the supplier file.

Brazil is outside the EU

Brazil is a third country to the European Union.
For a French IT services firm, this raises several questions:

• which law applies to the contract;
• how to qualify the service;
• how to handle the invoice;
• how to pay a non-EU supplier;
• how to document tax residence;
• how to avoid a situation comparable to an organised presence in France;
• how to prove that the relationship is a genuine service, and not disguised staff secondment.

These points are standard in non-EU subcontracting.
But they become blockers when they are not dealt with before signature.

For an overview of common countries and setups, you can read the country-by-country guide to working with France from abroad.

The IT services firm wants a defensible supplier

A French IT services firm is not only looking for a developer, a DevOps engineer or a data consultant.
It is looking for a supplier it can integrate into its internal process.

This generally implies:

• a clear legal identity;
• a contract consistent with the service;
• a purchase order or usable statement of work;
• an invoice compliant with its accounting process;
• identifiable deliverables or objectives;
• a traceable payment;
• basic documentation on the provider’s tax residence and real location.

If your file is incomplete, the IT services firm may consider that the administrative risk outweighs the value of the engagement.

The blocker is not always commercial.
It is often internal: procurement, finance, tax, compliance, legal.

What the IT services firm must understand before signing

For a Brazil–France collaboration to be contractable, the IT services firm must be able to answer three simple questions.

Who is the supplier?

If you invoice directly from Brazil, the IT services firm must create a foreign supplier.
This means checking your information, bank details, local status, and sometimes tax or administrative documents.

Some IT services firms accept this process.
Others avoid it, especially if the engagement must start quickly or if the financial volume does not justify onboarding an international supplier.

The problem is not that Brazil is impossible.
The problem is that the Brazilian supplier must be readable for a French company.

What is the nature of the service?

The contract must describe a service.
It must avoid wording that looks like staff secondment.

The distinction matters.

A healthy service is based on:

• a scope;
• deliverables;
• responsibilities;
• autonomy in execution;
• a price linked to a service;
• useful reporting, without subordination;
• a coherent contractual chain.

Conversely, a relationship where the IT services firm directly “uses” the freelancer as an integrated employee, without a service framework, may create risks.

The right angle is not “placing a consultant”.
The right angle is “contracting for a tech service with deliverables and a defensible framework”.

How will the international payment be handled?

International payment is rarely the first topic in an interview.
Yet it becomes central at the point of signing.

The IT services firm must know:

• which currency it pays in;
• whom it pays;
• to which bank account;
• with which invoice;
• on what payment term;
• with what accounting documentation;
• how to handle VAT or the VAT reverse charge if applicable;
• how to trace the payment in its ERP.

The subject therefore goes beyond a simple bank transfer.
It relates to supplier compliance.

To explore this flow in more detail without unnecessarily broadening the Brazil topic, see invoicing and paying for a non-EU service: the complete flow.

Tax residence in Brazil: what the IT services firm wants to avoid

Tax residence is a sensitive point.
It cannot be dealt with by a sentence in a contract.

If you are genuinely tax-resident in Brazil, genuinely work from Brazil, and have no organised presence in France, the situation is much more readable for an IT services firm.

The reality principle is central:

• your tax residence must match your real life;
• your activity must be carried out remotely from Brazil;
• you must not operate as if your professional base were in France;
• you must not use a foreign façade entity to conceal a French activity;
• your documents must be consistent with one another.

Healthy setup

A healthy setup looks like this:

• you actually live in Brazil;
• your centre of life and activity is in Brazil;
• you carry out the engagement remotely;
• you have no office, team or permanent commercial organisation in France;
• you do not authorise a person in France to conclude contracts on your behalf;
• your contract describes a service;
• your invoicing and payment match this reality.

In this setup, the tax topic still needs to be handled properly, but it is consistent with operational reality.

Abusive setup

An abusive setup is different.

For example:

• you claim to be in Brazil while working on a lasting basis from France;
• you use a foreign structure with no real substance;
• you seek to avoid tax through a shell entity;
• a person in France habitually negotiates and concludes contracts on your behalf;
• the engagement looks like an integrated employed role, without autonomy or deliverables.

This type of arrangement should be avoided.
It can expose the freelancer, the IT services firm and intermediaries to tax, social security or contractual risks.

StelarWork does not sell tax optimisation.
If a freelancer is already genuinely tax-resident outside the EU, StelarWork aims to remove administrative and contractual friction for the IT services firm.
Tax residence must always match reality.

The topic is comparable to other non-EU or non-French countries, with local nuances. For a similar angle on permanent establishment, you can read how to invoice a French IT services firm from Canada without creating a permanent establishment.

Permanent establishment: the point not to create unintentionally

Permanent establishment is one of the issues that worries finance departments.
The IT services firm wants to avoid a poorly structured relationship giving the impression that a foreign provider carries out an organised activity in France.

In a Brazil–France collaboration, several points must be monitored.

Do not conclude contracts in France on behalf of the freelancer

You must avoid a person or company in France becoming a dependent agent that habitually concludes contracts on behalf of the Brazilian freelancer.

This is an essential point.

StelarWork does not position itself as the freelancer’s representative in France.
StelarWork contracts in its own name with the IT services firm, then contracts in its own name with the freelancer for the corresponding service.

This distinction makes the contractual chain clearer.
It avoids presenting StelarWork as a person who “signs for you” or acts “on your behalf”.

Do not establish an organised presence in France

The risk increases if, in practice, the freelancer has:

• an office in France;
• a team in France;
• a French operational address;
• recurring commercial activity managed from France;
• permanent integration into the IT services firm’s organisation.

A freelancer in Brazil who genuinely works remotely on defined deliverables presents a different situation.

The documentation must reflect this.

Contract: what makes the engagement acceptable for the IT services firm

A good contract does not only protect the parties.
It also makes the engagement understandable for the IT services firm’s internal teams.

Describe an outcome-based service

The contract must specify what is expected.

For example:

• development of a module;
• corrective maintenance over a defined scope;
• technical audit;
• cloud migration;
• CI/CD automation;
• expert support on an architecture;
• contribution to sprint-based deliverables, if the framework remains that of a service.

The service may be organised with regular check-ins.
But the freelancer’s autonomy must remain visible.

The contract must avoid wording that gives the impression that the IT services firm exercises direct hierarchical authority.

Organise contractual back-to-back alignment

In engagements involving several parties, back-to-back alignment is important.
The obligations undertaken towards the IT services firm must be consistent with those entrusted to the freelancer.

This includes in particular:

• confidentiality;
• intellectual property;
• security;
• data protection;
• deadlines;
• deliverable quality;
• liability;
• service continuity;
• payment terms.

A poorly aligned contract creates a blind spot.
An aligned contract allows the IT services firm to defend the file.

Provide for data and security topics

A tech freelancer in Brazil may access code, environments, logs or data.
The IT services firm must therefore clarify the rules.

Depending on the engagement, it may be useful to provide for:

• limited access rights;
• a security policy;
• a confidentiality clause;
• rules on personal data;
• incident handling;
• restrictions on the tools used;
• traceability of deliverables.

The point is not to create an excessively heavy contract.
The point is to make non-EU subcontracting defensible.

Payment from France to Brazil: the concrete irritants

Even when the contract has been approved, payment can delay the start.

The invoice must fit into the accounting process

A French IT services firm must integrate the invoice into its internal process.
If the invoice is issued from Brazil, it must be understood by French accounting.

Frequent friction points include:

• wording that does not match the IT services firm’s expectations;
• a currency that was not planned;
• incomplete bank details;
• doubt about the beneficial recipient;
• no reference to the purchase order;
• uncertain VAT treatment;
• manual approval by finance.

These irritants do not make the engagement impossible.
They extend the timeline and increase the risk of refusal.

International payment must be anticipated

A France–Brazil transfer may depend on several banking and foreign exchange checks.
The IT services firm may also have restrictive internal policies on non-EU payments.

You should therefore avoid discovering the issue after the first month of work.

From the outset, the file must answer three questions:

• does the payer know exactly whom it is paying;
• does the beneficiary match the contract;
• does the invoice match the approved service.

When these answers are not clear, payment gets blocked.

Brazil–France time difference: an operational topic, not an obstacle

The time difference between Brazil and France is rarely insurmountable.
But it must be anticipated in how the engagement is organised.

The IT services firm wants to know whether the collaboration will remain smooth.

Define overlapping working windows

It is useful to define shared availability windows.
They are used to frame:

• daily meetings or project check-ins;
• code reviews;
• technical decisions;
• incidents;
• demonstrations;
• deliverable approvals.

The goal is not to reproduce a French working day from Brazil.
The goal is to ensure a professional operating model, compatible with a remote service.

Distinguish availability from subordination

An IT services firm can request coordination check-ins.
It can also require deadlines and quality commitments.

But the contract must remain that of an independent service.
The freelancer must not be presented as an internal resource placed under the IT services firm’s day-to-day authority.

Availability must support delivery.
It must not erase the provider’s autonomy.

How StelarWork makes the file easier for the IT services firm to accept

StelarWork operates between the French IT services firm and the tech freelancer based outside the EU.
The aim is to make the collaboration contractable, payable and documented for the IT services firm.

In practice, StelarWork:

• contracts in its own name with the French IT services firm;
• invoices the IT services firm from a French company;
• contracts in its own name with the freelancer in Brazil;
• organises a coherent documentation chain;
• pays the freelancer according to the agreed framework;
• carries supplier risk and the associated operational compliance.

The relationship between the freelancer and StelarWork is a B2B service arrangement, extending the contract signed in its own name with the IT services firm.
It is based on a defined engagement, deliverables and invoicing, not a hierarchical link.

What this changes for the freelancer in Brazil

For you, the value is to reduce the friction that often blocks the engagement before signature:

• the IT services firm does not have to onboard a Brazilian supplier directly;
• it receives a French invoice;
• the contractual framework is clearer for its procurement team;
• the service remains organised around deliverables;
• international payment is integrated into the process;
• the documentation is more coherent.

This does not change your genuine tax residence.
It does not turn an artificial situation into a compliant one.

If you genuinely live and work in Brazil, StelarWork can help make the relationship more acceptable for the IT services firm.
If your real situation is French, or if your foreign structure is a shell, the problem must be addressed upstream with competent advisers.

What this changes for the French IT services firm

For the IT services firm, the value lies in having an identifiable French supplier, with a contractual chain that is easier to manage.

It avoids some of the usual irritants:

• creating a non-EU supplier;
• reading a foreign invoice;
• direct international payment;
• uncertainty over the applicable contract;
• a supplier file that is difficult to defend;
• lack of consistency between engagement, invoice and payment.

This is particularly useful when the skill is rare, the freelancer is good, but procurement refuses to sign directly with them.

Similar blockers exist in other non-EU setups, for example invoicing a French IT services firm from Dubai or Bali: what blocks it and how to do it, or from Thailand: how a freelancer can invoice a French IT services firm compliantly.

The right file for invoicing a French IT services firm from Brazil

To make the collaboration concrete, the file must be simple, coherent and verifiable.

Freelancer side

You should generally prepare:

• your legal or professional identity;
• your invoicing information;
• your bank details, consistent with the contract;
• useful proof or certification of your tax residence, if requested;
• a clear description of your activity;
• your service scope;
• your availability constraints linked to the time zone;
• your confidentiality and security commitments.

The aim is to show that you are a structured provider, not an informal resource.

Engagement side

The scope must be framed:

• context;
• objectives;
• deliverables;
• duration;
• validation methods;
• price or pricing method;
• reporting cadence;
• tool access rules;
• responsibilities;
• end-of-engagement conditions.

The clearer this framework is, the easier the engagement is to get accepted.

Payment side

The payment chain must match the contractual chain.

You should avoid inconsistencies such as:

• a contract with one person and payment to another;
• an invoice with no reference to the purchase order;
• an undocumented bank beneficiary;
• a currency that was not agreed;
• a service described differently across documents.

These inconsistencies are often more blocking than the country itself.

For an IT services firm, a freelancer in Brazil is not necessarily a problem.
An incomplete file, unclear residence or inconsistent contract-invoice-payment chain is.

FAQ

Can a freelancer in Brazil invoice a French IT services firm directly?

Yes, in principle, if the freelancer has a suitable status, a coherent genuine tax residence, a clear contract and an invoice acceptable to the IT services firm.

In practice, some IT services firms refuse to onboard a non-EU supplier directly.
The blocker then comes from the procurement process, international payment, compliance or perceived tax risk.

Is being tax-resident in Brazil enough to avoid risks in France?

No.
Tax residence must match reality, but it is not sufficient on its own.

You must also avoid an organised presence in France, a façade entity, or a person who would habitually conclude contracts in France on behalf of the freelancer.
The engagement must remain a service performed remotely, with a coherent contractual framework.

Does StelarWork become the freelancer’s representative in France?

No.
StelarWork does not sign on behalf of the freelancer and does not present itself as their representative in France.

StelarWork contracts in its own name with the French IT services firm, then contracts in its own name with the freelancer.
This structure aims to make the collaboration clearer for the IT services firm, without creating a dependent-agent arrangement.

Is the time difference between Brazil and France a problem for an IT services firm?

Not necessarily.
It becomes a problem only if it is not anticipated.

It is preferable to define overlapping working windows, project rituals and response times compatible with the engagement.
The important point is to maintain a reliable service, without turning the relationship into day-to-day subordination.

Disclaimer

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

The applicable rules depend in particular on your genuine tax residence, your local status in Brazil, the applicable tax treaty, the nature of the engagement, whether or not there is a presence in France, the contracts signed and the payment flows.
Before structuring a collaboration or making a tax, legal or accounting decision, have your situation validated by a qualified professional.