Hire a Month-End Close Team in India: 12-Week Transition

Twelve weeks is enough time to move a month-end close to India. It is not enough time to hire the people, document the process, and then move the close, which is why most transition plans slip by a quarter before the first parallel run.

We have helped 300+ global companies build and run teams in India, including finance pods that own reconciliations and the close. The pattern is consistent. The process work is rarely what delays a close transition. The employment timeline is.

This plan assumes the decision is made. What follows is the sequence: what transfers and in what order, what the three close cycles inside twelve weeks are for, which hiring route can deliver the dates, and how you prove it worked.

The steady state it produces, meaning the roles you end up with and the rhythm of a close once it is running, is covered separately in this guide to an offshore record-to-report team in India.

This is a transition plan rather than a hiring primer. If you have not put anyone on an Indian payroll before, the legal steps come first, and they are set out in this guide to hiring and paying someone in India from the US.

What actually moves when you shift the month-end close to India?

Three things move: preparation, reconciliation, and first-pass analysis. Sign-off does not. A well-scoped transition sends rules-based and method-driven work to India in two waves, keeps judgment with the controller, and never asks the India team to defend a position it did not set.

Scope by evidence, not by task name. If a step produces the same answer whenever two competent people follow the documented method, it can move. If two competent people could reasonably disagree, it stays.

Split the work into waves so the second close is not carrying every unfamiliar task at once:

Reconciliation is the natural wave one anchor because the evidence already sits in the system, and the tooling side of that is covered in this breakdown of account reconciliation software.

Once the waves are agreed, the calendar decides everything else.

What makes twelve weeks the right window?

A close happens once a month, so a twelve-week window contains exactly three of them. That is the constraint the plan is built around: one close to observe, one to run in parallel, one to run for real. There is no way to buy a fourth close inside a quarter.

This is why the phases are four weeks each rather than an arbitrary split. Every other activity bends around three cycles, not the other way around.

It also means two clocks are running, and confusing them is the most common planning error:

• Clock A, the transition: twelve weeks and three closes, starting the day your India team is in seats with system access.
• Clock B, getting them there: sourcing, offers, notice periods and the employment setup underneath. Clock A cannot start until Clock B finishes.

Plans slip because the approval date is treated as week one. It is not. Week one is the first day the India team can watch a live close.

If the wider function is still being sized rather than scheduled, the operating context is set out in this guide to building an offshore finance and accounting team in India.

With the arithmetic fixed, the next question is what has to be ready before the clock starts.

What has to be true before week one?

Six things, and all of them are cheap compared with restarting a phase. Week one does not begin because a steering committee said so. It begins when your India team can log in and watch a live close, which means access, scope and ownership are already settled.

Before you commit to a start date, confirm:

• A close calendar that exists in writing: every task, owner, system, input, and the business day it is due. If this does not exist today, week one is really week three.
• A decided hiring route: an Employer of Record, your own entity, or a provider. It sets the start date, so it cannot stay an open item.
• A named US owner: one person who accepts or rejects each transferred task. Not a committee.
• An ERP access model: the roles your India team will hold, the approval thresholds, and where the preparer and approver split sits.
• A data-protection position: what personal and financial data crosses borders, on whose systems, and under what controls.
• A measured baseline: days to close, post-close adjusting entries, and reconciliation certification rate for the last three months.

The last one is what teams skip, and it is what makes the transition unprovable. Measure it before anything changes, because you cannot reconstruct it afterwards.

Where the preparer and the approver end up on different continents, the control design needs rework, and the mechanics of segregation of duties are where that conversation should start.

The data question deserves the same treatment before any ledger access is granted, and the obligations that fall on a foreign employer holding Indian employee and financial records are set out in this guide to India's DPDP Act for foreign employers.

With that gate cleared, phase one begins.

Weeks 1 to 4: how do you capture the close before you transfer it?

Phase one produces two artifacts: a task inventory at the level of individual reconciliations, and a captured version of how each one is actually performed. Your India team observes close one end to end with read-only access and posts nothing. Nothing transfers in this phase.

The inventory has to be specific enough to schedule. Not "bank reconciliations", but "reconcile fourteen bank accounts, three of them in foreign currency, from the day-two statement feed".

