ZATCA E-Invoicing & Compliance
End-to-end ZATCA Phase 2 e-invoicing implementation and Saudi regulatory compliance — ensuring your business meets all Zakat, Tax and Customs Authority requirements with automated invoice generation, validation, QR code integration, and real-time reporting to the Fatoorah platform.
Book a Free ConsultationWho must comply with ZATCA Phase 2, and by when?
ZATCA Phase 2, the integration phase of Saudi e-invoicing, requires taxpayers to connect their invoicing systems to ZATCA's Fatoora platform. It has been rolled out since 1 January 2023 in waves of taxpayer groups, and ZATCA notifies each group of its wave at least six months in advance. Standard tax invoices are cleared by Fatoora before they reach the buyer, and simplified invoices are reported within 24 hours; Mantiqi confirms your wave and deadline, then connects your existing ERP so invoices come back signed and QR-coded.
Typical timeline: 4–6 weeks for one ERP and one legal entity; 8–12 weeks for multi-entity deployments.
Why this matters
ZATCA Phase 2 is being made mandatory in waves across Saudi Arabia. Under the e-invoicing violations and fines ZATCA published in November 2021, failing to issue e-invoices starts at a SAR 5,000 fine and deleting or amending one after issuance at SAR 10,000, rising with repeat violations to as much as SAR 50,000 — on top of invoice rejection by your customers' AP teams. Your existing accounting system probably wasn't designed for real-time clearance, cryptographic stamps, and Fatoorah's strict UBL 2.1 schema — retrofitting it without breaking your day-to-day invoicing is the hard part. Mantiqi handles the integration so your finance team keeps issuing invoices the way they always have, while ZATCA gets the compliant XML behind the scenes.
What We Deliver
How we deliver
- 01
Wave & readiness audit
Week 1We confirm your ZATCA wave (your turnover band determines your integration deadline), audit your current invoicing flow, and produce a compliance gap-list with concrete remediation steps.
- Wave eligibility confirmation
- Current-state invoicing audit
- Gap-list against Phase 2 requirements
- Recommended integration architecture
- 02
Sandbox integration
Weeks 2–4We build the integration against ZATCA's sandbox environment — generating UBL 2.1-compliant XML, applying cryptographic stamps, embedding QR codes, and exercising both clearance (B2B) and reporting (B2C) flows end-to-end.
- Sandbox-certified integration
- Cryptographic stamp + CSID flow
- QR-code-rendered PDF invoices
- ERP / accounting connector code
- 03
Production cutover
Week 5Production CSIDs issued, Fatoorah onboarding completed, full invoice population tested under load. We run parallel for one billing cycle so you can compare ZATCA-cleared invoices against your historical baseline before going live.
- Production CSID issuance
- Fatoorah portal onboarding
- Parallel-run reconciliation
- Go-live runbook + rollback plan
- 04
Compliance support
OngoingMonitoring dashboard tracking clearance success, rejection codes, and signed-document storage. We patch against ZATCA schema updates within their published grace windows so you never wake up to a broken integration.
- Compliance dashboard with rejection-code drilldown
- ZATCA schema-update SLA
- Quarterly audit-ready export
- Direct line to our compliance engineer
Frequently asked questions
Your wave is set by your prior-year revenue. ZATCA publishes targeted waves on a rolling basis with ~6 months' notice per wave. The first 30 minutes of our engagement is spent confirming your wave and your specific integration deadline against the latest ZATCA bulletin — book the readiness assessment below if you're unsure.
No. ZATCA Phase 2 is an integration layer that sits between your existing ERP and Fatoorah. We build a connector so invoices generated in your current system get cleared by ZATCA in real time, returned with the cryptographic stamp + QR code, and stored as legally-signed PDFs. Your finance team doesn't change tools.
For a typical mid-sized business with one ERP and a single legal entity, full implementation runs 4–6 weeks from kick-off to production cutover. Multi-entity / multi-region deployments take 8–12 weeks. The gating constraint is usually ZATCA sandbox throughput on their side, not engineering on ours.
ZATCA publishes schema changes with a 30–60 day grace window. We monitor their developer portal and ship integration patches within the window, before your invoices start failing. Clients on our compliance support tier never have to think about this.
Yes — that's a baseline requirement of every ZATCA-compliant invoice we ship. Customer-facing PDFs render in both languages with correct RTL layout for the Arabic side; the underlying UBL XML carries the dual-language fields ZATCA validates against.
Still have questions?
Our team is ready to help. Reach out and we'll get back to you as soon as possible.
Free offer
Free 30-min ZATCA Phase 2 Readiness Assessment
We'll confirm your wave, audit your current invoicing flow, and send you a written gap-list against Phase 2 requirements — no sales pitch, no obligation. If you're already compliant, we'll tell you that and you owe us a coffee.
Book free assessment