MIS Consolidation after Acquisition: Entity Mapping, Reports, Controls

MIS consolidation after acquisition is the work of turning two or more sets of books into one monthly management view that the board, lenders and the statutory auditor can all rely on. In Indian deals, the acquired company usually runs on a different ledger, a different chart of accounts and different KPI definitions, and its finance team may not stay. The first group MIS is often a spreadsheet stitched together under deadline, and that spreadsheet quietly becomes the system of record. This guide covers the three layers that decide whether group MIS holds: entity mapping, reporting alignment and controls.

What is MIS consolidation after acquisition?

MIS consolidation after acquisition is the monthly process of mapping each group entity’s ledger to a common chart of accounts, aligning accounting policies, calendars, currencies and KPI definitions, eliminating intercompany balances, and producing one group management report. It precedes and feeds statutory consolidation under Section 129(3) of the Companies Act 2013, but runs monthly, on management definitions, with its own controls.

How MIS consolidation after acquisition differs from statutory consolidation and pre-deal reconciliation

MIS consolidation is a recurring management process; statutory consolidation is an annual reporting obligation; pre-deal reconciliation is a one-time proof exercise. They share inputs, but they answer different questions, run on different calendars and fail in different ways. Treating them as one workstream is the most common reason group MIS is late or untrusted in the first two quarters after closing.

Before closing, the target’s job was to prove that the numbers it showed the buyer tie to its books, GST returns and bank. That work is covered in our guide on MIS reconciliation before due diligence. After closing, the question changes. The acquirer now has to produce a group number every month, compare it with the deal model and explain the variance, while the statutory consolidation (purchase price allocation under Ind AS 103, goodwill, AOC-1) runs on its own timeline. The statutory side, along with completion accounts, FEMA filings and tax losses, is covered in our guide on virtual CFO support for post acquisition integration. This article stays on the monthly management layer.

Table 1: Three workstreams that share data but not purpose

Dimension	Pre-deal MIS reconciliation	MIS consolidation after acquisition	Statutory consolidation
Question answered	Are the numbers already shown true?	What is the group doing this month?	What must be reported to shareholders and MCA?
Frequency	One time, before data room	Monthly	Annual (quarterly if listed)
Definitions	Target’s historical MIS vs books and filings	Group management definitions	Ind AS 110 or AS 21
Perimeter	Target only	Management perimeter (may include associates, exclude dormant entities)	Legal perimeter under Section 129(3)
Main failure mode	Unexplained differences become price adjustments	Mapping drift, unreconciled intercompany, KPI mismatch	Late audit, qualified opinion
Owner	Seller’s finance team with advisor	Acquirer’s finance head	Acquirer’s finance head with statutory auditor

The practical consequence: build the MIS layer so that statutory consolidation can be derived from it with documented top-side adjustments, not rebuilt from scratch at year end.

Entity mapping after acquisition: perimeter, ownership chain and control

Entity mapping after acquisition starts with a written register of every legal entity in the group, the ownership chain to each, the date control passed, the accounting framework, functional currency and ledger system, and whether the entity sits inside the management perimeter, the statutory perimeter, or both. Every later mapping and elimination decision depends on this register.

Most acquirers start mapping accounts before they have mapped entities. The target often brings its own subsidiaries, a dormant LLP, a foreign sales entity, or a trust holding ESOP shares. Each one needs a perimeter decision.

Which entities belong in group MIS?

Include every entity the group controls under Ind AS 110 (or that is a subsidiary under AS 21 for Indian GAAP groups), and decide separately on associates and joint ventures. Control under Ind AS 110 rests on power, exposure to variable returns and the link between them; the Companies Act test in Section 2(87) looks at board composition or more than half of total voting power. The two can diverge, and the register should record both conclusions.

The management perimeter can legitimately differ from the statutory perimeter. A 30% associate in which the acquirer has a board seat may be shown in MIS as a single line (share of profit) or excluded entirely; a wholly owned but dormant subsidiary may be left out of monthly MIS and picked up only at year end. What matters is that the difference is written down and bridged.

Table 2: Entity register fields and why each matters

Field	Example entry	Why it matters for MIS
Legal name, CIN or foreign registration	Target Pvt Ltd, U72900MH2019PTC000000	Ties MIS to MCA and audit records
Ownership chain and percentage	Acquirer 100% → Target 76% → Target UK Ltd	Drives non-controlling interest and layering review
Control date	14/08/2026 (completion date, not SPA signing)	Pre-control profits never enter group MIS
Control conclusion	Ind AS 110: control; Section 2(87): subsidiary	Explains perimeter if tests diverge
Accounting framework	AS (target) vs Ind AS (acquirer)	Determines policy alignment adjustments
Functional currency	INR / GBP	Drives translation method and FX bridge line
Ledger system	Desktop ledger (target), cloud ERP (acquirer)	Sets data extraction and mapping approach
Financial year end	31/03 (India), 31/12 (UK)	Determines whether a reporting-date gap is allowed
Perimeter flag	Management: yes; statutory: yes	Prevents silent inclusion or exclusion

