Running several companies from one ERP login

It is common in Saudi Arabia, the Gulf and Egypt for one owner or family group to run a trading company, a small factory and a restaurant at the same time. Each is a separate legal entity with its own commercial registration, VAT number and bank accounts. Yet many owners end up with three systems, three logins and three sets of reports that never line up.

A multi-company ERP solves this. You sign in once and switch between companies the way you switch tabs, while each company keeps its own books. This guide explains what real separation means, what should be shared, how branches fit in, and how to set things up so your accountant and auditor are both comfortable.

What is a multi-company ERP?

A multi-company ERP is one system that holds several legally separate companies, each with its own books, stock, staff and tax, accessed through a single login. It is different from running several copies of the same software, and different from one company with a "department" filter.

The test is simple: could you hand one company's trial balance, VAT return and payroll to its auditor without touching the others? If yes, the separation is real. If you would need to filter, export and clean up first, it is not.

Why owners end up with too many systems

Most groups do not plan to have several systems; they collect them one company at a time. The pattern usually looks like this:

The first company buys an accounting package.
The second company is started by a different manager who picks a different tool.
The restaurant needs a point of sale, which comes with its own back office.
HR and payroll live in spreadsheets because none of the tools covers them well.

The result is that the owner sees the group only once a month, after someone copies figures from each system into a spreadsheet. Decisions are made on numbers that are already weeks old.

Signs you need it

You copy figures from several systems into one spreadsheet every month.
Your accountant re-keys invoices between your own companies.
Staff share logins because adding users to another system is a hassle.
You cannot answer "how did the group do last week?" without waiting for someone.

What "separate" has to mean

Running several companies in one system only works if the separation is enforced by the system, not by people being careful. At a minimum, check for:

Separate books. Each company has its own chart of accounts, fiscal years, journal entries and opening balances.
Separate stock. Warehouses and items belong to one company, so moving goods between companies is a sale and a purchase, not a simple stock transfer.
Separate staff and payroll. Employees, contracts, salaries and end-of-service obligations are recorded under the company that employs them.
Separate tax. Each company files its own VAT return and issues invoices under its own VAT number. In Saudi Arabia, each company also needs its own e-invoicing setup; see our ZATCA Phase 2 guide.
Separate documents. Invoices, statements and payslips print with the right company name, logo and registration details.

If a system cannot guarantee these, it is a shared database with a company filter, and your accountant will notice at year end.

What can be shared

Share what saves work without mixing the books: people, settings and the owner's view.

Area	Separate per company	Can be shared
Chart of accounts and journals	Yes	No
Stock and warehouses	Yes	No
Employees and payroll	Yes	No
VAT number and tax invoices	Yes	No
User accounts	No	Yes, with different permissions per company
Print templates and labels	Optional	Often yes
Owner's overview	No	Yes, looking across companies

The point is to avoid duplicate effort. One finance manager should not need three usernames, and a well-designed invoice template should not be rebuilt three times.

Branches inside each company

Branches sit one level below companies: they run day-to-day operations but post into their own company's books. Most companies have more than one location, so you end up with three levels:

Account. You, signed in once.
Companies. Each with its own books, stock, staff and tax.
Branches. Inside each company, each with its own cashiers, warehouses and sales figures.

This structure answers two different questions. "How is the Riyadh branch doing?" is a branch question. "How much VAT does the trading company owe?" is a company question. A good ERP lets you ask both without exporting anything.

Handling transactions between your companies

Treat every transaction between your own companies as a normal transaction between two separate businesses. That means:

When the factory supplies the restaurant, the factory issues a sales invoice and the restaurant records a purchase.
Each side records VAT according to its own position.
Loans or shared costs between companies are recorded as balances owed, not as transfers inside one ledger.

Keeping it this clean makes month-end simpler, because each company's balance with the others can be checked line by line. It also keeps you in a stronger position if a tax authority or bank asks questions about one company.

Permissions are where it pays off

The biggest benefit of one system is usually control, not the subscription price. With per-user, per-company permissions you decide who can:

see sales but not salaries,
approve purchases above a limit,
post journal entries or only draft them,
work in one company or branch but not the others.

When a branch manager moves from the restaurant to the factory, you change one user's access instead of creating an account in another system and remembering to close the old one. When an external accountant helps with one company, you grant access to that company only.

How to move to a multi-company setup

Move one company at a time, starting with the one whose current system causes the most pain. A practical sequence:

Map your structure. List each legal entity, its VAT number, branches, warehouses and bank accounts.
Agree a chart of accounts approach. Many groups use a similar structure across companies so reports are easy to compare, while keeping the books separate.
Set opening balances from the last closed period in the old system.
Create users and roles before go-live, so nobody shares a login on day one.
Run in parallel briefly if your accountant wants to compare figures, then switch off the old tool.

If you need help planning the move, our services team scopes, builds and supports the same projects end to end.

How Azha ERP handles several companies

Azha ERP was built with this structure from the start. One login manages several companies, each with its own books, stock, staff, branches and VAT number. Branches run inside each company, and permissions are set per user and per company.

All 12 modules, from Accounting, Sales and Inventory to HR, Payroll (including end of service), Fixed assets and Manufacturing, post to one ledger per company, and Reports give you P&L, balance sheet, trial balance, VAT return, aging, stock valuation, sales by branch and payroll summaries. Custom labels and print templates live in Settings, so a school can call customers "students". The interface works fully in Arabic right to left and in English. If you are still comparing systems, our guide on choosing a cloud ERP in Saudi Arabia or Egypt lists the questions to ask any vendor.

Frequently asked questions

Can one ERP really keep companies legally separate?

Yes, if the separation is built into the system. Each company needs its own chart of accounts, stock, payroll and VAT number, so its reports can be handed to an auditor on their own. Check this in a demo rather than relying on a feature list.

Does each company need its own VAT registration in the system?

Each legal entity that is registered for VAT has its own VAT number, and invoices must be issued under that number. In Saudi Arabia, that also means a separate ZATCA e-invoicing setup for each company.

What is the difference between a company and a branch?

A company is a legal entity with its own books and tax. A branch is a location inside a company, with its own cashiers, warehouses and sales, posting into that company's books.

Can I give an external accountant access to just one company?

In a system with per-user, per-company permissions, yes. You grant access to the company they work on and limit what they can see or post there.

If this sounds like your business, book a free 30-minute demo and see Azha switch between companies live. You can also read more about Phoonix or browse other guides on the blog.