ZATCA E-Invoicing Phase 2: The 2026 Compliance Checklist
The threshold for ZATCA's e-invoicing Phase 2 has been cut in half again. Wave 25, announced in July 2026, brings any business with taxable turnover above SAR 187,500 into scope, with an integration deadline of February 1, 2027. Two waves ago, that threshold was SAR 750,000. The direction is unmistakable: ZATCA is steadily pulling nearly every VAT-registered business in the Kingdom into full system integration, and the businesses still treating this as "not yet my problem" are running out of runway.
Most businesses get this wrong by treating e-invoicing as a software question — buy a compliant system, tick the box. It's actually a data and process question. The technical requirements are specific and unforgiving, and the businesses that scramble in the final weeks before their wave's deadline are almost always the ones that assumed their existing ERP setup would "just work."
What Phase 2 Actually Requires
Phase 2 — officially the Integration Phase — moves beyond Phase 1's requirement to simply generate e-invoices in a structured format. It requires your invoicing system to connect directly to ZATCA's platform, in real time, for every applicable invoice.
The core technical requirements:
- UBL 2.1 XML format — invoices must be generated in this specific structured format, not PDF or a proprietary export.
- Cryptographic stamp and digital signature — every invoice needs a cryptographic stamp issued through your ZATCA-registered device, proving authenticity.
- A UUID (universally unique identifier) generated per invoice.
- An embedded QR code, scannable and containing the required invoice data.
- Secure API connection to ZATCA for real-time clearance or same-day reporting, depending on invoice type.
Clearance vs. Reporting: Know Which Applies
This is where many companies make a costly mistake — assuming all invoices follow the same integration path. They don't.
Clearance (B2B and B2G — standard tax invoices). The invoice must be submitted to ZATCA and approved before it reaches the buyer. If ZATCA doesn't clear it, it isn't a valid invoice yet. This means your invoicing workflow needs a clearance step built in before the document goes out the door — not after.
Reporting (B2C — simplified tax invoices). The invoice is issued to the buyer first, then reported to ZATCA within 24 hours. There's no pre-approval gate, but the 24-hour window is firm.
Businesses that sell through both channels — a distributor with wholesale (B2B) and retail (B2C) arms, for example — need both integration paths working correctly, and it's common to see one path tested thoroughly while the other is left half-configured.
The Wave System: Why Your Deadline Keeps Moving Closer
ZATCA rolls Phase 2 out in waves, each defined by an annual taxable turnover threshold based on 2022, 2023, or 2024 figures. The pattern over the last several waves:
| Wave | Threshold | Deadline |
|---|---|---|
| Wave 23 | Above SAR 750,000 | 31 March 2026 |
| Wave 24 | Above SAR 375,000 | 30 June 2026 |
| Wave 25 | Above SAR 187,500 | 1 February 2027 |
Each wave roughly halves the threshold from the one before it. If your business wasn't in scope for Wave 23 or 24, it's worth checking your turnover against Wave 25 now rather than waiting for ZATCA's direct notification — by the time notifications go out broadly, the compliance clock is already running.
The Compliance Checklist
- Confirm your wave and deadline. Check your taxable turnover for 2022, 2023, and 2024 against the current threshold — you're in scope if any one of those years exceeds it.
- Confirm your invoicing solution is ZATCA-compliant, not just "e-invoicing capable." Many systems generate structured invoices but haven't been certified for the cryptographic stamp and API integration ZATCA requires.
- Separate your B2B/B2G and B2C invoice flows and confirm each connects to the correct integration path — clearance for one, reporting for the other.
- Test the clearance flow under real volume, not just a handful of sample invoices. Clearance failures at scale (API timeouts, malformed XML on edge-case invoices) surface only under real transaction volume.
- Assign ownership of the 24-hour B2C reporting window. This is a process failure point as often as a technical one — someone needs to own it operationally, not just configure it once.
- Reconcile invoices cleared through ZATCA against your VAT return. A cleared invoice and a correctly declared VAT return are two different things — integration doesn't replace reconciliation.
What Happens If You Miss the Deadline
E-invoicing non-compliance carries its own penalty track, separate from VAT filing and payment penalties — starting at SAR 1,000 and scaling up to SAR 50,000, doubling on repeat violations. Unlike VAT filing penalties, these apply per violation instance, which means a business issuing non-compliant invoices daily accumulates exposure daily, not just once at the deadline.
Frequently Asked Questions
What is the current e-invoicing threshold under ZATCA's Phase 2 rollout? As of Wave 25, businesses with taxable turnover above SAR 187,500 in 2022, 2023, or 2024 are in scope, with an integration deadline of February 1, 2027.
What's the difference between Phase 1 and Phase 2 e-invoicing? Phase 1 requires generating structured e-invoices with a QR code. Phase 2 adds direct, real-time integration with ZATCA's platform — invoices must be cleared or reported through a secure API connection, not just generated in the right format.
Do B2C invoices need ZATCA's approval before being issued? No. B2C simplified invoices follow the reporting path — issued to the buyer first, then reported to ZATCA within 24 hours. Only B2B and B2G standard invoices require pre-approval (clearance).
How do I know which wave my business falls into? Your wave is determined by your taxable turnover in 2022, 2023, or 2024 against ZATCA's published threshold for each wave — check the highest of those three years against the current threshold.
What format do Phase 2 e-invoices need to be in? UBL 2.1 XML, with a cryptographic stamp, a unique UUID, and an embedded QR code — a PDF invoice, even a well-formatted one, does not meet the requirement.
Are the penalties for e-invoicing non-compliance the same as VAT filing penalties? No. E-invoicing penalties run on a separate track — SAR 1,000 to SAR 50,000, doubling for repeat violations — independent of the VAT filing and payment penalties under the VAT Law.
Key Takeaway
The threshold has halved twice in the space of a year, and the pattern points toward near-universal coverage. Whether or not your business has received a direct notification, the responsible move is to check your turnover against the current wave now, get the clearance and reporting flows tested under real volume, and build reconciliation between cleared invoices and your VAT return into your standard process — not as a one-time integration project, but as an ongoing operational habit.