ZATCA E-Invoicing

ZATCA e-invoicing is Saudi Arabia’s phased e-invoicing program, rolled out by the Zakat, Tax and Customs Authority in waves by business revenue. Its Integration Phase requires structured XML invoices, QR codes, and digital signatures cleared in real time.

How ZATCA e-invoicing works

The program moved in two broad stages. The first, often called the Generation Phase, ended paper and free-form PDF invoices: invoices had to be produced by a compliant electronic system in a structured format with the required fields. The second, the Integration Phase, connects that system to the authority itself. Standard tax invoices are submitted for clearance before they reach the buyer, and simplified invoices are reported shortly after issue. Taxpayers were brought into the Integration Phase in waves, largest revenue bands first, with each wave notified ahead of its onboarding window.

The practical requirements are structural rather than cosmetic: an XML document following the mandated schema, a cryptographic stamp, a UUID, an invoice hash chaining each document to the one before it, and a QR code carrying the core fields. That chaining is what makes the invoice population tamper evident.

Why it matters beyond tax

Once invoices are structured and cleared, the tax file stops being the only consumer. The same XML carries the counterparty, line detail, VAT treatment, and timestamp for every sale, which is exactly the grain a revenue model needs. Finance teams that treat clearance as a compliance chore end up rebuilding the same data by hand from ERP exports later. Teams that treat cleared invoices as a first-class source get a revenue feed that a tax authority has already seen, which is a stronger starting point than a spreadsheet extract.

The failure mode is drift. Invoices are cleared in one system, revenue is recognized in another, and the two are reconciled quarterly at best. By the time a variance surfaces, the underlying documents are months old and nobody remembers which version of the export was used.

How Rexfin handles it

Rexfin ingests ZATCA-cleared e-invoice data as one more filed source document: extracted, reconciled against the ledger, and cited the same way a bank statement or ERP export is, never presented as a ZATCA accreditation. Every figure that traces back to a cleared invoice keeps a link to it, so a reconciliation question has an answer at the document level. The same handling applies to structured invoice formats elsewhere, including Peppol documents and E-Rechnung in Germany.