ZATCA E-Invoicing Phase 2 Wave 25: February 2027 Deadline

Your client's ERP is still generating PDF invoices, Wave 25's February 1, 2027 deadline is closer than the calendar suggests, and ZATCA's penalties for non-integration are not hypothetical — they begin from day one of non-compliance. If you are managing the finance function for a business that crossed SAR 187,500 in VATable revenue at any point during 2022–2025, this post is the brief you need to hand your team today.

Who Is Actually in Scope for Wave 25

ZATCA has been rolling out Phase 2 (Integration Phase) in waves since January 2023. Each wave targets a taxpayer cohort defined by their VATable revenue in a reference period. Wave 25 captures taxpayers whose VATable revenue exceeded SAR 187,500 during the calendar years 2022, 2023, 2024, or 2025.

Read that threshold carefully: it is not just the most recent year. If a business crossed SAR 187,500 in any of those four years — even if revenue later fell below that level — it falls within Wave 25's scope. ZATCA communicated this via official announcements on zatca.gov.sa; always verify your client's status against the portal rather than relying on a single year's figures.

Practically, the threshold is low enough to capture the vast majority of VAT-registered businesses in the Kingdom. A small trading company turning over SAR 200,000 in 2023 is as much in scope as a mid-size manufacturer.

Who is NOT in scope:

• Non-resident taxpayers who are VAT-registered but have no establishment in KSA
• Buyers who self-issue invoices under reverse-charge arrangements where the supplier is non-resident
• Taxpayers below the SAR 187,500 threshold across all four reference years (though they may be captured in a future wave)

What Phase 2 Integration Actually Requires

Phase 1 (Generation Phase) — live since December 4, 2021 — required taxpayers to generate structured electronic invoices with a QR code and store them digitally. Phase 2 goes further: it mandates real-time or near-real-time integration with ZATCA's Fatoora platform via API.

Under the ZATCA E-Invoicing Implementing Regulations (the technical and business rules annexed to the VAT Implementing Regulations), Phase 2 imposes two distinct workflows depending on invoice type:

Invoice Type	Fatoora Workflow	Timing Requirement
Standard Tax Invoice (B2B / B2G)	Clearance — invoice must be submitted to Fatoora and receive a ZATCA cryptographic stamp before it is delivered to the buyer	Real-time; cleared invoice only
Simplified Tax Invoice (B2C)	Reporting — invoice is generated and delivered, then reported to Fatoora within 24 hours	Within 24 hours of issuance

This distinction changes your AR workflow materially. For B2B clients, no cleared invoice means no valid invoice — the buyer cannot claim input VAT on an uncleared document. Build that clearance step into the sales order → invoice generation sequence, not as an afterthought.

Technical requirements per the Fatoora portal specifications include:

• UBL 2.1 XML format — ZATCA does not accept PDFs for clearance or reporting
• Cryptographic stamp and QR code generated by a ZATCA-compliant solution
• CSID (Cryptographic Stamp Identifier) obtained by onboarding your ERP or solution to the Fatoora platform
• UUID for every invoice to ensure uniqueness

The February 1, 2027 (7 Rajab 1448H) Hard Deadline

ZATCA announced the Wave 25 go-live date as February 1, 2027 (corresponding to approximately 7 Rajab 1448H). From that date, in-scope taxpayers must route all tax invoices — standard and simplified — through the Fatoora platform integration.

"Go-live" does not mean you start preparing in January 2027. ZATCA's onboarding process for Phase 2 involves:

1. Registering your compliant e-invoicing solution on the Fatoora Simulation Environment
2. Running test transactions and obtaining ZATCA approval
3. Onboarding to the Production Environment and receiving your live CSID
4. Parallel-running your existing invoicing process with the integrated solution

Each of those steps carries lead time. ZATCA's own guidance — published on the Fatoora portal at zatca.gov.sa — recommends beginning the simulation environment testing at least six months before the go-live date, which puts your preparation window opening squarely in August 2026.

If your client is running a Mu'tamad (ZATCA-approved) ERP such as SAP, Oracle, or Microsoft Dynamics with an existing Phase 2 module, your timeline is tighter than you think — configuration, testing, and UAT for a mid-size business routinely takes 12–16 weeks.

The Four Implementation Steps You Cannot Skip

Here is the sequence that actually works in practice, drawn from earlier wave rollouts:

Step 1 — Revenue Verification and Scoping (Do this week) Pull the VAT returns for 2022–2025. Confirm whether total taxable supplies (Box 1 on the VAT return) exceeded SAR 187,500 in any of those years. Document your conclusion in writing. If in scope, escalate to the technology and finance leads immediately.

