ZATCA E-Invoicing in Saudi Arabia 2026: The Complete Fatoorah Compliance Guide

If you're running a business in Saudi Arabia and haven't integrated your invoicing system with ZATCA yet — time is running out.

The Zakat, Tax and Customs Authority (ZATCA) is rolling out Phase 2 of the Fatoorah e-invoicing system in successive waves. Each wave covers a new group of businesses. If your turn arrives and you're not ready, penalties start at SAR 5,000 and can reach SAR 50,000 per violation.

This guide covers everything: technical requirements, timeline, common mistakes, and a practical preparation checklist.

What is E-Invoicing (Fatoorah)?

E-invoicing is a procedure that converts paper invoice issuance into an electronic process. An electronic invoice isn't just a PDF or scanned image — it's a structured XML document that's generated, transmitted, and processed electronically.

Phase 1 vs Phase 2

Bottom line: Phase 1 was "generate an e-invoice." Phase 2 is "connect your system directly to ZATCA and submit every invoice for validation."

Who Must Comply?

Every VAT-registered business in Saudi Arabia — no exceptions (except non-resident taxpayers).

The Waves — Is It Your Turn?

ZATCA rolls out Phase 2 in waves based on revenue thresholds:

Important: ZATCA notifies each business 6 months before their wave deadline. If you've received notification — start preparing immediately.

💡 Haven't received a notification yet? Waves continue until all VAT-registered businesses are covered. Check your ZATCA portal account regularly.

Phase 2 Technical Requirements

This is where business owners need a developer or solution provider.

1. Invoice Format (UBL 2.1 XML)

Every invoice must be generated in Universal Business Language (UBL) 2.1 XML format:

• Precisely defined fields (seller name, tax ID, line items, tax amounts)
• Standardized coding (currency codes, country codes, tax codes)
• Schema validation before submission

2. Cryptographic Stamp

Every invoice requires a digital signature using a ZATCA-issued certificate:

• Generate a Certificate Signing Request (CSR) from your system
• Register the device on ZATCA's portal to obtain the certificate
• Sign every invoice with the private key
• Embed the signature in the invoice XML

3. QR Code

The QR code must contain TLV (Tag-Length-Value) encoded data:

• Seller name
• Tax identification number
• Invoice date and time
• Invoice total (including VAT)
• VAT amount
• Digital signature (Phase 2)

4. ZATCA API Integration

Your system must connect to ZATCA's APIs:

# Key endpoints
POST /compliance/invoices    — Compliance check
POST /invoices/reporting     — Reporting (B2B tax invoices)
POST /invoices/clearance     — Clearance (B2C simplified invoices)

• Tax invoices (B2B): Reported to ZATCA within 24 hours
• Simplified invoices (B2C): Require real-time clearance before sharing with the customer

Need help integrating with ZATCA? At Noqta, we help businesses build professional API integrations. Whether you're using an off-the-shelf system or a custom solution — our team builds the technical integration from scratch.

Get ZATCA integration support →

Types of Electronic Invoices

Tax Invoice

Typically issued between businesses (B2B). Includes:

• Tax ID for both seller and buyer
• Full line item details
• Itemized tax amounts
• Phase 2: Reported to ZATCA (no real-time clearance required)

Simplified Tax Invoice

Typically issued from business to consumer (B2C). Includes:

• Seller's tax ID only
• Mandatory QR code
• Phase 2: Requires real-time clearance from ZATCA before delivery to customer

Penalties — What Happens If You Don't Comply?

Note: Fines are calculated per non-compliant invoice — not once. If you issue 100 invoices without QR codes, you could face a fine on each one.

Preparation Checklist: 10 Practical Steps

Step 1: Check Your Status

• Log in to the ZATCA portal
• Check if you've received a Phase 2 notification
• Identify your wave deadline

Step 2: Assess Your Current System

• Does your accounting/invoicing system support UBL 2.1 XML?
• Does it support digital signatures?
• Does it have APIs for external system integration?

Step 3: Choose Your Implementation Path

