Skip to content
Guide 13 min read Updated

ERP for multi-entity businesses in the UAE: mainland, free zone, VAT groups and consolidation

By Manager & CEO, SmartTech Studio

Very few established businesses in the UAE are a single company. A typical group has a mainland LLC that trades with local customers, a free-zone company that holds stock or intellectual property, perhaps a holding company above them, and increasingly a subsidiary in Oman, Egypt or Saudi Arabia. Each of these is a separate legal person with its own trade licence, its own bank accounts, its own VAT position and its own Corporate Tax obligations.

Most ERP advice is written for one company choosing one system. Our own guide to ERP systems for SMEs in the UAE is that kind of article: which modules you need, which products to shortlist and what it costs. This guide picks up where that one stops. It is for finance directors and owners of groups who already run several companies, or are about to, and who are tired of month-end being a spreadsheet exercise that takes two weeks.

We cover what “multi-entity” actually means for the system, the capabilities to insist on, how VAT groups and Corporate Tax groups should be modelled, how e-invoicing changes the picture, how packaged products compare with a custom build, and a realistic implementation order. SmartTech Studio builds and integrates ERP, CRM and POS systems for groups in the UAE and the region; this is the checklist we use ourselves. It is general information, not tax advice, so confirm your group’s tax treatment with your adviser or the Federal Tax Authority.

What “multi-entity” means for an ERP in the UAE

In ERP terms, an entity is anything that needs its own set of books: its own trial balance, its own balance sheet, its own tax returns and usually its own audit. In the UAE that list is longer than people expect. A mainland company and a free-zone company owned by the same shareholders are two entities, even if they share an office and a warehouse. A branch of a foreign company is usually reported as its own entity. A holding company that only owns shares still needs books. A subsidiary in Muscat or Cairo is an entity with a different currency, a different VAT rate and a different e-invoicing regime.

The opposite mistake is to treat everything that looks different as a separate entity. A second showroom, a second branch of the same LLC in another emirate, or a separate product line is normally a branch, a cost centre or a dimension inside one company, not a new set of books. Creating extra companies in the ERP for these multiplies the work of every month-end for no reason.

So the first design decision is a list: every legal entity, its licence authority, its functional currency, its VAT registration (alone or inside a VAT group), its Corporate Tax position (alone, inside a tax group, or a Qualifying Free Zone Person), and who owns what percentage of whom. That ownership chart drives consolidation and tax grouping, and it is the document an implementation partner should ask for in the first meeting.

Signs your current system has outgrown the group

Groups rarely decide to replace their ERP in the abstract. They notice symptoms, usually in finance first. If several of these sound familiar, the system is the problem, not the team:

Each company runs in a separate copy of the accounting software, or in a separate product altogether, so nobody can see group stock, group cash or group receivables without exporting and pasting. Intercompany invoices are typed twice, once as a sale in one company and again as a purchase in the other, and the two sides never quite agree at month-end. Consolidation is a workbook that one person understands, and the board pack arrives three weeks after the month closes. Customers and items are set up differently in each company, so the same product has three codes and the same customer has four spellings. The VAT return for the group is assembled by hand from several systems. Management fees and shared costs are recharged once a year as a single journal, so monthly entity profits are fiction.

None of these is a crisis on its own. Together they mean the group cannot answer basic questions quickly: what did we sell last month across all companies, how much do we owe ourselves, and which entity is actually making money. With UAE Corporate Tax and e-invoicing both now in force or arriving, the cost of those slow answers has gone up.

The capabilities a multi-entity ERP must have

Almost every ERP vendor will say its product is “multi-company”. That can mean anything from a true group design to the ability to keep several unrelated databases on one server. These are the capabilities that separate the two, and the questions to ask in a demo:

