The UUID in an e-invoice
A 128-bit identifier the device generates for each document, making it globally unique in exchanges with FATOORA.
The Security standard defines the UUID as a 128-bit number that is unique with high probability without consulting a central database, so the device generates it locally with no connection needed.
It goes in cbc:UUID and is sent in the body of the reporting or clearance request together with the hash and the document. Only letters, digits and dashes are allowed.
The UUID is not printed and does not replace the sequential invoice number. A new document after a rejection takes a new UUID.
In JooDax
BuiltA random version-4 UUID per document, unique in the data file.
crates/jdx-einvoice-sa/src/unit.rs
Related pages
- KSA-1 Unique invoice identifier (UUID)
- BT-1 Invoice number
- KSA-16 Invoice counter value (ICV)
- BR-KSA-03 · The document must carry a UUID generated by the issuing machine, made of letters, digits and dashes only.
Related concepts
- Reporting simplified invoices within 24 hoursSending a simplified invoice or note, already stamped and handed to the buyer, to FATOORA within 24 hours of issue.
- The invoice counter (ICV)A number that goes up by one with every document a device issues, never reset or reused, so any gap in the chain shows.
E-invoicing in Saudi Arabia (FATOORA)
Sources
- Security Features Implementation Standards to the E-Invoicing resolution dated 2023-05-19 (v1.2) — ZATCA
- Electronic Invoice XML Implementation Standard to the E-Invoicing resolution dated 2023-05-19 (v1.2) — ZATCA
- E-invoicing Detailed Technical Guidelines (vVersion 2) — ZATCA
Checked on: 4 November 2026. What concerns JooDax is taken from the programs’ own code.