Is e-invoicing mandatory for all businesses in Egypt?

E-invoicing is mandatory for all VAT-registered businesses in Egypt issuing B2B invoices — the rollout that began in 2020 now covers all registered companies. B2C sellers are being phased into the parallel e-receipt system in waves. Non-VAT-registered micro businesses are not yet required to comply, but B2B customers increasingly refuse paper invoices because they cannot deduct them.

How much does ETA e-invoicing setup cost in Egypt?

Manual submission through the ETA portal is free but impractical past roughly 50 invoices a month. Middleware tools cost about 15,000–40,000 EGP to set up. Full ERP integration — the only option that scales — runs 30,000–80,000 EGP for a typical SME on Odoo or ERPNext, covering certificate procurement, item code mapping, module configuration, and sandbox testing.

Do I need an ERP system for ETA e-invoicing?

No — the ETA portal allows free manual entry, and middleware tools can bridge existing invoicing software. But manual entry takes 5–10 minutes per invoice and error rates are high. Once volume passes a few hundred invoices a month, ERP integration becomes the only practical option: invoices are coded, signed, submitted, and status-tracked automatically.

What happens if an e-invoice is rejected by the ETA?

A rejected invoice legally does not exist — it is not tax-deductible for your customer and does not count as issued. Common rejection causes are unmapped item codes, expired signing certificates, and format errors. Someone in your business must monitor the rejection queue and resubmit corrected invoices; a good ERP integration surfaces rejections inside the invoice record itself.

ETA E-Invoicing in Egypt: Practical Compliance Guide

Since 2023, every VAT-registered business in Egypt has been required to issue electronic invoices through the Egyptian Tax Authority (ETA). Most guides on this topic are either ETA legalese or vendor pitches. This is the practical version: what the mandate actually requires, what it costs, and how to connect your invoicing to the ETA without making it a second job.

What the mandate actually requires

E-invoicing (الفاتورة الإلكترونية) means every B2B invoice you issue must be submitted digitally to the ETA's platform — signed with a digital certificate, in the ETA's JSON format, with your products mapped to GS1 or EGS coding. Paper invoices without a matching electronic submission are not tax-deductible for your customers, which in practice means B2B clients will stop buying from you if you can't issue compliant invoices.

The receipt mandate (e-receipts for B2C) is rolling out in waves behind it. If you sell to consumers, assume it reaches you.

Your three options, honestly compared

	ETA portal (manual)	Middleware tool	ERP integration
Setup cost	Free	15,000–40,000 EGP	30,000–80,000 EGP
Per-invoice effort	5–10 min manual entry	Semi-automated	Zero — automatic
Error rate	High (manual coding)	Medium	Low
Breaks at	~50 invoices/month	~500 invoices/month	Doesn't
Audit trail	Portal only	Tool + portal	Full, inside your ERP

Manual entry works when you issue a handful of invoices a month. The moment volume grows, the math flips: at 200 invoices a month, manual entry costs a full working week of someone's time — every month.

What an ERP integration actually does

A proper integration handles the full flow without anyone touching the ETA portal:

Invoice creation in your ERP, with items already mapped to EGS/GS1 codes.
Digital signing with your company's certificate (HSM token or signing service).
Submission to the ETA API, with automatic retry on the ETA's frequent downtime.
Status tracking — accepted, rejected, cancelled — synced back to the invoice record.
Credit and debit notes referencing the original ETA UUID, as the law requires.

Odoo has Egyptian localization modules for this; ERPNext has community modules; custom systems talk to the ETA API directly. The hard parts are always the same: item code mapping (weeks of cleanup for large catalogs), certificate handling, and surviving ETA API instability without losing invoices.

What it costs in practice

For a typical Egyptian SME on Odoo or ERPNext, expect 30,000–80,000 EGP for e-invoicing setup: certificate procurement, item mapping, module configuration, and testing against the ETA sandbox. Large catalogs (1,000+ SKUs) or custom ERPs sit at the top of that range or above it. Budget it as part of ERP implementation, not an afterthought — retrofitting is more expensive.

Where businesses get burned

Item mapping debt. Uncoded products mean rejected invoices at month-end close.
Certificate expiry. Signing certificates expire; if nobody owns the renewal, invoicing stops.
The ETA sandbox lies. Behavior differs from production; test both.
Ignoring rejections. A submitted-but-rejected invoice doesn't exist, legally. Someone must watch the rejection queue.

If you're evaluating ERP partly for e-invoicing, our ERP guide for Egypt covers how to choose the system, and the cost guide breaks down full implementation budgets.