ZATCA E-Invoicing (Fatoora): What It Means for Your ERP in Saudi Arabia

If you run a VAT-registered business in Saudi Arabia, your invoices are no longer just documents — they are structured data that the Zakat, Tax and Customs Authority (ZATCA) expects in a specific format, and in many cases wants to receive or clear electronically. The e-invoicing program, known as Fatoora, has changed what an "invoicing system" or ERP must do, and companies that treated it as an accounting detail have paid for it in fines, rejected invoices, and rushed migrations.

This guide explains the requirements in business terms, what they mean for the system you use or are planning to build, and how to decide between adapting your current software and moving to a compliant custom or ready-made ERP. Regulations evolve, so treat this as orientation and confirm current details with ZATCA or your tax advisor before implementation.

Phase 1 — Generation (in force since December 2021). Businesses must generate and store invoices electronically using a compliant system rather than handwritten or simple Word/Excel documents. Simplified invoices (B2C) must carry a QR code, invoices must include the required fields, and the system must not allow tampering — for example, no deleting issued invoices without a proper credit note.

Phase 2 — Integration (rolled out in waves since January 2023). Businesses are notified by ZATCA, in waves based on annual revenue, that their systems must integrate directly with the authority's platform. From that point, tax invoices (B2B) are sent to ZATCA for clearance before they are shared with the customer, and simplified invoices are reported within 24 hours. Invoices must be in a specific XML format, carry cryptographic stamps, and include a unique identifier and counter.

Each wave brings smaller companies into scope, so a business that was only in Phase 1 last year may be in Phase 2 next year. A system designed for Phase 2 from the start avoids a second migration.

Whether you use a ready-made package or a custom system, it must be able to:

For an ERP this touches sales, point of sale, accounts receivable, returns, and reporting — not just the "print invoice" button.

• Produce invoices in the required structure — all mandatory fields (seller and buyer details, VAT numbers, line items, VAT breakdown, totals) in the ZATCA-specified XML format, with a human-readable PDF/A-3 version that embeds the XML.
• Generate compliant QR codes on simplified invoices, containing the mandated fields in the required encoding.
• Apply cryptographic stamps and hashes — each invoice is signed and chained to the previous one, so gaps and tampering are detectable.
• Integrate with ZATCA's platform for clearance (B2B) and reporting (B2C) once your wave begins, including onboarding the device or solution with the authority.
• Handle credit and debit notes correctly — corrections must reference the original invoice; deletion is not an option.
• Store invoices securely for the required retention period, with audit logs.
• Keep working when the connection to ZATCA fails, queueing and retrying without losing invoices.

• Treating e-invoicing as a template change. Adding a QR code to an old invoice layout does not make the system compliant; the underlying data structure and integrity controls matter.
• Multiple disconnected systems. A POS in the shop, Excel in the office, and an accounting program that re-enters everything by hand produce mismatched invoices and reporting gaps.
• No plan for Phase 2. Companies wait for the notification, then discover their software vendor cannot integrate — and have weeks to move.
• Manual corrections. Staff editing or deleting invoices to fix mistakes, which breaks the invoice chain.
• Ignoring bilingual requirements. Invoices must be in Arabic (English can be added); many international systems get this wrong.

Ready-made systems that are widely used in Saudi Arabia have generally built Phase 1 and Phase 2 support, and for a standard trading or services company they can be the fastest route to compliance. The questions to ask are whether the vendor is actively maintaining ZATCA integration, whether the system fits your actual processes, and what per-user licensing costs at your size.

A custom ERP makes sense when your operations are specific — project-based contracting, manufacturing with complex costing, multi-branch retail with custom loyalty, or a business model that off-the-shelf software forces you to bend. In that case, compliance is designed into the system: the invoicing module produces ZATCA-format documents, applies stamps and QR codes, and integrates with the platform, while the rest of the system reflects how you actually work. We discuss the broader trade-off in custom ERP vs. off-the-shelf.

Either way, compliance should be verified, not assumed. Ask any vendor to show a ZATCA-cleared invoice from a live client.

• Is the system on ZATCA's compliant solutions list, or does the vendor demonstrate Phase 2 integration on real invoices?
• Does it generate the XML format, PDF/A-3, QR codes, stamps, and the invoice counter automatically?
• How are credit notes, returns, and partial refunds handled?
• Does it support Arabic invoices with optional English, and SAR with correct VAT rounding?
• What happens offline or when ZATCA's platform is unreachable?
• Does it connect to your POS, e-commerce store, and bank so invoices are not re-entered?
• Who maintains the integration when ZATCA updates its specifications?

Done properly, e-invoicing is an opportunity. Because every sale becomes structured data, you get real-time revenue and VAT reporting, cleaner receivables, fewer disputes with customers, and an audit trail that makes the annual VAT return straightforward. Companies that connect invoicing to inventory, CRM, and projects in one system — the point of an ERP — stop reconciling spreadsheets and start seeing the business as it happens.

Our ERP and CRM systems for Saudi clients are designed with the Fatoora requirements in the invoicing module from day one: compliant document structure, QR codes, stamps and chaining, credit-note workflows, Arabic/English invoices in SAR, and integration readiness for Phase 2 — connected to sales, inventory, and reporting so nothing is entered twice. If you already have a system, we can audit it against the requirements and either adapt it or plan a migration. See also our guide to choosing a software company in Saudi Arabia and our Saudi Arabia services page.