ZATCA e-invoicing (Fatoora): what your system needs to handle

What ZATCA e-invoicing is

The Zakat, Tax and Customs Authority (ZATCA) introduced e-invoicing, known as Fatoora, to replace paper and manually prepared invoices with structured electronic ones. It applies to businesses registered for VAT in Saudi Arabia, and it covers tax invoices as well as credit and debit notes.

For a business, the practical effect is simple to state: invoices must come out of a system, in a defined format, with defined security features, and in the integration phase that system must exchange invoices with ZATCA.

The two phases

E-invoicing was introduced in two phases:

• Phase 1, Generation (from 4 December 2021): invoices must be generated and stored electronically by a compliant solution. Handwritten invoices and invoices typed in a word processor are no longer accepted, and simplified invoices carry a QR code.
• Phase 2, Integration (from 1 January 2023, in waves): the invoicing system must be integrated with ZATCA's Fatoora platform. Businesses are brought in by groups based on revenue, and ZATCA notifies each group in advance of its deadline.

Standard and simplified invoices: clearance and reporting

The integration phase treats the two invoice types differently. Standard tax invoices, used between businesses and with government, follow a clearance model: the invoice is sent to ZATCA, validated and stamped, and only then shared with the buyer.

Simplified tax invoices, used for sales to consumers, follow a reporting model: you give the invoice to the customer immediately and report it to ZATCA within 24 hours. Credit and debit notes follow the model of the invoice they relate to.

What your system must be able to do

In the integration phase, the software that issues your invoices needs to handle these technical requirements, which ZATCA publishes in its e-invoicing specifications:

• Produce invoices in the required structured format (XML based on UBL 2.1, or PDF/A-3 with the XML embedded).
• Give each invoice a unique identifier and chain it to the previous one with a hash.
• Generate the QR code and apply the cryptographic stamp.
• Be onboarded with ZATCA so each invoicing unit receives its cryptographic stamp identifier.
• Send standard invoices for clearance before sharing them, and report simplified invoices within 24 hours.
• Handle rejections and warnings, and let your team correct and resubmit.
• Include the required invoice content, in Arabic, with other languages alongside if you need them.
• Store issued invoices securely for the retention period the regulations require.

Three ways to comply

Most businesses take one of three routes. The right one depends on where your invoices are created today.

• Use accounting or ERP software that supports ZATCA integration out of the box. This is simplest when all invoices come from one system that already has it.
• Connect your existing system to a specialised e-invoicing provider. Your system creates the invoice data; the provider handles formatting, stamping, clearance and reporting.
• Build a direct integration with the Fatoora platform, using ZATCA's developer portal and SDK. This fits companies with a custom ERP or high volumes, and it needs careful testing and maintenance.

A checklist before your wave

Whatever route you choose, these steps reduce the risk of a difficult switch-over:

• List every place invoices are created: ERP, point of sale, e-commerce, branches and manual processes.
• Clean your master data, especially customer VAT numbers and addresses, which standard invoices require.
• Decide the compliance route for each invoice source.
• Test in ZATCA's simulation environment before going live, including credit notes and rejections.
• Train the team on what happens when an invoice is rejected.
• Confirm your exact obligations and deadline with ZATCA's official guidance and your tax adviser.

If you run a custom system

Custom ERPs, operations platforms and SaaS products that issue invoices need e-invoicing designed into their data model: invoice sequences, hashes, stamps and the clearance status of each invoice are records, not afterthoughts.

When we build finance or operations systems for Saudi businesses, we design for these requirements from the start, and integrate either with the provider your accountants use or directly with Fatoora, after confirming the requirements with your tax advisers.