Saudi Arabia E-Invoicing Wave 24 Readiness Checklist

If you’re advising Saudi clients who only recently crossed the VAT threshold, Wave 24 is now on your critical path. The deadline is fixed, the integration scope is non-negotiable, and ZATCA penalties apply from day one of non-compliance.

This is not another “what is Phase 2” explainer. Below is an accountant-facing, step-by-step Wave 24 readiness checklist — focused on integration timing, vendor coordination, and where implementations usually break.

1. Confirm Wave 24 Applicability — Don’t Assume

Practical impact: This determines whether your client must integrate with ZATCA by 30 June 2026 (4 Dhul Hijjah 1447H approx.) or can legally stay on Phase 1 controls.

ZATCA assigns Phase 2 (Integration Phase) obligations in waves, based primarily on taxable revenue thresholds. For Wave 24, ZATCA has communicated that taxpayers meeting the VAT registration threshold of SAR 375,000 fall within scope, subject to the official notification issued to the taxpayer’s ZATCA portal.

Action steps for accountants:

• Log into the taxpayer’s ZATCA portal and check for a Phase 2 integration notification.
• Do not rely on ERP vendors’ blanket emails — ZATCA notification is decisive.
• If the client crossed SAR 375,000 recently, expect inclusion even if volumes are low.

Canonical source: Always validate against ZATCA announcements and taxpayer notifications at https://zatca.gov.sa.

2. Lock the Integration Deadline — Then Work Backwards

Practical impact: Missing the Wave 24 date exposes the client to penalties per invoice, not per period.

For Wave 24 taxpayers, the integration deadline communicated by ZATCA is 30 June 2026. From 1 July 2026, any non-compliant tax invoice is exposed.

Work backwards with a realistic timeline:

• T–120 days: ERP selection / contract finalised
• T–90 days: Technical onboarding with ZATCA (credentials, sandbox access)
• T–60 days: UAT testing of clearance & reporting flows
• T–30 days: Production cutover readiness

If you start in Q2 2026, you are already late.

3. Validate ERP Eligibility — “Mu’tamad” Is Not Optional

Practical impact: Non-Mu’tamad systems cannot legally integrate, even if technically capable.

ZATCA requires Phase 2 taxpayers to use Mu’tamad (approved) e-invoicing solutions. This applies whether the client uses:

• Tier-1 ERPs (SAP, Oracle)
• Mid-market ERPs (Odoo, Dynamics)
• Local accounting systems

Accountant checks:

• Confirm the ERP or e-invoicing layer appears on ZATCA’s Mu’tamad list.
• Validate which version is approved — upgrades may be mandatory.
• Clarify whether the ERP handles clearance (B2B) and reporting (B2C) natively or via middleware.

Do not assume an ERP used by another client is approved for this one.

4. Master the Technical Requirements That Actually Fail

Practical impact: Most Phase 2 failures are not conceptual — they’re XML, hash, or UUID errors.

Under the ZATCA E-Invoicing Implementing Regulation (notably Articles 53–56), Wave 24 taxpayers must comply with the same core controls as earlier waves.

Key failure points you must test:

• Invoice hash & UUID sequencing: Breaks when invoice series are manually reset.
• XML schema compliance: Arabic/English field handling often fails validation.
• Cryptographic stamp: CSR generation and certificate renewal delays.
• Time synchronisation: Server time drift causes clearance rejection.

Example:

A client issues 1,200 invoices/month. If 5% fail clearance due to UUID duplication, that’s 60 non-compliant invoices — each exposed to penalties.

Accountants should insist on:

• Sandbox clearance testing
• Failed-invoice logs
• Re-submission workflows

5. Align Tax Logic — VAT Errors Are Still Your Problem

Practical impact: ZATCA clears structure, not tax accuracy.

Phase 2 integration does not validate VAT logic beyond basic schema rules. The accountant remains responsible for:

• Correct VAT rates (15%)
• Zero-rated vs exempt classification
• Reverse charge treatment where applicable

Common Wave 24 issue:

Small businesses newly registered for VAT often misclassify supplies. Once integrated, every error is transmitted to ZATCA in real time.

Example:

• Invoice value: SAR 100,000
• VAT incorrectly charged: 0%
• Correct VAT: 15% (SAR 15,000)

The XML clears — but the VAT exposure remains, visible to ZATCA.

6. Run a Pre-Go-Live Accountant Checklist (Use This)

Below is a Wave 24 accountant-facing readiness checklist you should complete before sign-off:

Area	Check	Status
Applicability	ZATCA Wave 24 notification verified	⬜
Deadline	30 June 2026 integrated date confirmed	⬜
ERP	Mu’tamad status validated	⬜
Certificates	CSR generated & production cert issued	⬜
XML	Sample invoices validated	⬜
VAT	Tax logic reviewed & approved	⬜
Controls	Failed invoice reprocessing tested	⬜
Training	Client finance staff briefed	⬜

If you cannot tick all boxes, you are not ready.

7. Prepare for Post-Go-Live — This Is Where Clients Panic

Practical impact: Most client escalations happen after day one.

Wave 24 clients are typically smaller, less system-mature, and more reactive. Expect:

• Rejected invoices in the first week
• Confusion between B2B clearance and B2C reporting
• Pressure to “just issue manually” (which you must stop)

Your role post-go-live:

• Monitor clearance success rates daily for the first 30 days
• Ensure rejected invoices are corrected and re-cleared
• Reinforce that manual invoices outside the system are prohibited

ZATCA’s position on penalties and enforcement is consistently published on its official portal: https://zatca.gov.sa.

Why This Matters for Your Career

Wave 24 is where routine compliance becomes specialist value. Accountants who can manage integration, speak to vendors, and troubleshoot failures will be favoured over those who only file returns.

If you want to pressure-test your understanding, apply these concepts in scenario-based questions here: https://app.superaccountant.in/en/quiz

---

Sharpen your edge with SuperAccountant's next live cohort — small batches, real client workpapers, taught by partners. Details and seats at https://app.superaccountant.in/en/cohort.