Multi-Entity and Multi-Currency Consolidation

One group, several sets of books, no group numbers

Zoho Books is organised per legal entity. That is correct — a UAE company, a Saudi company and an Indian company each need their own organisation, their own chart of accounts, their own tax registration and their own filing. The problem appears the moment the board asks what the group earned last quarter.

There is no consolidated P&L across organisations. There is no automatic elimination of the management fee the UAE entity charged the Indian one, so group revenue is overstated by the amount of internal trade. There is no group balance sheet, so the intercompany receivable in one set of books sits opposite a payable in another and nobody nets them. And because each entity keeps its books in its own functional currency, translating everything to a single reporting currency means picking rates — closing rate for the balance sheet, average rate for the P&L, historical rate for equity — and doing it consistently every period.

So it goes into a spreadsheet. Someone exports trial balances at month end, maps accounts by hand because the charts of accounts drifted apart years ago, types in the rates, remembers most of the eliminations, and produces a group pack four working days after everyone wanted it. Next month a new account appears in one entity and quietly falls out of the mapping.

What ECOSIRE builds for you

ECOSIRE builds a consolidation and group reporting layer over your existing Zoho Books organisations. It reads from each organisation through the Zoho Books REST API using an authorised connection per entity, stores the mapped and translated figures in a Zoho Creator application, and presents group reports through Zoho Analytics or Creator dashboards. Your entity books are never written to — consolidation is read-only against source, which is what makes it safe to run every day rather than once a quarter.

A group chart of accounts everyone maps to

We build a group account structure and a mapping table from each entity's chart of accounts to it. Mapping is maintained by your team, and unmapped accounts are surfaced loudly rather than silently dropped — a new expense account created in the Saudi entity appears on an exceptions list before it can distort a group report.

Currency translation with the right rate on the right line

Each entity's functional currency is translated to the group reporting currency using the method you specify: closing rate for balance sheet items, period-average for P&L, historical rate for share capital and other equity components. The resulting translation difference is posted to a currency translation reserve line so the group balance sheet actually balances rather than being forced. Rates are stored per period with their source, so a restated report reproduces exactly.

Intercompany identification and elimination

Intercompany transactions are identified by counterparty entity tagging on customers, vendors and accounts. The engine pairs intercompany sales against intercompany purchases and intercompany receivables against payables, then generates elimination entries at group level. Where the two sides do not agree — different amounts, different periods, a missing document — you get an intercompany mismatch report naming both entities, both documents and the difference, which is the item your auditor will ask about anyway.

FX revaluation on foreign-currency balances

Open foreign-currency receivables, payables, bank balances and intercompany loans are revalued at period-end rates, with realised and unrealised gain or loss reported separately per entity and at group level. You get the workings, not just the number.

Ownership, minority interest and part-period entities

The consolidation respects ownership percentages, so partially owned subsidiaries consolidate with a non-controlling interest line rather than being included at one hundred percent or excluded entirely. Entities acquired or disposed of mid-year consolidate from or to the correct date.

The reports the group actually needs

Consolidated P&L, balance sheet and cash position; the same statements per entity in both local and group currency; entity-versus-entity comparatives; the elimination schedule; the intercompany mismatch report; the FX revaluation workings; and a drill path from any group figure back to the contributing entity balances and, where your permissions allow, to the source documents in Zoho Books.

Who this is for

Groups running two or more Zoho Books organisations — typically a holding company with operating entities across the UAE, Saudi Arabia, India, Pakistan, the UK or elsewhere; family groups with several trading companies; and businesses that have set up a free-zone entity, a mainland entity and an offshore entity and now need one set of numbers. It is equally relevant to any group whose auditor has started asking for consolidated statements with documented eliminations.

How delivery works

1. Scoping call. We list your organisations, their functional currencies, their charts of accounts and how far apart those charts have drifted, your ownership structure, the volume and nature of intercompany trade, your reporting currency, your period-end calendar, and which Zoho Books plan each entity is on. We ask to see your current consolidation spreadsheet — it is the most accurate specification of what you need.

2. Fixed quote and specification. You receive the group account structure, the mapping approach, the translation method per statement line, the elimination rules, the report list and a fixed price with a delivery window. one working week from sign-off is typical; groups with many entities, heavy intercompany trade or minority interests sit at the longer end.

3. Build. ECOSIRE develops the Zoho Books API connections per organisation, the group chart and mapping tables, the translation and elimination engine in Deluge, the Creator application, and the Analytics or Creator reporting layer.

4. Install in test. We connect to your organisations in read-only mode and reproduce a period you have already closed and signed off. You compare our consolidated output line by line against your existing spreadsheet pack. Differences get resolved before go-live, and in our experience the exercise usually finds something in the spreadsheet too.

5. Production go-live. We move to your live reporting cadence, run the first close with your finance team present, and hand over the mapping and rate maintenance.

6. Support. A support window covers the first close cycles. Account mappings, entity additions, rates and ownership percentages are maintained by your team afterwards in the Creator app.

Honest scope notes

This is a build-to-order engagement — we build it against your group's structure after a fixed quote and install it into your Zoho environment. It is a reporting and consolidation layer: it reads from your Zoho Books organisations and does not post entries back into them, so your statutory books stay exactly as your accountants left them. It produces consolidated management and reporting output; whether that output is used as the basis for statutory group accounts, and under which reporting framework, is a decision for you and your auditor. What is achievable depends on each entity's Zoho Books plan and API allowance, and on how consistently intercompany transactions are tagged at source — where tagging is weak we build the tagging discipline into the scope rather than pretending the eliminations will find themselves.