Can offshoring software development create a permanent establishment for a European company?
Yes — a European company can create a taxable permanent establishment (PE) in India or another offshore location if it exercises day-to-day control over individual engineers, keeps a fixed place at its disposal there, or lets someone habitually conclude contracts on its behalf. Buying a delivery outcome from an independent vendor is very unlikely to create a PE; directing named individuals as if they were your own employees is where the risk begins.
This matters because PE exposure is not a compliance footnote. It can pull a share of the group's profit into a foreign tax net, trigger local filing obligations, and create penalties and interest years after the arrangement started. The good news is that the risk is largely a function of how the relationship is structured and documented — both of which are within your control.
What actually triggers a permanent establishment?
Most European countries have a double taxation treaty with India, and those treaties follow a familiar structure. Three triggers do most of the work:
- Fixed place PE. A place of business in the other country that is at the disposal of the foreign company and through which its business is carried on. Renting your own floor, badging the space with your logo, or having exclusive use of dedicated desks all point this way.
- Agency PE. A person in the other country who habitually concludes contracts, or habitually plays the principal role leading to contracts, in the name of the foreign company.
- Service PE. Present in several treaties: services furnished through personnel in the other country for more than a threshold number of days in a twelve-month period. This is the trigger most often overlooked in engineering engagements.
Note what is not on the list: paying a foreign supplier, or receiving software written abroad. Cross-border purchasing on its own is normal trade.
How is a vendor engagement different from a captive team?
The substantive question tax authorities ask is who bears the entrepreneurial risk and who directs the work. The table sets out how the common models sit on that spectrum.
| Model | Who directs the engineers | Who carries delivery risk | Typical PE exposure |
|---|---|---|---|
| Outcome-based project with a vendor | Vendor | Vendor | Low |
| Dedicated managed team with a vendor delivery lead | Vendor lead, against your roadmap | Shared, defined in the SLA | Low to moderate |
| Staff augmentation, individuals embedded in your squads | You, directly | You | Moderate — depends on control and duration |
| Employer of record with your own management | You | You | Moderate to high |
| Own subsidiary or captive centre | You | You | By design — a taxable presence you plan for |
The pattern is consistent: the more the arrangement resembles employing people abroad, the more it is taxed like employing people abroad. If you are still choosing between these models, our comparison of GCC, build-operate-transfer and outsourcing walks through the operational trade-offs alongside the tax ones.
What is transfer pricing and when does it apply to you?
Transfer pricing governs the price charged between related parties — typically a European parent and its Indian subsidiary. The principle is the arm's length standard: the intercompany charge should be what unrelated parties would have agreed for the same services under the same conditions.
If you buy from an independent vendor, transfer pricing does not apply to that purchase; the price is arm's length by definition because the parties are unrelated. If you set up your own captive development centre, transfer pricing becomes central, and the usual method for a services entity is cost-plus: the subsidiary recovers its costs plus a margin, with the margin benchmarked against comparable independent service providers.
Three things then become mandatory rather than optional:
- An intercompany services agreement that describes the services, the cost base, the mark-up and the invoicing cadence.
- A benchmarking study supporting the chosen margin, refreshed periodically.
- Contemporaneous documentation — local file, master file and, above a group revenue threshold, country-by-country reporting.
Getting the cost base wrong is as common as getting the margin wrong. Stock-based compensation, shared tooling and group management recharges all need a defensible allocation.
What about withholding tax on payments to an offshore vendor?
Separate from PE, cross-border payments can attract withholding at source. Whether it applies depends on how the payment is characterised — service fee, royalty, or fees for technical services — and on the applicable treaty article. Software development invoices are usually treated as service fees, but the characterisation is fact-specific, and a badly drafted contract that bundles a licence into a services fee invites the harder treatment.
Practical steps: keep licence grants and service fees on separate contract lines, obtain the vendor's tax residency certificate for treaty relief, and confirm the correct treatment with your tax adviser before the first invoice rather than after the twelfth. The contractual mechanics that surround this — IP assignment, data processing, confidentiality — are covered in our guide to GDPR, IP and contracts when outsourcing software to India.
How do you keep a vendor engagement on the safe side of the line?
These are structural habits, not paperwork tricks. They only help if the day-to-day reality matches them.
| Practice | Why it reduces exposure |
|---|---|
| Contract for deliverables and service levels, not for named hours | Evidences purchase of a service rather than hire of labour |
| Let the vendor appoint, assess and replace its own engineers | Keeps employment-like control with the vendor |
| Route work through a vendor-side delivery lead | Prevents your managers from directing individuals |
| Give nobody offshore authority to sign or negotiate on your behalf | Closes the agency PE trigger |
| Do not take exclusive use of offshore premises or badge them as yours | Closes the fixed place trigger |
| Track travel days of your own staff into the country | Service PE thresholds count days, and they accumulate quietly |
| Review the arrangement annually against what is actually happening | Practice drifts; documentation that no longer matches reality is worse than none |
When is accepting a taxable presence the right answer?
Sometimes the answer is to stop avoiding PE and simply establish an entity. That is usually right when the offshore team exceeds a few dozen people, when you want to hold IP locally, when you need long-term retention through direct employment, or when the work is core enough that you want permanent institutional ownership of it. At that point you are choosing a planned, budgeted tax presence with proper transfer pricing rather than an accidental one discovered in an audit. Our guide to setting up a development centre in India covers what that transition involves.
What should you do this quarter?
- Map every offshore engagement to a model in the table above and write down who really directs the engineers.
- Re-read the master services agreement and ask whether it describes services or labour.
- Count your own employees' travel days into each offshore country over the last twelve months.
- Check that every vendor invoice references a deliverable or service level, not a timesheet of named individuals.
- Take a written position from a tax adviser in both jurisdictions and store it with the contract.
None of this is a reason to avoid offshoring — it is a reason to structure it deliberately. The related employment and compliance questions are covered in our guide to the legal and compliance side of hiring developers in India. If you would rather buy a managed outcome than manage individuals abroad, our dedicated engineering team service is structured with these boundaries in mind.
This article is general information, not tax or legal advice. Positions differ by treaty, by country and by facts — take advice on your specific arrangement.
