ZATCA E-Invoicing and SAP: What Your ERP Team Needs to Know in 2026

For businesses operating in Saudi Arabia, the Integration Phase of e-invoicing is no longer a future roadmap item. It is a live, enforced regulatory reality. Wave 23 recently brought businesses with revenues exceeding SAR 750,000 into the fold, requiring full Fatoora platform integration by March 31, 2026.

The next major milestone is Wave 24. With a lower revenue threshold of SAR 375,000, this wave enforces compliance by June 30, 2026. This deadline is bringing thousands of additional Saudi enterprises into a mandatory scope that carries significant stakes. Non-compliance is not a minor administrative hurdle; it can result in penalties of up to SAR 50,000 per violation.

If your organization runs on SAP, the most critical realization for 2026 is that ZATCA Phase 2 is not a simple tax configuration change. It is a complex ERP integration project. It requires a fundamental shift in how your SAP system communicates with external government portals, turning invoice issuance into a real-time data exchange. This transformation impacts everything from master data governance to middleware architecture.

What ZATCA Phase 2 Requires From Your SAP System

Phase 2 or Integration Phase is about your SAP system having the capability to make API calls directly to ZATCA’s Fatoora portal. This new model replaces Phase 1 in which generating and storing a QR code was enough.

Technical Requirements for SAP Teams

Compliance will require your SAP functional and technical leads to consider a few fundamental elements:

• API Integration: It is mandatory that your system can connect to the Fatoora portal securely and professionally. Digital certificates and cryptographic stamps for each transaction handling are part of this. This is not a one-time activity; if the certificates expire, the service will be disrupted, so they have to be renewed and managed regularly.
• XML and PDF/A-3 Formats: Invoices can no longer be simple PDFs. They must be generated in a specific XML format (UBL 2.1) or as a hybrid PDF/A-3 file that embeds the XML data within the visual document. This requires precise mapping of SAP fields to the ZATCA standard.
• Cryptographic Stamping (UUID): Every invoice must include a Universally Unique Identifier (UUID), a cryptographic stamp, and a sequential counter that prevents backdating or tampering. This ensures the integrity of the national tax ledger.
• The Clearance vs. Reporting Flow:
  • B2B Invoices (Clearance): These must be sent to ZATCA in real-time. The portal clears the invoice and returns it with a digital stamp before it can be legally shared with the buyer.
  • B2C Invoices (Reporting): These are issued to the consumer immediately, but the data must be reported to the Fatoora portal within 24 hours of issuance.

S/4HANA DRC vs. ECC Middleware

Your SAP version is the key factor that determines the method you adopt to meet these requirements. If you have S/4HANA, SAP offers the Document and Reporting Compliance (DRC) solution. This is a centralized platform dedicated to managing local electronic documents and statutory reporting requirements.

It is the most efficient way to achieve compliance as it is integrated out of the box and gets updates regularly as ZATCA regulations change.

However, if your company still uses SAP ECC or Business One, you are faced with more challenges. These older versions not only do not support Phase 2 compliance out-of-the-box, but they also need specialized connectors or middleware (such as SAP PI/PO or SAP Integration Suite) to connect to the Fatoora portal as an example. The ZATCA integration effort is proving to be a significant factor for many ECC users to justify their S/4HANA migration.

The Coordination Challenge: Finance vs. IT

The main reason why many ZATCA projects fail is the lack of coordination within the organization. As electronic invoicing is a tax requirement, quite a lot of companies hand over this task to the Finance department at first. Finance teams can interpret the tax mandate and the VAT rules, but they probably do not have the technical skills required for SAP API integration, XML schema mapping, or digital certificate security:

Similarly, if the project is entirely handed over to IT, they may fix the technical aspects but overlook the VAT accounting logic for various transaction types such as exempt supplies, zero-rated exports, or nominal supplies.

Those enterprises which designate ZATCA as a joint finance and IT workstream are the ones achieving their deadlines. Such a case needs a bridge role, an SAP Functional Consultant who understands both tax and ABAP, making sure that the financial information sent to ZATCA is not only legally accurate but also technically compliant. Without this coordination, you may have a technically perfect transmission of wrong tax data, which later could result in audits.

Why Talent Is the Bottleneck

The surge in Wave 23 and 24 deadlines has created a massive spike in demand for SAP talent specifically experienced in ZATCA integrations. Companies that already have embedded SAP functional consultants and integration architects are navigating these waves smoothly. They have the internal capacity to test the Fatoora API calls and adjust their document types without external help.

However, organizations trying to hire these specialists mid-wave are finding a very dry market. This talent squeeze is exacerbated by the broader SAP S/4HANA migration wave currently sweeping the Kingdom. The same professionals needed to secure your ZATCA compliance are often the same ones needed to manage your 2027 ECC-to-S4 migration.

Besides that, since ZATCA is a Saudi Arabia specific requirement, the talent must have a very proven Middle East experience in particular. For example, a consultant who has implemented e-invoicing in Europe or Latin America will still have a very difficult time figuring out the exact Fatoora portal requirements and Saudi tax law. The double push of global SAP demand versus local regulatory expertise is causing a rise in costs and longer project lead times.

Getting Ready for Wave 24 (July 1, 2026)

If your enterprise is considered Wave 24, or if you are still in the process of stabilizing after Wave 23, these four measures are essential:

• Evaluate Readiness Without Delay: Find out if your current SAP version supports the DRC framework or if you have to finance third-party middleware and connectors. Often, postponing this evaluation results in last-minute hardware or license expenditures.
• Engage Technical Talent Early: Do not wait until May to look for an integration architect. Securing a specialist who has already successfully delivered a Phase 2 project in KSA is the best way to avoid trial and error on your production system. These professionals are currently booking out months in advance.
• End-to-End Testing: ZATCA provides a “Sandbox” environment for Fatoora. Your team must run exhaustive end-to-end tests, not just for standard sales, but for credit notes, debit notes, and cross-border transactions. Real-world scenarios, such as system downtime or API timeouts, should also be tested to ensure your business continuity isn’t impacted by a technical glitch.
• Audit Your Master Data: ZATCA integration often fails because of dirty data. Incomplete VAT numbers, incorrect addresses, or missing mandatory fields in your SAP customer master records will cause the API call to be rejected by the government portal. Cleaning your master data is a non-technical task that takes significant time and should start immediately.

Conclusion 

ZATCA Phase 2 compliance is non-negotiable, and the June 30, 2026, deadline for Wave 24 is approaching faster than many ERP teams realize. While the regulatory pressure is high, the solution is purely technical.

By aligning your Finance and IT teams and securing the right SAP expertise early, you can move from a state of compliance urgency to a state of operational stability. In 2026, the businesses that succeed in the Kingdom are those that view ZATCA not as a tax hurdle, but as a catalyst for a more integrated, digitally mature SAP environment. Compliance is simply the first step toward a more transparent and automated financial future in Saudi Arabia.