ZATCA Wave 25: The 1 February 2027 Compliance Deadline for Saudi Micro-Businesses — What You Must Do Now
SAR 187,500 threshold, voluntary VAT filers in scope, Fatoora Phase 2 checklist, and how Odoo automates B2B clearance and B2C reporting before the deadline.
The Zakat, Tax and Customs Authority (ZATCA) has reached a decisive milestone in the rollout of Phase 2 (Integration Phase) of the Fatoora e-invoicing framework. Wave 25 establishes a statutory compliance deadline of 1 February 2027, targeting businesses whose taxable turnover exceeded SAR 187,500 in 2022, 2023, 2024, or 2025.
Why is Wave 25 unprecedented? Because SAR 187,500 is the voluntary VAT registration threshold in the Kingdom of Saudi Arabia. Previous waves brought large corporations, mid-tier enterprises, and standard SMEs into the Fatoora portal. Wave 25 reaches deep into the micro-business sector — including boutique consultancies, medical and dental clinics, single-outlet retail shops, specialized contractors, and independent professionals registered for VAT. If you fall into this bracket, passive invoice generation is no longer compliant.
Who is in Scope for ZATCA Wave 25?
Inclusion in Wave 25 is evaluated strictly against historic VAT return filings reported to ZATCA. You do not determine eligibility yourself — the Authority pulls your declared taxable supplies directly from your submitted returns across four evaluation years.
Key criteria qualifying a taxpayer for Wave 25 include:
- Taxable revenue exceeded SAR 187,500 in any single calendar year among 2022, 2023, 2024, or 2025.
- The taxpayer possesses an active VAT registration certificate issued by ZATCA.
- The business issues either Tax Invoices (B2B/B2G transactions) or Simplified Tax Invoices (B2C retail/consumer transactions).
Wave 24 vs. Wave 25: How the Requirements Shift
While the underlying technical schema (Saudi UBL 2.1 XML) remains identical, the operational realities between Wave 24 (mid-2026) and Wave 25 (early 2027) represent a major cultural shift for affected businesses.
| Feature / Criterion | Wave 24 (2026) | Wave 25 (2027) |
|---|---|---|
| Revenue Threshold | SAR 375,000+ | SAR 187,500+ |
| Statutory Deadline | 30 June 2026 | 1 February 2027 |
| Target Profile | Standard SMEs, wholesale traders | Micro-businesses, clinics, voluntary registrants |
| Typical Invoicing System | Legacy desktop ERP or accounting tool | Manual spreadsheets, standalone POS, or cloud apps |
| Technical Compliance Obligation | Full API integration with Fatoora | Full API integration with Fatoora |
What Phase 2 Integration Actually Demands
Many small business owners assume that producing a PDF invoice with a square QR code satisfies ZATCA. That was Phase 1 (Generation Phase). Phase 2 (Integration Phase) invalidates standalone PDF generation. Your system must converse directly with ZATCA's API servers in real time.
- Clearance Model for B2B/B2G: Every standard tax invoice issued to another business or government entity must be transmitted to ZATCA first. The Authority validates the XML, embeds a cryptographic stamp and clearance watermark, and returns it. Only cleared invoices can legally be shared with the buyer.
- Reporting Model for B2C: Simplified invoices issued to retail consumers or patients are generated and handed to the buyer immediately, but must be cryptographically reported to ZATCA via API within 24 hours of issuance.
- Cryptographic Stamp (CSID): Your ERP must hold a valid Production CSID generated from a private key uniquely identifying your solution unit. Unsigned or improperly signed invoices are rejected automatically.
- Cryptographic Hash Chaining: Each invoice must contain the SHA-256 hash of the immediately preceding invoice, creating an immutable cryptographic chain that prevents invoice backdating or sequence deletion.
The Step-by-Step Odoo Go-Live Sequence for Wave 25
For businesses utilizing Odoo Enterprise, the technical framework is pre-engineered within the official Saudi localization modules (l10n_sa and l10n_sa_edi). Execution requires a disciplined 5-step deployment path:
- Master Data Audit: Verify your company's official legal name (matching the Commercial Registration), 15-digit VAT number, National Address details (Building number, Street, District, Postal Code), and partner classification.
- Electronic Invoicing Configuration: Configure the Saudi Electronic Invoicing journal in Odoo Accounting, ensuring correct tax grid mapping for 15% standard VAT, zero-rated supplies, and exempt transactions.
- CSR Generation & Fatoora Portal Onboarding: Generate the Certificate Signing Request (CSR) directly from Odoo. Log in to the ZATCA Fatoora portal using your digital credentials, generate an Onboarding OTP, and exchange it for a Compliance CSID.
- Compliance Simulation Checks: Execute the mandatory simulation checks required by ZATCA (standard invoice clearance, simplified invoice reporting, debit note, and credit note test cycles) until all 4 checks return a SUCCESS status.
- Production CSID Activation & Automated Crons: Upgrade to the Production CSID. Verify that the automated background cron job is active to reliably transmit B2C simplified invoices to ZATCA within the 24-hour statutory boundary.
Need Rapid Phase 2 Onboarding for Wave 25?
iWesabe has connected over 200 Saudi businesses to the ZATCA Fatoora portal without a single compliance infraction. We handle CSR generation, schema validation, and live onboarding in days.
Four Costly Mistakes Micro-Businesses Make with Wave 25
Based on our fieldwork assisting businesses through Waves 1 through 24, small enterprises frequently stumble on the same avoidable operational hurdles:
- Assuming 'Phase 1 PDF' is Enough: Using an off-the-shelf billing app that only prints QR codes will trigger non-compliance penalties once your wave date passes. The QR code must contain the cryptographic signature generated during live API interaction.
- Incomplete Buyer VAT and Address Data: B2B invoices reject automatically if the buyer's 15-digit VAT number fails algorithm verification or if the mandatory national address fields are missing from the XML envelope.
- Postponing Onboarding to January 2027: During the final weeks before a wave deadline, ZATCA's simulation environments and support desks face peak traffic. Generating OTPs and troubleshooting validation warnings is far smoother months in advance.
- Manual Reporting of Simplified Invoices: Failing to configure automated server cron jobs means retail and clinic transactions pile up unsubmitted, violating the 24-hour statutory reporting requirement.
Wave 25 marks the final transition of Saudi Arabia's commerce into a fully transparent, digitally verified economy under Vision 2030. For businesses with turnover exceeding SAR 187,500, adopting an ERP like Odoo is not merely a tax compliance necessity — it is an upgrade that unifies your sales, accounting, inventory, and customer relationships on a single platform.
Prepare Your Business for ZATCA Wave 25 Today
Schedule a 30-minute readiness session with an iWesabe ZATCA integration specialist. We audit your existing accounting workflow and deliver a step-by-step Wave 25 roadmap.
Frequently Asked Questions
What is the revenue threshold for ZATCA Wave 25?
What is the official deadline for Wave 25 compliance?
Does Odoo handle both B2B clearance and B2C reporting automatically?
What penalties exist for missing the Wave 25 deadline?

