Invoice number
The unique identifier the seller gives its invoice; field 1 in both of the Ministry’s lists.
The mandatory-fields list describes it as a unique identification of the invoice. In the document it is cbc:ID directly under the Invoice or CreditNote root.
It is not the same as the UUID: the Ministry’s guidelines describe the UUID as a 128-bit number generated in addition to the invoice’s sequential number, so the document carries both.
| Identifier | IBT-001 |
|---|---|
| Path in the document | /Invoice/cbc:ID |
| Cardinality | 1..1 |
| Data type | Identifier |
| Applies to | Tax invoice and Commercial invoice |
In JooDax
BuiltJooDax writes the number in cbc:ID and refuses the document when it is blank, naming the gap by its number in the Ministry’s list (1). The same number becomes the file name in the ASP’s folder, with every character other than letters, digits and the hyphen replaced by an underscore. 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
- UAE Electronic Invoice Mandatory Fields (vV 1.1) — Ministry of Finance, United Arab Emirates
- 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)
- 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.