Issuing offline and the 24-hour window
A receipt is issued and checked locally, then submitted within 24 hours; anything later needs a late submission request.
The ETA describes "local validations" run before local storage: structure against the document type version, codes against cached tables (payment methods, currencies, tax types, units, GS1, EGS, activities and others), and core fields. So a receipt can be issued and stored, then submitted.
The submission limits: a receipt is submitted within 24 hours, except a resubmission carrying an old UUID, and the submission time cannot be in the future. An older receipt needs a late submission request from a yearly quota, with a window in days the ETA sets; no new request while one is active, and the access token is renewed after adding one.
The ETA’s example: with a 25-day window, a receipt issued 10 September is accepted on 1 October, one issued 4 September is rejected.
In JooDax
Not builtJooDax builds no submission queue, no local validation against the ETA tables and no late submission request; sending itself is not built.
crates/jdx-einvoice-eg/src/lib.rs
Related pages
Related concepts
- 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.
- 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.
E-receipts and e-invoices in Egypt
Sources
- 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.