E-invoices that reach ZATCA correctly the first time

ZATCA introduced e-invoicing in two phases. The generation phase, which began in December 2021, requires invoices to be created and stored in electronic form, with a QR code on simplified invoices. The integration phase, which started in January 2023, goes further. Your system must connect to the Fatoora platform and send each invoice, and ZATCA announces affected taxpayers in waves.

In this phase an invoice is a structured XML file following the UBL 2.1 standard with ZATCA's field requirements. It carries a cryptographic stamp, a QR code, a unique identifier, a sequence number and a hash of the previous invoice, so the chain cannot be edited quietly. Standard (B2B and B2G) tax invoices are sent to ZATCA for clearance before they are shared with the buyer. Simplified (B2C) invoices are issued to the customer and reported to ZATCA within twenty-four hours.

For you this means three practical needs: software that can produce the XML correctly, a secure way to hold the certificates, and a reliable way to deal with failure. The technical specifications and the sandbox are published by ZATCA, and we build and test against them.

The path depends on what you run. If your ERP is SAP, Odoo or Dynamics 365, there may be a localization you configure and extend. If you run custom billing software, a point-of-sale system or several channels, we build an integration layer that sits beside them, receives invoice data, builds and signs the XML, submits it and returns the result and the QR code.

Onboarding follows ZATCA's sequence. You register the solution units on the Fatoora portal, generate a certificate request, obtain a compliance certificate, run the required sample invoices through the compliance checks, and then obtain the production certificate. We guide each step, and the private keys stay in your control and are stored in a protected key store.

Edge cases take most of the time: credit and debit notes tied to earlier invoices, invoices in foreign currency, discounts and allowances at line and document level, prepayment invoices, zero-rated and exempt supplies, and cancellations. We list the cases you actually issue, write a test for each, and keep the test suite so any later change to your invoicing is checked before release. A typical integration takes three to eight weeks, depending on the number of source systems.

Going live is the start of the work. Fatoora can be briefly unavailable, a customer's tax number can be wrong, and a rounding difference can trigger a validation error. The integration therefore needs a queue, a retry policy and a visible error screen, so finance staff see a rejected invoice and know what to correct.

We set up monitoring that alerts when submissions fail, when the reporting window is near its limit, or when a certificate is close to expiry. Certificate renewal is a known source of surprise outages, so we put it on a calendar and test the renewal before it is needed.

Signed invoices and ZATCA responses are archived and linked to the ledger entry, so an auditor can follow a number from the general ledger to the cleared XML. Under the Personal Data Protection Law, invoices contain customer data, so we document where the archive is stored and who can read it, and we can host the integration inside the Kingdom.