Intercompany Reconciliation for India Multi-Entity Close

Why does intercompany reconciliation get harder every time you add an entity?

This guide is for controllers and finance leads closing books across two or more legal entities, usually a US parent with an Indian subsidiary, a services arm, or both.

We help global companies hire intercompany accountants and reconciliation analysts in India through our Employer of Record service, so this guide focuses on the judgment work that survives after the matching engine has run.

It covers where differences come from, what the tooling settles on its own, what it will never decide, the roles the process needs, and how to staff them without registering a company in India.

What is intercompany reconciliation, and why does it stall the close?

Intercompany reconciliation is the process of agreeing balances and transactions between two entities in the same group so they eliminate cleanly on consolidation. It stalls the close because a difference is not an arithmetic error you can post away. Someone has to decide which entity is right, and why.

Every intercompany line has two authors. One entity books a receivable, the other books a payable, and they only agree if both used the same amount, the same period, and the same rate.

Miss any one of those three and consolidation leaves a residual that does not net to zero.

That residual is usually the first thing an auditor asks about, which is why the work sits at the center of the record-to-report cycle you run in offshore finance and accounting.

Before you can fix the differences, you have to know where they come from.

Where do intercompany differences actually come from?

Most intercompany differences come from six places: timing and cutoff gaps, currency translation, service charges one side never agreed, missing counterparty coding, transfer pricing true-ups posted on one side only, and duplicated or disputed recharges. Almost none of them are arithmetic problems.

Here is what each source looks like in the ledger, and who owns clearing it:

Read the pattern: five of the six are agreement failures between two teams, not calculation failures inside one ledger.

A matching engine will surface all six in minutes, which is exactly what account reconciliation software is for.

Recharges usually originate in the payables queue, so accounts payable automation decides how many of them ever reach your intercompany matrix at all.

The mirror image sits on the billing side, where accounts receivable software controls what the counterparty entity actually sees on its statement.

So the tooling finds the differences. The question is what happens next.

How does an intercompany reconciliation run, step by step?

An intercompany reconciliation runs in three moves: agree the matrix of entity pairs and balances before you match, run the match and triage what did not pair, then clear or escalate every remaining item and hand a clean set to consolidation. Everything else is variation on those three.

Agree the intercompany matrix before you match

The matrix lists every entity pair, the accounts in scope, the agreed cutoff, and the rate source. Without it, matching is guesswork with a good user interface.

Rate source is the line people skip. If two entities pull FX from different places, you have built a permanent difference into the process.

This is the same data and SOP readiness precondition that decides whether any automation in your finance stack earns its keep.

Match, then triage what did not pair

The engine pairs the clean, rules-based items. What is left is your actual workload, and it needs sorting by cause rather than by size.

Payables-side breaks route back to the team that raised the recharge, which is why an offshore accounts payable team in India is usually the first stop.

Receivables-side breaks route the other way, to the offshore accounts receivable team in India that issued the intercompany invoice.

Clear, escalate, and hand a clean set to consolidation

Clearing means posting the agreed correction on the correct side, in the correct period, at the agreed rate. Escalating means naming an owner and a date, not moving the item to a spreadsheet.

Only then does financial consolidation software do its job, because elimination assumes the two sides already agree.

From our experience running closes for multi-entity groups, the teams that hit their calendar are the ones that escalate on day two rather than day four.

That sequence is straightforward on paper. What breaks it is the set of decisions no tool will make for you.

What can intercompany reconciliation software not do?

Matching software cannot decide which entity is right. It cannot agree a service charge, choose a transfer pricing rate, judge whether a timing difference is acceptable, write off a stale balance, or hold a counterparty controller to a date. Each of those is a human decision with an audit trail.

Here is the split, task by task:

Read the right-hand column again. It is a job description, not a configuration screen.

That is the honest ceiling on finance automation: it compresses the volume, then hands you the arguments.

The same pattern shows up wherever agents touch a ledger, which is why AI in accounts payable still leaves exception handling with a person.

Put simply, the tooling handles the rules and people handle the judgment, which is the whole premise of agentic offshoring.

Which means the real question is not which tool to buy. It is who you put on the queue.

Which roles does an intercompany reconciliation process need?

Five roles carry a multi-entity intercompany process: an intercompany accountant, a reconciliation analyst, a close and consolidation lead, an FX and transfer pricing reviewer, and a controller who signs off. Small groups combine the first two. Nobody should combine the last two.

Here is what each seat actually owns:

• Intercompany accountant: Owns the counterparty relationship, raises and agrees recharges, and confirms balances entity to entity before cutoff.
• Reconciliation analyst: Works the unmatched queue, gathers support, and clears breaks or names an owner for the ones that cannot close.
• Close and consolidation lead: Holds the close calendar, runs the elimination schedule, and decides what is material enough to delay a sign-off.
• FX and transfer pricing reviewer: Decides which rate applies to each entity pair and whether a true-up belongs in this period or the next.
• Offshore controller: Approves write-offs, certifies the reconciliations, and owns the audit trail the external auditor will test.

