If each entity in your group uses a different chart of accounts, your consolidated P&L is fiction — and your intercompany reconciliation will never balance cleanly.
Start here
- Accounting software — where your chart of accounts lives
- Profit & loss — the report that breaks when accounts don’t match
- Trial balance — the first place misalignment shows up
Why this matters in UAE groups
Dubai holding structures commonly operate 3–8 entities: a developer, a contractor, a property manager, a brokerage, a trading company. Each entity might have been set up independently with its own accountant and its own chart of accounts.
The result: “Revenue” means one thing in Entity A and something else in Entity B. Cost categories don’t align. Intercompany transactions map to different account codes on each side. Month-end consolidation becomes a manual spreadsheet exercise.
The standardization approach
- Pick a master chart — choose the most complete entity’s chart as the template. Don’t build from scratch.
- Map every entity’s accounts to the master — create a mapping table: entity account code → master account code. This is the single most important artifact.
- Standardize account naming — use consistent naming conventions. “Revenue - Property Sales” across all entities, not “Property Sales Revenue” in one and “Sales - Properties” in another.
- Lock the master — changes to the master chart require approval. Use your approval policies to enforce this.
- Propagate additions — when a new account is needed, add it to the master first, then propagate to entities that need it.
Intercompany alignment
Intercompany transactions must use matching account pairs. If Entity A books an intercompany receivable to account 1200, Entity B must book the corresponding payable to a mapped account. Without this, your intercompany reconciliation will surface false exceptions.
Define an intercompany account mapping table and enforce it in your ERP setup.
Consolidation reporting
Once accounts are standardized, consolidated reporting becomes a summation problem instead of a translation problem. Your report builder can pull trial balances across entities and roll them up using the master chart.
Review the mapping quarterly. New accounts appear. Entities evolve. The mapping drifts if no one owns it.
Who owns it
Assign a single person — usually the group financial controller — as the owner of the master chart. Entity-level accountants propose changes. The controller approves and propagates. Document changes in your audit logs.