Feature
Multi-country — three countries, three tax regimes, one tenant
The multi-BG architecture isn't a roadmap claim. It's live in the demo right now. Three Business Groups, three currencies, three e-invoicing regimes, running side-by-side under a single AION tenant. Log in and see country-correct numbers.
The three Business Groups live in our demo
Each is a complete demo — currency, tax, CFO user, master data, transaction history.
Qatar
Pearl F&B Co. W.L.L.
- Currency
- QAR
- VAT rate
- 0%
- E-invoicing
- Not yet
- CFO login
- cfo.qatar
- Annual revenue
- QAR 18M
Saudi Arabia
Oasis Fresh Beverages Co.
- Currency
- SAR
- VAT rate
- 15%
- E-invoicing
- ZATCA-PHASE2
- CFO login
- cfo.saudi
- Annual revenue
- SAR 65M
Egypt
Nile Foods Co. S.A.E.
- Currency
- EGP
- VAT rate
- 14%
- E-invoicing
- ETA-SERIAL
- CFO login
- cfo.egypt
- Annual revenue
- EGP 50M
What multi-country actually means
Lots of ERPs claim multi-country. The claim usually means "supports multiple currencies" — which is necessary but not sufficient. Real multi-country support means everything country-specific is configurable per Business Group, not hard-coded.
For an MENA F&B group, the differences across countries are not subtle:
- Currency. SAR, QAR, EGP, AED, OMR — each with their own FX dynamics. Saudi is pegged to USD; Egypt is floating; others sit in between.
- VAT rate and treatment. 15% in KSA, 14% in Egypt, 5% in UAE, 10% in Bahrain, 0% in Qatar and Kuwait. Plus the GCC Unified VAT Agreement that zero-rates intra-GCC exports — but only if you can document them.
- E-invoicing. ZATCA Phase 2 in KSA (real-time clearance with XML + QR). ETA serial in Egypt (portal submission with item-code mapping). UAE Phase 1 coming in 2026. Each has its own technical format and integration pattern.
- Withholding tax. 5% on services in Egypt. Specific industry rates elsewhere. The mechanism varies — deducted at invoice entry, paid to authority monthly.
- Payroll regulations. Saudi WPS for wages. Qatar pension system for nationals. Egyptian social insurance with employer/employee split. Each country's calculations are non-trivial.
- Banking patterns. Bank file formats differ. IBAN structures differ. Settlement timing differs.
AION handles all of these via the country profile per Business Group. The same operational workflow (post an invoice, run payroll, close a period) produces country-correct output in each BG.
How the architecture works
Country profile per BG
Each BG references a country profile that drives currency, VAT rate, e-invoicing format, regulator integration, banking patterns, and statutory chart of accounts. Adding a new country means adding a profile.
Shared engine, country-aware behaviour
The same SLA engine, costing engine, BOM rollup, period close, and reporting layer run in every BG. The country profile determines the rate parameters; the engine handles the math.
Master data sharing — opt in per entity
Customers, suppliers, items can be shared across BGs (Carrefour parent → Carrefour KSA + Carrefour Egypt children) or kept BG-specific. The MOAC model controls who sees what.
Intercompany — automated matching
A sale from KSA BG to Egypt BG posts the matching journals in both books. Intercompany invoices and payments are matched and eliminated at consolidation. No manual reconciliation.
Group consolidation — one click
Translate each BG's books into a group reporting currency. Eliminate intercompany. Produce consolidated trial balance, income statement, and balance sheet. From close to consolidated report in a day.
Add countries via configuration, not rebuild
When UAE Phase 1 e-invoicing mandates in 2026, you flip the UAE BG's country profile to the new format. When Qatar publishes its VAT framework, same. No code changes, no implementation project.
Why this matters for MENA F&B groups
The alternative to multi-country architecture is one ERP per country. Saudi books on a Saudi system. Egyptian books on an Egyptian system. UAE books on a UAE system. Group reporting comes from manual consolidation in Excel.
Three failures in that pattern:
- Intercompany reconciliation is manual. Every cross-border sale is two systems' worth of paperwork. Mismatches surface at consolidation, weeks after the transaction.
- Master data drifts. Carrefour as a customer has three slightly different versions in three systems. Reporting "what did Carrefour buy from us globally this year" requires reconciliation, not a query.
- Compliance projects multiply. Each country's ZATCA, ETA, FTA mandate is a separate implementation in a separate system. Each upgrade is a multi-system risk.
With multi-country architecture, all three failures disappear. The cost of operating in a new country drops to "configure the country profile." The cost of consolidation drops from "two weeks of manual reconciliation" to "run the report." The cost of compliance mandates drops to "configuration update."
Common questions
How many countries can one AION tenant support?
Architecturally unlimited. Practically, the demo runs three (KSA, Qatar, Egypt) with full e-invoicing, currency, and tax configurations. Adding UAE, Oman, Bahrain follows the same pattern — each is a Business Group with its own country profile. We have customers planned for 5-7 country deployments.
Do all Business Groups share master data?
Shared where it makes sense, separate where it must be. A customer like Carrefour can be a parent entity with country-specific child accounts (Carrefour KSA, Carrefour Egypt, Carrefour UAE) — each with local terms, contacts, and AR balances. Items and suppliers follow the same pattern. The MOAC (multi-org access control) model governs cross-BG visibility per user role.
How does group consolidation work?
The reporting layer translates each BG's books into a group reporting currency at configurable rates (period-end spot, period-average, year-end). Intercompany invoices and payments are matched and eliminated automatically. Consolidated trial balance, income statement, and balance sheet generate from the consolidated data layer.
What happens when one country adds a new e-invoicing mandate?
You toggle the country profile for that BG. The e-invoicing format, tax accounts, and SLA rules update via configuration. No rebuild. UAE Phase 1 e-invoicing expected in Q2 2026 — when it lands, the UAE BG flips on without affecting Saudi, Qatari, or Egyptian operations.
See three countries running side-by-side
Open the demo, pick a region, log in. The same product running with Saudi, Qatari, and Egyptian books in parallel.