Tier every line into three buckets: rules-based, method-driven, and judgment-only. That tiering is your wave assignment, and it is also the honest answer to how much of the close is genuinely transferable.

Pro Tip: Capture the close while it is happening, not afterwards. A procedure written after a close records what people believe they do. A narrated screen recording of the live close records what they actually do, including the two spreadsheet steps nobody documented because they are not in the system. Those undocumented steps are what break the first parallel run.

Close one is a shadow close. Your India team follows along in real time, annotates the captured procedures where reality differs, and logs every question.

The question log is a deliverable, not a byproduct. Its length in week four predicts how close two will go, so read it rather than filing it.

The phase-one gate is concrete. The inventory is signed by the US owner, wave one procedures are captured and annotated, contracts are signed with confirmed start dates, and sandbox access is granted.

Documented process knowledge is a business asset, and Indian law does not default it to you the way US work-for-hire does. Because India's Copyright Act 1957 assigns ownership to the creator unless the contract says otherwise, the assignment clause matters as much for procedure documentation as it does for code.

With the close captured and the team in seats, the second phase is where the transfer is actually tested.

Weeks 5 to 8: how does the parallel run and reverse shadowing work?

Close two runs twice. Your India team prepares wave one in a parallel set of workpapers while the US team prepares the same items as normal, and the two are compared line by line before anything posts. Only the US version reaches the ledger.

A parallel run is a controlled experiment, so treat differences as data. A reconciliation that agrees on the balance but was built a different way is still a finding, because it will diverge the moment an edge case appears.

Shadowing and reverse shadowing are not the same thing, and running only the first is the most common reason a handover fails in month four:

• Shadowing: your India team watches the US team perform the work. It transfers sequence and context. It does not test competence, because nobody has done anything yet.
• Reverse shadowing: your India team performs the work while the US owner watches and intervenes only on error. It is the only step that produces evidence the team can do it.

Reverse shadowing starts partway through close two, once the parallel comparison on the first few accounts comes back clean. It is a mode you switch into account by account, not a separate phase to schedule.

One operational detail decides how smoothly this runs. India sits about nine and a half to ten and a half hours ahead of US Eastern, so the working overlap is a US morning and an India evening.

Design the close around a written handoff at the end of the India day rather than a standing call, and treat the overlap as review time. Practical patterns for that cadence are set out in this guide to managing a US and India team across time zones.

The phase-two gate: every wave one item has been prepared by your India team at least once and compared clean, the exception log carries nothing older than one cycle, and the US owner has signed off on moving wave two.

Weeks 9 to 12: how do you go live without losing a cycle?

Close three is India-led. Your India team prepares and posts waves one and two under normal approval thresholds, and your controller reviews and signs. Nothing about the control structure changes. What changes is who prepares, and that is the only variable you want moving.

Go-live is a decision made against the exit criteria, not a date on a plan. If close three does not clear them, run a fourth close in the same mode rather than absorbing the problem into business as usual.

Resist the pull to optimize during the transition. Changing the close calendar, the tooling and the people in the same quarter makes any later problem undiagnosable. Optimization starts after the first clean India-led close.

Wave two lands in this cycle, so the first India-prepared flux commentary appears here. Reviewing it well is a skill of its own, and the method is set out in this walkthrough of variance analysis.

Multi-entity work is where week eleven usually gets uncomfortable, because eliminations depend on both sides closing on time. The failure patterns are worth reading in advance in this walkthrough of intercompany reconciliation.

By the end of week twelve you should be able to state in one line which activities your India team owns, which the US team retained, and what days to close now reads against the baseline.

Which India hiring route can actually deliver this timeline?

Four routes exist, and they differ mostly in how long it takes before someone can watch a close. An Employer of Record puts a named accountant in seat fastest because the entity already exists. Your own entity gives you full control and a start date measured in months.

Build in-house on your own Indian entity

You incorporate, register, and employ the team directly. Full control, your own contracts, and the compliance obligation is yours. We put setup at three to six months with experienced local help, and closer to six to twelve months if you assemble it yourself.

Use an Employer of Record

A provider that already holds an Indian entity becomes the legal employer while you direct the work day to day, which is how companies hire employees in India without an entity. A compliant offer issues in 24 to 48 hours and an Indian national typically starts within one to two weeks, as of September 2026.

Staff augmentation

