What JooDax builds today for the Egyptian e-receipt
The receipt 1.2 document from the ETA’s table, its canonical serialization and the UUID chain per POS; no sending, because sending needs a taxpayer and a POS registered in Egypt.
The jdx-einvoice-eg module builds the receipt 1.2 document from the ETA’s field table, with field names and order as written there, the canonical serialization by the ETA’s rules, and each receipt’s UUID as a hash chained to its predecessor. Before the ETA would, it refuses a receipt with no lines; a missing RIN, branch code, POS serial or activity code; a line without an item code; a business buyer without its RIN and name; a person’s receipt of EGP 150,000 or more without the buyer’s ID and name; and a submission without the issuer’s signature.
Not built: POS registration, the access token, submission and its follow-up, the QR code, an offline submission queue, returns, taxes other than T1, non-commercial discounts, making the signature (the submission takes the issuer’s signature, but the module does not produce it), and the B2B e-invoice. No JooDax program uses the module yet.
No JooDax receipt has ever been sent to the ETA, so none is called accepted. Sending needs a POS registered and linked to a taxpayer carrying the B2C tag, and client credentials issued to it; so it waits for a registered Egyptian customer.
In JooDax
Partly builtThe document, serialization and chain are built, with four tests; sending and everything around it is not.
crates/jdx-einvoice-eg/src/lib.rs; crates/jdx-einvoice-eg/src/tests.rs; docs/DECISIONS.md (S-36)
Questions and answers
Has the ETA accepted a JooDax receipt?
No; none has been sent yet. The document is built and tested in code only.
Related pages
Related concepts
- The UUID chain: how each receipt links to the one beforeEach receipt’s UUID is the SHA-256 of its content, and that content includes the previous receipt’s UUID from the same POS, so the receipts form a chain from which no link vanishes unnoticed.
- The ETA’s canonical serialization of a documentBefore hashing, the document becomes one line of text by fixed rules: field names upper-cased in quotes, values as they are, and the array name before each element.
- Registering a point of sale with the ETANo receipt is issued except from a POS registered and linked to the taxpayer’s RIN, which obtains an access token with its serial number, key and client credentials.
- Submitting receipts and how they are validatedReceipts go in JSON batches to one API, which answers at once with a submission ID while full validation runs afterwards.
E-receipts and e-invoices in Egypt
Sources
- Receipt v1.2 (v1.2) — Egyptian Tax Authority (ETA) – eInvoicing & eReceipt SDK
- Document Serialization Approach — 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.