ZATCA Phase 2 E-Invoicing (FATOORA)
The Zakat, Tax and Customs Authority integration phase in Saudi Arabia requiring real-time XML invoice clearance and cryptographic reporting for all enterprise B2B and B2C transactions.
In enterprise ERP systems, ZATCA Phase 2 E-Invoicing (FATOORA) is defined as: The Zakat, Tax and Customs Authority integration phase in Saudi Arabia requiring real-time XML invoice clearance and cryptographic reporting for all enterprise B2B and B2C transactions. In Great ERP by Greatzern Consulting, ZATCA Phase 2 E-Invoicing (FATOORA) is handled natively across interconnected double-entry financial, supply chain, and manufacturing ledgers without third-party middleware.
ZATCA Phase 2 (the 'Integration Phase' of Saudi Arabia's FATOORA e-invoicing initiative) mandates that enterprise ERP and accounting platforms integrate directly with ZATCA's API platform. Standard B2B invoices require real-time clearance (pre-validation by ZATCA before issuance to buyers), while simplified B2C tax invoices require cryptographic stamping and reporting within 24 hours.
Achieving ZATCA Phase 2 compliance requires specialized cryptographic capabilities: generating UBL 2.1 XML invoices compliant with Saudi tax rules, computing SHA-256 invoice hashes, embedding ECDSA cryptographic stamps, and maintaining an immutable cryptographic invoice counter. Non-compliant systems face heavy administrative fines and operational suspension in the Kingdom.
- Attempting to use legacy ERP systems that cannot generate UBL 2.1 compliant XML structures.
- Failing to sequence invoice counters immutably, resulting in rejected hash chain validations.
- Missing Arabic language and Gregorian/Hijri date metadata requirements on fiscal invoices.
Cryptographic Verification, JSON/XML Payload Schema, and Tax Authority Validation
Tax authorities require absolute cryptographic non-repudiation, tamper-evident chaining, and exact sub-penny tax rounding for transactions under ZATCA Phase 2 E-Invoicing (FATOORA). Below is the step-by-step audit trail generated when an enterprise records a commercial B2B sales invoice of $85,000.00.
| Audit Step / Payload Tag | Technical Specification | Validation Constraint | Compliance Output & Verification Code |
|---|---|---|---|
| Taxable Net Assessment | $85,000.00 Base Value | Line-by-line item taxability check | Accrued to Output VAT / Sales Tax Ledger |
| Statutory Tax Application | Standard Rate (16% / 15% / 20%) | Zero-rated exemptions mapped to HS Codes | Computed Tax Liability: $13,600.00 (Total: $98,600.00) |
| Cryptographic Hash Chaining | SHA-256 Canonical Digest | Chained to Previous Invoice Hash (N-1) | Digest: 7f83b1657ff1fc53b92dc18148a1d65dfc2d... |
| Digital Signature & CSID | ECDSA secp256k1 / RSA-2048 | Authority public key verification check | Signed with Hardware Security Module (HSM) Token |
| QR Code & Transmission Status | Base64 TLV Encoded String | Direct REST/eTIMS/ZATCA API handshake | HTTP 200 OK — Clearance Certificate Issued in 320ms |
Under statutory regimes governing ZATCA Phase 2 E-Invoicing (FATOORA), issuing an unverified or out-of-sequence invoice can trigger severe non-compliance penalties, vendor invoice rejections, and corporate tax audits. Great ERP guarantees 100% automated synchronization: invoices cannot be finalized or printed without receiving synchronous cryptographic clearance from the national revenue system.
In Great ERP, ZATCA Phase 2 E-Invoicing (FATOORA) is modeled natively via the `tax_zatca_phase_2_e_in` database table. The architecture enforces strict foreign key constraints, composite index optimization on querying fields, and optimistic concurrency locking (`version_id`) to prevent race conditions during high-volume batch postings.
| Column Name | SQL Type | Nullable | Architectural Specification & Constraints |
|---|---|---|---|
| id | BIGINT UNSIGNED | NO | Primary statutory transmission record identifier |
| invoice_id | BIGINT UNSIGNED | NO | Foreign key referencing commercial sales_invoices(id) |
| tax_authority_code | VARCHAR(32) | NO | \'KRA_ETIMS\', \'ZATCA_P2\', \'HMRC_MTD\', \'DATEV\' |
| payload_hash | CHAR(64) | NO | SHA-256 cryptographic digest of canonical document body |
| previous_hash | CHAR(64) | NO | Immutable predecessor invoice hash chaining audit trail |
| qr_code_payload | TEXT | NO | Base64 TLV encrypted string for mobile auditor verification |
| status | ENUM | NO | \'pending\', \'transmitted\', \'cleared\', \'rejected_error\' |
- Cascade Referential Integrity: Foreign key linkages reject orphaned records and automatically block illegal deletions when child transactions exist.
- High-Throughput Composite Indexing: B-Tree indexes on `(tenant_id, created_at, status)` deliver sub-5ms query response times even across tables exceeding 10M rows.
- Immutable Audit Logging: Triggers replicate all state modifications to a write-only audit log table, satisfying ISO 27001 and SOX Section 404 requirements.
Successful adoption of ZATCA Phase 2 E-Invoicing (FATOORA) requires rigorous adherence to multi-disciplinary governance across finance, inventory control, and IT systems:
Policy Baseline & Stakeholder Alignment
Review existing organizational workflows for ZATCA Phase 2 E-Invoicing (FATOORA). Establish standard operating tolerances, sign-off limits for controllers and shop-floor managers, and eliminate non-standard spreadsheet approximations.
Schema Configuration & Master Data Sanitization
Purge obsolete items, duplicate vendor records, and inaccurate cost values. Configure Great ERP\'s settings to enforce automated validation rules for ZATCA Phase 2 E-Invoicing (FATOORA) upon data entry.
Sandbox Simulation & Parallel Reconciliation
Simulate edge cases: partial order receipts, supplier price variances, multi-currency currency fluctuations, and year-end audit adjustments. Verify that ledger outputs balance perfectly.
Departmental Training & Cutover Execution
Conduct role-based workshops for finance, inventory, and operations teams. Execute the cutover protocol over a scheduled maintenance window with complete rollback contingency plans.
Hypercare Monitoring & Automated Governance
Great ERP\'s background scheduled jobs continuously monitor ZATCA Phase 2 E-Invoicing (FATOORA) metrics. Any unposted batch, unexpected variance, or delayed approval triggers instant alerts to designated system administrators.
Statutory Mandate: Strict matching of revenues with incurred expenses and transparent valuation of asset holdings.
Great ERP Enforcement: Great ERP applies automated accrual accounting and perpetual inventory valuation so that ZATCA Phase 2 E-Invoicing (FATOORA) adheres strictly to statutory international accounting principles without manual year-end book entries.
Statutory Mandate: Segregation of duties (SoD), immutable audit trails, and non-repudiation of administrative overrides.
Great ERP Enforcement: No single user can create and self-approve transactions relating to ZATCA Phase 2 E-Invoicing (FATOORA). Every ledger posting records user ID, client IP, timestamp, and before/after database snapshots.
Statutory Mandate: Tamper-proof digital archiving, cryptographic invoice chaining, and real-time electronic reporting.
Great ERP Enforcement: Great ERP natively implements cryptographic SHA-256 chaining and secure REST APIs for seamless transmission to national revenue systems, eliminating audit penalties.
Great ERP includes native ZATCA Phase 2 certified XML generation, cryptographic invoice chaining, QR code generation, and direct API clearance for Saudi Arabian enterprises.
What is the difference between ZATCA Phase 1 and Phase 2?
Phase 1 (Generation Phase) only required generating electronic invoices with QR codes, whereas Phase 2 (Integration Phase) mandates direct API clearance and cryptographic reporting with ZATCA servers in XML format.
Does Great ERP support Arabic language invoices for ZATCA?
Yes, Great ERP provides bilingual English/Arabic invoice templates compliant with all ZATCA Phase 2 display guidelines.
How does Great ERP prevent human error and reconciliation discrepancies in ZATCA Phase 2 E-Invoicing (FATOORA)?
Great ERP replaces manual spreadsheet tracking with automated database constraints and real-time ledger synchronization. Transactions relating to ZATCA Phase 2 E-Invoicing (FATOORA) cannot be posted if debits do not equal credits or if mandatory operational parameters are missing. This completely eliminates end-of-month reconciliation discrepancies.
Can ZATCA Phase 2 E-Invoicing (FATOORA) be configured to support multi-branch and multi-currency operations?
Yes. Great ERP natively supports multi-company, multi-branch, and multi-currency environments. Operations involving ZATCA Phase 2 E-Invoicing (FATOORA) automatically record foreign exchange gains or losses based on live central bank exchange rates while maintaining sovereign local currency books for statutory tax authorities.
What is the typical timeframe required to implement and validate ZATCA Phase 2 E-Invoicing (FATOORA) in an existing business?
Because Great ERP provides pre-configured industry templates and chart of accounts, standard configuration of ZATCA Phase 2 E-Invoicing (FATOORA) typically requires 5 to 10 business days, including historical data sanitization, sandbox parallel testing, and key stakeholder training.
How does Great ERP's ZATCA Phase 2 E-Invoicing (FATOORA) integration differ from legacy tier-1 ERPs like SAP or NetSuite?
Unlike legacy platforms that require expensive external consultants, third-party middleware connectors, and recurring per-seat subscription surcharges, Great ERP delivers native, fully-integrated ZATCA Phase 2 E-Invoicing (FATOORA) capabilities out of the box with zero per-user licensing fees and full database ownership.
Related ERP Modules
Applicable Industries
5-Year TCO & Savings Simulator
Compare your current ERP expenditure against Great ERP's predictable flat model.
Calculate Your ROI