Businesses operating across the GCC are facing significant changes to how invoices are generated, validated, exchanged, and reported to tax authorities. In each jurisdiction; UAE, KSA, Bahrain, Oman, and Qatar, e-invoicing transformation comes with distinct technical requirements, reporting obligations, and deadlines.
Saudi Arabia's ZATCA clearance is already live. The UAE's Peppol-based framework begins with a pilot and voluntary phase from 1 July 2026, followed by mandatory rollout in phases through 2027. Bahrain is moving toward its own centralised validation model. Oman will begin mandatory Fawtara e-invoicing in August 2026, with phased adoption extending through 2027. On 6 May 2026, Qatar approved its e-invoicing law, with compliance requirements expected to take effect from 2027.
Finance teams managing multiple Gulf entities require an invoicing infrastructure that can adapt to evolving regulatory requirements.
Key Takeaways
- Saudi Arabia's ZATCA clearance requirement requires standard tax invoices (B2B) to be validated and stamped before they can be shared with the buyer. Simplified tax invoices (B2C) are generated and issued first, then reported to ZATCA within 24 hours of issuance.
- The UAE Peppol framework opens a pilot and voluntary phase from 1 July 2026, with mandatory adoption starting on 1 January 2027 for the largest taxpayers.
- Bahrain's forthcoming system is expected to mirror Saudi Arabia's real-time control model, though final details are yet to be confirmed.
- Oman's August 2026 rollout requires businesses to prepare ERP integrations, ASP connectivity, and Peppol compliance before their onboarding phase.
- Qatar's legal framework is now in place, with a phased rollout expected from 2027.
- Operating across multiple Gulf markets means navigating different invoice formats, submission channels, and implementation timelines simultaneously.
Multi-country GCC e-invoicing compliance is essentially a business's ability to meet the electronic invoicing requirements of several Gulf jurisdictions at the same time. This must be achieved without letting local obligations compromise the consistency of financial controls, tax reporting, or operational governance across subsidiaries.
What makes this particularly nuanced is that while governments across the region are working toward the same broad goal, greater tax transparency and GCC VAT compliance, they've taken a different path to get there. Companies operating across all three markets cannot rely on a single invoicing process to meet the requirements of each jurisdiction.
Saudi Arabia requires standard tax invoices (B2B) to go through ZATCA's clearance process before they can be shared with buyers. Simplified tax invoices (B2C) are issued directly and reported to ZATCA within 24 hours of issuance. The UAE is building its framework around Peppol, with invoice exchange handled through accredited service providers. Bahrain is anticipated to adopt a centralised model closer to Saudi Arabia's, though its regulatory framework remains under development.
Oman has adopted a Peppol-based five-corner model, where ASPs validate and exchange invoices while reporting transaction data to the Oman Tax Authority. Qatar is expected to introduce a hybrid framework that combines clearance and reporting models, supported by Peppol-based invoice exchange and structured XML invoices.
Each GCC country is introducing e-invoicing at a different pace and through different regulatory models. Below is a breakdown of the current e-invoicing frameworks and requirements in each jurisdiction.
The UAE is introducing e-invoicing as part of its wider digital tax transformation. The framework is set out in Ministerial Decision No. 243 of 2025 on the Electronic Invoicing System, Ministerial Decision No. 244 of 2025 on its implementation (as amended by Ministerial Decision No. 66 of 2026), Ministerial Decision No. 64 of 2025 on Accredited Service Providers, and Cabinet Decision No. 106 of 2025 on violations and administrative penalties.
Rather than following Saudi Arabia's centralised clearance model, the UAE has opted for a decentralised 5-corner model built on the Peppol network. Suppliers and buyers exchange invoices through their respective Accredited Service Providers, while the fifth corner, the Federal Tax Authority, receives the reporting data.
The framework is set out in Ministerial Decision No. 243 of 2025 on the Electronic Invoicing System, Ministerial Decision No. 244 of 2025 on its implementation (as amended by Ministerial Decision No. 66 of 2026), Ministerial Decision No. 64 of 2025 on Accredited Service Providers, and Cabinet Decision No. 106 of 2025 on violations and administrative penalties.
The rollout is structured in phases:
Before the set deadlines, companies need to designate an Accredited Service Provider who will be able to send invoices via the authorised system. Invoices must follow the UAE's PINT-AE specification, which is based on UBL 2.1 and the EN 16931 semantic model, and must include the supplier's and buyer's Tax Identification Numbers (TINs), Tax Registration Numbers (TRNs) where applicable, invoice number, tax amount, transaction value, and line-level details.
Saudi Arabia continues to be the leading country to follow GCC e-invoicing compliance. The Zakat, Tax, and Customs Authority (ZATCA) is the regulatory body of the Fatoorah project that has revolutionised the way taxable invoices are created, transmitted, and reported. The rollout is structured in two phases, with Phase 2 still being implemented in successive waves.
Phase 1: Generation Phase
This phase came into effect on 4 December 2021 and required all VAT-registered taxpayers in Saudi Arabia to generate and store invoices in structured electronic format, replacing manually prepared paper documents. Companies had to keep records of invoices in a structured manner and make sure that the invoices had the mandatory fields specified by ZATCA.
Phase 2: Integration Phase
Phase 2, the Integration Phase, took effect on 1 January 2023 and is being rolled out in waves determined by taxpayer turnover, with each wave notified by ZATCA at least six months before its go-live date. Under this model, invoices must be transmitted to ZATCA for validation before they are issued to customers. Once validated, the invoice receives a clearance stamp and can be legally shared with the buyer.
This distinction has major operational implications. In many countries, invoices are generated and delivered immediately after a transaction occurs. In Saudi Arabia, invoice issuance is dependent on successful clearance. If invoice data fails validation checks, the invoice must be corrected and resubmitted.
Businesses must also comply with technical requirements defined by ZATCA. This includes prescribed XML formats, mandatory invoice fields, cryptographic stamping on all invoices, and QR codes specifically on simplified (B2C) tax invoices, in line with ZATCA specifications.
Bahrain is still in the preparatory stage of its e-invoicing journey, but several indicators suggest the country is moving toward a centralised validation framework. The National Bureau for Revenue has conducted consultations and initiated procurement activities for a national e-invoicing platform.
While final regulations are yet to be published, the expectation across the industry is that Bahrain will adopt a continuous transaction control model, like Saudi Arabia's. Under such a framework, businesses would be required to connect to a central platform, submit invoice data in a structured format, and adhere to defined reporting standards.
Oman is implementing its Fawtara e-invoicing programme under the supervision of the Oman Tax Authority (OTA). Unlike Saudi Arabia's centralised clearance model, Oman has adopted a Peppol-based five-corner model, where invoices are exchanged through OTA-accredited service providers that validate invoice data and report transaction information to the tax authorities.
Mandatory implementation begins in phases from August 2026, with taxpayer groups being onboarded over multiple stages. Businesses operating under the Fawtara framework will need to comply with several technical and operational requirements, including:
Qatar has begun establishing the legal foundation for its e-invoicing programme following the approval of its draft e-invoicing law and executive regulations in May 2026. Although the General Tax Authority (GTA) hasn't released the final technical details or when it will start, the new framework shows that Qatar is moving towards ongoing checks of transactions, similar to other digital tax efforts in the GCC.
The final model is yet to be confirmed, businesses should expect requirements such as:
The following table summarises the most important differences businesses must address when operating across multiple GCC jurisdictions.
GCC e-invoicing compliance Area | UAE | Saudi Arabia | Bahrain | Oman | Qatar |
Exchange Model | Decentralised Peppol Network | Centralised Clearance | Expected Centralised Clearance | Peppol Five-Corner Model | Expected Hybrid Model |
Authority Interaction | Through Accredited Service Providers (ASPs) | Direct ZATCA Validation | Expected NBR Validation | Through OTA-Accredited Service Providers | Expected through GTA-approved Framework |
Invoice Standard | PINT-AE XML | ZATCA XML | Pending | PINT OM (UBL 2.1 XML) | Expected Structured XML |
Implementation Status | Phased Rollout | Mandatory | Under Development | Phased Rollout | Legal Framework Approved |
B2C Requirements | Out of scope: business-to-consumer transactions are not covered by the UAE Electronic Invoicing System.
| QR Code Requirements | Pending | 24-hour reporting window | Expected Reporting Model |
Reporting Structure | Tax Data Reporting | Real-Time Clearance | Expected CTC Reporting | Real-Time Tax Data Reporting | Expected Clearance & Reporting |
These differences create one of the biggest challenges in multi-country e-invoicing GCC programs.
A successful e-invoicing strategy requires businesses to assess existing systems, identify GCC e-invoicing compliance gaps, and prepare each subsidiary for upcoming requirements. The following steps outline a practical approach.
The first step is understanding which subsidiaries fall within the scope of current or upcoming mandates. This assessment should cover:
Without a consolidated view of regulatory obligations, organisations often allocate resources incorrectly and underestimate implementation timelines.
One of the most common causes of invoice rejection is poor master data quality. Many multinational groups run separate ERP systems and local accounting or customer databases that they maintain independently.
As a result, discrepancies arise over time in tax registration numbers, customer data, product classifications, and VAT treatments. Standardised controls are a must for companies before they set up country-specific integrations, and they should cover the following:
A common misconception is that e-invoicing is simply an output format change. In reality, different jurisdictions impose different process requirements that affect invoice generation, approval, and transmission workflows. As a result, ERP systems must be configured to support country-specific business rules. Organisations should evaluate whether existing systems can:
Once internal systems are ready, businesses must establish connectivity with the relevant compliance infrastructure. The required integrations differ significantly across jurisdictions.
Country | Integration Requirement |
UAE | Accredited Service Provider (ASP) |
Saudi Arabia | ZATCA Fatoora Platform |
Bahrain | Expected NBR Platform Integration |
Oman | OTA-Accredited Service Provider |
Qatar | Expected GTA Platform / Accredited Service Provider Integration |
Implementation is only the stepping stone of the compliance journey. Once e-invoicing becomes operational, businesses need controls that ensure ongoing compliance. Key controls include the following:
The most successful regional implementations balance local execution with centralised oversight. A centralised governance framework should define the following:
With implementation timelines drawing closer, it is important for businesses to evaluate how prepared they are in the following areas.
Readiness Area | Key Question |
Regulatory Assessment | Have all country-specific obligations been identified? |
ERP Readiness | Can existing systems generate required invoice formats? |
Data Governance | Is invoice master data standardised and validated? |
Integration Planning | Are required connections with ASPs and tax platforms defined? |
Internal Controls | Are validation failures monitored and resolved? |
Record Retention | Can invoice records be stored according to local requirements? |
Governance Structure | Is there a central owner for regional compliance? |
As the e-invoicing rules in the GCC countries are still evolving, companies should not see compliance just as a one-time project. There will be regular changes due to new e-invoicing regulations in the UAE, KSA, Bahrain, Oman, and Qatar, technical updates, and reporting requirements even after the implementation is over.
The companies need to concentrate their efforts on three crucial areas: always keep the invoice data accurate, ensure ERP and integration systems are capable of adapting to future changes, and give a clear definition of the compliance duties among the subsidiaries.