Two Indian-specific checks belong in the register. First, where the target has its own subsidiaries, the Companies (Restriction on Number of Layers) Rules 2017 cap investment layers for most companies at two; the register should show the layer count so legal can confirm compliance. Second, Rule 6 of the Companies (Accounts) Rules 2014 exempts certain intermediate wholly owned unlisted subsidiaries from preparing their own consolidated statements; if the target qualifies, the register should say so, because it changes what the target’s own auditor will expect.

What date should the target enter group MIS from?

From the date control passes, which in most Indian share deals is the completion date under the share purchase agreement, not signing. Revenue and costs before that date are pre-acquisition and stay out of the group P&L. The trial balance at the control date becomes the opening position for the target in group MIS, and every subsequent month is measured from it.

Which consolidation method applies to each entity in the register?

The method depends on the relationship and the framework. Subsidiaries are consolidated line by line under both frameworks. Associates are equity accounted under both. Joint ventures are where Indian GAAP and Ind AS diverge: AS 27 requires proportionate consolidation for jointly controlled entities, while Ind AS 111 requires the equity method for joint ventures. An acquirer on Ind AS that buys a target holding a joint venture on AS will see that joint venture move from line items to a single line in group MIS.

Table 2A: Consolidation method by relationship and framework

Relationship	Ind AS treatment	Indian GAAP (AS) treatment	How it shows in group MIS
Subsidiary (control)	Full consolidation, Ind AS 110	Full consolidation, AS 21	Every line, with non-controlling interest separated
Associate (significant influence, usually 20% to 50%)	Equity method, Ind AS 28	Equity method, AS 23	One line: share of profit or loss
Joint venture	Equity method, Ind AS 111	Proportionate consolidation, AS 27	Ind AS: one line. AS: group share of each line
Joint operation (Ind AS only)	Share of assets, liabilities, income and expenses, Ind AS 111	Not separately defined	Group share of each line
Minority stake without influence	Financial asset at fair value, Ind AS 109	Investment at cost less diminution, AS 13	Investment line only; no P&L share

How should non-controlling interest appear in group MIS?

Where the acquirer buys less than 100%, group MIS consolidates 100% of the target’s revenue and costs, then shows the minority holders’ share as a separate line below profit after tax. Ind AS 110 requires profit or loss and each component of other comprehensive income to be attributed to owners of the parent and to non-controlling interests (paragraph B94), and non-controlling interest is presented within equity, separately from the parent’s equity (paragraph 22).

Most boards read EBITDA at 100% and value the stake at the acquirer’s percentage. Group MIS should therefore show both: consolidated EBITDA at 100%, and “EBITDA attributable to the group” as a memo line. Where the share purchase agreement includes a call option over the remaining stake, or the stake steps up in tranches, the register should carry each step date. A step-up after control is an equity transaction under Ind AS 110 (paragraph 23) and does not change the P&L; a step-up that creates control is an acquisition and resets the perimeter.

Opening balances and acquisitions completed mid-month

The control-date trial balance becomes the target’s opening position in group MIS. When completion falls mid-month (say 14/08/2026), the target’s August results must be split into pre-control and post-control portions. Three approaches are used in practice:

1. Hard cut-off close. The target closes its books as at the completion date. This is the most accurate and is usually needed anyway for completion accounts.
2. Time apportionment. August results are apportioned by days. Acceptable for MIS only when revenue and costs accrue evenly, and never for one-off items such as deal bonuses or transaction costs, which must be traced to the right side of the date.
3. Month-end convenience date. Control is treated as 31/08 or 01/08 for MIS, with the stub difference quantified and disclosed. Acceptable only where the stub period is immaterial, and the statutory auditor must agree the same date for year-end consolidation.

Transaction costs need care at this boundary. Advisory, legal and valuation fees on the acquisition are expensed in the acquirer’s books under Ind AS 103 (paragraph 53), and deal bonuses paid by the target to its staff on completion are usually pre-control costs of the target. Both should sit in a separate integration and transaction cost line in MIS so that they do not distort operating EBITDA.

Pro forma comparatives: showing the group as if combined

