South Africa: subcontracting development from Cape Town or Johannesburg

You have identified an English-speaking developer in South Africa, but your procurement team refuses to onboard a non-EU supplier, your legal team wants an enforceable framework, and your finance team does not want to manage a poorly documented international payment.

Subcontracting development in South Africa can be relevant for a French IT services firm. The country has an English-speaking tech talent pool, with profiles used to international environments, particularly around Cape Town and Johannesburg.

The blocking point is therefore not only sourcing. It is the ability to turn a South African freelancer into an acceptable supplier for a French IT services firm, with a purchase order, deliverables, a usable invoice, a clear liability chain and compliance safeguards.

Why South Africa is a credible tech destination

South Africa is not an “exotic” destination for software development. It is an English-speaking market, with a work culture close to international standards and real exposure to SaaS, fintech, cloud, data, cybersecurity and digital product projects.

For a French IT services firm, the value is concrete:

• access to experienced English-speaking profiles;
• simpler collaboration than with highly offset time zones;
• mature development practices;
• ability to work on international client environments;
• a good level of autonomy on engagements framed by deliverables.

Cape Town has a higher concentration of profiles oriented towards product, startups, SaaS, design engineering and digital platforms. Johannesburg offers a more corporate talent pool, with profiles exposed to banks, insurance, telecoms, internal IT systems and enterprise environments.

This distinction is not absolute. Above all, it helps procurement teams and managers understand why a profile based in South Africa can be credible for a demanding technical engagement.

The decisive criterion is not the country itself. It is the ability to document the supplier, frame the service and secure the contractual chain between the French IT services firm and the non-EU contributor.

The real issue: making the freelancer contractable for the IT services firm

A French IT services firm may want to work with a South African freelancer without being able to onboard them directly.

The usual blockers are well known:

• non-referenced non-EU supplier;
• foreign services contract difficult to validate;
• no French invoice;
• uncertainty around VAT, reverse charge or supporting documents;
• poorly understood risk of economic dependence or reclassification;
• insufficient intellectual property clauses;
• KYC, sanctions, corruption or due diligence checks that are difficult to perform;
• international payment in a foreign currency or to a foreign account;
• difficulty flowing down end-client obligations back-to-back.

These objections are similar to those encountered in other non-EU destinations. They also explain why some French companies still block Dubai structures, even when the profile is technically excellent.

In an IT services firm, the problem is not “finding someone”. The problem is fitting that person into a supplier chain that procurement, legal and finance can accept.

What to check before subcontracting development in South Africa

Subcontracting development in South Africa requires serious qualification, without turning the exercise into a full international tax audit.

The objective is to answer three simple questions:

1. is the freelancer genuinely based and organised outside the EU?
2. is the service framed as an outcome-based service?
3. does the IT services firm have a clear and compliant contractual supplier?

Genuine residence and remote performance

The first point is the reality of the situation.

A healthy setup assumes that the freelancer genuinely lives and works outside the EU, with an effective presence in their country of residence, a real remote activity and no organised presence in France.

The point is not to artificially create a foreign structure to invoice an activity managed from France. A shell entity, a front address or a freelancer supposedly based abroad but in practice operating from France creates legal and tax risk.

Healthy setup: a South African freelancer genuinely established in South Africa, who works remotely, invoices a defined service and has no permanent organisation in France.

Abusive setup: a foreign front structure, with no substance, used to conceal an activity carried out from France. This type of arrangement must be ruled out.

The principle remains the same as for other non-EU destinations: genuine residence, effective presence, consistency of evidence and no organised presence in France. The presence threshold, often analysed around more than 183 days depending on the situation, does not replace a full tax residence analysis, but it does recall the requirement for reality.

Outcome-based service, not staff secondment

The framework must remain that of a service.

An IT services firm must not treat the freelancer as an outsourced employee or as a resource seconded without autonomy. The right reflex is to define:

• a technical scope;
• deliverables;
• acceptance criteria;
• a schedule;
• responsibilities;
• acceptance procedures;
• confidentiality and security obligations.

The issue is not to “place a consultant”. The issue is to entrust a development service to a supplier, with an expected outcome.

This point is important to reduce the risks of reclassification, unlawful labour lending or unlawful labour supply. The operating model must be consistent in the documents and in actual performance.

Intellectual property, confidentiality and security

Software development almost always raises intellectual property issues.

An IT services firm must be able to demonstrate to its end client that the necessary rights over the deliverables are properly transferred, that open-source components are controlled and that confidentiality commitments are aligned with the client contract.

Procurement and legal teams will look in particular at:

• the assignment or licensing of rights over the code;
• traceability of deliverables;
• any use of third-party components;
• security rules;
• access to environments;
• obligations in the event of an incident;
• confidentiality of client information.

If the South African freelancer accesses European personal data, GDPR must also be addressed. South Africa has its own data protection framework, but this does not exempt the IT services firm from framing transfers and access outside the EEA where GDPR applies.

Financial flows and invoicing

An IT services firm’s finance department wants to avoid invoices that are difficult to process.

A non-EU supplier can trigger practical questions: currency, invoice wording, supporting documents, potential withholding tax, reverse charge depending on the nature of the flow, bank checks, consistency between contract and invoice.

These issues are not necessarily blockers. They simply need to be addressed before the engagement starts.

The key point is clarity. An invoice must correspond to a purchase order, a service scope and an identified supplier. Without this, the engagement may be technically approved but administratively blocked.

For the broader framework, the IT services firm guide to non-EU subcontracting details the basic reflexes to apply before engaging a contributor located outside the European Union.

Cape Town, Johannesburg: local constraints to anticipate

Sourcing in South Africa requires a practical approach.

