Skip to content
Flowyana

Guides · Multi-branch

One company, branches in Dubai, Riyadh and Kuwait: running multi-country books in the GCC

Updated

In short

A group with branches in Dubai, Riyadh and Kuwait faces three VAT positions — 5%, 15% and none — and three currencies. The workable model is one platform with books per country, each in its own currency and tax setup, one way of working everywhere, branch access enforced by the platform, per-branch branding, and group figures added up from each country’s reports. Filing and e-invoicing stay country-specific, and no platform should be assumed to cover them.

The shape of the problem

A group with an outlet in Dubai, a trading arm in Riyadh and a branch in Kuwait City is not three businesses in the eyes of its owner. It is one business whose numbers must add up. But the three sit in three different tax positions and three different currencies, and in most cases three legal entities that each file their own returns in their own currency.

That last point decides the design. A UAE company files VAT in dirhams, a Saudi company in riyals, and a Kuwaiti company has no VAT at all. Each needs its own books in its own currency. What the owner needs on top is one platform, one way of working, and figures that can be put side by side.

Three tax positions, three sets of books, one platform

As of October 2026, the three states differ as follows.

CountryVAT standard rateZero rateCurrencyDecimals
United Arab Emirates5%0%AED2
Saudi Arabia15%0%SAR2
KuwaitNone in force—KWD3

In Flowyana, each country runs as its own workspace. The UAE workspace ships with VAT at 5% and 0% and the registration label “TRN”; the Saudi workspace with VAT at 15% and 0%; the Kuwait workspace with no rate, because none is in force. The defaults are yours to change, because rates in this region are not permanent. Bahrain and Oman, at 10% and 5%, work the same way: expanding there is a new workspace on the same platform, not a second system.

The workspace’s country and home currency lock once transactions exist, which protects the books from a setting being changed under them. The same people can belong to several workspaces and switch between them from one login, and every workspace works the same way, so your team learns one system.

Whatever the rate, the behaviour underneath is identical: every sale, purchase, expense and POS settlement posts a balanced double-entry voucher with the tax split to its own ledger, and the tax reports read from those postings. Three countries on three rates, one method.

Inclusive and exclusive pricing works per workspace too. A Dubai shop shows shelf prices including VAT; the Riyadh trading arm quotes exclusive; the Kuwait branch shows a price with no tax component at all.

Currencies, decimals, and group figures

Each country’s books are kept in that country’s currency, which is what its tax authority and its auditors expect. Two details catch people out.

First, the Kuwaiti dinar has three decimal places, as do the Bahraini dinar and the Omani rial. Put a three-decimal amount through any vendor’s documents, receipts and ledger, ours included, and check the three agree before you buy. In Flowyana, amounts follow the home currency’s decimals on documents, tills and ledgers, and tills can round cash to a set step, such as 5 fils.

Second, group reporting is a separate question from country reporting. The Riyadh manager wants his numbers in riyals; the owner wants the group in one currency. Flowyana keeps an exchange-rate table up to date daily, but it does not merge several workspaces into one consolidated set of statements today, and invoices and bills in a second currency are not available. Group figures are added up from each country’s statements, exported to Excel, at the rate your accountant chooses. Ask any vendor how they handle this, and what “multi-currency” means in their product, before you buy.

Access that is scoped, not filtered

Within each country, the rule to insist on is that branch scoping is enforced by the platform itself. A cashier in the Deira outlet should be unable to retrieve an invoice from the Abu Dhabi branch, not merely unlikely to see it because a filter defaults that way. A filter is a convenience; scoping is a boundary, and only one of them survives a curious user or an exported report.

In practice that means every record carries its branch, staff are assigned the branches they may work in, and ownership and finance see all of them. Reports come in two shapes, per branch and for the whole company, from the same data. Across countries the boundary is simpler still: a person only sees a country’s workspace if they are a member of it. See reports for what that looks like in use.

Documents that look local

Each branch has its own licence details, its own address, and often its own logo treatment. Document templates carry letterheads per branch, so a Riyadh invoice is unmistakably from the Riyadh entity, while the 25 printable document types stay in one template family, with no parallel sets that drift apart.

In all three countries, paired Arabic and English labels on one page is the right default: the customer reads one half, the accountant the other, and there is only one document to file. The bilingual documents guide has the full test.

Financial years and locks

Each workspace has a configurable financial year with a close date and a lock date, so a corrected entry cannot land in a quarter already reported. Keep the years aligned across countries if your group reports on one calendar, or follow local practice where your accountant advises it.

What stays country-specific

Filing formats and e-invoicing mandates differ by country and are changing across the region right now: the UAE has a phased Accredited Service Provider model running to 2027, Saudi Arabia has ZATCA Phase 2 waves already live, and Kuwait has no VAT at all. No platform should be assumed to cover any of it. Ask every vendor for their integration status in writing — including ours; Flowyana claims no e-invoicing clearance integration, ASP accreditation or ZATCA certification — and let your accountant confirm your obligations. See the UAE and ZATCA Phase 2 guides for the questions to ask.

A demo you can run in twenty minutes

  1. Open a UAE workspace and a Kuwait workspace from the same login. Sell the same product in each and compare the tax splits.
  2. Post an amount in Kuwaiti dinars with three decimals, and check the invoice, the receipt and the ledger agree.
  3. Create two branches in the UAE workspace. Sign in as a staff member of one and try to open the other’s invoice.
  4. Print an invoice from each branch and check the letterhead and the paired Arabic–English labels.
  5. Read the P&L per branch, then for the whole company. Lock last quarter and try to post into it.
  6. Export each country’s P&L to Excel, and ask how your accountant will add them up for the group.

To try that with your own branches and rates, book a demo.

See it in the product

Where this lives in Flowyana

Questions

Asked alongside this guide.

Can one Flowyana workspace hold branches in several countries?

Not with separate currencies. A workspace keeps its books in one home currency and one country’s tax setup, both locked once transactions exist. A group with companies in the UAE, Saudi Arabia and Kuwait runs one workspace per country, each in its own currency, and the same people can switch between them from one login.

How is branch access controlled?

By the platform itself, not by a dropdown filter. Every record carries its branch, and staff see only the branches they are scoped to, while ownership reads across all of them. Reports can be read per branch or for the whole company.

Can we see the group in one currency?

Not as one automatic report. Each country’s books report in its own currency, and group figures are added up from each country’s statements, exported to Excel, at the rate your accountant chooses. Flowyana keeps an exchange-rate table up to date daily, but it does not consolidate several workspaces into one set of statements today.

Do we need a separate financial year per country?

Each country’s workspace has its own financial year, close date and lock date, so you can keep them aligned or follow local practice. Your accountant will advise where statutory reporting needs a different treatment.

Keep reading

More guides.

See this working on your own data.

Seeing it on your own data answers the rest fastest. Tell us what your business runs; we’ll set Flowyana up the way you would use it and walk you through it.