Statutory consolidation shows the target only from the control date, so year-on-year growth in group MIS looks inflated in the first twelve months. Boards and lenders need a like-for-like view. Group MIS should carry two comparisons for the first four quarters after closing:

• Reported: acquirer standalone in the prior period, group from the control date in the current period.
• Pro forma: acquirer plus target in both periods, with the target’s pre-acquisition history restated on group mapping, group accounting policies and group KPI definitions.

The pro forma view is management information, not a statutory disclosure for an unlisted Indian group, but listed acquirers face SEBI disclosure expectations where acquisitions are material; check the applicable SEBI (Listing Obligations and Disclosure Requirements) Regulations 2015 provisions with the company secretary before publishing pro forma figures externally. Pro forma figures must be labelled as such on every page they appear.

Related reading: Our guide on Ind AS applicability for private companies explains when an acquirer or target moves from AS to Ind AS, which decides the framework column in the entity register.

Chart of accounts mapping: building the group account structure

Chart of accounts mapping assigns every ledger in every entity to one line in a group chart of accounts, with a documented rule for accounts that do not map cleanly. In most Indian acquisitions, the right first move is a mapping layer that sits above unchanged entity ledgers, not an immediate migration of the target to the acquirer’s system.

The target’s ledger is often Tally, with ledgers created ad hoc over years: “Sundry expenses”, “Misc income”, party-wise expense heads, and suspense accounts that carry real balances. The acquirer may be on a cloud ERP with a different account structure. Migrating the target mid-year splits one financial year across two ledgers and two audit trails, which the statutory auditor will then have to test separately.

Mapping layer or immediate ERP migration?

Use a mapping layer for at least the first financial year, and migrate the target’s ledger at the start of a financial year (01/04) once the first group audit is through. A mapping layer gives group MIS from month one; migration gives cleaner data later. Doing both at once usually delays both.

Table 3: Mapping layer vs immediate ERP migration

Factor	Mapping layer first	Immediate migration
Time to first group MIS	4 to 8 weeks (Treelife engagement experience, indicative)	Usually after migration completes
Audit trail continuity	Entity ledger audit trail unbroken	Split across two systems within one year
Risk of data loss	Low; source ledgers untouched	Opening balances and open items must be migrated and tied
Effort per future acquisition	Add one mapping table	Another migration project
Best fit	First 12 months after closing	After first group audit, at start of FY

The design rules that keep a mapping layer stable:

1. Map at ledger level, not group level. Every individual ledger maps to one group account. Mapping Tally groups (such as “Indirect Expenses”) instead of ledgers loses the detail needed for review.
2. Keep the group chart lean. Around 150 to 300 group accounts (practitioner range, not a standard) is usually enough for a mid-size group; more invites inconsistent use, fewer forces manual reclassification every month.
3. Ban catch-all destinations. “Miscellaneous” ledgers in the target are reclassified at source or split by rule; they never map to a group “Other” line above a set threshold.
4. Map the balance sheet as carefully as the P&L. Gateway clearing accounts, GST input and output ledgers, TDS receivable and payable, and gratuity provisions each need their own group account, because they drive working capital and cash in MIS.
5. Flag intercompany ledgers in the mapping. Every ledger that records a balance or transaction with another group entity carries an intercompany flag and a counterparty code, so elimination can run automatically.
6. Version the mapping. Every change carries a date, a reason, the person who made it and the reviewer. This becomes a control in its own right (covered in the controls section).

Getting data out of the target’s ledger every month

A mapping layer is only as good as the monthly extract that feeds it. Agree one extract format per source system in the first month: a ledger-level trial balance with opening balance, debits, credits and closing balance for the month, plus a separate intercompany ledger report. For Tally-run targets, a fixed export template run by the target accountant on the close day works well; retyping balances into the consolidation file does not, because it breaks traceability to the audit trail.

Three checks should run on every extract before mapping: the trial balance sums to zero, the opening balance equals last month’s closing balance in the consolidation file, and no ledger appears that was not in last month’s extract without a mapping entry. The third check is what catches new ledgers created by the target team after closing.

Master data harmonisation: vendors, customers and items

Account mapping makes totals comparable; master data harmonisation makes analysis possible. When the acquirer and target share customers or vendors, each will be recorded under different names and codes. Without a common key (GSTIN works well for Indian counterparties, PAN for those without GST registration), group MIS cannot report customer concentration, top vendor spend or combined receivables ageing by customer.

Build a cross-reference table, not a merged master, in the first year: target code, acquirer code, GSTIN or PAN, and a group customer or vendor ID. Merging masters belongs to the ERP migration later. The cross-reference is also what lets intercompany parties be identified reliably, because each group entity’s GSTIN appears as a counterparty in the other entity’s books.