Cape Town attracts many profiles used to international environments, digital products and distributed teams. Candidates may be approached by foreign companies, which requires a clear framework from the outset: scope, duration, invoicing method, actual availability and expected level of commitment.

Johannesburg often offers profiles more exposed to large accounts, complex information systems and regulated environments. For an IT services firm working with corporate clients, this can be an advantage.

Certain operational points should also be anticipated without making them the core of the contract:

• connection stability;
• power continuity;
• equipment;
• remote organisation;
• availability during French working hours;
• written and spoken English level;
• ability to produce documentation;
• verifiable project references.

These elements must be qualified upstream, because they reassure delivery teams as much as procurement. An IT services firm must be able to explain why this profile is selected, how the service is framed and how the risks are reduced.

A good supplier file is not based solely on the CV. It is based on the consistency between the profile, the country, the contract, the deliverables, the invoicing and the end-client obligations.

How StelarWork fits into the contractual chain

StelarWork helps make a non-EU freelancer contractable by a French IT services firm.

The principle is simple: StelarWork contracts in its own name with the IT services firm, invoices the French IT services firm and carries the supplier relationship. In parallel, StelarWork contracts with the freelancer located outside the EU for performance of the service.

This allows the IT services firm to work with a French supplier, with a contractual chain that is clearer for procurement, legal and finance.

StelarWork does not sign on behalf of the freelancer. StelarWork is not the freelancer’s representative in France. This distinction is important to avoid an interpretation as a dependent agent, which could create permanent establishment risks.

StelarWork is also not an employer, an umbrella employment solution or an EOR. There is no employment contract, no salary and no staff secondment.

The intended framework is that of a service, with a supplier, a purchase order, deliverables and documented obligations.

This logic already exists in other non-EU destinations. For example, working with French IT services firms from Tunis addresses the same issue: making a technically relevant profile acceptable within a French supplier chain.

The reasoning is comparable with the playbook for a freelance developer in Morocco, where the challenge is to arbitrate between commercial opportunity, compliance and contractual clarity.

Each country nevertheless retains its specific features. This is why how an IT services firm contracts with a Georgian freelancer is a useful counterpoint: the method remains similar, but the control points vary depending on the destination.

What reassures procurement, legal and finance

For a French IT services firm, a solid file must speak the language of each function.

Procurement side

Procurement wants an identifiable, referenced and acceptable supplier.

They will look at:

• the identity of the contractual supplier;
• the invoicing country;
• KYC evidence;
• consistency with the supplier policy;
• the level of dependence;
• the ability to flow down the end client’s conditions back-to-back;
• compliance obligations.

The value of a French supplier such as StelarWork is to reduce the friction linked to directly onboarding a South African freelancer.

Legal side

Legal wants to avoid an ambiguous contract.

Sensitive points include:

• classification of the relationship as a service;
• absence of subordination;
• defined deliverables;
• intellectual property;
• confidentiality;
• liability;
• security;
• data protection;
• compliance with the end-client contract.

The contract must avoid any ambiguity of the staff secondment type. Delivery can manage the engagement, but the documentary framework must remain that of an outcome-based service.

Finance side

Finance wants a usable invoice and a justifiable flow.

It will look at:

• consistency between purchase order, invoice and deliverables;
• currency and payment terms;
• VAT treatment or reverse charge depending on the relevant flows;
• accounting evidence;
• bank account identity;
• payment compliance;
• absence of an artificial tax arrangement.

StelarWork does not create a tax advantage for the freelancer. If a freelancer is already genuinely tax-resident outside the EU, StelarWork removes administrative friction on the IT services firm side. It does not transform tax residence and must not be used to conceal an activity located in France.

When South Africa is a good option for a French IT services firm

South Africa is relevant when the need combines several conditions:

• English-speaking profile required;
• engagement compatible with remote work;
• clearly definable deliverables;
• end client open to properly framed non-EU subcontracting;
• security requirements compatible with remote access;
• ability to document the relationship;
• no organised presence in France for the freelancer.

It is less suitable when the engagement requires regular presence in France, permanent integration into the end client’s teams or an operational relationship of subordination.

In that case, the problem is not South Africa. It is the mismatch between the real need and an independent non-EU subcontracting model.

FAQ

Can a French IT services firm subcontract development in South Africa?

Yes, a French IT services firm can consider subcontracting development in South Africa, provided that the relationship is framed as a service, the reality of the freelancer’s situation is verified, and contractual, tax, GDPR and supplier issues are addressed. The central point is the compliance of the contractual chain.

Can a South African freelancer invoice a French IT services firm directly?

It is possible in theory, but often difficult in practice. Procurement may refuse a non-EU supplier, finance may block payment, and legal may require a more robust framework. This is precisely the friction StelarWork aims to reduce by becoming the French supplier of the IT services firm, without being the freelancer’s employer or representative.

Do you need to use an EOR to work with a developer in South Africa?

Not necessarily. An EOR relates to a local employment model. If the need concerns an independent service performed by a freelancer, the subject is different. The challenge is to contract for a service, not to hire locally or second personnel.

What are the main risks to anticipate?

The main risks concern the classification of the relationship, intellectual property, confidentiality, data access, supplier compliance, financial flows, the freelancer’s genuine residence and the absence of an artificial arrangement. These issues must be documented before the engagement starts.

Disclaimer

This article provides general information for French IT services firms. It does not constitute personalised legal, tax, employment or accounting advice. The applicable rules depend on the precise situation of the IT services firm, the end client, the freelancer, the country of residence, the contractual flows and the data processed. Before making any decision, it is recommended that the arrangement be validated by the company’s usual advisers.