Two e-invoicing mandates are running simultaneously in 2026 — ZATCA’s Fatoora Phase 2 in Saudi Arabia and the UAE Federal Tax Authority’s new e-invoicing framework. Both affect businesses using SAP, Oracle, and Microsoft Dynamics. Vivek Infotechs helps companies across UAE, Saudi Arabia, and the GCC connect their ERP systems to both frameworks before penalty deadlines hit. This guide tells you exactly what is required, when, and what your ERP needs to do to comply.
Two Compliance Clocks Are Running at the Same Time — Is Your ERP Ready?
If your business operates across the UAE and Saudi Arabia — or even just in one of these markets — 2026 has put two significant compliance deadlines on your calendar simultaneously. ZATCA’s e-invoicing Phase 2 is reaching its final waves, pulling in thousands of smaller Saudi businesses that were not previously in scope. And the UAE Federal Tax Authority has launched its own e-invoicing mandate, with the first hard deadline for large businesses falling in July 2026.
These are not distant regulatory changes to add to next year’s planning cycle. ZATCA’s Wave 24 deadline is June 30, 2026. Businesses in Saudi Arabia with annual VATable revenue exceeding SAR 375,000 — a threshold that for the first time captures a large proportion of SMEs — must have their invoicing systems integrated with the Fatoora portal by that date. Miss it, and invoices issued after the deadline are not legally valid. The penalty waiver that ZATCA extended until June 30, 2026 will not be extended again.
The UAE’s timeline is slightly later but moving fast. Businesses with revenue above AED 50 million have until July 31, 2026 to appoint an Accredited Service Provider. The full PINT AE format mandate follows in 2027. Companies that are starting their ERP integration work now will make these deadlines comfortably. Those that are waiting for more clarity from regulators are running out of runway.
This guide covers what each mandate requires, what your ERP system needs to do technically, and what the integration work actually involves for businesses on SAP, Oracle, and Microsoft Dynamics.
Understanding ZATCA Phase 2 — What the Fatoora Integration Actually Requires
ZATCA’s e-invoicing project — officially called Fatoora — has been rolling out in two phases since 2021. Phase 1 required businesses to generate invoices electronically with the correct data fields and a QR code. Most businesses managed this with relatively modest system changes. Phase 2 is fundamentally different, and significantly more demanding from an ERP integration perspective.
Phase 2 requires direct real-time integration between your invoicing system and ZATCA’s Fatoora portal via API. Invoices are not just generated electronically — they must be transmitted to ZATCA for clearance before being shared with the buyer in B2B transactions. Only after ZATCA validates, time-stamps, and digitally signs the invoice is it considered legally valid. For B2C transactions, the invoice must be reported to ZATCA within 24 hours of issuance.
The technical requirements under Phase 2 are specific. Every invoice must include a Universally Unique Identifier (UUID) — a 128-bit unique number generated automatically for each document. It must include a Previous Invoice Hash (PIH), which is a digital fingerprint linking the current invoice to the one immediately before it, creating a chain that makes it impossible to delete or alter past invoices without detection. And it must carry a cryptographic stamp — a digital signature applied to the invoice XML that proves the invoice was issued by your specific business and guarantees the data has not been tampered with after issuance.
These are not fields you can add manually or through a workaround. They require genuine ERP-to-Fatoora integration, where your SAP, Oracle, or Dynamics system generates the correct XML format and transmits it to ZATCA’s API in real time.
The Wave Timeline — Where Your Business Sits
ZATCA has been rolling out Phase 2 in waves based on annual VATable revenue thresholds. Wave 19, which covered businesses with VAT-liable income exceeding SAR 7 million for 2022 or 2023, had an integration deadline of January 1, 2025. Wave 23 covered businesses with SAR 750,000 to SAR 1 million in VATable revenue, with a March 31, 2026 deadline. Wave 24 — the most significant from an SME perspective — brings businesses with annual VATable revenue exceeding SAR 375,000 into mandatory Phase 2 scope, with a June 30, 2026 deadline.
If your Saudi business has not yet confirmed which wave it falls into, that is the first thing to check. ZATCA notifies businesses at least six months before their wave deadline, but if you have not received a notification and your revenue is above SAR 375,000, you should not assume you are out of scope.
Understanding UAE FTA E-Invoicing 2026 — A Different Framework
The UAE’s e-invoicing framework is architecturally different from Saudi Arabia’s Fatoora system, which is important to understand if your business operates in both markets. Saudi Arabia uses a clearance model where invoices must be validated by ZATCA before they are legally valid. The UAE is implementing a reporting model under the Peppol network, using a format called PINT AE (Peppol International for the UAE).
Under the UAE framework, businesses do not submit invoices to the Federal Tax Authority for pre-clearance. Instead, invoices are transmitted through accredited Peppol Access Service Providers (ASPs) who handle the format conversion and network delivery. The FTA receives the invoice data for audit and reporting purposes, but the invoice itself flows directly from seller to buyer through the Peppol network.
The PINT AE format is structured XML and requires specific data fields — including Tax Registration Numbers, Unit of Measure codes, and 51 mandatory data fields that must be correctly mapped from your ERP’s invoice master data. Companies that have not started this master data mapping work are likely underestimating how much preparation is involved.
UAE Deadlines — Who Is Affected and When
The UAE is phasing its mandate by revenue threshold. Businesses with annual revenue exceeding AED 50 million must formally appoint an accredited ASP by July 31, 2026. Missing this deadline carries an administrative penalty of AED 5,000 per month. The full Phase 1 go-live — where all B2B and B2G invoices must be issued in PINT AE format through an ASP — follows in early 2027 for this group. A second phase covering businesses above AED 5 million follows in late 2027.
Businesses operating in free zones — DMCC, JAFZA, IFZA, DIFC, ADGM, RAKEZ, and others — are in scope if their revenue meets the phase threshold. The free zone designation does not exempt businesses from the e-invoicing requirement. Pure B2C retail transactions are explicitly excluded from Phase 1, 2, and 3 as currently published.
What ERP Integration Actually Involves — System by System
The question we hear most from finance and IT teams across UAE and Saudi Arabia is: “Our ERP already generates invoices electronically — aren’t we already compliant?” Almost always, the answer is no. Electronic invoice generation and e-invoicing compliance are two very different things. The second requires your ERP to transmit specific XML formats to specific regulatory endpoints via certified API connections, with cryptographic signatures and real-time validation. Here is what that looks like for each major ERP platform.
SAP and ZATCA / UAE FTA Integration
SAP has invested significantly in building ZATCA compliance into its ERP portfolio. For businesses on SAP S/4HANA, the most current approach uses SAP’s Document and Reporting Compliance (DRC) solution, which handles ZATCA Phase 2 XML generation, cryptographic stamping, and Fatoora portal transmission natively within the SAP environment. For businesses on SAP Business One, SAP has released specific e-invoicing add-ons for Saudi Arabia, though the implementation approach varies depending on the version and deployment model.
For UAE FTA compliance, SAP’s DRC solution is being extended to support PINT AE format output, with ASP integration available through certified SAP partners. The critical work for SAP users is ensuring that master data — customer TRNs, item unit of measure codes, and the 51 mandatory PINT AE fields — is correctly populated in the SAP system before integration testing begins.
The most common issue we see in SAP-based ZATCA integration projects is data quality in the invoice master data. SAP can generate the correct XML structure, but if the underlying data has gaps — missing TRNs, incorrect unit codes, inconsistent address formats — the invoices will fail ZATCA validation. Data cleanup before integration is not optional; it is the single most important preparation step.
Oracle ERP and ZATCA / UAE FTA Integration
Oracle’s approach to ZATCA compliance in Saudi Arabia runs through Oracle Financials Cloud and Oracle NetSuite, both of which have Saudi-specific localisation capabilities. Oracle Financials Cloud handles ZATCA Phase 2 through Oracle’s Tax Reporting Cloud Service, which generates the required UBL 2.1 XML format, applies cryptographic stamps, and manages Fatoora API integration. NetSuite’s ZATCA integration is handled through Oracle’s certified localisation extensions.
For UAE FTA compliance, Oracle is extending its regional localisation capabilities to support the PINT AE format requirement. Oracle customers should ensure their implementation partner is tracking Oracle’s quarterly update releases for UAE-specific compliance features, as these are delivered through the standard update cycle rather than as separate projects.
Oracle’s multi-entity architecture creates a specific advantage for businesses operating in both Saudi Arabia and the UAE. A single Oracle Fusion instance can handle both ZATCA Fatoora integration for Saudi entities and UAE FTA reporting for UAE entities simultaneously, with appropriate localisation configurations per legal entity. This is operationally more efficient than managing separate compliance tools for each jurisdiction.
Microsoft Dynamics 365 and ZATCA / UAE FTA Integration
Microsoft Dynamics 365 Finance has Saudi Arabia e-invoicing capabilities available through Microsoft’s Electronic Invoicing Service (EIS), which is part of the Regulatory Configuration Service (RCS). The Dynamics 365 ZATCA integration handles Phase 2 XML generation, UUID and hash chain management, and Fatoora portal submission. Microsoft has been releasing ZATCA-specific Electronic Reporting configurations that can be deployed into existing Dynamics 365 Finance environments.
For businesses on Dynamics 365 Business Central — Microsoft’s mid-market ERP — ZATCA compliance typically requires a certified ISV solution rather than native Dynamics functionality, as Business Central’s e-invoicing capabilities for Saudi Arabia are less mature than Finance’s. Several Microsoft-certified partners offer ZATCA-compliant add-ons for Business Central.
The UAE FTA Peppol integration for Dynamics 365 is following a similar pattern, with Microsoft’s Electronic Invoicing Service being extended to support PINT AE format and ASP connectivity. Dynamics 365 users should be in active conversation with their Microsoft partner about UAE readiness timelines, as the July 2026 ASP appointment deadline is approaching.
The Data Problem No One Warns You About Early Enough
Every ERP-based e-invoicing integration project we have worked on in the UAE and Saudi Arabia has encountered the same issue: the data in the ERP system is not ready for compliance-grade invoicing. This is not a criticism of how businesses have managed their systems — it reflects the reality that ERP master data was historically maintained to support internal operations, not to meet the strict field requirements of a regulatory e-invoicing framework.
ZATCA Phase 2 and the UAE PINT AE format both require specific data that many ERP systems do not have cleanly populated. Customer Tax Registration Numbers must be present and correct for all VAT-registered customers. Unit of measure codes must follow standardised classifications. Address fields must be complete and correctly formatted. Invoice sequence numbers must be gapless and tamper-proof.
The businesses that experience smooth e-invoicing go-lives are those that run a data assessment early — before integration work begins — and address the gaps systematically. A data assessment that surfaces 2,000 customer records with missing TRNs three months before the deadline is manageable. The same discovery two weeks before go-live is a crisis.
We recommend building a data readiness checklist that covers: customer master TRN verification, supplier master data completeness, unit of measure standardisation, chart of accounts alignment for VAT categorisation, and invoice template review against all 51 mandatory PINT AE fields. This work takes time, and it cannot be compressed indefinitely regardless of how capable the integration team is.
Common Mistakes That Lead to ZATCA Rejections
ZATCA rejections are more common than businesses expect, particularly in the early weeks after Phase 2 go-live. Each rejection comes with a specific error code that needs to be resolved before the invoice is resubmitted. Understanding the most common rejection causes helps businesses avoid them in testing.
The most frequent rejection cause is incorrect or missing cryptographic stamps. This typically indicates a configuration issue in the ERP-to-Fatoora integration rather than a data problem — either the digital signing certificate is not correctly installed, or the stamp generation process in the ERP is not producing output that matches ZATCA’s validation rules. Catching this in sandbox testing, rather than in live production, is critical.
The second common rejection cause is hash chain errors — where the Previous Invoice Hash in a new invoice does not correctly reference the immediately preceding invoice. This can happen when invoice batches are processed out of sequence, or when a system restart causes the hash chain to break. ERP configurations need to enforce strict sequential invoice processing to prevent this.
The third is incorrect invoice classification. ZATCA distinguishes between standard tax invoices (B2B and B2G, requiring clearance) and simplified tax invoices (B2C, requiring reporting within 24 hours). If an ERP system classifies a B2B transaction as simplified, or vice versa, the invoice will fail validation. ERP configurations need to correctly classify transactions based on whether the buyer is a VAT-registered business or an end consumer.
The Practical Timeline for Getting ERP Integration Done Before Deadlines
Businesses that are reading this in April or May 2026 and have not yet started their ZATCA Phase 2 or UAE FTA integration work are in a tight but still manageable position — provided they start immediately and do not encounter significant data quality issues. Here is a realistic timeline for what needs to happen.
The first two weeks should be spent on assessment: confirming which ZATCA wave your Saudi entity falls into, confirming UAE FTA applicability based on revenue threshold, running a data quality review against ZATCA and PINT AE field requirements, and engaging an implementation partner with demonstrated ZATCA Phase 2 experience. This is not the time to go through a lengthy vendor selection process — businesses that are already in scope need a partner who can start immediately.
Weeks three through six cover the technical integration work: ERP configuration for ZATCA XML generation and Fatoora API connectivity, digital signing certificate procurement and installation, and sandbox testing against ZATCA’s test environment. Most ERP platforms have sandbox environments available that allow full end-to-end testing before production go-live.
Weeks seven and eight should be dedicated to user acceptance testing with real business scenarios — B2B clearance invoices, B2C reporting invoices, credit notes, and debit notes — and resolving any rejection errors that surface in testing. Go-live should be planned with a support buffer of at least two weeks before the compliance deadline to allow time for any post-go-live issue resolution.
For UAE FTA compliance, the immediate priority for businesses above AED 50 million is ASP selection and appointment before July 31, 2026. The ERP integration work for PINT AE format can follow in Q3 and Q4 2026, with full go-live targeted for Q1 2027 ahead of the Phase 1 mandatory date. Starting the ERP field mapping work now — even before the ASP is formally appointed — will save significant time later.
How Vivek Infotechs Approaches E-Invoicing Compliance
At Vivek Infotechs, we work with businesses across UAE, Saudi Arabia, and the wider GCC on ERP-based e-invoicing compliance for both ZATCA and UAE FTA requirements. Our work covers SAP, Oracle, and Microsoft Dynamics implementations, and we have been involved in ZATCA Phase 2 projects across multiple waves.
Our starting point is always a compliance assessment — not a sales presentation. We look at your ERP system, your current invoice data quality, your legal entity structure, and your revenue threshold position to give you a clear picture of what compliance requires, what the implementation timeline looks like, and what the risks are if deadlines are missed.
We handle the full integration scope: ERP configuration, digital certificate management, Fatoora API connectivity testing, sandbox validation, and post-go-live support. For UAE FTA compliance, we support the ASP selection process, ERP master data mapping, PINT AE format configuration, and integration testing.
The businesses that engage us early — three to four months before their deadline — have straightforward projects. Those that come to us six weeks before the deadline have stressful ones. Both can be done, but the experience is very different.
The Bottom Line — Time Is the Variable You Cannot Recover
ZATCA Phase 2 compliance and UAE FTA e-invoicing preparation are not projects that can be compressed indefinitely by adding resources. Data quality issues take the time they take. Sandbox testing surfaces problems that need resolution. Certificate procurement has its own lead times. ERP configuration changes need testing cycles before production deployment.
The businesses that will be in a comfortable position on June 30, 2026 (ZATCA Wave 24) and July 31, 2026 (UAE FTA ASP appointment) are those that started their integration work in the first quarter of 2026. If you are reading this and that work has not started, the most important thing you can do right now is get an honest assessment of where you stand — not a vendor demo, not a proposal, but a clear-eyed evaluation of what your specific ERP environment needs to do to comply and how long that realistically takes.
Penalties for non-compliance are real. ZATCA has demonstrated it enforces them — in July 2025 alone, the authority conducted over 15,000 compliance reviews. The penalty waiver that has given businesses additional time will end. And after June 30, 2026, invoices issued by Wave 24 businesses that are not Phase 2 compliant will not be legally valid under Saudi law.
ZATCA Deadline Approaching — Is Your ERP Ready?
Vivek Infotechs provides ZATCA Phase 2 and UAE FTA e-invoicing integration for SAP, Oracle, and Microsoft Dynamics — across UAE, Saudi Arabia, and the GCC. Get a free compliance assessment before your deadline hits.
Frequently Asked Questions — ZATCA and UAE E-Invoicing 2026
What is the ZATCA Wave 24 deadline and who does it affect?
ZATCA Wave 24 has a deadline of June 30, 2026. It covers all VAT-registered businesses in Saudi Arabia with annual VATable revenue exceeding SAR 375,000 in 2022, 2023, or 2024. This is the first ZATCA wave to include small and mid-sized businesses at this revenue level. After this date, businesses in Wave 24 scope must have their invoicing systems integrated with ZATCA’s Fatoora portal via API — invoices issued without Phase 2 integration will not be legally valid.
What is the UAE FTA e-invoicing deadline in 2026?
UAE businesses with annual revenue exceeding AED 50 million must formally appoint an Accredited Service Provider (ASP) by July 31, 2026. Missing this deadline carries a penalty of AED 5,000 per month. The full Phase 1 go-live — where all B2B and B2G invoices must be issued in PINT AE format through an ASP — follows in early 2027 for this group. Free zone companies (DMCC, JAFZA, DIFC, ADGM, and others) are in scope if their revenue meets the threshold.
Does SAP support ZATCA Phase 2 integration natively?
Yes. SAP S/4HANA supports ZATCA Phase 2 through SAP’s Document and Reporting Compliance (DRC) solution, which handles XML generation, cryptographic stamping, UUID and hash chain management, and Fatoora portal API connectivity. SAP Business One has ZATCA-specific add-ons available through certified SAP partners. In both cases, the critical preparation work is ensuring ERP master data — customer TRNs, unit of measure codes, and address fields — meets ZATCA’s field requirements before integration testing begins.
Can Oracle ERP handle both ZATCA and UAE FTA compliance simultaneously?
Yes. Oracle Fusion Cloud ERP’s multi-entity architecture allows a single Oracle instance to handle ZATCA Fatoora integration for Saudi legal entities and UAE FTA PINT AE reporting for UAE legal entities simultaneously, with entity-specific localisation configurations. This is more operationally efficient than maintaining separate compliance tools for each jurisdiction. Oracle NetSuite handles ZATCA compliance through certified localisation extensions.
What happens if a business misses the ZATCA Phase 2 deadline?
After the deadline, invoices issued by businesses in scope without Phase 2 integration are not legally valid under Saudi tax law. Buyers cannot claim input VAT credit on these invoices. ZATCA has demonstrated active enforcement — conducting over 15,000 compliance reviews in July 2025 alone. The penalty waiver that has been extended until June 30, 2026 will end on that date. There is no indication it will be extended further.
What is the PINT AE format required for UAE e-invoicing?
PINT AE (Peppol International for the UAE) is the structured XML invoice format mandated by the UAE Federal Tax Authority. It requires 51 mandatory data fields including seller and buyer Tax Registration Numbers, standardised Unit of Measure codes, and specific invoice classification fields. Invoices must be transmitted through an FTA-accredited Peppol Access Service Provider (ASP) rather than submitted directly to the FTA. Most major ERP platforms — SAP, Oracle, and Microsoft Dynamics — are developing or have released PINT AE format support through their standard localisation frameworks.