Choosing the consolidation tool

The tool decision follows the entity count and intercompany volume, not the other way round.

Table 3A: Consolidation tool options for Indian mid-size groups

Option	Fits when	Strength	Main control risk
Controlled spreadsheet	Two or three entities, low intercompany volume	Fast to build, no licence cost	Formula errors, no native change log
Reporting or consolidation add-on over existing ledgers	Three to eight entities on different systems	Keeps entity ledgers, automates mapping and eliminations	Mapping governance moves to a new tool owner
Single group ERP with multi-entity module	After first group audit, entities on one system	Intercompany posted once, eliminations automatic	Migration risk, audit trail split in migration year

Whatever the tool, the same three artefacts must exist outside it: the entity register, the mapping with its change log, and the top-side journal register. A tool change should never mean the loss of these.

Dimensions: where management reporting actually lives

Accounts tell you what was spent; dimensions tell you where and why. Group MIS usually needs at least entity, business unit or product line, geography, and cost centre. The target will have coded some of these inconsistently or not at all. Agree the group dimension list in the first month, map the target’s cost centres and departments to it, and accept that the first two or three months of history may need a one-time allocation rather than transaction-level coding.

Group reporting alignment: policies, calendar, currency and KPI definitions

Group reporting alignment means the same transaction is measured the same way in every entity before numbers are added together. It covers four things: accounting policies, the close calendar, currency translation and KPI definitions. Policy and currency differences can be handled by top-side adjustments; calendar and KPI differences cannot, and must be fixed at source.

Accounting policy alignment in monthly MIS

Ind AS 110 requires uniform accounting policies for like transactions in consolidated statements (paragraph B87); AS 21 has an equivalent requirement for Indian GAAP groups. For monthly MIS, the practical question is which differences to adjust every month and which to leave for year end.

The usual mismatches in Indian acquisitions:

• Revenue recognition: the target recognises subscription or project revenue on invoicing; the acquirer recognises it over time under Ind AS 115. This difference moves monthly revenue materially and must be adjusted every month. Our guide on Ind AS 115 for SaaS and subscription businesses covers the recognition rules.
• Capitalisation: different thresholds for fixed assets, or one entity capitalising product development and the other expensing it.
• Depreciation: written down value (common in Tally-run targets that mirror tax depreciation) against straight line in the acquirer.
• ESOP cost: the acquirer records Ind AS 102 expense monthly; the target may book nothing until year end.
• Provisions: gratuity, leave encashment and bonus accrued monthly in one entity and annually in the other.

Set a materiality threshold for monthly adjustments, and adjust revenue and ESOP every month regardless of size, because both feed KPIs the board tracks.

Close calendar: one group timetable

A group close calendar fixes the working day by which each entity closes, intercompany is confirmed, consolidation runs and the MIS pack is issued. A typical starting point for an Indian mid-size group is entity close by working day 5, intercompany confirmation by working day 6, consolidation by working day 8 and board pack by working day 10 to 12 (practitioner benchmark, adjust to group size). The target’s existing close is often working day 15 or later, with GST filing deadlines driving the timetable rather than reporting needs. Our guide on financial reporting SOP drafting covers how to write the calendar down so it survives staff changes.

Where a foreign subsidiary has a different financial year end, Ind AS 110 allows consolidation using statements as of a date not more than three months from the parent’s reporting date, with adjustments for significant transactions (paragraph B93); AS 21 allows up to six months. For monthly MIS, use calendar-month actuals from every entity regardless of statutory year end.

Currency translation in group MIS

Each entity records transactions in its functional currency under Ind AS 21 (or AS 11 under Indian GAAP); translation into the group presentation currency follows. Statutory translation uses closing rates for assets and liabilities and transaction-date or average rates for income and expenses, with the difference going to a foreign currency translation reserve.

Many acquirers use a single budget rate in MIS so that operating performance is not distorted by currency. That is a legitimate management choice, provided MIS shows a separate FX bridge line reconciling budget-rate results to actual-rate results. Without it, the year-end statutory number will not tie to twelve months of MIS.

KPI definitions: the alignment that breaks most often

Accounting policies are written down; KPI definitions usually are not. The acquirer and target may both report “ARR”, “gross margin”, “active customers” or “headcount”, and mean different things.

Table 4: Common KPI definition conflicts after acquisition

