Multi-Entity, Multi-Country: When One Company Isn't Really One Company | ERP for Beginners S2 Ep5

Season Two of ERP for Beginners, episode five. Every ERP demo you'll ever see starts with one company, one chart of accounts, one currency, one P&L at the bottom of the page. Every real enterprise looks almost nothing like that. Real companies are groups of companies — a parent at the top, subsidiaries scattered across countries, each its own legal entity with its own books, its own bank accounts, its own tax authority, its own regulator. The ERP has to hold all of that together and still, at the end of the quarter, produce one consolidated set of numbers that tells the parent how the whole group did. This episode is a vendor-neutral, plain-English tour of that complexity. Why one company is usually fifteen legal entities. The three-currency rule on every transaction. Why the German version of SAP looks different from the US one. Why intercompany reconciliation is where every month-end close goes to die. And the three-step consolidation engine that pulls it all back into one group P&L. What You'll Learn: - Why one group is usually ten to two hundred legal entities, and the mundane reasons for that structure - Group chart of accounts versus local charts, and why the mapping is one of the highest-leverage decisions in any implementation - The three-currency rule — transaction, local, group — and the FX gain/loss account that catches the drift - The tax regime zoo — VAT in Europe, sales tax in the US, GST in India, withholding everywhere — and why each needs a different ERP treatment - Localisations — how ERP vendors ship country-specific packs of configuration, fields, and statutory reports - Intercompany — why sub-to-sub transactions have to net to zero at the group level, and why reconciling them breaks every close - Consolidation — the three-step translate / aggregate / eliminate engine that produces the consolidated financials - Why multi-entity is the last track to stabilise on every ERP program, and the one that separates strategic from technical decisions Timestamps: 0:00 - Intro — when one company isn't one company 0:20 - What's in this episode 0:48 - One group, many legal entities 1:53 - Chart of accounts — group plus local 2:48 - Three currency layers at once 3:58 - Tax regimes — VAT, GST, sales tax, withholding 5:08 - Localisations — the same invoice, three countries 6:03 - Intercompany — the painful bit 7:08 - Consolidation — translate, aggregate, eliminate 8:08 - Why this is the hardest thing in ERP 8:53 - Why this matters — the senior-decision lens 9:38 - Recap — multi-entity in five points 10:26 - Coming next — the Season 2 finale Key Takeaways: 1. One group is usually many legal entities. A parent holding company plus ten to two hundred separately incorporated businesses, each with its own books, bank accounts, and tax authority. 2. Chart-of-accounts mapping is a make-or-break decision. Every local chart maps to one group chart. Done well, consolidation is mechanical. Done badly, it's a perpetual spreadsheet problem. 3. Every transaction carries three currencies at once. Transaction, local, group — three rates, three rounding paths, and one dedicated FX gain/loss account to catch the drift. 4. Tax regimes need localisations. VAT, GST, sales tax, and withholding each ship as country-specific packs — fields, forms, and statutory reports. That's why the German ERP screen looks different from the US one. 5. Consolidation is translate, aggregate, eliminate. Translate every entity's balances to group currency, aggregate into group-chart accounts, eliminate intercompany transactions and parent-subsidiary investments. One group P&L comes out. The senior lens — the moment a company has a second legal entity or a second country, this whole complexity stack starts to apply. Finance directors, controllers, and CIOs use this lens to turn ERP decisions from technical into strategic ones. Taught by CelesteAI. Like and subscribe to catch the Season 2 finale.