One project, three tax regimes — running UAE, KSA and Egypt jobs from a single platform

A growing UAE contractor doesn't stop at the Emirates border. Saudi mega-projects, Egyptian residential developments, the occasional Bahrain or Oman job — the work is regional. The compliance is not.

UAE FTA wants 5% VAT plus a 9% Corporate Tax filing and e-invoicing readiness. ZATCA in KSA wants Phase 2 e-invoicing on every B2B transaction, with QR codes embedded in PDFs. Egypt's ETA wants per-line items reported in real time on every invoice over EGP 250.

Most contractors handle this by keeping three different accounting tools running in parallel — one per country — and reconciling at year-end. That works at low volume; at scale it produces double the audit pain and zero portfolio visibility.

What a regional tax engine actually has to do

Three things make a multi-region tax engine real instead of marketing:

1. Per-project regime selection. Project A in Abu Dhabi runs on FTA rules; Project B in Riyadh runs on ZATCA. Same tenant, same database, different rules per invoice.

2. Native e-invoicing wire format. Not "we can export". ZATCA Phase 2 requires XML-signed invoices submitted to the government API before issue. If the engine generates a PDF and then a separate tool submits the XML, you have a synchronisation problem in production.

3. Currency lock per project. A KSA project contracted in SAR shouldn't re-rate when the AED/SAR FX moves. The exchange rate at contract signing has to lock; in-flight invoices use the locked rate; reporting neutralises to the tenant's base currency.

ORKSTRA's tax engine handles all three. Tax regime is a per-project setting. Currency is per-project with a lock-at-award option. The e-invoicing wire format generates from the same invoice record that prints the PDF — one source of truth.

Cross-region reporting

The other half of multi-region work is consolidation. The CFO wants to see total receivables across UAE + KSA + EGY in AED, with FX neutralised to the contract rate.

ORKSTRA gives that view directly. Each project reports in its native currency; the portfolio dashboard neutralises to a chosen base currency using either daily ECB mid-market rates or the per-project locked rate. The CFO can switch between "as-billed" and "constant-currency" views in a click.

What this means at audit

Every invoice carries its regime stamp (FTA / ZATCA / ETA), its wire format (PDF + XML / PDF + QR / PDF + ETA submission ID), and its currency lock. The audit pack exports per-regime in the format the local auditor wants — without three different export jobs.

That's the difference between three tools held together by Excel and one platform that actually thinks in multiple regions.