iWesabe Editorial Team
Practitioner insights on Odoo ERP, ZATCA compliance, and Saudi enterprise digital operations — written by iWesabe's consulting, finance, and engineering teams.
Related Articles
ZATCA Wave 24: The 30 June 2026 SME Compliance Deadline — What You Must Do Now
SAR 375,000 threshold, 20-day window, Fatoora go-live checklist, and how Odoo-powered Saudi businesses can complete Phase 2 Integration before the deadline.
Odoo ERP for ZATCA Phase 2 e-Invoicing: The 2026 Compliance Playbook for Saudi Arabia
Wave schedule, Fatoora clearance mechanics, XML + cryptographic stamp, production CSID path, rejection diagnostics, and the audit-defence chain that keeps Saudi businesses ZATCA-clean.
ZATCA Phase 2 Rejection Errors in Odoo ERP: Causes, Fixes & Troubleshooting Guide
An exhaustive technical and financial troubleshooting guide for Saudi CFOs, financial controllers, and IT administrators resolving clearance failures, cryptographic stamp mismatches, and hash chaining errors in Odoo ERP.
Explore Related Solutions
Financial Management
Automate your Saudi Arabia accounting — ZATCA Phase 2 e-invoicing, VAT returns, Zakat provisioning, multi-currency bank reconciliation, and real-time financial reporting — all inside one connected Odoo platform. Fully localised for KSA and the GCC by iWesabe.
ExploreRetail Management ERP
From the POS counter to the back-office ledger — Odoo Retail connects point of sale, multi-store inventory, customer loyalty programmes, and ZATCA e-invoicing in one real-time platform. Configured for Saudi Arabia's retail market by iWesabe.
ExploreSupply Chain Management
From purchase order to final delivery — Odoo Supply Chain connects procurement, multi-warehouse inventory, demand forecasting, and vendor management into one real-time platform. Purpose-configured for Saudi Arabia and the GCC by iWesabe.
ExploreCRM & Customer Relationship Management
Turn every lead into a closed deal. Odoo CRM gives your sales team a structured Kanban pipeline, automated follow-up sequences, and a 360° customer view — all connected natively to Accounting, Inventory, and Email Marketing.
Explore