Skip to content
E-invoicing in Saudi Arabia (FATOORA)

Local test mode in the JooDax programs

Until the business onboards its device with ZATCA, the programs stamp documents with a self-signed certificate and print them with a QR code, sending nothing anywhere.

This mode belongs to the JooDax programs; it is not a ZATCA term. When a Saudi company is set up, the programs create a local issuing unit, a secp256k1 key and a self-signed certificate named JooDax-Test valid for five years, so documents come out in full phase-2 form from the first minute, with hash, counter, stamp and a nine-tag QR.

The stamp is not ZATCA's, though: no ZATCA certificate authority issued the certificate, and tag 9 is a self-signature. Such documents carry the status "local", are never sent, and ZATCA's tools will not verify their stamp.

When the business onboards its device (OTP, compliance certificate, production certificate) a new unit starts a new chain at counter 1 and the local unit stops. Documents issued locally stay "local" and are not reported, so the mode suits the time before the business must integrate, not after.

In JooDax

Built

Built and tested: the tests check that local mode issues a correct chain and sends nothing. Nothing in the programs claims that this mode, or acceptance by the developer sandbox, is ZATCA certification.

crates/jdx-app/src/setup.rs

Questions and answers

Is a locally stamped document accepted by ZATCA?

No. It is a phase-2-format document stamped with a self-signed certificate, and it was never sent to ZATCA.

Related pages

Related concepts

E-invoicing in Saudi Arabia (FATOORA)

Sources

  1. Security Features Implementation Standards to the E-Invoicing resolution dated 2023-05-19 (v1.2) — ZATCA

Checked on: 4 November 2026. What concerns JooDax is taken from the programs’ own code.