Integrating your system with ZATCA e-invoicing: the complete 2026 guide

Phase 1, the generation phase, began on 4 December 2021. It required every VAT-registered business to issue invoices from a compliant electronic system instead of handwritten invoices or Word and Excel files, with a QR code on simplified invoices. In this phase your system does not connect to ZATCA; it only has to issue an electronic invoice with the required fields and store it.

Phase 2, the integration phase, began on 1 January 2023 and is rolled out in waves by revenue size. Your system connects to ZATCA’s Fatoora platform and sends every invoice as a digitally signed XML file. The practical difference is large: a system that prints a correctly formatted invoice is enough for Phase 1, but not for Phase 2 unless it can sign, submit and receive ZATCA’s response.

ZATCA defines the waves by a threshold of VAT-taxable revenue in reference years named in each wave’s announcement, and notifies the businesses in scope at least six months before their deadline. With every wave the threshold drops, bringing smaller businesses into scope.

Wave 25 is the widest yet: announced on 24 July 2026, it covers businesses whose revenue exceeds SAR 187,500, which must complete integration by 1 February 2027. That threshold is close to the voluntary VAT registration threshold, so a very large share of small registered businesses now face a near deadline.

Integration is not a button added to your software but a set of requirements the invoicing system must meet. Understanding them helps you assess any quote you receive, and tells you whether your current system can be integrated at all.

ZATCA provides a developer portal and a simulation environment where the system is tested before connecting to production. Good testing is not one successful invoice; it covers every case that happens in your real business: a B2B invoice and a B2C one, a discount, a credit note for a return, an exempt or zero-rated item, a foreign-currency invoice, and an internet outage mid-submission.

Most post-launch problems come from untested cases: customers without a valid VAT number, rounding that differs between the total and the line items, or a POS that works offline and submits its invoices late. So budget time for testing in your plan, and do not make the wave deadline your first day live.

The first route is an off-the-shelf cloud accounting and invoicing package that includes Phase 2. It is the fastest and cheapest for a small business with no other system, and Phase 2 is usually in the mid-tier plans rather than the cheapest. Its drawback is that it imposes its own way of working, so if your sales and stock live in another system you will enter data twice.

The second route is integrating your current system, whether a POS, a custom system or an ERP, directly with Fatoora or through an approved provider’s API. This keeps your team’s way of working, but requires a system that can still be developed and whose code someone owns. The third route is a new ERP or quotation and invoicing system with the integration built in, best when integration is a chance to move off Excel or legacy software anyway.

At FortuneCode we do not treat e-invoicing as an afterthought but as part of every system that issues invoices: ERP systems, quotation and invoicing systems, and sales and booking systems. The invoice logic is designed from the start around Phase 2 requirements and tested in the simulation environment before go-live, so you never discover after launch that your system needs rebuilding.

When you have an existing system we are working on or connecting to your other systems, we assess whether it can be integrated as part of the project scope, and the written quote states what the integration covers and how long it takes. The scope and contract are written before we start, the code and accounts belong to your company, and the delivery date is written into the contract with on-time delivery guaranteed and fast technical support after go-live.

Start early. The deadline is the date for full operation, not the date to start thinking. This list sums up what you need to do, in order:

The first mistake is leaving it to the last month, when providers are swamped, prices rise and testing time shrinks. The second is assuming a system is “compliant” because it prints a QR code; that is a Phase 1 requirement, while Phase 2 needs signing, submission and receiving ZATCA’s response.

The third is forgetting side sources of invoices: an online store, a POS in one branch, or manual invoices for a major client. Every source that issues tax invoices must go through integration. The fourth is integrating a system whose code you do not own and whose developer no longer supports it, so the integration breaks at ZATCA’s first update and nobody can fix it.

The cheapest quote is not always the best value. Ask every provider to answer the same questions in writing; they reveal the difference between real integration and cosmetic integration: