Previous receipt UUID
The UUID of the last receipt from the same POS; empty only on its first receipt.
The field table calls it a reference to the previous receipt, empty only on the first receipt from the POS. The ETA checks that it has 64 characters.
When a receipt mid-chain is rejected, the chain does not break: the corrected receipt gets a new UUID because its content changed, keeps the same previous UUID, adds a reference to the rejected one (referenceOldUUID), and the receipts after it stay unchanged.
| Identifier | header.previousUUID |
|---|---|
| Path in the document | $.receipts[*].header.previousUUID |
| Cardinality | 1..1 |
| Data type | SHA-256 hash as 64 hexadecimal characters (empty for the first receipt) |
| Applies to | E-receipt |
In JooDax
BuiltJooDax takes the previous UUID as a parameter, writes it and hashes it in; a test shows that the same receipt with a different predecessor gets a different UUID. The module does not store the chain, so the program must pass the last UUID of each POS, and it does not build referenceOldUUID. 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
Checked on: 4 November 2026. What concerns JooDax is taken from the programs’ own code.