Multi-entity ERP checklist
CapabilityWhat it doesAsk in the demo
Separate ledgers per entityEach legal entity has its own books, tax settings and numberingCan one user post to two companies without logging out and in?
Shared master dataOne customer, supplier and item list used by all entities, with entity-level exceptionsIf we change an item description, does it change in every company?
Automatic intercompanyA sale in one entity creates the matching purchase in the otherShow an intercompany order flowing to the second company without retyping
Consolidation and eliminationsGroup statements with intercompany balances removedRun a consolidated P&L for last month, live, with eliminations
Multi-currencyEntities in AED, OMR, EGP or SAR, translated to the group currencyHow are exchange differences on intercompany balances posted?
Group-aware permissionsUsers see only the entities and data they are allowed toCan a branch accountant see one company but not the holding?
Tax per entity and per groupVAT and Corporate Tax settings that follow the legal structureCan two companies share one VAT return while filing separate accounts?

If a product cannot show the intercompany and consolidation rows live, with your kind of data, treat the claim as unproven. These two are where most “multi-company” systems quietly fall back to spreadsheets.

VAT groups: how the ERP should model them

UAE VAT law lets related companies register together as a tax group. According to the Federal Tax Authority, every member must be a legal person with a place of establishment or a fixed establishment in the UAE, the members must be related parties, and each must make taxable supplies or import relevant goods or services. The group gets one Tax Registration Number, files one return through a representative member, and the members are jointly responsible for the group’s VAT.

The practical consequence for the ERP is that supplies between members of the same VAT group are generally disregarded for VAT. An invoice from the mainland company to the free-zone company inside the same group should not carry output VAT, while the same invoice to a sister company outside the group must. Your system therefore needs to know, for each pair of entities, whether they share a VAT group, and apply the right tax code automatically. Leaving that choice to the person raising the invoice is how VAT errors happen.

The second consequence is reporting. Each company still keeps its own books, but the return is prepared for the group as a whole. A good design lets each entity run its own VAT report for review, then produces the group return by combining members and excluding intra-group lines. If the group later adds or removes a member, the ERP should handle that from a date, not by rewriting history.

Designated zones add a further layer for goods, because some movements of goods in designated free zones are treated differently for VAT. Not every free zone is a designated zone, and the rules are specific, so this is a point to confirm with your tax adviser before the tax codes are configured.

Corporate Tax groups and Qualifying Free Zone Persons

Corporate Tax, introduced by Federal Decree-Law No. 47 of 2022, has its own grouping rules, and they are stricter than VAT. A parent company that is resident in the UAE can form a tax group with resident subsidiaries in which it holds, directly or indirectly, at least 95% of the share capital and the voting rights and is entitled to at least 95% of the profits and net assets. The members must share the same financial year and use the same accounting standards. Exempt persons and Qualifying Free Zone Persons cannot join. The group then files one Corporate Tax return.

Two consequences follow for the system. First, the VAT group and the Corporate Tax group are often different sets of companies. A 60%-owned subsidiary can be in the VAT group as a related party and still be outside the Corporate Tax group. A free-zone company that benefits from the 0% rate on qualifying income as a Qualifying Free Zone Person stays outside the tax group. Your ERP has to record both groupings separately instead of assuming one “group” flag.

Second, a Corporate Tax group needs aggregated financial statements in which transactions between members are eliminated, which is close to what management consolidation already does. If the ERP can produce eliminations by entity and by period, the tax group computation starts from system data rather than a separate workbook. Transfer pricing still applies to dealings with related parties outside the tax group, so intercompany prices and agreements should be stored with the transactions they cover.

The headline rates are 0% on taxable income up to AED 375,000 and 9% above it, with Qualifying Free Zone Persons able to apply 0% to qualifying income. Whether a group is better off inside or outside a tax group depends on losses, free-zone status and the cost of compliance, which is a decision for your tax adviser. The ERP’s job is to make whichever structure you choose cheap to report.

Intercompany transactions and eliminations, done properly

Intercompany work is where a group ERP earns its cost. The common flows in a UAE group are: one entity buys stock centrally and sells it to the trading companies; a free-zone company invoices a mainland company for goods or services; a holding or shared-services company recharges management fees, rent, salaries or IT costs; and one company lends cash to another.

The rule for the system is simple: record each intercompany transaction once and let the ERP create the mirror entry. When the mainland company raises a purchase order on the free-zone company, the free-zone company should receive it as a sales order, with the same items, prices and dates. When it invoices, the purchase invoice should appear in the mainland company’s books, waiting for approval, with the correct VAT treatment for that pair of entities. Both sides then reconcile by design, and month-end becomes a review instead of a hunt.

