ZATCA E-Invoicing Phase 2: Complete Integration Guide for Saudi Businesses

Saudi Arabia's ZATCA e-invoicing programme, known as Fatoora, is mandatory for every VAT-registered business. Phase 1 required structured electronic invoices with a QR code. Phase 2, the integration phase, goes further: your billing or ERP system has to connect to ZATCA's platform so that invoices are cleared or reported electronically. Finance and IT need to start months before your wave date to avoid disrupting sales.

Phase 1 vs Phase 2

Phase 1 (generation): issue invoices electronically with the mandatory fields and a QR code, and store them in the required XML/PDF format. Handwritten or plain PDF invoices are no longer valid.

Phase 2 (integration): your system connects to ZATCA through its API. Standard tax invoices (B2B) need clearance: ZATCA validates the invoice before you share it with the buyer. Simplified invoices (B2C) are reported within 24 hours of issue. Map your B2B and B2C mix early, because the two follow different flows.

Which wave are you in?

ZATCA brings taxpayers into Phase 2 in waves based on VAT-subject revenue. ZATCA announced Wave 25 of Phase 2 (integration) e-invoicing on 24 July 2026. It applies to taxpayers whose VAT-subject revenue exceeded SAR 187,500 in any year from 2022 to 2025, with an integration deadline of 1 February 2027. ZATCA notifies each taxpayer of its wave, but always confirm your own date on zatca.gov.sa rather than relying on a third party.

Pre-integration checklist

- Confirm your integration wave deadline on zatca.gov.sa - Assign a project owner in finance with IT support - Clean master data: customer VAT numbers, product tax categories, units of measure - Check whether your ERP or POS is natively compliant, or select an integrator - Plan how you'll issue credit notes, debit notes and amended invoices

Technical integration steps

1. Onboard your devices or solution units and obtain cryptographic stamp identifiers (CSIDs) through the Fatoora portal
2. Configure your ERP, accounting system or POS, with a solution provider if it isn't natively compliant
3. Test in the ZATCA sandbox with standard invoices, simplified invoices, credit notes, exports and exempt supplies
4. Go live before your wave deadline and monitor rejection codes daily for the first 30 days
5. Train finance and sales teams on credit notes, debit notes and how to reissue a rejected invoice

Sandbox testing

Cover every invoice type you actually issue. Document each rejection code and the fix. Don't move to production until clearance and reporting tests pass consistently.

Common rejection reasons

Invalid or missing buyer VAT numbers, wrong tax category codes, expired certificates, clock or timezone mismatches, missing supply dates and the wrong invoice type (standard vs simplified) cause most production rejections.

Penalties

ZATCA publishes penalties for e-invoicing violations, including failing to integrate by the deadline and issuing non-compliant invoices. Treat Fatoora as part of your billing critical path, not an optional IT project.

Go-live and monitoring

Plan go-live on a low-volume day. Check the first 100 production invoices manually, and keep a ZATCA specialist available for the first month.

ISZ Global can shortlist vetted ZATCA e-invoicing consultants in Riyadh, Jeddah and Dammam for gap analysis, solution selection, sandbox testing and go-live support. Tell us your ERP and wave date and we'll introduce you to the right advisor, free of charge.