KPI	Typical acquirer definition	Typical target definition	Alignment rule
ARR	Contracted recurring revenue, annualised, excluding one-time fees	Last month’s billing × 12, including implementation fees	Adopt group definition; restate target history for comparatives
Gross margin	Revenue less hosting, payment fees and support staff cost	Revenue less hosting only	Map cost lines to a single cost of revenue group
Headcount	Employees on payroll at month end	Employees plus full-time consultants	Report both lines separately
Active customers	Customers with billing in the last 30 days	Customers with a live contract	Adopt group definition; keep target metric as secondary
EBITDA	Before ESOP cost (adjusted)	After all costs	Show reported and adjusted EBITDA separately

Write a KPI dictionary in the first month: definition, source system, owner and the ledger line it reconciles to. Restate the target’s prior 12 months on the group definition so that growth comparisons are like for like. The earn-out metric, if there is one, follows the share purchase agreement wording exactly and sits outside the KPI dictionary. For how investors expect these metrics to be defined, see our guide on SaaS metrics investors track.

Segment reporting: does the acquisition create a new segment?

An acquisition often adds a business line the board wants to see separately. For MIS, that is a dimension choice. For listed acquirers, and other entities whose debt or equity is traded or in the process of being listed, Ind AS 108 requires operating segment disclosure based on the information the chief operating decision maker reviews. If group MIS starts showing the target as a separate line to the board, that is evidence the auditor will use in deciding whether it is a reportable operating segment. Design the MIS segment view deliberately, and agree it with the auditor before year end rather than letting the board pack set it by default.

Group cash and the consolidated cash flow view

Group MIS that reports only P&L misses what most boards ask first after an acquisition: where the cash is and whether it can move. Each entity’s bank balances, overdraft limits and fixed deposits should roll into a group cash schedule, with intercompany loans and fund transfers eliminated and shown separately.

Three constraints make Indian group cash different from a simple sum:

• Trapped cash. Cash in the target cannot be upstreamed freely. Dividends need distributable profits under Section 123 of the Companies Act 2013, and loans from the target to the acquirer must fit Section 185 and Section 186 limits.
• Foreign subsidiary cash. Cash in an overseas subsidiary is reported in the group total but its repatriation is governed by local law and by FEMA overseas investment rules for the Indian parent.
• Lender restrictions. Facility agreements at entity level often restrict distributions or intercompany lending.

Show group cash in two lines: total consolidated cash, and cash freely available to the parent within 30 days. The difference is usually the number the board did not know it needed.

Group budget, reforecast and integration tracking in MIS

After closing, the group needs one budget to measure group MIS against, and the acquirer’s pre-deal budget plus the target’s own budget is rarely it. The deal model, the target’s budget and the acquirer’s budget were built on different assumptions, mappings and KPI definitions. Group MIS should be measured against a reforecast built on the group chart of accounts, issued within the first quarter after closing.

The reforecast has three layers, and MIS should keep them visible rather than netted:

1. Base business. Each entity’s run-rate plan on group mapping and policies, with no deal effects.
2. Synergies. Revenue and cost synergies from the deal model, each with an owner, a start month and the MIS line where it will appear. A synergy with no MIS line cannot be tracked.
3. Integration costs. One-time costs (systems migration, severance, retention bonuses, rebranding, advisory) in a separate cost centre, so adjusted EBITDA can exclude them cleanly and the board can see spend against the integration budget.

Table 4A: Tracking integration in group MIS

Item	Where it sits in MIS	Measured against	Common distortion if untracked
Cost synergy (e.g., duplicate tools cancelled)	Relevant cost line, tagged with synergy code	Deal model monthly phasing	Savings absorbed by new spend, never visible
Revenue synergy (cross-sell)	Revenue by entity and customer, tagged	Deal model, with customer list	Organic growth counted as synergy
Integration cost	Separate cost centre below EBITDA in adjusted view	Integration budget	One-time spend depresses reported EBITDA with no explanation
Retention bonus to target staff	Integration cost centre, accrued over service period	Retention plan	Lumped into salaries, inflating run-rate cost
Earn-out metric	Separate schedule reconciled to reported EBITDA	Share purchase agreement definition	Disputes with sellers over definitions

Lenders add one more requirement. Where the acquisition was debt funded, the facility agreement usually tests covenants such as net debt to EBITDA and debt service coverage on a consolidated or pro forma basis from the first test date after closing. Compute covenant ratios from group MIS every month, on the exact basis the facility agreement defines, so a likely breach is visible a quarter before the compliance certificate is due. Our guide on rolling budget forecast implementation covers how to keep the reforecast current.

Intercompany elimination: rules that make group MIS reconcile

