A AION Academy

MENA compliance

GCC + Egypt VAT — multi-country in one ERP

Five countries, five tax regimes, one tenant. KSA 15% with ZATCA Phase 2. UAE 5%. Qatar 0% (VAT-ready). Oman 5%. Egypt 14% with ETA. AION handles all of them simultaneously — three are live in our demo right now.

The MENA VAT landscape — at a glance

Where each country sits today, and what AION handles for each.

Country VAT rate Regulator E-invoicing Live in AION demo?
🇸🇦 Saudi Arabia 15% ZATCA Phase 2 — XML, QR, clearance ✓ Oasis Fresh BG
🇪🇬 Egypt 14% ETA Serial-numbered submission ✓ Nile Foods BG
🇶🇦 Qatar 0% (VAT-ready) GTA (draft framework) Not yet mandated ✓ Pearl F&B BG
🇦🇪 UAE 5% FTA Phase 1 rolling — Q2 2026 expected Roadmap
🇴🇲 Oman 5% OTA Not yet mandated Roadmap
🇧🇭 Bahrain 10% NBR Not yet mandated Roadmap
🇰🇼 Kuwait 0% (no VAT) MoF Not mandated Roadmap

The GCC VAT framework — common ground

The GCC Unified VAT Agreement (signed 2016) established the common framework: standard rate (typically 5%, country-set), input/output VAT mechanism, mandatory registration thresholds, monthly or quarterly returns depending on size, and zero-rating for exports and certain essential goods. Each member state implements at its own pace and rate.

Six countries have implemented or scheduled VAT:

  • Saudi Arabia (2018, raised to 15% in 2020) — highest rate, most mature e-invoicing regime (ZATCA Phase 2)
  • UAE (2018, 5%) — established mature system; e-invoicing Phase 1 expected to mandate in Q2 2026 with phased rollout
  • Bahrain (2019, 5%; raised to 10% in 2022) — second-highest rate after KSA
  • Oman (2021, 5%) — most recent GCC implementation
  • Qatar (drafted 2024, not yet implemented) — framework published, go-live date pending
  • Kuwait (not implemented) — government has discussed but no firm timeline

Egypt is not a GCC member but operates a similar (older) VAT model — 14% standard rate, 5% withholding tax on services, ETA e-invoicing platform. For MENA F&B groups operating across both Egypt and the GCC, the same accounting engine must handle both regimes simultaneously.

How AION handles multi-country VAT

One tenant. One source of truth. Country-specific behaviour activated per BG.

Country profile per BG

Each Business Group references a country profile that drives VAT rate, e-invoicing format, regulator handoff, and ledger currency. Adding a new country means adding a profile — not re-implementing the ERP.

Unified COA template, localised per BG

The same chart of accounts structure underlies all three live BGs. VAT Input, VAT Output, COGS, AR, AP — same conceptual accounts; localised codes and naming per country.

SLA engine — country-aware journal generation

The same SLA rules apply across countries; the rate parameter is the country's VAT rate. A Saudi invoice posts 15% VAT; a UAE invoice would post 5%; a Qatar invoice posts no VAT line. Configuration, not custom code.

Group consolidation across BGs

A MENA F&B group with entities in Saudi + Egypt + Qatar can consolidate financials at the tenant level. Intercompany eliminations post automatically. The reporting layer translates each BG's books into a group reporting currency.

VAT returns generated per country

KSA VAT return, Egypt VAT return (Form 10), each generated from the same data that powers e-invoicing in that country. WHT remittance for Egypt is on the same foundation. No re-keying.

Future-proofed for new mandates

When UAE e-invoicing Phase 1 mandates (expected Q2 2026), the country profile flips. When Qatar publishes VAT, the same. No rebuild — your historical data stays untouched and forward transactions follow the new rules.

Multi-country VAT — common questions

Can one AION tenant operate in all GCC + Egypt simultaneously?

Yes. The multi-BG architecture is built for exactly this. The demo proves three (KSA, Egypt, Qatar) running side-by-side with their own currencies, tax regimes, CFO users, customer/supplier rosters. Adding UAE, Oman, Bahrain follows the same pattern.

How do intercompany transactions work — KSA entity sells to Egypt entity?

Intercompany flows post the matching journals on both sides — sale in KSA books (with VAT zero-rated for exports), purchase in Egypt books (import accounting). The MOAC model preserves separation of books while automating the matching at month-end consolidation.

What about transfer pricing documentation?

AION captures the data — every intercompany invoice carries the currency, FX rate, item cost basis, and markup. Transfer pricing documentation (master file, local file) is a downstream deliverable; AION provides the underlying transactional data, not the legal documentation itself.

If we operate only in one country today, can we expand later?

Yes. The architecture supports adding BGs incrementally. Start with KSA only; add Egypt next year when you open the Cairo factory. The existing BG keeps running; the new one comes online with its own country profile.

How does AION handle GCC export zero-rating?

VAT zero-rating for intra-GCC exports is captured per invoice based on the buyer's country and the goods classification. The VAT line shows 0% with the export documentation reference. The return treats zero-rated exports differently from standard-rated sales — the report categorization is automatic.

See multi-country VAT in the live demo

Three regions, three tax regimes, one product. Pick any one from the demo page and log in.