If your business invoices across the GCC, you are no longer managing one compliance timeline. UAE finance teams that once tracked a single VAT framework now sit between five different tax authorities, each moving toward mandatory e-invoicing at a different pace, using different models, formats, and thresholds. This guide compares the 2026 status of e-invoicing mandates across the UAE, Saudi Arabia, Oman, Bahrain, and Kuwait, so CFOs, compliance officers, and ERP leads know exactly which obligations are already live, which land this year, and where planning slack still exists.
The GCC is no longer a uniform tax bloc. Saudi Arabia has run a live clearance model for four years. The UAE and Oman are activating Peppol-based frameworks within months of each other. Bahrain is drafting its rules, and Kuwait is still in early scoping. For any UAE headquartered group with regional entities, this creates operational risk in three places: master data, invoice format, and Accredited Service Provider (ASP) selection. Treating the region as one project usually causes delays, rejected filings, or duplicated integration work. A per country readiness view is now the baseline expectation for finance and IT leadership.
The UAE Federal Tax Authority (FTA) has anchored its regime in the Peppol International Invoice UAE Profile (PINT-AE), running on a 5-corner model where every invoice moves through an ASP, is validated, and is reported to the FTA. Under Cabinet Decision No. 106 of 2025 and Ministerial Decisions No. 243 and 244 of 2025, the mandate covers e-invoicing B2B B2G UAE transactions in a phased rollout, with the ASP appointment deadline for large businesses extended to 30 October 2026 through Ministerial Decision No. 56 of 2026. The immediate priorities for UAE finance teams are appointing an ASP, mapping ERP data to the PINT-AE data dictionary, and testing tax code logic before go-live. Groups that leave any of these to the last quarter of 2026 usually find themselves scrambling on integration testing while ASP capacity tightens.
The Zakat, Tax and Customs Authority (ZATCA) launched Phase 1 of Fatoora in December 2021 and has been rolling out Phase 2 integration in waves since January 2023. Standard invoices (B2B and B2G) are cleared in real time, and simplified B2C invoices are reported within 24 hours. Wave 23 required businesses with taxable turnover above SAR 750,000 to integrate by 31 March 2026, and Wave 24 pulls in taxpayers above SAR 375,000 by 30 June 2026, according to ZATCA. For UAE groups with Saudi entities, the operational reality is different from the UAE model. KSA runs a centralised clearance flow with UUIDs, cryptographic stamps, and QR codes, and does not use Peppol. Reusing your UAE ASP setup will not work; the KSA arm needs a separate, ZATCA-integrated solution.
The Oman Tax Authority (OTA) became a Peppol Authority in January 2026 and published the PINT OM specification shortly after. Phase 1 of the Fawtara mandate applies to approximately 100 to 150 pre-notified large taxpayers from August 2026, with all remaining large VAT-registered businesses covered by February 2027, and every VAT-registered entity, including SMEs, by August 2027. Oman mirrors the UAE architecture more closely than KSA, using a 5-corner model, Continuous Transaction Control (CTC) reporting, and OTA-accredited service providers. UAE groups with Omani operations can often reuse their PINT design principles, but tax codes, currency handling, and OTA registration still need country-specific configuration.
The National Bureau for Revenue (NBR) has been consulting on a national e-invoicing platform, and updated VAT guidance now allows electronic invoices without prior NBR approval. However, no mandatory e-invoicing regime is in force in Bahrain as of mid-2026, and full technical specifications have not been published. Industry expectation, drawn from the NBR earlier tender documents, is a KSA style clearance model rolled out in phases by turnover. For UAE finance leaders overseeing Bahraini entities, the reasonable posture is monitoring, keeping ERP configuration flexible, and holding back on Bahrain-specific integration work until the NBR issues final rules.
Kuwait remains the least advanced of the five. Without a broad VAT framework in place, the country is still scoping its digital tax infrastructure, and no formal e-invoicing legislation, format standard, or mandate deadline has been published. UAE businesses with Kuwaiti operations should treat this as a monitoring item rather than a 2026 project. The practical risk is not missing a Kuwaiti deadline; it is under-designing a regional invoicing architecture that cannot flex when Kuwait eventually follows the KSA or UAE route.
The GCC is running four different maturity levels at once. That has direct operational consequences. Master invoice data needs to satisfy the strictest live regime you touch, which today is KSA. ERP design should be modular enough to plug into Peppol for the UAE and Oman without a full rebuild. ASP selection is not a single decision, it is one per jurisdiction. Internal controls, especially around VAT tax codes, credit notes, and cross-border supplies, need to be re-tested against each authority validation rules. The teams that struggle most are those forcing one shared solution across all five countries. The teams that move fastest treat each country as its own workstream, coordinated by a single regulatory owner. That coordination role, along with the readiness assessment, ASP shortlisting, ERP data mapping, and go-live testing that sits under it, is exactly where independent advisory support pays for itself.
By late 2026, KSA is deep into Phase 2, the UAE is activating its Peppol PINT-AE mandate with ASP appointments due by 30 October 2026, Oman is running its first Fawtara wave, Bahrain is close to publishing final rules, and Kuwait is still framing its approach. The framework that works across all five is the same: assess readiness, map data, choose the right ASP per country, and test early. If your finance, tax, and IT teams need an independent view of where your group actually stands against each mandate, book a UAE e-invoicing readiness assessment with our compliance team.
Saudi Arabia leads by a clear margin. ZATCA Fatoora has been live since December 2021, with real-time clearance for B2B and B2G invoices and 24-hour reporting for B2C. Phase 2 integration is now in Waves 23 and 24, covering businesses with taxable turnover above SAR 375,000. The UAE and Oman are still activating their mandates in 2026, which leaves KSA as the operational benchmark for the region.
No. The UAE uses the Peppol PINT-AE profile on a 5-corner model, where invoices flow through an Accredited Service Provider and are validated by the FTA. Saudi Arabia uses a centralised clearance model with ZATCA at the centre, cryptographic stamps, and QR codes, and does not rely on Peppol. A single technical solution cannot cover both, so groups operating in both countries need separate ASP and integration setups.
Oman Fawtara mandate begins on 1 August 2026 for approximately 100 to 150 pre-notified large taxpayers. From February 2027, it extends to all remaining large VAT-registered businesses, and from August 2027 to every VAT-registered entity in the country, including SMEs. The framework uses the Peppol 5-corner model and the PINT OM specification, similar in architecture to the UAE profile, and is administered by the Oman Tax Authority (OTA).
Not yet. The Bahrain National Bureau for Revenue is still finalising its e-invoicing framework, and businesses are currently allowed to issue electronic invoices in formats such as PDF without prior approval. No mandatory rollout date, format, or turnover threshold has been officially confirmed. Bahraini entities of UAE groups should monitor NBR announcements, keep their ERP flexible, and avoid committing to specific technical work until final specifications are published.
Treat each country as a separate compliance workstream with one coordinating owner. KSA is the strictest live regime, so master data should meet its rules first. The UAE and Oman can share Peppol-based design principles but not full configurations. Bahrain and Kuwait remain monitoring items. A structured readiness assessment across all five countries usually prevents duplicated integration work, rejected filings, and rushed ASP selection close to go-live dates.
