Chart of accounts mapping is the work of aligning every account an acquired company uses to the accounts your group reports on, so two sets of books can be added together and actually mean something. It is unglamorous, low-status work. And it is the part of buying a company that quietly decides whether your first consolidated month-end takes an afternoon or a fortnight. Every acquisition creates the problem, because no two companies keep their books the same way, and someone has to reconcile that difference before the group numbers can be trusted.
This piece is for finance leaders and operators at companies that have started acquiring. If you have just closed your first deal, or you are about to, chart of accounts mapping is one of the first practical jobs that lands on the finance team, and how you handle it sets the pattern for every deal after. Here is what the work actually involves, the decision that matters most (map their chart, or replace it), a phased process that keeps reporting live without locking in future pain, and the trap that catches serial acquirers who skip the second half.
What is chart of accounts mapping after an acquisition? Chart of accounts mapping is the process of connecting each account in one company's chart to the matching account in another, so financial data can be standardized, consolidated, and reported accurately (insightsoftware ). After an acquisition it has a specific job. The company you bought arrives with its own account numbers, its own names, and its own structure, and very little of it lines up with yours. Mapping is the translation table that says “their account 4100, Trading Income, is our account 6000, Revenue,” line by line, until every figure the subsidiary produces can be rolled into the group view.
The important thing to understand is that mapping is not a one-time setup if you let the acquired company keep its own chart. It becomes a recurring step at every close: each period, the subsidiary's trial balance has to be run through the mapping before its numbers can join the consolidation. That is fine for a while, and it is often the right first move. It only turns into a problem when the mapping table is never retired and the count of them grows with every deal. More on that below.
Why does every acquisition create a chart of accounts problem? Because two companies almost never keep their books the same way, and the differences run deeper than account names. Acquired businesses use different segment lengths, different numbering logic, regional or product sub-accounts that have no equivalent in your chart, and a level of detail that is either far coarser or far finer than yours. None of that is wrong; it reflects how that business chose to run. It just means the two charts cannot be added together until someone builds the bridge.
Mapping the account names is only the visible layer. Underneath it sits a deeper alignment job that the accounting standards actually require. Under IFRS 3, an acquirer is expected to review the consistency of the acquired subsidiary's accounting policies and estimates with the parent's, covering things like revenue recognition, inventory valuation, and depreciation methods, and to bring the subsidiary's reporting period into line (Grant Thornton ).
So a clean map is not just “account X equals account Y.” It is “account X, measured their way, equals account Y, measured our way.” That is why the first consolidated close after a deal so often surfaces surprises that have nothing to do with the spreadsheet, and everything to do with two finance teams having quietly done the same thing differently for years.
Should you map the acquired company's chart, or standardize it onto your group chart? It depends on how often you acquire and how deeply you integrate. There are two broad approaches, and most acquisitive companies end up using both over the life of a deal: map on day one to get reporting working, then standardize later once the dust has settled. The question is rarely “which one forever” and more “how long do we run the mapping before we commit to the group chart.”
Deloitte frames the underlying choice as a single global chart of accounts versus multiple local charts: a global chart means streamlined consolidation and consistency, while different charts per entity increase consolidation complexity (Deloitte ).
AccountingTools lays out the practical middle ground for groups that cannot impose one chart overnight: require subsidiaries to notify the parent before they create any new account, require them to map their results to the group chart before month-end, or install a centralized accounting system that every entity uses (AccountingTools ). The three options trade speed against control.
Comparison table, build manually in Webflow: select the code below, copy it, delete this block, add an HTML Embed here, and paste.
<style>.cmp{width:100%;border-collapse:collapse;font-size:15px;line-height:1.45;color:#334155}.cmp th,.cmp td{padding:10px 12px;text-align:left;vertical-align:top;border-top:1px solid #E2E8F0}.cmp thead th{background:#F1F5F9;color:#0F172A;font-weight:600}.cmp tbody tr:nth-child(even){background:#F8FAFC}.cmp tbody th{font-weight:600;color:#0F172A}</style>
There is no universally right answer. A company doing one bolt-on every couple of years should usually standardize quickly and avoid carrying maps at all. A company buying four businesses a year needs the mapping approach to keep reporting alive, then a disciplined plan to retire each map on a schedule.
How do you map a chart of accounts after an acquisition, step by step? A phased approach works best: map first to get reporting live, rationalize the acquired chart toward your group standard within the first few months, then migrate the entity onto your group system and retire the mapping table once the deal is fully integrated. Treating it as three deliberate phases (rather than one heroic project) is what keeps the monthly close running while the deeper work happens in the background.
Phase 1: build the translation table Map every active account in the acquired company's trial balance to a group account before your first consolidated close. Start from the accounts that carry real balances, not the full chart; most subsidiaries use a fraction of the accounts they have defined.
Decide how to handle one-to-many cases (their three travel accounts collapse into your one) and many-to-one cases (their single “Other income” needs splitting), and write down the policy alignment decisions from the IFRS 3 review so the map reflects how the numbers are measured, not just where they sit. The output is a documented table, owned by a named person, that produces a group-ready trial balance every period.
Phase 2: rationalize toward the group standard Once reporting is live, start reshaping the acquired chart so it needs less translation, and ideally none. This is the phase most teams skip, and it is the one that pays off. Most groups aim to complete this rationalization within roughly 90 to 180 days of the acquisition (multi-entity COA guidance ), while the deal is fresh and the acquired team still expects change.
Retire accounts with no equivalent, adopt the group's numbering and naming, and close the gaps the mapping table was papering over. This is part of broader post-acquisition financial integration , and it goes far more smoothly inside the first quarter than it ever does a year later.
Phase 3: migrate onto the group system and retire the map When the acquired entity is fully integrated, move it onto your group ledger with the standardized chart and switch the mapping table off. At that point the translation step disappears, the entity transacts directly in group accounts, and a whole category of monthly work and risk goes with it. This is usually the last step of ERP consolidation after a merger , and not every deal needs to reach it; a small, stable subsidiary on a clean standardized chart can sit on its own ledger indefinitely. But the option to retire the map should be a decision, not something you forget to make.
What is “chart debt,” and why does the mapping table become a trap? Chart debt is the accumulated complexity of leaving mapping tables in place permanently, deal after deal, until no one fully understands the web of translations the group depends on. It is the single most common source of long-term pain for serial acquirers, and it builds quietly. Each deal adds another map. Each map needs maintaining. Every time any subsidiary creates a new account, someone has to remember to map it, and the close that nobody mapped it in is the close where the consolidation silently goes wrong.
The mapping approach is the right first move; the mistake is treating “first move” as “permanent state.” A map is meant to be a bridge, not a building. The mitigation is mostly discipline: require each subsidiary to notify the group before creating any new account, so the map is updated before the books close rather than after they break (AccountingTools ), and put a target date on retiring every map you create.
In the consolidation work we do, the mapping table is reliably where the most month-end time disappears and where the hardest-to-find errors hide, especially when the map lives in a consolidation spreadsheet with no validation behind it. That is exactly why getting multi-entity consolidation right means planning the map's retirement from the day you build it.
What makes a group chart of accounts easy to map into? A group chart that is standardized enough to consolidate automatically but flexible enough for genuinely different businesses to record their activity accurately. The whole mapping job gets easier when the target chart is well designed, so it is worth getting the group chart right before you have several subsidiaries pointing at it.
A few principles do most of the work:
Use consistent numbering ranges across the group. A predictable structure (for example, current assets in one band, income in another, expenses in another) means an account's number tells you what it is anywhere in the group, which makes every future map faster to build (emfino ).Reserve dedicated ranges for intercompany accounts. Keeping intercompany activity in its own clearly marked accounts is what makes eliminations clean and unambiguous, instead of buried inside ordinary trade accounts where they are easy to miss.Use dimensions, not new accounts, for reporting detail. As Deloitte puts it, “if the value of a segment can be derived from another, then it should not be a unique segment” (Deloitte ). Slice by entity, department, or location with dimensions rather than minting a new account for every combination, and the chart stays small enough to manage.Keep the account count sane. Mid-market groups generally function well with a few hundred group-level accounts rather than thousands; multi-entity design guidance points at roughly 300 to 600 as a workable range (multi-entity COA guidance ). A leaner chart is easier to map into and far easier to keep clean as you add entities.Where chart of accounts mapping fits in consolidated reporting Chart of accounts mapping is the foundation the entire group view sits on, which is why it is the first thing to get right and the easiest thing to underestimate. Every consolidated number (group revenue, adjusted EBITDA, cash, leverage) is only as trustworthy as the map that brought each subsidiary's figures into a common language. Get the map right and consolidation becomes routine; leave it shaky and every report carries a quiet asterisk.
This is the layer we build for companies growing through acquisition. At PMI Stack, consolidated financial reporting starts by normalizing each acquired company's chart of accounts to a group chart and reporting currency in the data transformation layer, working with a fractional-CFO partner who owns the accounting judgment. The dashboard and its AI assistant then read one consistent, traceable set of numbers rather than a pile of differently shaped trial balances.
We treat the financial core (a single, reliable group view of P&L, balance sheet, and cash) as the part to get right first. Operational and CRM reporting is genuinely valuable, but it depends on each company's systems, so it is scoped business by business rather than promised as one universal switch.
Whether that group view is best served by a consolidation tool or a bespoke reporting layer over your existing ledgers depends on your stack, and either way the mapping has to be solid underneath it. If you would rather have the whole layer built for you, that is what we do .
Getting chart of accounts mapping right as you keep acquiring Chart of accounts mapping is unavoidable the moment you own more than one company, and it is not a sign anything went wrong. It is simply the bridge between how the business you bought kept its books and how your group needs to read them.
The teams that stay sane through a buying spree are the ones that treat the map as a deliberate, temporary tool: build it carefully before the first close, rationalize the acquired chart while the deal is still fresh, and put a retirement date on every map so chart debt never has a chance to compound. Do that, and the group numbers stay trustworthy no matter how many deals you add. Skip the second half, and the mapping table you built to solve the problem slowly becomes the problem.
By Dylan Harrocks , Founder of PMI Stack, which builds consolidated reporting for companies growing through acquisition. Published 26 June 2026.
