GCC e-invoicing compared: UAE, Saudi Arabia, Bahrain, Oman, Qatar and Kuwait
Updated 2026-08-01 · 8 min read
Companies operating across the GCC hit the same wall: six markets, six sets of rules, and an invoicing system built for one of them. The way out is not six systems. It is one canonical invoice and a swappable compliance profile.
What is genuinely different
The differences that matter are narrow and enumerable: standard VAT rate, tax registration identifier and its label, currency, language expectations, whether a tax QR code is required, and the export format expected by the authority.
Everything else — parties, lines, discounts, totals, payment terms — is common across all six. That common core is the thing worth building once.
- United Arab Emirates: 5% VAT, TRN, AED, Peppol-aligned structured invoicing
- Saudi Arabia: 15% VAT, VAT registration number, SAR, ZATCA XML plus TLV QR and Arabic presentation
- Bahrain: 10% VAT, VAT account number, BHD
- Oman: 5% VAT, VAT identification number, OMR
- Qatar and Kuwait: VAT frameworks still maturing; structured invoicing prepared in advance avoids a scramble
The architecture that survives rule changes
Keep a jurisdiction-neutral invoice document in your database. Attach a compliance profile — rate rules, identifiers, formats, QR requirements, language — at the moment of export.
When a country changes a rate or adds a field, you edit a profile file and ship. Your invoicing screens, approval flow, reporting and integrations do not move.
Failing loudly beats defaulting quietly
A subtle but expensive design decision: what happens when someone requests an export for a profile you do not support? Defaulting to your home jurisdiction produces a document that looks valid and is not.
Unknown profiles should raise a hard error. In a tax context, a failed export is cheap and a wrong export is not.