You get named people embedded in your team and direct their work, while they remain employed by the supplying company. Useful for surge capacity, weaker for a close, because continuity of the same individuals across cycles is the whole point.

Managed services or a business process outsourcing provider

You hand the process to a provider who owns delivery against a service level agreement and staffs it as they see fit. The provider runs their own transition method, and you trade day-to-day control for a contracted outcome.

Which of these can legally and practically hold each finance process, and where the audit trail breaks when the process owner is not the employer, is worked through in this comparison of EOR, BPO and GCC for an India finance back office.

Set against the twelve-week plan, the routes separate cleanly on the only variable that matters here, which is time to a person in seat.

These figures come from what we publish on Employer of Record and capability centre setup, as of September 2026.

The crossover between the first two routes is a cost question as much as a control one, and it is modeled out in this comparison of an Employer of Record against your own entity in India.

Whichever route you pick, we can support the employment and hiring side of it for teams in India, from Employer of Record engagements through to company registration in India and capability centre builds.

Now the arithmetic that sets your start date. Notice periods in India are set mainly by the employment contract, with state Shops and Establishments Acts prescribing a minimum, and they commonly run one to three months, as of September 2026.

Example, and it is illustrative rather than a real client: you approve the project on March 1 and sign an employment agreement the same week. Offers go out on March 20 and are accepted on March 25. Two of your three hires serve 60 days and start on May 26. Close one, the shadow close, is the May close run in early June. Close three is signed in early August. The twelve-week plan was accurate. The go-live is five months after approval.

The fix is not to compress the plan. Run sourcing in parallel with phase-one documentation, and publish two dates to your CFO rather than one. The durations behind both are broken down in this India hiring timeline.

What does moving the close to India cost?

Two costs, and they behave differently. The transition cost is a one-off period of running two teams across three closes. The run-state cost is per seat per month, and it is the number that shows up in next year's budget.

Budget the transition as roughly one quarter of double-running on the activities in scope, plus the US owner's time. That reviewer time is the item most plans understate.

For run state, the components are salary, the statutory employer layer, the employment fee, and software seats. Our own calculator gives a worked example on a ₹6 lakh gross seat with employer Provident Fund added on top and health insurance included.

That seat returns $6,350 gross, $229 employer Provident Fund, $106 health insurance, an $1,188 annual platform fee, and provisions of $135 leave encashment and $158 gratuity, for about $8,166 a year in total employer cost, as of September 2026.

That puts the statutory layer at roughly 8% on top of gross for that band. It is not a flat percentage, and the reason matters before you model a senior hire.

Provident Fund, India's mandatory retirement savings scheme, is capped at the ₹15,000 monthly wage ceiling, and Employee State Insurance stops applying above ₹21,000 a month. So the statutory add-on shrinks as salary rises and can fall to low single digits for senior roles.

We publish the headline band as 15% to 22% of gross, with total cost of employment landing around 110% to 125% of gross salary, as of September 2026.

Those figures are estimates on the calculator's own assumptions: a standard 50/25/10 Basic, House Rent Allowance and Leave Travel Allowance structure, flat statutory Provident Fund of ₹1,800 a month, and professional tax assumed at ₹200 a month, which varies by state. Rebuild any of it with the employee cost calculator.

For the full role-by-role model rather than a single seat, the layered breakdown sits in this analysis of the cost of an offshore finance team in India.

What derails a close transition, and how do you see it coming?

Six failure modes account for most of it, and every one is visible before it becomes a missed close. The two that do the most damage are structural: the reviewer seat filled last, and a notice period nobody modeled.

The reviewer seat filled last. Teams hire three preparers and plan to add the senior reviewer once volume justifies it. Then close two arrives with nobody in India able to challenge a number.

Wisemonk Insight: Hire the reviewer first. Across the India capability builds we have supported, the underperforming ones share a root cause: the first hire was an operations manager rather than a leader. Teams with active governance in week one also retain 20 to 25% more of their people through year one. On a close transition the reviewer is your knowledge insurance, because they are the person who can rebuild a procedure when a preparer resigns.

Attrition inside the window. Losing one of three people in the first year restarts a third of your knowledge transfer, and the retention mechanics that reduce it are covered in this guide to managing attrition in India.