Step 2 — Solution Selection or Gap Assessment If the client already runs a Mu'tamad ERP, engage the vendor to confirm Phase 2 readiness of the current version. ZATCA maintains a list of approved solutions on its portal. If the client is on a bespoke or legacy system, a middleware/connector approach (API gateway sitting between the ERP and Fatoora) is the most common remediation path. Budget SAR 15,000–80,000+ for implementation depending on transaction volume and system complexity — small businesses often opt for a ZATCA-approved SaaS invoicing tool at SAR 300–800/month.

Step 3 — Fatoora Simulation Environment Testing Register the solution using the Fatoora Developer Portal. Generate test invoices in UBL 2.1 XML. Validate clearance responses (HTTP 200 with stamped XML) and error codes. Common failure points include incorrect VAT registration number formatting, missing mandatory XML fields under ZATCA's business rules, and timestamp mismatches. Do not underestimate this phase — earlier waves saw businesses spend 6–8 weeks in simulation before achieving clean clearance rates.

Step 4 — Production Onboarding and Go-Live Submit the CSID onboarding request for the production environment. Conduct a controlled go-live with a subset of invoice types, monitor the ZATCA portal for rejection rates, and maintain a reconciliation log of cleared vs. reported invoices. The first 30 days post-go-live are the highest-risk period.

Penalties for Non-Compliance

ZATCA's penalty framework under the VAT law and its implementing regulations is not on a sliding scale of goodwill. Failure to comply with Phase 2 integration requirements exposes taxpayers to:

• Fines for non-compliant invoices — issuing an invoice that does not meet e-invoicing requirements can attract a fine per Article 41 of the VAT Implementing Regulations
• Input VAT disallowance — buyers receiving uncleared B2B invoices risk having their input VAT claims rejected on audit
• Reputational risk with government and semi-government buyers who increasingly require cleared invoices as a prerequisite for payment processing

ZATCA has operated a grace-and-correction period in the early weeks of previous waves, but the pattern across Wave 1 through Wave 20+ has been that enforcement tightens after the first 60–90 days. Do not plan around a grace period that may not materialise for Wave 25.

What Your Checklist Should Look Like Right Now

If you are responsible for a client heading into Wave 25, your immediate action list is:

• Confirm scope — review 2022–2025 VAT returns; document the SAR 187,500 threshold check
• Notify client leadership — this is a technology project, not just a tax filing; the IT lead must be in the room
• Audit current invoicing system — does it output UBL 2.1 XML? Is the vendor Phase 2-certified by ZATCA?
• Obtain a project timeline from the ERP vendor or solution provider; push for simulation start by August 2026 at the latest
• Map invoice types — identify which flows are B2B (clearance) vs. B2C (reporting) and document the 24-hour reporting SLA for simplified invoices
• Review AR and AP workflows — clearance must precede delivery for standard invoices; this may require changes to your sales-order-to-cash process
• Train the invoicing team — accounts receivable staff need to understand what a ZATCA rejection code means and how to resubmit
• Set a go-live date of January 1, 2027 — build in one month of buffer before the February 1 hard deadline

Want to check your own readiness on Phase 2 concepts before advising clients? Run through the SuperAccountant knowledge quiz — it covers ZATCA e-invoicing, VAT, and Zakat scenarios calibrated for KSA practitioners.

Common Mistakes from Earlier Waves

The implementation lessons from Waves 1–20 are worth internalising before Wave 25:

Treating it as an IT project only. The finance team owns the UBL XML field mapping (VAT registration numbers, supply type codes, line-item tax categories). IT cannot complete this without detailed input from accountants.

Ignoring credit notes and debit notes. These must also be cleared or reported through Fatoora. Many implementations go-live clean on standard invoices and then generate errors on the first credit note because the reference to the original cleared invoice UUID was omitted.

Assuming the ERP vendor handles everything. Vendors configure the system; your team must validate that the configured output matches actual business transactions — invoice dates, supply descriptions, VAT amounts — before go-live.

Not testing the 24-hour reporting SLA for B2C. Businesses with high B2C volume (retail, F&B, services) need an automated batch-reporting job that runs reliably within the window. A manual upload process will break under volume.

---

The February 1, 2027 deadline is 18 months away — which is exactly the amount of time it takes to do this properly. Businesses that start in Q3 2026 will be scrambling; those that start now will go live clean.

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?utm_source=blog&utm_medium=cta&utm_campaign=accountants.