Intercompany elimination removes transactions and balances between group entities so the group reports only dealings with third parties. Ind AS 110 requires full elimination of intragroup assets, liabilities, income, expenses and cash flows (paragraph B86). In monthly MIS, elimination fails not because the rule is unclear but because the two sides of the same transaction are recorded differently.

New intercompany flows usually start the day after closing: shared services, cost recharges, management fees, loans from the acquirer to fund the target, and transition services from the sellers’ group. Each creates two entries in two ledgers, often on different dates and sometimes in different currencies.

The matching rules that prevent month-end disputes:

1. One counterparty code per entity, used in both ledgers, so that every intercompany ledger can be paired automatically.
2. Invoice-led recording. The supplying entity raises the invoice; the receiving entity books on the same invoice number and date. Supplies between distinct persons under GST are taxable even without consideration (Schedule I, CGST Act 2017), so invoices are needed anyway.
3. A confirmation cut-off. Both entities confirm intercompany balances by a fixed working day; differences above a threshold are resolved before consolidation runs, not after.
4. A single FX rule. Foreign currency intercompany balances are translated at the same rate on both sides for MIS purposes, with the remaining difference shown as an FX line.
5. Unrealised profit. Where one entity sells inventory or capitalised services to another, unrealised profit in closing balances is eliminated. Most service businesses can apply a materiality threshold here.

Intercompany pricing also has a tax side: cross-border recharges are international transactions under the transfer pricing provisions and reported in Form 3CEB, and domestic charges between related parties need approval under Section 188 of the Companies Act 2013 above the prescribed thresholds. These are covered in our note on transfer pricing audit triggers in India and in the post acquisition integration guide linked above. For MIS, the point is narrower: the amount charged in MIS must equal the amount in the intercompany agreement and the tax position, or the difference becomes a reconciling item every month.

Related service: Treelife’s MIS and budgeting team builds group mapping layers, KPI dictionaries and close calendars for multi-entity groups.

Consolidation controls: what auditors will test in the first year

Consolidation controls are the checks that make group MIS reliable: who can change mappings, who posts top-side adjustments, how intercompany differences are cleared, and how every number traces back to an entity ledger. In India, these controls now matter for statutory purposes too, because the audit trail and internal financial control requirements reach the consolidation process, not just entity books.

Does the audit trail rule apply to the consolidation workbook?

Rule 3(1) of the Companies (Accounts) Rules 2014, applicable from 01/04/2023, requires companies to maintain books in accounting software with an audit trail of each change that cannot be disabled. Entity ledgers are clearly covered. A consolidation done in an uncontrolled spreadsheet, where top-side adjustments and mapping changes leave no log, is not itself the books of account, but it is the bridge from those books to the reported numbers, and auditors increasingly ask how changes to it are tracked. The position on spreadsheets used for consolidation is not settled in MCA guidance; treat the consolidation layer as if the rule applied, because the cost of doing so is low and the cost of an audit query is not.

Two related requirements apply. Books and papers, including the edit log, are retained for eight years under Section 128(5) of the Companies Act 2013. Where books are kept electronically, back-ups on servers physically located in India must be maintained daily under Rule 3(5) of the Companies (Accounts) Rules 2014, which matters if the acquirer moves the target to a cloud ERP hosted abroad.

Internal financial controls over consolidation

The statutory auditor reports on the adequacy and operating effectiveness of internal financial controls with reference to financial statements under Section 143(3)(i) of the Companies Act 2013. Private companies with turnover below ₹50 crore and borrowings below ₹25 crore are exempt from this reporting (MCA notification G.S.R. 583(E), 13/06/2017); an acquisition frequently pushes the group above both thresholds in the first year. For listed acquirers, the directors’ responsibility statement under Section 134(5)(e) covers internal financial controls. Under CARO 2020, paragraph 3(xxi), the auditor of consolidated statements reports qualifications or adverse remarks in the CARO reports of included companies, so a weak target close becomes visible at group level.

Table 5: Core consolidation controls after acquisition

Control	What it prevents	Evidence the auditor expects	Frequency
Mapping change approval	Silent reclassification moving margins or EBITDA	Versioned mapping log with maker and reviewer	Every change
Unmapped ledger check	New target ledgers dropping out of group MIS	Exception report showing zero unmapped balances	Monthly
Entity TB to MIS tie-out	Group MIS diverging from entity books	Sum of mapped entity TBs equals pre-elimination group TB	Monthly
Intercompany confirmation	Unbalanced eliminations parked in suspense	Signed confirmations, difference log below threshold	Monthly
Top-side journal approval	Undocumented adjustments at group level	Journal register with support and approver	Every journal
Policy adjustment schedule	Inconsistent monthly treatment of Ind AS differences	Schedule tying each adjustment to a written policy	Monthly
Access control	Unauthorised edits to consolidation model	User access list, review of changes	Quarterly
Perimeter review	Entities added or dropped without approval	Entity register sign-off	Quarterly and on any group change