Notice that four of the five spend most of their time deciding rather than matching.

For the salary bands and fully loaded cost of each seat, our offshore record-to-report team in India breakdown carries the numbers, and this guide defers to it.

If you are modeling a whole function rather than one process, the cost of an offshore finance team in India guide is the wider view.

Wisemonk issues a compliant Indian offer in 24 to 48 hours, and hiring an Indian national typically takes one to two weeks. Wisemonk, 2026

With the seats named, the calendar is what turns them into a close you can trust.

What does an intercompany close calendar look like across a multi-entity group?

A workable calendar front-loads the matching and back-loads the judgment. Continuous matching runs before cutoff, the break queue is triaged on days one and two, disputes are escalated with named owners by day three, and eliminations and sign-off land on days four and five.

Here is how a five-day intercompany close splits between automated work and human decisions:

The calendar only holds if day three is treated as a decision day rather than a chasing day.

The same discipline pays off downstream, because the group numbers your offshore FP&A team in India reports on are only as clean as the eliminations behind them.

If you are deciding what to move first, our view on which business functions to offshore to India starts with exactly this kind of rules-plus-judgment work.

Before you buy anything to support that calendar, price it properly.

What should you ask before you buy intercompany reconciliation tooling?

Intercompany matching is quote-based, so ask about components rather than a list price. The four that move the number are entity and account volume, connector work into each ledger, configuration of tolerance and elimination rules, and the audit support you will need every year afterwards.

Here is what to price, and the question to put in front of a vendor:

The pattern in that last column is deliberate. Every question is about what happens after the demo.

City choice moves the same budget more than most buyers expect, which is why we keep a current view on the best Indian cities for offshore finance operations.

At larger scale the tooling question turns into an operating model question, and building a shared services center in India is the version of that conversation we have most often.

That leaves the part most guides skip: who does the work, and how you employ them.

How do you staff intercompany reconciliation in India without setting up an entity?

Use an Employer of Record. You define the seats, the EOR holds the Indian employment contracts and runs payroll and statutory contributions, and your controller keeps the estimates and the sign-off. The team can be live in weeks, with no company registration in India first.

That gap is the whole reason offshoring to India works for a process you need running by next quarter's close.

It is also why finance has become one of the most common functions in outsourcing to India programs for US mid-market groups.

Here is the sequence we use with finance teams:

• Scope the matrix first: Write down the entity pairs, accounts, and cutoff before you hire, because the scope decides whether you need two seats or five. It is the same first step as building an offshore team in India for any other function.
• Hire the judgment seats early: Start with the intercompany accountant and the reconciliation analyst, the two people who make decisions daily. This is where accounting outsourcing to India differs from a pure processing arrangement.
• Fix the upstream books: Clean subledgers are what make the match work, so outsourcing bookkeeping to India usually happens alongside rather than afterwards.
• Run one close in parallel: Shadow a full cycle before handover, and measure break volume and days to sign-off rather than headcount.
• Decide on the entity later: Keep the option open and revisit it on volume, using our EOR vs entity in India comparison when the numbers change.

Sequenced that way, the first close on the new team is a rehearsal rather than a risk.

If the model itself is new to you, start with what an employer of record is and how the employment relationship is split.

Here is where we fit.

How can Wisemonk help you build intercompany reconciliation in 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 intercompany reconciliation, that means an accountant and an analyst working your entity pairs and your break queue within weeks, on compliant Indian employment contracts, without registering a company in India first.

Your controller keeps the write-offs, the transfer pricing calls, and the sign-off. The team in India carries the daily agreement work that makes those calls possible.

We support 300+ global clients, employ 2,000+ people, process $20M+ in annual payroll, and hold a 4.8/5 rating on G2, with EOR pricing from $99 per employee per month as of August 2026.

Here is how we help:

• Recruitment: Source intercompany accountants, reconciliation analysts, and close leads who have already worked a multi-entity ledger.
• Managed payroll: Run monthly payroll with EPF, professional tax, and TDS handled, so your finance team spends its time on the group ledger.
• Contractor management: Engage a transfer pricing or systems specialist on a defined scope at 6% per payment, compliantly.
• Background checks: Verify credentials and employment history from $50 per candidate before anyone gets access to your general ledger.
• GCC setup: Build a captive finance center when your close volume justifies owning the operation outright.
• Entity setup: Register an Indian company when you decide to hold the employment relationship yourself.

From our experience standing up intercompany teams in India, the break queue shrinks fastest when the analyst talks directly to the counterparty controller instead of working through a ticket queue.