E-invoicing for Egyptian hospitals: e-receipts, e-invoices and what the ETA needs from you
A hospital in Egypt issues two kinds of electronic tax documents: e-receipts to patients and e-invoices to insurers and companies. This guide explains both, and how Nabd prepares them.
This article explains how a hospital system prepares electronic tax documents. It is not tax advice, and the Egyptian Tax Authority’s rules and timelines change. Confirm your obligations with the hospital’s tax adviser.
Two documents, two kinds of buyer
The Egyptian Tax Authority (ETA) runs two related systems: the e-invoice for business-to-business sales and the e-receipt for sales to individuals. A hospital touches both every day. When a patient pays at the cashier, the transaction is a sale to an individual. When the hospital bills an insurer, a TPA or a contracting company for the covered share, it is a sale to a business. A hospital system therefore has to split each episode of care correctly and produce the right document for each side.
In Nabd this split already exists for billing reasons: every service is captured as a priced charge and divided between the patient share and the payer share at the moment it is recorded. The tax documents follow from the same split, so there is no second calculation and no re-keying. You can read more about the billing side on our billing and insurance page.
The patient side: e-receipts
Patient invoices produce an e-receipt (receipt version 1.2). The buyer is the patient, identified by national ID or passport. Only the patient share appears on the receipt; when the patient is covered by insurance, the insurer is recorded as the contractor. Each receipt carries the payment method code of how the patient paid.
- Item codes: each line uses an EGS or GS1 code, taken from the code configured on the service or generated in the form EG-<tax number>-<service code>.
- Tax codes: healthcare services and medicines are mapped by default to the exempt code (T1 / V003); taxable lines use T1 / V009. Your tax adviser should confirm the mapping for your service catalogue.
- Cancelled invoices produce a return receipt that references the original receipt’s UUID.
- Printed receipts (80 mm) and A4 bilingual invoices carry the ETA QR code.
Why the UUID chain matters
E-receipts are not independent files. Each receipt’s UUID is a SHA-256 hash of its ETA serialisation, and receipts are chained per point of sale through the previous receipt’s UUID. In a hospital, the natural point of sale is the cash box at which the payment was taken, so Nabd keeps a separate chain per cash box and per facility. If two cashiers share one chain, or a receipt is edited after it was issued, the chain breaks; generating it inside the billing system avoids both problems.
The payer side: B2B e-invoices
Payer invoices produce a business-to-business e-invoice (type I). Cancelling a payer invoice produces a credit note that references the original UUID. Insurance deductions are handled the same way: when a payer rejects or deducts part of a claim and the amount is written off, Nabd issues a credit note for the written-off amount, so the tax record matches what the hospital actually collects. The rejection workflow itself is described in our article on insurance approvals and claim rejections.
The submission queue
Every invoice has an e-invoice status, and a background job processes the queue every five minutes. The billing team works from one screen that shows the queue, errors and the 24-hour window, and can submit a document, preview or download its JSON, and record the UUID returned by the portal.
| Status | Meaning |
|---|---|
| Pending | Waiting to be submitted |
| Submitted | Handed to the provider (file written or sent); the returned UUID is recorded |
| Failed | Submission failed; retried automatically after 15 minutes, error shown |
| Not required | Zero patient share, so no receipt is needed |
| Void | Invoice cancelled before submission |
| Credit pending / Credited | Invoice cancelled after submission; the return receipt or credit note is in progress or done |
What Nabd does today, exactly
Nabd produces the ETA e-receipt and e-invoice documents and the submission queue. The connection to the Tax Authority is configured with each hospital’s own ETA credentials. Out of the box, the default provider writes each document to a monthly folder on the server as a JSON file, ready for upload through the ETA portal or signing tool, and the returned UUID is recorded on the invoice. Switching to a live API provider is a configuration step once the hospital has its ETA registrations; the full live connector (POS registration, signing and submission API) is the next item on our roadmap.
This distinction matters when you compare vendors. Producing correct documents and a reliable queue is the system’s job; the registrations, the electronic seal and the legal responsibility for submission belong to the hospital as the taxpayer.
What the hospital needs from the ETA
Before a live connection, the hospital’s finance team gathers the following. Starting early saves weeks at go-live, because some items depend on the Tax Authority’s own processing time.
- ERP registration on the e-invoicing portal, with a client ID and client secret for the e-invoice API.
- POS registration for each cashier station: device serial, operating system version and a client ID and secret for the e-receipt API.
- Approved item codes for your services (EGS codes registered with the ETA, or GS1 codes).
- The electronic seal or USB token used to sign B2B e-invoices.
- The taxpayer activity code (8610 hospital activities, 8620 medical and dental practice, or 8690 other human health activities) and the branch code.
In Nabd these values are entered in the e-invoice settings per facility: enabled flag, provider, activity code, branch code, taxpayer registration number (by default the facility’s tax number), the default point-of-sale cash box, the POS serial per cash box and the item code type.
Common mistakes we see
- Issuing one e-invoice for the whole visit, without separating the patient share from the insurer share.
- Free-text service names without approved item codes, which the portal rejects.
- Sharing one point-of-sale registration across several cashiers, which breaks the receipt chain.
- Forgetting credit notes when an insurer deducts part of a claim, so tax records overstate revenue.
- Leaving the registration work until the week of go-live.
If you run Odoo
Hospitals and medical centres that already use Odoo can run Nabd on Odoo 19, where e-invoicing goes through Odoo’s own Egypt localisation rather than Nabd’s queue. The patient and payer split is the same; only the tax engine differs.
A practical go-live sequence
- Review the service catalogue and assign item codes and tax codes with your tax adviser.
- Register the hospital and each cashier station with the ETA.
- Configure the e-invoice settings and the POS serial per cash box in Nabd.
- Run a week in file mode: generate documents, upload them through the portal and record the UUIDs.
- Move to the live provider when the credentials are confirmed, and monitor the queue daily.
Want to see the queue, a bilingual invoice with its QR code and a credit note for an insurer deduction? Request a demo on fictional data, or read about what makes Nabd fit for Egyptian hospitals.