Dubai · Riyadh · Bahrain · Cairo · AmmanEN · AR

Guide · Egypt · e-InvoicingEgypt's ETA e-invoicing: what your ERP has to do

Every invoice to a business in Egypt goes through the Egyptian Tax Authority. What the document must carry, how it is signed and validated, what to do with the invoices you receive, and where the e-receipt fits.

Updated 10 Oct 20267 min readEgypt
About this guide
Topic
e-Invoicing
Country
Egypt
Updated
10 Oct 2026
Reading time
7 minutes
The product
ERP Core

Facts checked against the ETA's published guidance; codes and procedures change, so confirm on eta.gov.eg before you go live.

Egypt was one of the first countries in the region to put every business invoice through the tax authority. The Egyptian Tax Authority (ETA) brought e-invoicing in from late 2020, in phases by group of taxpayers, until it covered registered companies in general. An invoice to a business or a government body that has not been accepted by the ETA's system is not a valid tax invoice, and its buyer cannot deduct the VAT on it. This guide is what that means for the software that issues the invoice. Our Egypt page covers payroll, social insurance and the rest of the country's rules.

The e-invoice, field by field

The ETA does not receive a PDF. It receives a structured document, in JSON or XML, through its API, and the printed invoice is only a copy of it. The parts that trip up systems built for paper:

PartWhat the ETA expects
IssuerThe company's tax registration number, the branch it issues from, and its activity code
ReceiverA business's tax registration number with its address; for an individual, the national ID above the ETA's threshold
Your referenceYour own invoice number, unique for your company, and the date and time of issue
LinesAn item code per line, either a GS1 barcode or an EGS code registered on the ETA portal, with the unit type, quantity, price and discount
TaxesThe tax types and subtypes per line: VAT at 14%, and where they apply table tax, withholding and the others in the ETA's code list
CurrencyThe invoice currency and its exchange rate, with the amounts in Egyptian pounds
Most rejections are master data. A product without a registered item code, a customer without a registration number, a tax type left blank. Clean the item and customer records before the first live invoice, not after the first rejection.

The electronic signature

Each document is signed before it is submitted, with the company's electronic signature certificate issued by a licensed provider. Most companies hold the certificate on a USB token, so the signing has to run on a computer where the token is plugged in. In practice the ERP prepares the document, a small signing program on that computer signs it with the token, and the ERP submits the signed document. Plan who holds the token, which computer runs the signing, and what happens when that person is on leave.

Submission, validation and the UUID

  • The ERP authenticates against the ETA's API with the credentials registered for the company, then submits the signed document.
  • The ETA validates it and returns it as valid or invalid, with the reasons when it is invalid.
  • A valid document gets its UUID, which belongs on the printed or PDF copy the customer receives.
  • An invalid document has no legal effect: the data is corrected at the source and the document submitted again.
  • After validation, the ETA allows a short window in which the issuer can cancel a document and the receiver can reject it. After that, a correction is a credit or debit note referencing the original.

The invoices you receive

E-invoicing works in both directions. Every invoice your suppliers issue to your registration number appears in your company's ETA account. That is useful: the purchase side of your VAT can be checked against what the authority already holds, and a supplier invoice that never reached accounts payable shows up. An ERP that reads those documents back, matches each one to its supplier by registration number and puts it in front of the person who handles that supplier turns the ETA into a control, not only an obligation.

The e-receipt is a different system

The e-invoice covers sales to businesses and government. Sales to consumers at a till fall under the ETA's e-receipt system, a separate platform with its own registration of the points of sale and its own rollout by sector. A business that sells both to companies and over the counter needs both. CorporateStack integrates with the ETA's e-invoicing system; it does not issue ETA e-receipts today, so a retail counter in Egypt needs an e-receipt solution beside it.

An integration checklist

  1. Register on the ETA portal, obtain the API credentials and the electronic signature certificate, and decide where the token lives.
  2. Register the item codes (GS1 or EGS) for everything you sell, and attach each code to its product in the ERP.
  3. Complete the customer records: registration numbers for businesses, national IDs where the threshold applies, addresses.
  4. Map every tax you charge to the ETA's tax types and subtypes, VAT and table tax first.
  5. Test in the ETA's pre-production environment with real documents: an invoice, a credit note, a foreign-currency invoice.
  6. Go live branch by branch, and watch the invalid documents daily for the first weeks.
  7. Read the received documents back and give accounts payable a daily list to match.
How CorporateStack does it

The ETA from the invoice itself, in ERP Core

On an Egypt tenant the ETA credentials are set per branch, on one settings page that checks every field the ETA needs before saving. A sales invoice is submitted from the record: the signing client, on the computer with the company's token, signs the invoices waiting for it, and the ETA's answer comes back to the same invoice, whose PDF carries the UUID. The invoices your suppliers issue are pulled from the ETA every day, matched to the supplier by tax registration number and listed for review.

INV-26-0937 · Cairo branch · e-invoiceETA
✓Prepared from the invoice · item codes and tax types complete11:02
✓Signed by the signing client · company token11:04
✓Valid · UUID on the invoice and its PDF11:04
See ERP Core

Questions we are asked

Do we need a USB token to issue ETA e-invoices?

Every document is signed with the company's electronic signature certificate, issued by a licensed provider. Most companies hold it on a USB token, so the signing runs on a computer where the token is plugged in; the ERP prepares the document and the signing client signs it before submission.

What happens when the ETA rejects an invoice?

The ETA validates each submitted document and returns it as valid or invalid with the reasons. An invalid document has no legal effect: the data is corrected at the source, usually a missing item code, a tax type or the receiver's registration number, and the document is submitted again.

Is the e-receipt the same as the e-invoice?

No. The e-invoice covers sales to businesses and government. The e-receipt is a separate ETA system for sales to consumers, issued at the point of sale, with its own rollout. CorporateStack integrates with the e-invoicing system; it does not issue ETA e-receipts today.

Can an invoice be issued in US dollars?

Yes. The document carries its currency and the exchange rate, and the amounts are also stated in Egyptian pounds; the ERP has to keep the rate it used on the invoice.

Submit one of your invoices to the ETA

A consultant sets up an Egypt tenant with your items and a customer, and submits an invoice to the ETA's pre-production system, with the answer on the record.

Book a demo