Unique invoice identifier (UUID)
A 128-bit identifier the invoicing solution generates for each document so that it is unique worldwide.
The UUID is a technical identifier generated by the issuing device, not a number the seller chooses. It identifies the document in exchanges with the FATOORA platform and is sent with every reporting or clearance request alongside the hash.
BR-KSA-03 requires it and allows only letters, digits and dashes; the rule notes that Windows calls it a GUID. The data dictionary example is 3cf5ee18-ee25-44ea-a444-2c37ba7f28be.
A rejected document that is corrected and sent again is a new document: the technical guidelines say the UUID and counter value of a rejected document must not be reused.
| Identifier | KSA-1 |
|---|---|
| Path in the document | /Invoice/cbc:UUID |
| Cardinality | 1..1 |
| Data type | Identifier |
| Applies to | Standard tax invoice and Simplified tax invoice |
In JooDax
BuiltEach document gets a random version-4 UUID when it is issued, and the data file refuses duplicates.
crates/jdx-einvoice-sa/src/unit.rs
Applies to
| Tax invoice | Debit note | Credit note | Simplified | Simplified debit | Simplified credit |
|---|---|---|---|---|---|
| Mandatory | Mandatory | Mandatory | Mandatory | Mandatory | Mandatory |
Rules that check it
- BR-KSA-03 · The document must carry a UUID generated by the issuing machine, made of letters, digits and dashes only.
Related fields
Fields — E-invoicing in Saudi Arabia (FATOORA)
Sources
- Electronic Invoice XML Implementation Standard to the E-Invoicing resolution dated 2023-05-19 (v1.2) — ZATCA
- Electronic Invoice Data Dictionary to the E-Invoicing resolution dated 2023-05-19 (v1.2) — ZATCA
- E-invoicing Detailed Technical Guidelines (vVersion 2) — ZATCA
- الضوابط والمتطلبات والمواصفات الفنية والقواعد الإجرائية اللازمة لتنفيذ أحكام لائحة الفوترة الإلكترونية (قرار المحافظ رقم 62738 وتاريخ 1443/11/23هـ) (vfile dated 20230519 (decision 62738)) — ZATCA
Checked on: 4 November 2026. What concerns JooDax is taken from the programs’ own code.