Receipt UUID
The SHA-256 fingerprint of the serialized receipt, computed by the point of sale itself and written into the receipt.
It is not a random number: the ETA calls it a system-level unique key generated from the receipt’s content. The Receipt Issuance FAQ gives the steps: include every field, the previous receipt’s UUID from the same POS among them; leave the receipt’s own UUID empty; serialize the receipt into one line; hash it with SHA-256; and turn the 32 bytes into 64 hexadecimal characters.
The ETA checks that it is 64 characters derived from the serialized receipt and that it differs from any old-receipt reference. Because the previous receipt is part of the input, this field links the receipts of each POS in a chain.
| Identifier | header.uuid |
|---|---|
| Path in the document | $.receipts[*].header.uuid |
| Cardinality | 1..1 |
| Data type | SHA-256 hash as 64 hexadecimal characters |
| Applies to | E-receipt |
In JooDax
BuiltJooDax computes the hash from the canonical form with the field empty, in lower case, then writes it into the receipt; a test checks that emptying the field and hashing again gives the same value. The code comment and the country matrix call emptying the field "how implementers read it, unconfirmed", while step 3 of the ETA’s FAQ says to leave the receipt’s UUID empty; the official text supports the code’s method, and practical proof waits for a first acceptance. The module is not yet wired to the point-of-sale programs, and no receipt from it has been sent to the ETA.
crates/jdx-einvoice-eg/src/lib.rs
Related fields
Fields — E-receipts and e-invoices in Egypt
Sources
- Receipt v1.2 (v1.2) — Egyptian Tax Authority (ETA) – eInvoicing & eReceipt SDK
- Receipt Issuance FAQ — Egyptian Tax Authority (ETA) – eInvoicing & eReceipt SDK
- Document Serialization Approach — Egyptian Tax Authority (ETA) – eInvoicing & eReceipt SDK
Checked on: 4 November 2026. What concerns JooDax is taken from the programs’ own code.