Unique identifier number (UUID)
A 128-bit universally unique identifier for each invoice, in addition to its sequential number.
Not in the Ministry’s two lists, but mandatory in PINT AE (1..1) and required by rule IBR-193-AE. The guidelines define it as a 128-bit number generated by an algorithm in the e-invoicing system to distinguish each tax invoice, in addition to its sequential number.
The guidelines’ responsibilities table includes generating a UUID for every e-invoice so that each is uniquely identified and duplicates are prevented.
| Identifier | BTAE-07 |
|---|---|
| Path in the document | /Invoice/cbc:UUID |
| Cardinality | 1..1 |
| Data type | Identifier (128-bit UUID) |
| Applies to | Tax invoice and Commercial invoice |
In JooDax
Partly builtJooDax writes the UUID the caller gives it in cbc:UUID and refuses a blank one (IBR-193-AE); it does not generate one or check its form. The module is not yet wired to the programs’ invoices, and its output has not been through the official Schematron or an ASP’s validation.
crates/jdx-einvoice-ae/src/lib.rs
Related fields
Fields — E-invoicing in the UAE (PINT AE)
Sources
- PINT AE Billing 1.0.4 – Invoice transaction, semantic model (v1.0.4) — OpenPeppol AISBL (docs.peppol.eu)
- PINT AE Billing 1.0.4 – Invoice transaction, syntax binding (v1.0.4) — OpenPeppol AISBL (docs.peppol.eu)
- PINT AE Billing 1.0.4 – AE specific PINT rules (jurisdiction aligned rules) (v1.0.4) — OpenPeppol AISBL (docs.peppol.eu)
- UAE Electronic Invoicing Guidelines (vV 2.0) — Ministry of Finance, United Arab Emirates
Checked on: 4 November 2026. What concerns JooDax is taken from the programs’ own code.