Saudi Arabia ZATCA E-Invoicing Integration for SAP

Saudi Arabia’s e-invoicing regime, run by the Zakat, Tax and Customs Authority (ZATCA), is in its integration phase: taxpayers are being connected to the central FATOORA platform in turnover-based waves, and the thresholds now reach small businesses. SAP teams should confirm which wave applies and what the integration deadline means for invoice generation, validation, and operational monitoring.

How should SAP integrate with Saudi Arabia ZATCA?

An SAP–ZATCA implementation should separate document generation, cryptographic and security requirements, clearance or reporting exchange, authority responses and operational monitoring. The correct design depends on the applicable ZATCA phase, taxpayer wave, document type and SAP release, so teams should validate current specifications before building or activating a solution.

Executive Summary

Mandate name	Saudi Arabia ZATCA e-invoicing (FATOORA)
Current status (as of July 2026)	Phase 1 (generation) mandatory since December 2021. Phase 2 (integration with FATOORA) rolling out in waves since January 2023, from the largest taxpayers downwards. Wave 23 had a 31 March 2026 deadline. For Wave 24, ZATCA identified taxpayers whose VAT-subject revenue exceeded SAR 375,000 in 2022, 2023 or 2024 and required notified taxpayers to integrate by 30 June 2026. ZATCA notification is decisive; later waves require a fresh official check.
Who is affected	Phase 2 applies through taxpayer waves. A business is in scope for a specific wave when it meets that wave’s published conditions and receives the relevant ZATCA notification.
Model	Clearance for standard (B2B) tax invoices — cleared by FATOORA in real time before sharing with the buyer; simplified (B2C) invoices are reported within 24 hours. Invoices are UBL-based XML with cryptographic stamps, hashes, and QR codes.
Business risk	Invoice rejection, reporting gaps, integration failures, and audit-trail issues.
SAP impact	SD billing, FI invoices, tax codes, XML generation with hash/counter chain, QR data, certificate handling, and authority workflow.
Recommended next step	Confirm the applicable wave and deadline, then run a technical review of invoice scenarios and integration assumptions.

What Is the Requirement?

Phase 2 is not a document-format change but a systems integration: the invoicing solution must register with FATOORA (onboarding with cryptographic stamp identifiers), maintain an unbroken invoice counter and hash chain, and follow the clearance flow for standard invoices and the 24-hour reporting flow for simplified invoices. B2B invoices that fail clearance are not valid tax invoices, which puts real-time error handling in the critical path of billing.

Business Impact for Finance and Tax Teams

Teams need accurate invoice data, controlled validation, and clear monitoring of clearance and reporting status. The distinction between standard and simplified invoice flows — with different timing and technical treatment — needs to be reflected in process design, not handled ad hoc.

How This Impacts Your SAP Environment

• Invoice, tax, and customer data must be complete and mapped to the ZATCA XML structure, including Arabic-text requirements where applicable.
• The hash chain and invoice counter impose sequencing constraints on how SAP-generated invoices are processed.
• Clearance rejections need an owner and a correction process that keeps billing moving.
• Certificates and cryptographic stamp management affect Basis and security planning.

How S4FN Supports ZATCA Compliance

S4FN can review SAP source data, invoice mapping, validation workflow, authority communication assumptions, and exception handling for ZATCA readiness.

Primary Source and Verification

Verified on: 10 July 2026. Wave eligibility and the integration deadline must be confirmed from the taxpayer’s ZATCA notification and the latest official wave notice.

• ZATCA — Phase 2 Wave 24 announcement