ZATCA Phase 2 E-Invoicing: What Your ERP Must Do
ZATCA's Phase-2 e-invoicing (Fatoora) moved Saudi Arabia from simple PDFs to cryptographically signed, machine-cleared invoices integrated directly with the tax authority. If your ERP can't do this natively, you're exposed. Here's what compliant e-invoicing actually requires.
Clearance vs reporting — know which you need
Standard tax invoices (B2B) must be cleared with ZATCA in real time before they're shared with the buyer. Simplified invoices (B2C) are reported within 24 hours. Your ERP has to route each invoice to the correct flow automatically based on the transaction type.
The technical pieces your ERP must handle
- EGS onboarding: EC keypair, CSR and the compliance/production CSID via OTP
- UBL 2.1 invoice XML generation
- SHA-256 invoice hash and the XAdES digital signature
- The TLV QR code (Phase-2 nine-tag format)
- The PIH hash chain and the ICV counter that link invoices together
Why byte-level correctness matters
ZATCA rejections usually come down to small formatting traps: the decimal certificate serial, XML canonicalization, verbatim certificate extraction, and where the QR timestamp is sourced from. A single wrong byte is the difference between CLEARED and rejected. This is why generic international ERPs often struggle here and a locally-built integration wins.
Build it in, don't bolt it on
E-invoicing should be part of your finance module, not a fragile plugin. IntellaQ Flow implements ZATCA clearance and reporting inside the ledger, so every invoice is signed, QR-stamped and cleared the moment it's issued — with a full audit trail. If you're unsure whether your current system is truly Phase-2 ready, that's a conversation worth having now, not at your next audit.