In short
Multi-entity accounting means keeping a separate set of books for each legal company, in one system, and combining them into a group view when you need it. A group with a UAE company and a Saudi subsidiary, for example, has to keep AED and SAR books apart, apply 5% and 15% VAT, print different registrations on documents and still give the owner one set of numbers. The hard parts are consolidation across currencies and trade between your own companies, so plan both from day one.
What is multi-entity accounting?
Multi-entity accounting is running the books of several legal entities in one system. Each entity keeps its own ledger, currency, tax registrations and accounting periods, because each one files its own returns. The system shares what can safely be shared, such as the chart of accounts structure, customers and items, and combines the ledgers through financial consolidation when management or the bank asks for group figures.
It’s different from running branches. A branch shares its company’s books; a Saudi subsidiary of a UAE company is a separate legal person with its own commercial registration, VAT number and statutory accounts. The multi-entity approach respects that separation without two unconnected systems.
Why is a two-country group harder than two separate companies?
Each company follows its own country’s rules, and the group view has to bridge them. For a UAE company and a Saudi subsidiary, these differences affect daily accounting most.
| UAE company | Saudi company | |
|---|---|---|
| Functional currency | UAE dirham (AED) | Saudi riyal (SAR) |
| Standard VAT rate | 5% | 15% |
| Key registrations on documents | VAT TRN, trade licence, corporate tax TRN | Commercial registration (CR), VAT number, unified number |
| Address format | Emirate, area, PO box | Saudi national address (building number, street, district, postal code, additional number) |
| Invoice language | English is accepted; the tax authority can ask for an Arabic translation | Tax invoice details must be in Arabic, with other languages allowed alongside |
| E-invoicing | Mandatory in phases from 1 January 2027, through Accredited Service Providers | ZATCA e-invoicing; Phase 2 integration rolling out in waves, the latest due by 1 February 2027 |
| Direct tax | UAE corporate tax | Zakat and income tax, depending on ownership |
None of this is unusual on its own. The work is doing all of it every month without mixing the two companies up.
Separate systems or one multi-entity system?
You can run each company in its own system, or both in one system with separate books. Both work; they suit different groups.
| Separate systems | One multi-entity system | |
|---|---|---|
| Setup | Each company configured on its own | One setup, with country-specific settings per entity |
| Customers, suppliers and items | Maintained twice, often with different codes | Shared where sensible, so codes match across the group |
| Group figures | Exported from both, combined in a spreadsheet | Combined in one consolidation run |
| Exchange rates | Entered and applied by hand in the spreadsheet | One rate table, applied consistently |
| Access | Separate logins; hard to see across companies | One login, limited to the entities each person works in |
| Risk of posting to the wrong company | Low, because the systems are separate | Real, unless the system always shows which entity you’re in |
| Best for | Unrelated businesses under one owner | Companies that share customers, suppliers, stock or management |
If your companies share products, customers or suppliers, or one buys from the other, one system usually saves more than it costs.
What should “one system” mean in practice?
A multi-entity system should keep entities separate by default and combine them only on purpose. Check for each of these:
- Separate books per entity: own journals, periods and opening balances, on a shared chart of accounts structure.
- Per-entity settings: functional currency, time zone, fiscal year, tax codes, document numbering and costing method.
- Per-entity identity on documents: legal name (including Arabic, where needed), registrations, address, letterhead, bank details and signatory.
- Warehouses that belong to an entity, so stock is valued in the right company’s currency.
- A visible entity indicator on every screen, and access by entity, so a Riyadh accountant works in the Saudi books without seeing the UAE ones.
- Consolidation into a group currency, with the translation method shown, not hidden.
- A clear intercompany method for trade and loans between your own companies.
How does consolidation work across AED and SAR?
Consolidation translates each entity’s ledger into one group currency, then adds them up. The common method, used in IFRS-style reporting, works like this:
- Income and expenses are translated at the period’s average exchange rate.
- Assets and liabilities are translated at the closing rate on the last day of the period.
- The difference created by using two rates is shown as a currency translation difference, rather than buried in profit.
The AED and SAR are both pegged to the US dollar (AED 3.6725 and SAR 3.75 to USD 1), so the rate between them barely moves. Translation differences between a UAE and a Saudi company are therefore usually small. They grow when the group currency floats against both, for example if you report in EUR or GBP, or when you add an entity with a floating currency such as INR.
Two more decisions matter. Close each entity’s month before the group close, so you don’t consolidate numbers that will still change. And if a subsidiary isn’t wholly owned, statutory group accounts need a minority (non-controlling) interest.
Intercompany: plan it before your companies trade with each other
Intercompany transactions are sales, recharges and loans between companies in the same group. They’re real for each company, but they cancel out for the group as a whole. Intercompany elimination removes them on consolidation, so the group doesn’t report revenue it earned from itself.
Elimination only works when both sides agree. Common problems:
- Timing: the UAE company invoices on 30 September; the Saudi company books it on 2 October.
- Currency: the invoice is in AED, but the Saudi company records it in SAR at a different rate.
- Missing tags: nothing on the transaction says which group company is on the other side.
Rules that prevent most mismatches:
- Use dedicated intercompany receivable, payable, revenue and cost accounts.
- Record the counterparty company on every intercompany transaction.
- Agree a month-end cut-off and confirm balances between companies before closing.
- Settle intercompany balances regularly rather than letting them build up.
- Document pricing between companies; both countries have transfer pricing rules for related parties, so agree the approach with your tax adviser.
How does 1flux handle companies in two countries?
1flux runs several legal entities in one workspace, each with its own books. Legal entities can be registered in the UAE, Saudi Arabia and India.
A setup checklist for a two-country group
Tick items as you go; your progress stays in this browser.
Two-country group setup
For the wider regional picture, read about running 1flux in Saudi Arabia.
Related solution
1flux for business groups and holding companies
Separate books per company, entity-level access and a consolidated view across the group.