Setting up Egyptian e-invoicing — the three mappings and two credentials

Nothing can be sent until three tables are filled, and none of them can be guessed for you.

The mapping is the setup

Three tables have to be filled before a single document can be sent, and none of them can be guessed for you.

1. Products → EGS or GS1 codes. One code per product you invoice.
2. Units → the Authority’s unit list. Your “carton” has to become their code, not your word.
3. Taxes → type and sub-type. The pair, not just the rate.

Then the two credentials

The client credentials the Authority issues to the company, and the e-seal used to sign. Without the second the system raises rather than sending — there is no unsigned mode.

What to test first, and how

Issue one invoice with one line and check three things in order: that validation passes, that a UUID comes back, and that the printed document carries the QR and the status. If validation fails it names the field — fix the mapping, not the invoice.

Reading the status report

The report separates submitted, rejected and never-submitted. Never-submitted is its own state on purpose: it is not a failure, it is work that has not been done, and folding it into rejected would make a backlog look like a fault.

One habit worth keeping

Resubmit from the queue, not by re-issuing. Re-issuing creates a second document for one sale, and reconciling that later costs more than the original problem.