Introduction: The New Era of Saudi Tax Compliance
Saudi Arabia's Zakat, Tax and Customs Authority (ZATCA) has transformed the Kingdom's commercial ecosystem with the mandate of Fatoora (E-Invoicing). While Phase 1 (Generation Phase) introduced basic digital invoicing and QR codes, Phase 2 (Integration Phase) mandates real-time system-to-system integration with ZATCA servers.
Whether you run a multi-branch retail network, a manufacturing facility, or a fast-paced restaurant chain, compliance with ZATCA Phase 2 is not just a regulatory obligation—it is a core business requirement.
In this guide, we break down everything you need to know about ZATCA Phase 2, key technical requirements, common pitfalls, and how WaslaSoft ERP provides instant, hassle-free compliance.
Key Pillars of ZATCA Phase 2 (Integration Phase)
Phase 2 imposes strict technical standards on Electronic Invoice Generation Solutions (EIGS):
1. Two-Tiered Invoice Architecture
- B2B Standard Invoices (Tax Invoices): Must be transmitted to ZATCA in real time for Clearance before being issued to the customer.
- B2C Simplified Invoices: Must be issued instantly to consumers with a mandatory Phase 2 compliant QR code, and reported to ZATCA within 24 hours.
2. Cryptographic Stamps & Digital Signatures (CSID)
Each POS unit or ERP server must onboard with ZATCA's portal to obtain a unique Cryptographic Stamp Identifier (CSID) certificate. Invoices are cryptographically signed using SHA-256 hashing to prevent tampering.
3. XML / UBL 2.1 Standard Syntax
Invoices can no longer be plain PDFs or text receipts. They must follow ZATCA’s strict XML schema (UBL 2.1 standard) with embedded Universal Unique Identifiers (UUID) and previous invoice hashes (PIH) for sequential integrity.
ZATCA Phase 2 Requirements Checklist
| Requirement | B2B Standard Invoice | B2C Simplified Invoice |
|---|---|---|
| XML UBL 2.1 Format | Mandatory | Mandatory |
| Cryptographic Stamp (CSID) | Mandatory | Mandatory |
| Phase 2 QR Code | Optional (Recommended) | Mandatory |
| Clearance Deadline | Real-time (Instant API call) | N/A |
| Reporting Deadline | N/A | Within 24 hours |
| Buyer VAT Identification | Mandatory | Optional |
4 Costly Mistakes Businesses Make During ZATCA Onboarding
- Relying on Legacy Software Patches: Trying to retrofit non-Arabic or legacy desktop POS software often leads to API timeouts and failed invoice clearances during peak store hours.
- Ignoring Sequential Hash Chaining (PIH): ZATCA requires every invoice to reference the SHA-256 hash of the preceding invoice. A single missing invoice breaks the chain and invalidates subsequent transactions.
- Manual Certificate Renewal: CSID certificates expire. Solutions that require manual renewal risk sudden invoice clearance rejections.
- Poor Offline Support: Internet disruptions occur. If your solution cannot queue simplified B2C invoices offline and auto-sync within ZATCA’s 24-hour window, you face compliance penalties.
How WaslaSoft ERP Solves ZATCA Phase 2 Compliance
WaslaSoft ERP was built natively for Saudi Arabian tax regulations and financial compliance.
Native Integration & Auto-Onboarding
WaslaSoft connects directly to ZATCA’s Fatoora portal with automated OTP onboarding. Generate your CSID certificates with a single click.
Sub-Second Invoice Clearance
Our lightweight API engine generates the required UBL 2.1 XML, signs the document, and clears B2B invoices with ZATCA in under 400 milliseconds.
Resilient Offline Engine for Retail & POS
Keep selling even when your internet drops. WaslaSoft stores offline B2C transactions securely with local cryptographic hashing and auto-submits them the moment connectivity returns.
Built-in Audit Trail & Rejection Monitoring
View live ZATCA transmission status on your dashboard. Receive immediate notifications if ZATCA flags warning codes or validation errors.
Conclusion: Get Fully Compliant with WaslaSoft
Don't wait for your revenue wave deadline. Transitioning to a certified, native ZATCA Phase 2 solution eliminates tax risks, modernizes your operations, and protects your business from penalties.