Option A: Update your current system (if it's extensible)

Option B: Purchase a ready-made compliant solution

Option C: Build a custom solution (for complex systems or special requirements)

Step 4: Register on the Developer Portal

• Create an account on ZATCA's developer portal
• Use the sandbox environment for testing
• Don't start directly in production

Step 5: Generate Your Digital Signing Certificate

• Generate a CSR from your system
• Register the device on ZATCA's portal
• Receive and securely store the certificate

Step 6: Develop the Integration

• Build an XML generator per UBL 2.1 specifications
• Implement digital signing
• Build QR code generation in TLV format
• Program ZATCA API connectivity

Step 7: Test in Sandbox

• Submit test invoices to the compliance endpoint
• Fix errors (most common: encoding errors and XML structure issues)
• Ensure 100% of test invoices pass

Step 8: Request Official Compliance Check

• Submit a batch of test invoices via the Compliance API
• Receive compliance confirmation from ZATCA

Step 9: Go to Production

• Activate the integration in the live environment
• Monitor each invoice's status (accepted / rejected / needs correction)

Step 10: Monitor and Fix

• Track submitted invoice statuses daily
• Fix any rejected invoices immediately
• Maintain complete records for 6 years

Common Mistakes (and How to Avoid Them)

❌ Mistake 1: "PDF Is Enough"

No. An electronic invoice is not a PDF. It must be a structured XML document.

❌ Mistake 2: Waiting Too Long

ZATCA gives you 6 months from notification. Building the technical integration takes 2-4 months minimum. Don't wait.

❌ Mistake 3: Skipping the Sandbox

Many businesses build the integration and go live directly. Result: rejected invoices and fines. Use the sandbox first.

❌ Mistake 4: Not Securing Certificates

The digital signing certificate is sensitive. If you lose it, you need to re-register.

❌ Mistake 5: Forgetting Credit Notes

Credit notes and debit notes are subject to the same e-invoicing requirements.

How to Choose an E-Invoicing Solution Provider

Key Criteria

1. ZATCA-certified — Check the solution providers directory
2. UBL 2.1 support — Not just PDF or image generation
3. Open API — For integration with your other systems (ERP, accounting)
4. Built-in digital signing — You don't want to build this yourself
5. Arabic support — For handling ZATCA queries

Popular Solutions

• Enterprise: SAP, Oracle — Native ZATCA support
• Mid-market: Odoo, Zoho Books — Via add-ons
• Saudi-native: Cleartax, Salla (for e-commerce)
• Custom build: When no off-the-shelf solution fits

FAQ

Is e-invoicing mandatory for all companies?

Yes, for every VAT-registered business in Saudi Arabia. Phase 1 (generation) has been enforced since December 2021. Phase 2 (integration) rolls out in waves.

How much does ZATCA integration cost?

It depends on your system. If you use SAP or Odoo, updates may be free or low-cost. Custom builds range from SAR 5,000 to SAR 50,000 depending on complexity.

What if I issue fewer than 100 invoices per month?

Volume doesn't matter — the requirements are the same. But ready-made solutions are usually more cost-effective for small businesses.

Can I use Excel to issue electronic invoices?

No. Excel doesn't produce structured XML or support digital signatures. You need a compliant invoicing system.

What happens with rejected invoices?

You need to fix the issue and resubmit. Simplified (B2C) invoices that are rejected must not be shared with the customer before clearance.

Does integration cover credit and debit notes?

Yes. Every financial document (invoice, credit note, debit note) is subject to the same requirements.

Conclusion

E-invoicing in Saudi Arabia is not optional — and every day of delay brings you closer to penalties. The good news: preparation isn't complicated if you start early and choose the right path.

Your next steps:

1. Check your status on the ZATCA portal
2. Assess your current system's readiness
3. Start implementation (or get specialized help)

Need a technical team to build your ZATCA integration? At Noqta, we deliver system integration and API projects. Our team based in Tunisia serves companies across Saudi Arabia and the Gulf — competitive pricing, high quality.

Start your ZATCA integration with Noqta →

Related Articles

• AI Agents for Business Automation 2026 — How AI agents can automate invoicing workflows
• AI Agent Readiness Playbook for MENA SMEs — Digital transformation roadmap
• API-First Development: Why Every Successful Project Starts with the API — The same methodology used for ZATCA integration