The workspace decision gets the attention. The legal and regulatory groundwork is what determines whether the GCC can hire, pay, and operate on day one.
Most GCC planning energy goes into the visible decisions. Which city, how many seats, which workspace model, what the floor plate looks like. Those decisions matter. They are also not the ones that delay a launch when they go wrong. The launches that stall do so on the groundwork beneath them: an entity that is not yet registered when the first offer letter needs to go out, a banking relationship that is not operational when payroll runs, a compliance configuration that is incomplete when the first audit arrives.
For an enterprise establishing its first GCC in India, the legal and regulatory setup is a sequence with dependencies. Several stages cannot begin until earlier ones complete, and a delay early in the sequence compounds through everything downstream. The checklist below is the order in which that groundwork is best understood, structured for the legal, finance, and operations leaders who carry accountability for getting an India entity operational on a board-approved timeline.
1. Entity Structure and Registration
The first decision is the legal form of the India entity. Most GCCs are established as a private limited company, which offers limited liability, the ability to hire directly, and a structure that international parent organisations and Indian regulators both recognise. The alternative structures, a limited liability partnership or a branch office, carry different tax, liability, and operational implications, and the choice has consequences that persist for the life of the operation.
Registration involves incorporating with the Ministry of Corporate Affairs, obtaining a Corporate Identity Number, and securing the directors' identification and digital signature credentials required to transact. For a first-time entrant, this stage typically runs several weeks and gates everything that follows. No bank account, no tax registration, and no employment can proceed until the entity legally exists.
2. Tax Registration and Transfer Pricing
Once the entity exists, the tax registrations follow. A Permanent Account Number and Tax Deduction Account Number are required before the entity can transact or deduct tax at source on payroll. Goods and Services Tax registration is required for the entity to invoice and to claim input credits.
The structurally significant tax consideration for a GCC is transfer pricing. Because the India entity provides services to its overseas parent, the pricing of those intercompany services must satisfy the arm's length standard under Indian transfer pricing regulations. The cost-plus markup model is the common approach, but the markup must be benchmarked and documented to withstand scrutiny. Getting the transfer pricing framework defined at setup, rather than retrofitted at the first assessment, is the difference between a clean compliance posture and a recurring exposure.
3. Banking and Foreign Exchange Compliance
The India entity requires an operational bank account before it can fund operations or run payroll. Establishing that account involves the entity documentation from registration alongside the parent organisation's verification, and for a foreign-owned entity, the process carries additional steps.
Foreign direct investment into the India entity must comply with the Foreign Exchange Management Act. Most GCC activity falls under the automatic route, which does not require prior government approval, but the inward remittance must be reported to the Reserve Bank of India through the prescribed filings within defined timelines. Missing those reporting windows creates a compliance gap that is straightforward to avoid at setup and disproportionately costly to resolve later.
4. Employment, Payroll, and Statutory Benefits
A GCC is, fundamentally, a hiring operation. The employment infrastructure has to be operational before the first hire, not assembled around them. This spans compliant employment contracts, the statutory benefit registrations, and the payroll infrastructure to run them.
The statutory framework includes Provident Fund registration, Employees' State Insurance where applicable, professional tax registration in the relevant states, and gratuity provisioning. Each carries its own registration, contribution, and filing obligations. For a GCC hiring across multiple cities, several of these obligations vary by state, which means the compliance configuration is not uniform across an organisation building in Bengaluru, Hyderabad, and Pune simultaneously.
"The mistake first-time entrants make is treating the legal setup as paperwork that runs alongside the real work. It is the real work. An entity that is not registered, a bank account that is not operational, a payroll framework that is not configured, these are the things that stop a GCC from hiring on the day it intended to. We built Global Connect because the enterprises that get this right are the ones that do not try to run it as a side project."
Kunal Mehra, Co-CEO and President
5. Data Protection and Regulatory Compliance
A GCC processing data on behalf of a global parent operates under two layers of obligation. India's own data protection framework under the Digital Personal Data Protection Act governs how personal data is handled within the country. For operations processing data originating in other jurisdictions, the parent's regulatory obligations, GDPR for European data, HIPAA for healthcare data in the US, and sector-specific frameworks for BFSI, extend into the India operation.
This is where the workspace and the legal setup intersect. Compliance with SOC2, ISO 27001, GDPR, or HIPAA requires a dedicated network perimeter, private server infrastructure, and documented physical access controls. These are not policy documents. They are physical and infrastructural requirements that have to be present in the workspace from day one of occupancy. A GCC that registers its entity correctly but occupies a workspace that cannot meet its compliance brief has solved one half of the problem and left the other half open.
6. Intellectual Property and Contractual Framework
The intellectual property a GCC produces must vest correctly with the parent organisation. This is governed by the intercompany services agreement and the employment contracts, both of which must assign IP ownership clearly and in a manner that holds under Indian law. For a GCC established to do product engineering, research, or any work that generates IP, this assignment is foundational rather than administrative. An ambiguity here surfaces years later, at the worst possible time, when ownership of something valuable is contested.
The Setup Sequence at a Glance
How the Setup Sequence Compresses
The conventional model assumes the enterprise's internal India leadership drives this entire sequence. For a first-time entrant, that creates a circular problem. The leadership team needed to run the setup is often not fully in place until the setup is complete, and the operation cannot hire that leadership until the entity, banking, and payroll infrastructure exist.
Table Space's Global Connect offering inverts that sequence. It covers entity registration, banking, HR and payroll setup, and compliance configuration alongside workspace delivery under a single integrated framework. The India leadership team arrives into an operation that is already legally established, banked, and compliance-configured, into a workspace that is already audit-ready, and begins hiring rather than building. For a first-time entrant, that compression from setup programme to operational capability is the variable that determines whether the India investment generates returns in year two or year four.
The legal setup of a GCC is not the part of the project that gets discussed in the board presentation. It is the part that determines whether the rest of the plan can execute on schedule. The enterprises that treat it as foundational, and resource it accordingly, are the ones whose India operations are hiring while their peers are still navigating registration.