Segregation of duties in a small finance team

Most Indian acquirers integrating a target have a finance team of three to eight people, which makes classic segregation of duties hard. The minimum workable split: the person who maintains mappings does not post top-side journals; the person who prepares the consolidation does not approve it; and intercompany confirmations are exchanged between entity accountants, not prepared by the consolidator. Where one person must hold two roles, add a detective control, such as a monthly review of the mapping change log by the finance head.

A 100-day plan for MIS consolidation after acquisition

The first 100 days set the structure that group MIS will run on for years. The sequence below assumes a share acquisition of an Indian target with one foreign subsidiary, and an acquirer that wants a board-ready group MIS by the end of the first full quarter.

1. Days 1 to 10: entity register and access. Complete the entity register, confirm the control date, obtain read access to every ledger, freeze the control-date trial balance for each entity.
2. Days 11 to 30: group chart and mapping v1. Agree the group chart of accounts and dimensions, map every ledger, set up the unmapped-ledger exception report, issue the KPI dictionary draft.
3. Days 31 to 45: first shadow consolidation. Run the first month’s consolidation in parallel with each entity’s existing MIS; bridge differences line by line. Do not send it to the board yet.
4. Days 46 to 60: policy, intercompany and reforecast. Write the policy adjustment schedule, sign intercompany agreements, set counterparty codes and the confirmation cut-off, and issue the group reforecast with synergy and integration cost lines.
5. Days 61 to 80: calendar and controls. Publish the group close calendar, implement mapping change approval, top-side journal register and access control.
6. Days 81 to 100: first board-ready group MIS. Issue group MIS with the entity bridge, reported and pro forma comparatives, KPI restatement of target history, FX bridge, group cash schedule, covenant ratios and a one-page control summary. Our guide on board reporting pack preparation covers pack contents and sign-off.

Run the shadow consolidation for at least two months before relying on it. The first run almost always surfaces ledgers that were mapped by name rather than by content.

Common mistakes in MIS consolidation after acquisition

Mistake 1: Mapping Tally groups instead of ledgers. It is faster, and it hides the “Indirect Expenses” ledger that actually contains salary for contract staff. Correct approach: map every ledger, and review the ten largest balances in each group line before sign-off.

Mistake 2: Including pre-control profit in group results. The target’s April to August profit appears in the first group MIS because the full-year TB was loaded. It overstates group EBITDA and will be reversed by the auditor. Correct approach: load the control-date TB as the opening position and report only movements after it.

Mistake 3: Letting intercompany differences sit in suspense. A ₹15 lakh unmatched recharge parked in a group suspense account in month two becomes ₹1 crore of unexplained balances by year end. Correct approach: a hard confirmation cut-off, and no consolidation run until differences above threshold are resolved.

Mistake 4: Reporting target KPIs on legacy definitions. The board sees target ARR growing faster than the group’s, because the target counts implementation fees. Correct approach: one KPI dictionary from month one, with the target’s history restated.

Mistake 5: Running consolidation in an unlogged spreadsheet. It works until the person who built it leaves, or the auditor asks who changed a mapping in month four. Correct approach: version the mapping and keep a top-side journal register from the first run, even if the tool stays a spreadsheet.

MIS consolidation after acquisition succeeds when three layers are built in order: an entity register that fixes the perimeter and control date, a reporting alignment that settles policies, calendar, currency and KPI definitions, and controls that make every group number traceable to an entity ledger. Build the mapping layer first, migrate systems later, and keep the consolidation as auditable as the books underneath it. Done in the first 100 days, MIS consolidation after acquisition gives the board a group view it can trust and gives the statutory auditor a process it can test.

FAQs on MIS consolidation after acquisition

Q: Is MIS consolidation the same as preparing consolidated financial statements?

A: No. MIS consolidation is a monthly management process on group definitions; consolidated financial statements are prepared annually under Section 129(3) of the Companies Act 2013 using Ind AS 110 or AS 21. A well-built MIS layer feeds statutory consolidation through documented top-side adjustments.

Q: Does group MIS change any tax position?

A: Not directly. Income tax is assessed entity by entity, and there is no group tax consolidation in India. Intercompany charges shown in MIS must still match the amounts in transfer pricing documentation and GST invoices, or MIS will diverge from the tax position.

