A software center has no “listening” phase: from day one it has engineers writing code, a service contract with the parent or customers, and revenue. That feature cuts the Indian investor’s form question down to a single operable answer — a subsidiary — and moves all the analysis to two accompanying items: claiming software production tax incentives correctly, and managing the related-party relationship with the parent itself, the center’s largest customer.
This article is separated from the multinational’s regional distribution hub in this team’s piece EXP-0926: there, goods flows create distribution rights and the ENT problem; here, the “goods” are engineer hours and intellectual products. The construction contractor’s angle is in EXP-0929.
Why only a subsidiary can operate a software center
Software production and information technology services in Vietnam carry no foreign ownership cap, so a wholly-owned Indian subsidiary is the complete structure: signing service/software development contracts with the parent and customers, issuing invoices, hiring and paying the engineering team, and registering incentive programs where eligible. A representative office is excluded for operating reasons, not sector reasons: a software center must contract and collect money from the first month, while a rep office under Decree 07/2016/ND-CP signs no commercial contracts and has no revenue — there is no rep-office market-testing phase for a delivery center. A JV with a Vietnamese partner makes sense only when the investor needs the partner’s ready team or customers; for a group development center model, a JV merely adds a shareholder to an activity whose value lies in code quality control and confidentiality.
What must be designed from the start is the center’s revenue model: developing for the parent under a service contract (revenue as a service fee on costs plus a margin), or developing products owned in Vietnam and licensing them to customers. These two models produce fundamentally different tax, incentive and IP files, and switching between them later is a tax event — a transfer of intellectual property assets — not a simple licence adjustment.
Software tax incentives and transfer-pricing discipline with the parent
Software production is a field enjoying corporate income tax incentives in Vietnam under the current incentive schedule of the Law on Corporate Income Tax 67/2025/QH15: the project must be designed and registered correctly from the investment file (business lines, software production revenue conditions) so incentivised income is determined separately from other service income. This is real money larger than any form-cost difference, and the reason a software center’s file should be prepared by people who understand both sides of the incentive boundary — qualifying software and non-qualifying work often sit in the same building.
The parent relationship is a textbook related-party transaction: the development service fee the center charges the parent must follow the arm’s length principle, with transfer pricing documentation proportionate to scale; and who owns the intellectual property created by engineers in Vietnam must be fixed in employment contracts and the group service agreement (work results assigned to the parent under contract, or owned in Vietnam and licensed back) — leaving this open means years later the center cannot prove rights over the very products it wrote. The biggest wrong-form risk, correspondingly, is trying to run the center through a rep office or cross-border contracts while the Vietnam team is already a permanent delivery center: service revenue actually arising in Vietnam under a structure with no Vietnamese taxpayer is the classic permanent-establishment and back-assessment risk.
After 2–3 years: expansion and model change
A software center’s expansion happens within the same subsidiary: scaling the team, adding offices in other cities (branches/business locations of the same entity), or creating a second entity when a product line needs a separate IP and incentive structure. Changing the revenue model — from fee-based development to product ownership in Vietnam — is a substantive change to be valued and taxed as an asset transfer between related parties. And “converting” from a group cost center into an independent product company serving the market is a group strategic decision, executed through contract and IP restructuring, not through an investment form conversion procedure.
Recommendation for this profile: incorporate the subsidiary from the start with software business lines and incentive file designed correctly; sign the group service agreement and transfer pricing file before the first engineer writes code for the parent; and fix IP ownership in every employment contract. The software center is the profile where “choosing the form” is done in a day, while the consequences of the tax — IP design follow for a decade.
For an Indian software center, the form is the shortest answer in the whole profile group: a wholly-owned subsidiary, because a delivery center has revenue from day one and a rep office cannot contract. The long-term work sits in two accompanying designs — software production tax incentives claimed on exactly the qualifying income, and transfer pricing plus IP discipline in the parent relationship.
Frequently Asked Questions
For a profile like an Indian investor opening a software center, which investment form should be chosen?
Incorporate a wholly-owned Indian subsidiary: software production and IT services carry no foreign ownership cap, and a software center must sign service contracts, issue invoices and pay engineers from the first month — things a representative office cannot do, as a rep office signs no commercial contracts and has no revenue. A JV is worth considering only when the Vietnamese partner’s ready team or customers are needed. (Separated from the goods distribution hub profile in piece EXP-0926.)
How much do cost and time differ between each form?
There is no cheaper rep-office alternative to compare substantively, because a rep office cannot operate a software center. Real costs comprise subsidiary establishment (IRC, enterprise registration) and a services enterprise’s recurring compliance, in exchange for the ability to claim CIT incentives on software production income under the current schedule — value far larger than any form difference, provided the project is designed and registered to the incentive conditions from the start.
What is the biggest risk for an Indian investor opening a software center if it chooses the wrong form?
The biggest risk is operating a delivery center in Vietnam under a structure with no Vietnamese business subject — a rep office or long-term cross-border contracts — leaving service revenue actually arising domestically outside declaration, creating permanent-establishment risk for the parent and back-assessment. The second long-term risk is leaving the transfer pricing design blank (development fees charged to the parent not at arm’s length, missing documentation) and the IP ownership of products created by engineers in Vietnam.
Can the form be converted after 2-3 years?
Expansion runs inside the same subsidiary (team growth, additional business locations) or a second entity for a product line needing its own structure — no form conversion is needed. The substantive change, if any, is switching the revenue model from fee-based development to product ownership in Vietnam: a transfer of intellectual property between related parties to be valued and taxed accordingly, not an investment form adjustment procedure.
This article has been quality-reviewed by the FLAW AI Legal Council