Recharges deserve their own setup. Allocate shared costs monthly using a rule the auditors and the tax adviser agree with, such as headcount, floor area or revenue, and post the allocation automatically. That gives each entity a true monthly profit and leaves a documented basis for transfer pricing.

On consolidation, the ERP should eliminate intercompany revenue and cost, intercompany receivables and payables, intercompany loans and interest, and unrealised profit on stock that one group company sold to another and that is still on the shelf. Ask to see elimination entries as journals you can audit, not as a black-box total.

Entities in Oman, Egypt and other currencies

Once a group crosses the border, three things change at the same time: the currency, the tax rules and the e-invoicing system. An Omani subsidiary keeps its books in Omani rials and is preparing for the Fawtara e-invoicing programme; we explain that market on our Oman page. An Egyptian subsidiary keeps its books in Egyptian pounds, charges Egypt’s VAT, and must already issue e-invoices and e-receipts through the Egyptian Tax Authority’s systems; see our Egypt page for how that works.

The ERP should let each of these entities run fully in its own currency and its own tax rules, then translate its figures into the group’s reporting currency for consolidation. Intercompany balances between, say, an AED entity and an EGP entity will create exchange differences every month, and the system should post them consistently rather than leaving them for the auditors to find.

Localisation is the other test. A product that is strong in the UAE may have weak or partner-only support for Egyptian or Omani requirements. Before choosing, list the statutory reports and integrations each country needs, and check who in the vendor’s ecosystem actually maintains them.

E-invoicing in a group: one integration, several senders

The UAE’s Electronic Invoicing System adds a new reason to get the group structure right in the ERP. Businesses with revenue of AED 50 million or more go live on 1 January 2027; those below AED 50 million must appoint an Accredited Service Provider by 31 March 2027 and go live on 1 July 2027. The dates, the Peppol model and the penalties are covered in our UAE e-invoicing guide, and you can check your own deadline and penalty exposure with our free e-invoicing calculator.

For a group, the practical points are these. Each invoice is sent as a structured document that carries the seller’s and buyer’s identifiers, so the ERP must hold clean, correct tax and registration data for every entity and every customer. Intercompany invoices between UAE entities are business-to-business invoices too, so the same rules apply to them as to external sales unless guidance says otherwise. And it is usually cheaper to build one integration between the ERP and the provider that every entity uses, than to connect each company separately from different systems.

One point is now settled. Ministerial Decision No. 197 of 2026 excludes transactions between members of the same VAT group from the system for 24 months from 1 January 2027, so the ERP should be able to tell those sales apart from sales to group companies outside the VAT group, which stay in scope. How the revenue threshold applies across a group is a question to settle with your adviser and provider against the Ministry of Finance’s current guidance. The ERP design should not assume an answer; it should be able to send for any entity on its own date.

Design the chart of accounts and master data once

The single most useful decision in a group implementation is a common chart of accounts. Every entity uses the same account numbers for the same things, with entity-specific accounts added only where the law or the business genuinely requires them. Consolidation then becomes a sum, not a mapping exercise, and a finance manager can move between companies without relearning the books.

Use dimensions instead of accounts for the things that cut across entities: branch, department, project, product line, sales channel. That keeps the chart short and lets the group report revenue by channel across all companies with one query.

Treat customers, suppliers and items the same way. One master record per real-world customer or product, owned by a small data team, with entity-level settings such as price lists, payment terms or tax codes where they differ. This is also what makes integration easier later, because the CRM, the POS and the online store all point to the same records. Our article on ERP and CRM integration covers that side in more detail.

Packaged ERP or a custom build for a group?

The main packaged products used in the region all have some form of multi-company support, but they approach it differently. The table below is a general orientation from public product documentation, not a ranking; capabilities change by version and edition, so verify each point in a demo. We compare the wider buy-or-build question in custom versus off-the-shelf ERP in the Gulf.