Q: Should the acquirer appoint an outside advisor or build MIS consolidation in-house?

A: In-house if the finance team has built a multi-entity consolidation before; otherwise use an advisor for the first two to three quarters to set the register, mapping and controls, then hand over. The design decisions made in the first 100 days are the expensive ones to reverse.

Q: How long does it take to get a reliable group MIS after closing?

A: Typically 60 to 100 days to the first board-ready group MIS, including at least two months of shadow consolidation. Groups with a foreign subsidiary, a different accounting framework or heavy intercompany flows tend to sit at the upper end.

Q: What documents are needed to start?

A: The executed share purchase agreement (for control date and earn-out definitions), ledger-level trial balances for each entity at the control date and for the prior 12 months, existing charts of accounts and cost centre lists, each entity’s current MIS pack, and any intercompany or transition services agreements.

Q: How are foreign subsidiaries handled in monthly MIS?

A: Translate from the functional currency under Ind AS 21 or AS 11, either at actual rates or at a budget rate with a separate FX bridge line. FEMA reporting for the overseas investment is a separate compliance track and does not change MIS mechanics.

Q: Does a co-founder or promoter-held entity in the group need different treatment?

A: It depends on control. An entity controlled by a promoter rather than the acquirer sits outside the perimeter even if it trades with the group; its transactions are related party transactions under Section 188, shown in MIS as third-party flows and tagged for disclosure.

Q: Does DPIIT startup recognition affect consolidation?

A: No. DPIIT recognition does not change accounting or consolidation requirements. It can be affected by a later merger of the target, which should be reviewed separately before any restructuring.

Q: What if the acquisition is unwound or a target is sold within a year?

A: The entity leaves the perimeter from the date control is lost. Group MIS shows its results up to that date and a gain or loss on disposal; the entity register records the exit date and the mapping is archived, not deleted.

Q: What will a lender or investor in the acquirer look for in group MIS?

A: A reconciliation from entity numbers to the group number, separate lines for one-time integration costs, KPIs on a consistent definition, and covenant ratios computed on the basis the loan agreement specifies (standalone or consolidated).

Q: Can group MIS stay on spreadsheets?

A: Yes, for a small group, if the mapping is versioned, top-side journals are registered and approved, and entity trial balances are imported rather than retyped. Move to a consolidation tool once the group has more than three or four entities or monthly intercompany volumes become hard to match manually.

Q: How should ESOP holders in the target be reflected in group MIS?

A: Through the Ind AS 102 expense on the group’s replacement or continuing awards, accrued monthly, and shown below reported EBITDA in the adjusted EBITDA bridge. Treatment of the awards at the deal itself is covered in the post acquisition integration guide.

Q: What if the target’s auditor and the group auditor are different firms?

A: The group auditor relies on or reviews the target auditor’s work for consolidation. Agree reporting instructions, materiality and the intercompany confirmation format with both before the first year end.

Q: How is an acquisition that completes mid-month handled in group MIS?

A: Close the target’s books at the completion date wherever possible. Time apportionment of the month is acceptable only for evenly accruing items, and deal bonuses or transaction costs must be traced to the correct side of the date.

Q: Should group MIS show 100% of a partly owned target?

A: Yes. Subsidiaries are consolidated at 100%, with the non-controlling interest’s share of profit shown separately under Ind AS 110, paragraph B94. Add a memo line for EBITDA attributable to the group.

Q: Can cash in the acquired company be used to repay acquisition debt?

A: Only through permitted routes. Dividends need distributable profits under Section 123 and loans must fit Sections 185 and 186 of the Companies Act 2013, so group MIS should show freely available cash separately from total cash.

Q: Is the target required to keep its own MIS after joining the group?

A: Not legally, but the target’s board still approves its own financial statements and must be able to explain them. Most groups issue entity-level MIS from the same mapped data, so the target’s view is a filtered version of group MIS rather than a separate pack.

Regulatory references:

• Companies Act 2013: Section 2(87) (subsidiary), Section 128(5) (retention of books), Section 129(3) (consolidated financial statements), Section 134(5)(e) (directors’ responsibility on internal financial controls), Section 143(3)(i) (auditor reporting on internal financial controls), Section 188 (related party transactions)
• Companies (Accounts) Rules 2014: Rule 3(1) (audit trail, from 01/04/2023), Rule 3(5) (daily back-up on servers in India), Rule 6 (exemption from consolidation for certain intermediate subsidiaries)
• MCA notification G.S.R. 583(E) dated 13/06/2017 (exemption from Section 143(3)(i) reporting for certain private companies)