Setting up a global capability centre in India is a programme, not a purchase. Done well, a finance and accounting centre goes from decision to running your month-end close in four to six months. Done as a do-it-yourself captive, the same journey usually takes twelve to eighteen. The difference is rarely ambition; it is sequencing, and knowing which of the dozens of tasks sit on the critical path.
This guide walks through the six steps we use to establish finance GCCs, the timings that hold up in practice, and the handful of items that decide whether a programme lands on schedule.
Three decisions before the clock starts
Scope. Decide which processes move first. Transaction-heavy work with clear rules — accounts payable, bank reconciliations, fixed assets, intercompany — transitions cleanly and builds confidence. General ledger and close activities follow. Management reporting, FP&A and treasury come once the centre is stable. A first wave that tries to move everything at once is the most common reason programmes stall.
Model. A captive you build yourself, a managed centre a partner sets up and runs, or a build-operate-transfer arrangement that starts as one and becomes the other. The choice changes who carries the set-up work and how fast the centre can be live; the comparison of GCC, BPO and captive models sets out the trade-offs.
Location. Bangalore offers the deepest pool of qualified accountants and the most competition for them; a second city such as Kolkata offers lower attrition and cost with a strong Chartered Accountant base. Many centres end up with a hub in one and a delivery team in the other.
Step 1 — Strategy and business case (weeks 0–4)
The business case does two jobs: it tells the board what the centre will cost and save, and it tells the programme what it is building. A useful one contains the baseline cost of the finance function today, a target operating model showing which roles stay onshore and which move, a team model with grades and headcount by wave, a cost comparison over three to five years, a timeline with decision gates, and a risk register that names the people-related risks candidly.
Two numbers matter more than the rest. The first is the fully loaded cost per role in India against the equivalent onshore cost, including office, technology, management and attrition. The second is the transition cost — the months of parallel running, travel and retained-team time that the savings have to pay back. Programmes that skip the second number tend to look better on paper than in year one.
The gate at the end of this step is a signed mandate: scope, model, location, budget and a named executive sponsor.
Step 2 — Entity and regulatory set-up (weeks 2–10)
If you are building your own entity, the standard vehicle is a private limited company that is a subsidiary of the group. Incorporation runs through the Ministry of Corporate Affairs on the integrated SPICe+ form, which also allots the company's PAN and TAN and lets you apply for GST, provident fund and state insurance registrations in the same filing. Directors need digital signatures and identification numbers, foreign documents need to be notarised and apostilled, and at least one director must be resident in India. With documents ready, incorporation typically takes two to four weeks.
The longest single item is usually the bank account. Know-your-customer checks on foreign directors and shareholders can take several weeks, and nothing else — premises, payroll, vendor contracts — can move until the account is open. Start it the day the certificate of incorporation arrives, and expect to send documents more than once.
Investment from the parent is on the automatic route for finance and accounting services, but the share allotment has to be reported to the Reserve Bank of India within thirty days, and the annual foreign liabilities return follows. Tax registrations, a shops-and-establishments licence, professional tax and a payroll set-up round out the list. Special economic zone or software-park options are worth a look for a large centre, but they rarely change the timeline and add administration.
The managed route is faster because the partner's existing entity employs the team from day one; your own entity can be formed in parallel and the team transferred later, or never, depending on how you want to own the centre.
Step 3 — Infrastructure and technology (weeks 4–12)
Premises come in two phases. A managed office or serviced floor can be live in weeks and is the right first home for a team of ten to thirty; a leased, fitted-out floor takes three to six months and belongs in year two, when headcount is known. Do not let the lease sit on the critical path.
Technology is where finance centres differ from other GCCs: the team works inside your ERP, so the real work is access, not hardware. Provision roles in SAP, Oracle, NetSuite or Dynamics with segregation of duties designed in from the start, deliver access through virtual desktops or a managed VPN rather than local installs, and put device management, multi-factor authentication and data-loss controls in place before the first hire logs in. Write the information-security policy against your group standard — most centres align to ISO 27001 — and make sure it addresses both India's data-protection law and the rules of the jurisdictions whose data the team will handle, such as GDPR for UK and European entities.
Redundant connectivity, a helpdesk arrangement with your IT team across time zones, and a decision on where documents live (your SharePoint, not a local drive) complete the set-up.
Step 4 — Talent acquisition (weeks 4–16)
Hire the centre lead first. A controller-grade leader with experience of transitions will shape the team, own the relationship with your finance leadership and stop a hundred small problems reaching you. Team leads come next, then the accountants and analysts in the order the waves need them.
India's talent pool for finance is deep — Chartered Accountants, CPAs, CMAs and large numbers of experienced graduates — but the market moves at its own pace. Notice periods of sixty to ninety days are standard at every level above entry, which means an offer made in week eight lands a person in week sixteen. Plan the hiring calendar backwards from the transition dates, not forwards from the mandate.
Write a competency framework for each role, benchmark compensation against the market rather than against onshore costs, and invest in the employer story: candidates choose between several GCCs, and the ones that describe the work, the systems and the career path win. Attrition is managed the same way it is anywhere — by a good manager, visible progression and work that matters.
Step 5 — Process transition (weeks 12–24)
Transition is the step that most rewards discipline. It starts with knowledge capture: documented process maps and standard operating procedures, recorded walkthroughs, control descriptions and a clear list of exceptions and workarounds that live in people's heads today. Then the waves.
Wave one moves the high-volume, rule-based work. The team shadows the onshore process owners for a cycle, runs it alongside them for one or two more, and reconciles every difference before the process is signed over. Wave two brings close activities and reporting, with the same shadow-parallel-sign-off rhythm. Controls are tested in the new location before the old one lets go, so the auditors see an unbroken chain of evidence.
Two things make or break this step. The first is the retained team: the onshore people whose work is moving need a clear future role and a reason to transfer knowledge well. The second is the service-level agreement — agreed before wave one, with a small number of measures that matter (close days, accuracy, turnaround, backlog) and a review rhythm that starts immediately.
Step 6 — Go-live and stabilisation (week 24 onward)
Go-live is a date; stabilisation is a period. Plan four to eight weeks of hypercare with daily check-ins, an issue log that is worked to zero, and KPI baselining so that month three can be compared with month one. Then the governance settles into a rhythm — weekly operations calls, a monthly performance review against the SLA with your finance leadership, and a quarterly business review that looks at scope, people and the improvement pipeline.
A centre that has met its service levels for two consecutive months, passed controls testing and published its first management-information pack is stable. From there the conversation turns to what else it could do: FP&A, treasury operations, audit support, procurement, the next entity.
The timeline, side by side
| Phase | Managed centre | Do-it-yourself captive |
|---|---|---|
| Business case and mandate | Weeks 0–4 | Weeks 0–8 |
| Entity, bank account and registrations | Runs in parallel; the partner's entity employs the team meanwhile | Weeks 4–20, with the bank account on the critical path |
| Premises and technology | Weeks 4–12 in a managed office | Weeks 8–30 if a leased floor is fitted out first |
| Leadership and team hiring | Weeks 4–16 | Weeks 12–36, gated by the entity and payroll |
| Process transition | Weeks 12–24 | Weeks 30–60 |
| Steady state | Month 5–6 | Month 12–18 |
Where programmes slip
- The bank account. Weeks lost to KYC are the most common delay in India and the easiest to plan for.
- Notice periods. Offers made too late push the whole transition by a quarter.
- Access approvals at headquarters. ERP roles, VPN and identity requests queue behind everything else in a group IT function unless someone owns them.
- Documentation debt. Processes that were never written down take three times longer to move.
- An over-ambitious first wave. Confidence is built by early, visible wins.
- The retained team. Transition succeeds or fails on whether the people handing work over want it to succeed.
What done looks like at month six
The team is in place and led locally; the first two waves run to service levels; controls have been tested in the new location and the auditors are comfortable; the dashboard and MIS pack go out on time; and there is an agreed roadmap for what the centre takes on next. That is the point at which a GCC stops being a project and starts being part of the finance function.
How Finactro approaches this
Finactro designs, establishes and operates finance and accounting GCCs in India as a fully managed service: our entity and infrastructure carry the team from day one, your ERP, policies and data stay yours, and you can internalise the centre whenever you choose. If you would like a sized plan for your own finance function — scope, team model, cost comparison and a realistic timeline — book a discovery call and you will have a business case within two weeks, without obligation.