Setting Up Payroll for a GCC in India: 2026 Guide

Setting Up Payroll for a GCC in India: 2026 Guide

If you're standing up a Global Capability Centre in India this year, GCC payroll is probably the single most underestimated line item on your setup plan. Everyone budgets time for real estate, hiring, and IT infrastructure. Far fewer teams budget enough time for getting payroll for a GCC in India right from day one — and the ones who don't usually find out the hard way, three weeks before the first salary run, that India payroll is not a smaller, cheaper version of what they run at headquarters.

2026 is a particularly live moment for this. The GCC wave that used to be dominated by the largest global banks and tech companies has broadened. Mid-market multinationals — companies with a few hundred to a few thousand employees globally — are now setting up their own captive centres in India instead of routing work through a BPO or staffing partner. That shift changes the payroll conversation entirely. A vendor-managed outsourcing arrangement hides almost all of India's payroll complexity from the HQ finance team. Running your own GCC does not. Suddenly your Bangalore, Pune, or Hyderabad office is a legal employer, and someone at HQ has to own statutory compliance, multi-state rules, benefits structuring, and a payroll calendar that looks nothing like the one back home.

This guide walks through what actually needs to happen — from the pre-launch checklist through the first 90 days to steady-state operations — so that HR, finance, and operations leaders building a GCC can plan payroll as a workstream with real dependencies, not an afterthought bolted onto the entity registration.

A quick but important note before we go further: this article deliberately avoids naming specific statutes, filing thresholds, or citing case law. Indian labor and tax law changes, is applied differently by different state authorities, and genuinely needs a qualified payroll compliance advisor or CA firm familiar with your specific state and industry. Treat everything here as an operating framework, not legal or tax advice.

Why GCC Payroll Is a Different Animal

It's worth being explicit about why "payroll for a GCC in India" deserves its own playbook, separate from generic India payroll guidance written for domestic SMBs, and separate from what a BPO or IT services vendor handles when you outsource work to India instead of owning it.

It's not the same as a typical India SMB

A homegrown Indian startup or SMB usually builds its payroll practices gradually, often reactively, as headcount grows. A GCC does the opposite: it usually launches with an aggressive hiring plan already locked in — 50, 150, sometimes 500 people in year one — because the business case for the centre depends on hitting a delivery or cost target quickly. That means:

• Statutory registrations, banking, and payroll systems need to be ready before the first employee joins, not built up organically.
• Compensation structures need to be competitive with well-established tech and GCC employers from day one, because you're hiring against Amazon, Goldman Sachs, Walmart Global Tech, and hundreds of other centres in the same cities.
• HQ expects reporting, headcount cost visibility, and audit trails at a level most local SMBs never bother with.

It's not the same as an outsourced/vendor arrangement either

Many companies expanding into India for the first time have prior experience with India — but only as a client of an IT services or BPO vendor. In that model, the vendor is the legal employer. Their payroll, their compliance, their statutory registrations, their risk. You saw none of it.

Once you set up your own GCC as a wholly owned subsidiary or branch entity, your India entity becomes the employer of record. That is the whole point of a GCC — you want direct control over the team, the IP, and the talent relationship, instead of paying a vendor markup. But it means payroll compliance, statutory contributions, and employment law exposure all sit with you now, not a vendor's legal team.

This is the single biggest mental shift HQ teams need to make. GCC payroll isn't a service you buy the same way you bought outsourcing. It's an operational function you now own, even if you use vendors to execute parts of it.

Pre-Launch Checklist: What Has to Be True Before You Run Your First Payroll

Before anyone gets paid, a set of legal, banking, and registration steps need to be complete. Timelines vary a lot by state and by how quickly your entity incorporation moves, so build in buffer — this stretch commonly takes six to twelve weeks even when things go smoothly, and can run longer.

Entity and foundational setup