How common options handle multi-entity groups (verify per version)
OptionMulti-entity approachWatch for
OdooSeveral companies in one database, with shared or company-specific records and inter-company rulesConsolidation depth and localisation vary by edition and partner
Microsoft Dynamics 365 Business CentralSeparate companies in one environment, with intercompany postings and a consolidation featureLarger groups often add reporting tools or extensions
Oracle NetSuite (OneWorld)Designed around subsidiaries, multi-currency and consolidated reportingSubscription cost grows with modules and users
SAP Business OneUsually one database per company, with intercompany and consolidation through add-onsCheck who supplies and supports the group add-ons
Custom buildEntity model, intercompany flows and tax groupings designed around your structureNeeds a clear specification and a partner who will maintain it

In practice many groups end up with a mix: a packaged ledger for core accounting, with custom modules or integrations for the parts that make the group different, such as a central purchasing flow, a franchise or branch model, a POS estate or a specific approval chain. A custom build makes most sense when the intercompany flows are the business itself, for example a distributor that buys centrally in a free zone and sells through several mainland and overseas companies, and no package models that cleanly.

A realistic implementation order for a group

1. Map the structure. The entity list, ownership chart, VAT and Corporate Tax groupings, currencies and licence authorities, signed off by finance and the tax adviser.

2. Agree the common design. Chart of accounts, dimensions, master data ownership, numbering, approval rules and intercompany policies, including how shared costs are allocated.

3. Start with the parent and one trading entity. Prove the ledger, VAT codes, intercompany flow and a first consolidation on real data with two companies before adding the rest.

4. Add the other UAE entities, then the overseas ones. Each new company should take days, not months, because the design is already settled. Overseas entities come last because they add currency and localisation.

5. Connect the operational systems. POS, online store, CRM, payroll and banks, each pointing at the shared master data. Our POS and ERP integration guide covers the retail side.

6. Switch on e-invoicing per entity on its date, then retire the spreadsheets: run one month-end with the old workbook and the new consolidation in parallel, compare, and stop the workbook.

What it costs and how we work

For a packaged product, the cost is a licence or subscription per user plus an implementation partner, and in a group the partner’s days grow with the number of entities, currencies and integrations. For a custom or hybrid build, our ERP, CRM and POS systems start from AED 25,000 excl. VAT for a focused system; a group with several entities, intercompany flows and overseas companies is scoped and quoted after a short discovery, because the structure decides the effort.

SmartTech Studio is a software house in Abu Dhabi. We are not a tax adviser or an auditor, so we work with yours: they decide the tax treatment, and we make the system apply it consistently, produce the reports and connect it to the e-invoicing provider and your other systems. If you are planning a group ERP, start by sending us your entity list and ownership chart; that alone tells both sides most of what the project involves.

FAQ

What is a multi-entity ERP?

It is an ERP that keeps separate books for each legal company in a group while sharing master data, automating intercompany transactions and producing consolidated group reports with intercompany balances eliminated.

Does a mainland and a free-zone company need separate ledgers?

Yes. They are separate legal entities with their own licences, accounts and tax positions, even with the same owners. The ERP should keep a ledger for each and consolidate them for group reporting.

Are the VAT group and the Corporate Tax group the same thing?

No. A VAT group needs related UAE-established companies, while a Corporate Tax group needs at least 95% ownership, the same financial year and the same accounting standards, and excludes Qualifying Free Zone Persons. The two can contain different companies.

Do intercompany invoices need VAT?

Supplies between members of the same VAT group are generally disregarded for VAT. Supplies between group companies that are not in the same VAT group are normally taxed like any other sale. Confirm your case with your tax adviser.

Can one ERP run our UAE, Oman and Egypt companies?

Yes, if it supports each entity’s currency, tax rules and e-invoicing system and translates results into the group currency. Check local support for Egypt and Oman before you choose, as it varies by product and partner.

How much does a multi-entity ERP cost in the UAE?

Custom ERP, CRM and POS systems from SmartTech Studio start from AED 25,000 excl. VAT. A group with several entities, intercompany flows and overseas companies is quoted after a short discovery, since the structure drives the effort.

العربية