A very common UAE structure looks like this. A mainland company that sells locally. A free zone company that imports, holds stock or handles regional trade. Sometimes a second mainland entity, or a branch in another emirate. Each has its own licence and needs its own books, and the owner wants one clear answer to a simple question: how is the group actually doing?
Most groups answer that question with spreadsheets. This post explains how to run several UAE entities in one ERP properly, keeping their books legally separate while giving the owner a single view, and the one structural decision that most setups get wrong.
Why the Books Must Stay Separate
Separate Licences, Separate Entities
A mainland company and a free zone company are different legal entities, each licensed separately. Their transactions, assets and obligations belong to them individually. Whatever system you use has to respect that separation, not blur it.
Tax Can Treat Them Differently
Corporate tax adds another reason to keep entities cleanly separated. The UAE applies 0 percent on taxable income up to AED 375,000 and 9 percent above it, with specific rules for qualifying free zone businesses.
Related companies can sometimes form a tax group and be treated as a single taxable person, but only if they meet strict conditions. The Federal Tax Authority’s Tax Groups guide sets out 95 percent ownership thresholds, a requirement for the same financial year and accounting standards, and excludes Qualifying Free Zone Persons. Which entities qualify is a question for your tax adviser. The point for your ERP is simpler: each entity’s numbers must be clean and separate enough to support whatever treatment applies.
How Groups Usually Get This Wrong
One Copy of the Software per Company
Each company runs its own separate accounting file. Customers and items are typed into each one separately, sales between the companies are entered twice by hand, and the group view is assembled in Excel at month end. It works, slowly, until the two sides of an internal sale stop matching.
Everything in One Set of Books
The opposite mistake is worse. All companies run in one set of books, with “departments” or “divisions” used to tell them apart. It looks tidy, but it mixes legal entities that are meant to be kept apart, and separating them later for an audit or a tax return becomes painful.
Consolidation by Copy and Paste
Even groups with separate books often build the group picture by exporting reports and adding them together. Internal sales between the companies get counted as if they were real revenue, which overstates how the group is actually performing.
How a Multi-Company ERP Handles It
One System, Several Companies
ERPNext is built for this. A single installation can hold multiple companies, each with its own chart of accounts and base currency, organised under a parent group company if you want one. Each company produces its own trial balance, profit and loss and balance sheet, exactly as if it had its own system.
Shared Masters, Separate Books
What the companies share is the master data. A customer who buys from both your mainland and free zone companies exists once, not twice. The same goes for items. That alone removes a surprising amount of duplicate typing and mismatched names.
Different Currencies Where Needed
If your free zone company trades mainly in US dollars, it can keep its own base currency while the mainland company runs in dirhams. ERPNext’s multi-currency accounting handles transactions in other currencies inside each company.
Trading Between Your Own Companies
Inter-Company Invoices
The most common link between group companies is internal trade: the free zone company imports stock and sells it on to the mainland company. ERPNext supports inter-company invoices. Once the internal customer and supplier are set up to represent each company, a submitted sales invoice in one company can create the matching purchase invoice in the other.
One Direction Only
ERPNext’s own guidance contains a rule worth remembering: choose one direction for each transaction, and do not create both sides independently, or the same trade gets recorded twice. Decide early which company raises internal documents, and stick to it.
Loans and Recharges
Not every internal movement is a sale. Shared rent, salaries paid by one company for staff working for another, or a loan from the parent can be recorded with inter-company journal entries, keeping both companies’ balances in step.
The Decision Most Setups Get Wrong: Company or Branch?
A Company in the ERP Should Mean a Legal Entity
Not every location deserves its own company in the system. A separate company should represent a separate legal entity, with its own licence and its own books.
Branches Belong Inside the Company
A second showroom, a warehouse in another emirate or a regional sales office that belongs to the same legal entity is a branch, not a company. Branch performance is better tracked inside that company using cost centres or accounting dimensions, so each branch gets its own profit picture without splitting the books of a single entity.
Getting this wrong in either direction causes trouble. Too many companies means unnecessary inter-company paperwork. Too few means entities that should be separate end up mixed together.
Who Sees What
Restricting Staff to Their Own Company
Staff at the free zone company usually should not see the mainland company’s payroll or margins. ERPNext’s user permissions can restrict a user to the data of a specific company, so each team works in its own entity while the owner and finance team see everything.
Getting the Group View Right
Separate Results, One Picture
With every company in one system, the owner can review each entity’s results and the group’s position together, without collecting spreadsheets from each team.
Remove Internal Trade From Group Totals
For a true group picture, sales and balances between your own companies must be removed, otherwise internal trade inflates group revenue. This is where consistent inter-company recording pays off: when both sides of every internal transaction were created properly, they can be identified and eliminated cleanly.
Month-End in a Group
Close each company in the same order every month, and reconcile the inter-company balances before anything else. What the free zone company says the mainland company owes it should exactly mirror what the mainland company says it owes. If the two sides disagree, the group view is wrong until they match. Catching a mismatch in the month it happens takes minutes. Finding it at year-end, across twelve months of internal trade, can take days.
Setting It Up Without Regret
Map the Structure Before Touching the System
List every legal entity, its licence, its base currency, its financial year and which entities trade with each other. Then list every branch and decide which company it belongs to. This one page shapes everything else.
Clean the Shared Masters First
Because customers and items are shared, duplicates in one company’s old data become duplicates for the whole group. Clean them before migrating, as we explain in ERPNext data migration.
Budget for Each Entity
The number of entities affects implementation effort, as we cover in what ERP software costs in Dubai. Each company needs its own setup, opening balances and testing. If you are still comparing platforms, our ERPNext vs Odoo comparison looks at how each handles group structures.
The Bottom Line
Running a mainland company, a free zone company and perhaps a branch or two is normal in the UAE. Running them from separate spreadsheets, or worse, from one mixed set of books, is what makes group reporting slow and unreliable.
A multi-company ERP keeps each entity’s books legally separate, shares the customers and items they have in common, links internal trade on both sides automatically, and gives the owner the group view without a spreadsheet. The setup starts with one honest decision for every location: separate company, or branch.
If you run more than one UAE entity and want to see how your structure would look in ERPNext, our ERP Solutions team can map it with you and walk through it in a live demo. You can also browse our case studies to see the kind of work we do.
WhatsApp Fadil or call +971 56 544 6259 for a free consultation.
Separate companies need separate books. They do not need separate systems.