• Indian legal entity incorporated (most GCCs use a private limited subsidiary structure; some use a branch or LLP structure depending on the parent's tax and legal strategy — this decision should be made with local counsel, not payroll teams)
• Registered office address finalized in each state you'll operate from
• Bank account opened in India for the entity, with the operating structure (who can approve/release payroll funds) agreed between HQ finance and local finance
• Corporate tax registration (PAN) and India-specific banking KYC completed

Statutory registrations you'll generally need

Exact requirements depend on headcount, state, and industry, and thresholds do change — verify current applicability with your registered advisor. But at a general level, most GCC entities will need to register for:

• A tax deduction account number for withholding income tax from employee salaries (payroll TDS)
• Provident fund registration, for retirement savings contributions shared between employer and employee
• Employee State Insurance registration, which covers a health and social security scheme for eligible employees below a wage threshold
• Professional tax registration, which is a state-level tax and therefore needs a separate registration in every state where you have employees, not just where you're headquartered in India
• Shops and establishments (or equivalent) registration in each state/city where you have a physical or registered place of work
• Labour welfare fund registration where applicable, again state-specific

Payroll operational readiness

• Payroll software or HRMS platform selected and configured (more on this below)
• Salary structure templates designed — fixed pay, variable pay, allowances, statutory deductions
• Leave policy, holiday calendar (state-specific gazetted holidays), and attendance/timesheet process defined
• Employee onboarding data flow agreed — who captures bank details, PAN, prior employment info, and how it reaches payroll
• Payroll approval and fund release workflow signed off between India finance and HQ finance/treasury
• First-payroll dry run scheduled at least one full cycle before the actual go-live date

A practical checklist for the payroll go/no-go decision

Before you commit to a launch date and start extending offers with specific start dates, confirm:

• [ ] TAN and PF/ESI registrations are active (or applications are far enough along that first-month contributions can be filed on time)
• [ ] Bank account is operational and funded, with payment rails tested (not just opened)
• [ ] Payroll system or vendor is live and has processed at least one parallel/dry-run cycle
• [ ] Salary structures have been benchmarked and approved, including any city-specific allowance differences
• [ ] Compliance calendar for the first 90 days is documented and owned by a named person, not "the team"
• [ ] A qualified local advisor (CA firm or payroll compliance consultant) is engaged and has reviewed your setup

Choosing Your Payroll Operating Model

This is the decision most HQ teams underinvest in, usually because they assume it's a smaller version of a decision they've already made elsewhere. It isn't. Get this wrong and you'll be re-platforming or re-staffing within 18 months, usually right when headcount growth makes that the most disruptive possible time to do it.

There are three broad models, and most GCCs actually end up on a spectrum between the second and third rather than picking one in isolation.

In-house payroll team. You hire a payroll manager (and eventually a small team) in India who processes payroll directly, files statutory returns, and manages the payroll system. This gives you the most control and the deepest institutional knowledge, but it's slow to stand up — you need to hire someone with genuine India payroll compliance expertise before you can even run your first cycle, which is a chicken-and-egg problem for a brand-new GCC.

Fully outsourced payroll processing. You hand payroll execution to a specialist payroll outsourcing firm or a CA firm with a payroll practice. They run the calculations, file returns, and hand you reports. This is fast to start and reduces compliance risk in the early months, since the vendor already has the registrations and process muscle. The tradeoff is weaker real-time visibility for HQ, slower turnaround on ad hoc requests (a new joiner needing urgent processing, a compensation change mid-cycle), and a dependency that can be hard to unwind later if the relationship doesn't scale with you.

HRMS-led model with self-service and a lean internal team. A modern HRMS/payroll platform handles the statutory calculation engine, compliance filings, and employee self-service (payslips, tax declarations, reimbursement claims), while a small internal team (often one to three people even at a few hundred employees) owns exceptions, approvals, and the relationship with HQ. This is increasingly the default for GCCs launching in 2026, because it combines speed of setup with long-term control, and it scales more predictably than either pure in-house or pure outsourcing as headcount grows into the hundreds.

A useful framing for HQ finance: don't pick a model based on what worked in your home country. Pick it based on how fast you're hiring, how many states you'll be in within 18 months, and how much real-time payroll cost visibility your CFO actually needs versus what they think they need.

Multi-State and Multi-City Complexity

This is the area where multinational HQs are most consistently surprised, so it deserves its own section. India is not payroll-uniform the way many countries are. A meaningful share of payroll rules — professional tax, shops and establishments registration, labour welfare fund, minimum wage notifications, and some leave entitlements — are set or administered at the state level, not the national level.

If your GCC has, say, an engineering hub in Bangalore (Karnataka), a finance and analytics team in Pune (Maharashtra), and a smaller satellite office in Hyderabad (Telangana), you are not running "India payroll." You are running three parallel, related-but-distinct payroll compliance regimes under one payroll calendar. Concretely, that means:

• Separate professional tax registration and remittance for each state, with different slab structures
• Separate shops and establishments registration per location
• State-specific gazetted holiday calendars, which affect leave accrual and payroll date calculations
• Potentially different minimum wage notifications by state and by employment category (which matters even for GCCs paying well above minimum wage, since some downstream calculations reference these notifications)
• Different practical timelines for how fast local authorities process registrations and respond to queries

The operational risk isn't usually the calculation itself — modern payroll software handles multi-state tax and deduction logic fine. The risk is registration lag. Teams open a new city office, start hiring immediately because the business needs headcount now, and only realize weeks later that professional tax and shops and establishments registrations for that state haven't been completed. Retroactively fixing that is possible but painful, and it's the kind of gap that shows up in due diligence later if the GCC is ever audited, restructured, or sold.

Multi-state readiness checklist, per new location:

• [ ] Confirm whether the new office counts as a new "establishment" requiring its own shops and establishments registration
• [ ] Register for state-specific professional tax before the first payroll run in that state
• [ ] Update the payroll system's location/work-state mapping for every affected employee, including remote employees who may be based in a different state than the registered office
• [ ] Add the new state's gazetted holidays to the leave calendar
• [ ] Confirm PF and ESI filings correctly reflect the new location's employee count (some thresholds and sub-code requirements are location-specific)
• [ ] Brief local managers on any state-specific leave or working-hours differences they need to communicate to their teams

One more layer worth flagging: hybrid and remote work has made "where is this employee actually based" a genuinely harder question than it used to be. If someone is hired into your Bangalore entity but works from a smaller city in a different state, that can trigger state-level obligations you didn't plan for. Build a simple process for capturing and periodically re-confirming each employee's actual work location — don't assume it matches the office they're nominally assigned to.

Compensation and Benefits: Competing for Talent, Not Just Compliance

Payroll setup and compensation strategy are tightly linked for a GCC in a way they often aren't for a domestic SMB, because your pay bands are set by competition with established GCCs and India-headquartered tech companies, not by what similar roles cost at HQ.

A few structural things to get right early:

Salary structuring. Indian compensation is typically broken into a cost-to-company (CTC) figure that includes basic pay, allowances (house rent allowance, and others depending on company policy), statutory employer contributions (PF, gratuity provisioning, sometimes ESI), and variable/bonus components. How you split fixed versus variable, and how you structure allowances, affects employees' in-hand pay and tax outcomes meaningfully — this is a genuine area of expertise, and getting the structure wrong (either too rigid, mirroring a foreign pay structure, or poorly benchmarked) is a common source of early attrition and candidate pushback during offer negotiations.

Benefits benchmarking. GCCs competing for engineering, finance, and analytics talent in cities like Bangalore, Pune, Hyderabad, Chennai, and the NCR region are up against companies with mature benefits stacks: comprehensive health insurance for employees and dependents, wellness stipends, flexible benefits/allowance baskets, robust parental leave, and increasingly, mental health support. A GCC that launches with a bare-minimum statutory-only benefits package will struggle to compete for mid-to-senior talent, even with a strong base salary offer.

Variable pay and equity. Many multinational parents want to extend their global equity or stock plan to India employees. This is workable but needs coordination between HQ legal, tax, and your India payroll provider, since equity compensation has its own tax treatment and reporting obligations in India that differ from cash bonus treatment.

Gratuity and long-term benefits. Gratuity (a lump-sum benefit tied to tenure) and provident fund are long-horizon liabilities that need to be provisioned for correctly from the start, not bolted on once someone reaches a tenure milestone. HQ finance teams sometimes miss these because there's no equivalent line item in their home-country payroll.

The practical takeaway: treat compensation benchmarking as a parallel workstream to statutory setup, ideally using current market data from your target cities (not a generic "India" number — Bangalore and a tier-2 city can have meaningfully different market rates for the same role). Revisit bands at least annually; the GCC talent market has been moving fast enough in recent years that stale benchmarks lose credibility with candidates and recruiters quickly.

Building a Compliance Operating Rhythm

India payroll compliance isn't a once-a-year event — it's a recurring monthly and quarterly rhythm, and missing dates has real financial consequences (interest, penalties, and in repeat cases, reputational risk with authorities). The specific due dates and forms change periodically and vary somewhat by registration type and state, so don't treat what follows as a definitive filing calendar — treat it as the shape of the rhythm you need to build and staff for.

Monthly cadence, roughly:

• Payroll processing and payslip generation
• TDS (income tax withholding) deposit
• PF contribution deposit and return filing
• ESI contribution deposit and return filing (for eligible employees)
• Professional tax deposit (state-specific, monthly or as per state rule)

Quarterly and periodic cadence:

• TDS quarterly return filings
• Labour welfare fund contributions (frequency varies by state — some are annual or half-yearly)
• Periodic reconciliation between payroll registers and statutory filings

Annual cadence:

• Annual tax computation and Form 16-equivalent issuance to employees for their personal tax filing
• Annual bonus computations where applicable
• Salary structure and compliance policy review, ideally timed with your fiscal year and compensation review cycle
• Statutory audit support (PF/ESI/labour inspections, where applicable)

The operating rhythm matters more than any single deadline. What separates GCCs with clean compliance records from those constantly firefighting is whether there's a named owner, a shared calendar visible to both India and HQ finance, and a standing monthly close process that reconciles payroll numbers against filings — not a scramble every time a due date approaches. If you're using an HRMS/payroll platform, this calendar should ideally live inside the system with automated reminders and filing status tracking, rather than in someone's personal spreadsheet.

Data Privacy and Cross-Border HR Data Flows

Every GCC payroll setup eventually runs into a question HQ legal and IT security should weigh in on early: how does employee HR and payroll data move between the India entity and the global HRIS, and under what safeguards?

This is genuinely a legal and compliance topic, and India's data protection framework has continued to develop, so you should get current guidance from your privacy counsel rather than relying on this article. But at a practical, non-legal level, here's what typically needs attention when setting up the data architecture for a new GCC:

• Mapping the data flow. Understand exactly what employee data (salary details, bank information, tax identifiers, performance data, health-related information tied to benefits) flows from your India payroll/HRMS system to your global HRIS, and who at HQ can access it.
• Consent and notice. Employees should be clearly informed, typically through onboarding documentation and policy, about what data is collected, why, and where it may be transferred or processed, including any cross-border transfer to HQ systems or third-party processors.
• Vendor and sub-processor visibility. If you're using an outsourced payroll vendor or an HRMS platform, understand where that vendor hosts data, whether they use sub-processors, and what contractual data protection commitments are in place.
• Access controls and data minimization. HQ teams often want broad visibility into India payroll data for reporting purposes. It's worth pushing back internally on this by default — HQ HR business partners generally need aggregated cost and headcount data, not raw salary-line or bank-detail access, and narrower access is both a better security posture and easier to defend if data handling practices are ever reviewed.
• Data localization considerations. Depending on the type of data and current regulatory guidance, some categories of data may have localization or retention expectations. This is an evolving area — loop in privacy counsel specifically on this point rather than assuming last year's guidance still fully applies.

The practical instinct that serves GCCs well: treat cross-border HR data flow as a designed system, documented once, reviewed periodically — not something that accretes ad hoc as different HQ stakeholders individually request export access to India payroll data over time.

Technology Stack: HRMS, Payroll Engine, and Global Integration

Your technology choice shapes almost everything else in this article — how fast you can add a new state, how much manual reconciliation your team does every month, and how visible India payroll data is to HQ.

Key things to evaluate when choosing your platform:

Statutory compliance coverage. Does the platform natively handle PF, ESI, professional tax (across the specific states you're in or plan to expand into), TDS computation, and gratuity provisioning, with filing support or filing automation — not just gross-to-net calculation?

Multi-state and multi-entity architecture. Can the system cleanly handle employees across multiple states and, if relevant, multiple legal entities in India, with location-aware tax and compliance logic built in rather than manually maintained in spreadsheets alongside the software?

Employee self-service. A GCC workforce, especially younger tech and analytics talent, expects to manage their own tax declarations, download payslips, submit reimbursement claims, and view leave balances without raising a ticket. Weak self-service creates unnecessary HR ops load as headcount scales.

Integration with your global HRIS. This is often the most underestimated integration project in a GCC launch. HQ usually runs a global HRIS (for org structure, headcount reporting, sometimes global payroll consolidation) that needs to talk to your India-specific payroll engine, since very few global platforms handle India statutory payroll natively with full local accuracy. Clarify early: is India payroll data pushed into the global HRIS via API, exported on a schedule, or manually reconciled? Underspecifying this leads to duplicate data entry and version-of-truth disputes between India HR and HQ HR.

Reporting for HQ finance. HQ finance will want standardized cost reporting — headcount cost by function, currency-converted payroll cost trends, statutory liability accruals — in a format they can consume alongside other regional payroll data. Confirm the platform (or your internal team) can produce this without a manual monthly export-and-reformat exercise.

Scalability. Choose a platform that can handle your 18-month headcount plan, not just your launch-day headcount. Re-platforming payroll mid-growth is disruptive and risky — it's one of the few processes where "we'll upgrade later" is genuinely expensive to defer.

Common Pitfalls HQ Teams Run Into

Some patterns show up again and again when multinational HQs stand up their first India GCC. Worth naming directly:

Assuming India payroll is monthly-and-done, like a simpler version of home-country payroll. In reality, the compliance overhead — multiple statutory contributions, multiple filing cadences, state-specific rules — makes India payroll operationally heavier than payroll in many single-jurisdiction Western countries, even though average pay levels are lower.

Treating professional tax and shops and establishments registration as one-time, national steps. They're state-specific and need to be repeated (or at least reassessed) every time you open in a new state or city.

Under-provisioning for gratuity and other long-tenure liabilities. These don't show up as a monthly cash cost early on, so HQ finance sometimes forgets to model them into long-run cost projections until they become material.

Benchmarking compensation against "India" as a single market. Pay expectations, cost of living, and competitive intensity vary significantly by city. A single national pay band undermines your ability to compete in higher-cost hiring markets and overpays in others.

Centralizing payroll approval too tightly at HQ. If every payroll run needs sign-off from a finance approver in a very different time zone with limited India payroll context, you introduce delay and error risk into a process that has hard statutory deadlines. Build an approval workflow that respects both control and the calendar.

Not budgeting time for registration lead times. PF, ESI, and other registrations can take weeks, and delays compound if paperwork is incomplete. HQ teams that set an aggressive launch date without buffer for this routinely end up delaying start dates for hired employees — a bad first impression for a workforce you're trying to make feel like a first-class part of the company, not an outsourced afterthought.

Assuming one vendor or platform can be "set and forget." GCC payroll needs, especially around multi-state expansion and headcount scale, change quickly in the first two years. Build in periodic reviews of whether your operating model and technology stack still fit, rather than assuming the year-one decision is permanent.

A Phased Rollout: Pre-Launch to Steady State

Here's a practical way to sequence the work, structured as a numbered walkthrough with a rough timeline. Adjust the exact durations to your entity incorporation timeline and hiring plan — the sequence matters more than the exact week numbers.

1. Weeks 1–4: Entity and foundation. Finalize entity structure and incorporation, open banking relationships, confirm registered office locations, and select your payroll operating model and technology platform.

1. Weeks 4–10: Statutory registration. File for TAN, PF, ESI, professional tax, and shops and establishments registrations for your first location. Engage a local compliance advisor if you haven't already. Begin designing salary structures and benefits benchmarking in parallel.

1. Weeks 8–12: System configuration and dry runs. Configure your payroll/HRMS platform, load organizational structure and policies, and run at least one full parallel payroll cycle before go-live to catch configuration errors while there's no real money and no real employee impact on the line.

1. Launch (first payroll run): First 90 days. Process live payroll, closely monitor statutory filing accuracy, and hold a weekly (not monthly) check-in between India payroll ops and HQ finance to catch issues early. This is also when you'll onboard the bulk of your initial hiring cohort, so expect payroll volume and edge cases (new joiners, offer letter discrepancies, relocation allowances) to be highest in this window.

1. Days 90–180: Stabilize and expand. Move check-ins to a steady monthly rhythm once the first quarter's filings have gone cleanly. This is typically when a GCC opens its second location — begin the multi-state readiness checklist well before the first employee in that state is hired, not after.

1. Months 6–12: Benchmark and refine. Revisit compensation bands against updated market data, review whether your payroll operating model is still fit for purpose at your new headcount, and formalize the compliance calendar as a shared, owned artifact rather than something a few individuals carry in their heads.

1. Year 2 and beyond: Steady state with periodic review. Payroll should now be a predictable monthly rhythm with minimal HQ intervention needed for routine cycles. Schedule an annual review of your operating model, technology stack, and compliance posture — GCCs that skip this tend to be the ones still running on year-one decisions that no longer fit a much larger organization.

Frequently Asked Questions

Do we need a separate professional tax registration for every state we operate in? Generally yes — professional tax is a state-level tax, and most states that levy it require a separate registration and separate periodic remittance. Some states don't levy it at all. Confirm the current position state-by-state with your advisor before opening a new location.

Can we run India payroll entirely through our global HRIS without a local payroll engine? In practice, most global HRIS platforms don't natively handle India's statutory payroll calculations (PF, ESI, TDS, gratuity, state-specific professional tax) accurately, so most GCCs use a India-specific payroll engine or HRMS underneath, integrated with the global HRIS for reporting and org data rather than for the actual statutory calculation.

How long does it typically take to get PF and ESI registrations done? It varies by state and by how complete your documentation is, but budget several weeks, not days. Start this process as early as possible in your entity setup timeline, and don't set employee start dates that assume same-week registration.

Should we outsource payroll or build an in-house team first? Most new GCCs are better served starting with an outsourced or HRMS-led model to get compliant quickly, then building internal capability (even a lean one to two-person team) as headcount and complexity grow. Committing to a fully in-house build before you've hired your first cohort is usually premature.

How different is compensation benchmarking across Indian cities? Meaningfully different, especially between the established hubs (Bangalore, Pune, Hyderabad, NCR, Chennai) and emerging tier-2 GCC locations. Use city-specific data, not a single national number, especially for competitive tech, engineering, and finance roles.

What happens if we miss a statutory filing deadline? Consequences typically include interest and penalties, and repeated lapses can draw closer scrutiny from authorities. The financial exposure is usually smaller than the operational and reputational cost of a pattern of late filings, so the priority should be building a reliable operating rhythm, not just budgeting for occasional penalties.

Can our GCC extend global stock or equity plans to India employees? Often yes, but it requires coordination between HQ legal/tax and your India payroll setup, since equity compensation has distinct tax treatment and reporting requirements in India. Plan this as its own workstream rather than assuming it plugs in automatically alongside cash payroll.

Do remote employees change our multi-state compliance picture? They can. An employee based in a state different from your registered office location may trigger state-specific obligations you haven't planned for. Capture and periodically verify actual work location for every employee, not just their assigned office.

Bringing It Together

Setting up payroll for a GCC in India is a genuine operating build, not a checkbox on an entity-setup timeline. The companies that get it right treat statutory registration, payroll model selection, multi-state complexity, compensation benchmarking, and compliance rhythm as parallel workstreams that need to be sequenced deliberately — starting well before the first offer letter goes out, not after.

Get the foundation right in the first 90 days, and payroll becomes a quiet, reliable function that lets your GCC focus on the work it was built for. Get it wrong, and it becomes a recurring distraction that HQ finance and India leadership both end up managing by hand.

If you're building or scaling a multi-state, multi-entity GCC in India and want to see how a modern payroll and HRMS platform handles this kind of complexity end-to-end, CozyHR is worth a look. We'd be glad to walk you through how it supports GCCs navigating exactly these challenges.