City choice moves this more than any retention policy. Annual attrition runs around 25% in Bengaluru against 12 to 15% in tier II cities on our own India capability centre data, and the trade-offs by location are compared in this look at the best Indian cities for offshore finance operations.

Access granted late. Sandbox access in week one is not optional. A team that cannot see the system during the shadow close is watching a screen share, which is not the same thing.

Undocumented steps surfacing in close two. Expect them. Recording the close in phase one reduces the count, it does not reach zero. Budget review time in phase two specifically for this.

Control design left implicit. If the same person prepares and approves because the approval matrix was never updated, the transition has created an audit finding, and where the close feeds a formal control framework the requirements are set out in this overview of SOX compliance software.

Regulatory obligations treated as an IT question. India's Digital Personal Data Protection Act Rules were notified in November 2025 and phase in through May 2027, covering consent management, 72-hour breach reporting and cross-border transfer controls.

India's four Labour Codes also came into force on 21 November 2025, consolidating 29 central laws, which changed contracts and payroll setup. The filing calendar underneath both is mapped in this guide to payroll compliance in India.

One more is worth naming early. If your India team starts signing contracts or closing deals on your behalf rather than performing finance work you direct, the tax question changes shape, and the triggers are explained in this guide to permanent establishment risk in India.

How do you know the transition worked?

Six measures, all baselined in phase one and read again after close three. A transition that cannot be measured against a before state has not been proven, it has only been completed.

Judge close three against these:

• Days to close: business days from period end to sign-off, counted the same way as your baseline. Flat is a pass in quarter one, because the improvement comes later.
• Post-close adjusting entries: the honest quality signal. If this rises, the transition moved work before it moved understanding.
• Reconciliation certification rate by day three: measures whether wave one genuinely landed.
• Open exceptions older than one cycle: should be zero. Anything carried is a procedure that was never really transferred.
• Escalations to the US per close: the count matters less than the direction. Rising between close two and close three means the gate was opened too early.
• Audit findings and control exceptions: unchanged or better. Anything else outweighs every other number here.

Publish the six against the baseline in a single view, and make the wave two go-ahead conditional on them rather than on the calendar. That one discipline separates a transition from a handover.

Once the close is stable, the same discipline extends to the next process tower, and the wider build is mapped in this guide to building a shared services center in India.

How can Wisemonk help you move your month-end close to India?

Wisemonk is an India-native Employer of Record (EOR) that helps global companies hire, pay, and manage talent in India without setting up a local entity.

For a close transition, that means named reconciliation and general ledger accountants working your calendar within weeks, on compliant Indian employment contracts, without registering a company in India first.

Your controller keeps the estimates, the sign-off and the approval thresholds exactly as they are today. What changes is who prepares the work, and where they sit.

We support 300+ global clients and more than 2,000 employees across India, process $20M+ in annual payroll, and hold a 4.8/5 rating on G2. Pricing starts from $99 per employee per month as of September 2026.

Here is how we help:

• PEO services: if you already hold an Indian entity, we run payroll, statutory filings, benefits and onboarding under your own registrations, including equipment procurement for the team.
• Managed payroll: the monthly India pay run and its filings executed on your close calendar, so payroll cutoff never becomes a close dependency.
• TalentScout: sourcing and screening reconciliation, general ledger and close analysts against your own scorecard, with notice periods surfaced before you commit to a date.
• Background verification: identity, employment and education checks before anyone touches your ledger, from $50 per candidate for the standard package as of September 2026.
• Capability centre setup: when the finance team outgrows a pod, we stand up and staff the centre it becomes.

We came across Wisemonk and met with the CEO and staff to explain our situation, and were very impressed with their customer-focused approach to their business. Wisemonk onboarded all of my employees in one or two days. They paid my employees' salaries on the day after my payment cleared. Needless to say, my employees and I were very satisfied with their service then and remain so over a year later. We are an American company, so I was very happy to see that they have a US bank account where I can make ACH payments to minimize bank charges. All salary payments are timely. They worked directly with my employees to enroll them in the health care program and explain any coverage-related issues. The best part is that we get to work with a dedicated person assigned to our company. I would highly recommend Wisemonk and think of them as our Indian HR department.
- Frank Menes, Founder & CEO at Senem RFP

From our experience standing up finance pods in India, the transitions that hold are the ones where the India reviewer is in seat before the first shadow close, not the ones with the most detailed process documentation.