نفكّر. نُظهر. نُنجز.Think. Show. Deliver.
E-invoicing

E-Invoicing in Egypt: A Practical Guide for Companies (2026)

Reading time: 9 minFacts checked on Omega Trove Egypt

هذا المقال باللغة الإنجليزية.

A finance manager working on a laptop at his office desk, preparing the company's e-invoices

Short answer: In Egypt, a company sells to another company or to the government with an electronic invoice that is signed with the company's e-seal and sent to the Egyptian Tax Authority (ETA) in real time. The ETA checks it and gives it a unique ID. Sales to consumers use a separate system, the e-receipt. The legal basis is Law 206 of 2020, and since July 2023 every taxpayer is expected to be on the system.

Key takeaways

  • Law 206 of 2020 (Article 35) makes the signed electronic invoice the valid tax document; paper invoices no longer support deductions.
  • B2B and B2G sales use the e-invoice; sales to consumers use the separate, phased e-receipt system.
  • Every invoice is signed with the company's e-seal, validated by the ETA and given a unique ID.
  • Items must carry GS1 or EGS codes, and breaching Article 35 carries a fine of EGP 20,000 to 100,000 (Article 71).

This guide is written for finance managers, foreign-owned companies and owners who need to understand the system before they choose software or a provider. If you want the registration screens one by one, read our step-by-step registration guide in Arabic.

What is Egypt's e-invoicing system?

It is a clearance system. Your invoice does not become a valid tax document when you print it; it becomes valid when the ETA's platform accepts it.

The obligation comes from Article 35 of the Unified Tax Procedures Law (Law 206 of 2020), published in the Official Gazette on 19 October 2020. Article 35 requires the system to include "issuing an electronic invoice for each sale transaction, electronically signed by the source". The detailed rules sit in the law's executive regulations, issued by Ministerial Decree 286 of 2021.

Two consequences matter for any finance team:

  • Paper invoices lose their tax value. PwC's Egypt tax summary (last reviewed 17 August 2026) says that "only E-invoices are recognized by the ETA as valid documentation for deductible costs". A supplier who still sends paper can cost you deductions.
  • The ETA sees your sales as they happen. The platform receives every invoice when it is issued, so your VAT return and your invoices must tell the same story.

Who must issue e-invoices and e-receipts

The system was rolled out in waves. According to Sovos (8 December 2020), the pilot started on 15 November 2020 with 134 large companies under Decree 386 of 2020, followed by a second group from 15 February 2021. Government bodies stopped accepting paper invoices from 1 October 2021 under Ministerial Decree 1206 of 2021 (PwC). PwC's summary then states: "Effective July 2023, all taxpayers in Egypt are required to implement the e-invoicing system." Some vendor guides date the last wave to April 2023 instead; either way, if you are a registered taxpayer today, assume the obligation applies to you.

The split that confuses most owners is between two documents:

Who buys from youDocumentWhere it goes
Another company (B2B)E-invoiceETA e-invoicing platform
A government body (B2G)E-invoiceETA e-invoicing platform
A consumer (B2C)E-receiptETA e-receipt platform
Export customerExport invoiceETA e-invoicing platform

The e-receipt is phased by lists of named taxpayers, not by one date for everyone. Each ETA decision names tax offices or taxpayers and a start date. For example, Resolution 281 of 2025 brought in taxpayers at the Sixth District and Fifth Settlement tax offices in Cairo from 15 September 2025 (Comarch summary), and Decision 361 of 2025 started the first sub-phase of the ninth main stage from 15 November 2025 (Arabic business press). The ETA's e-receipt page links to the decisions and to a lookup where a taxpayer can check whether it is listed. Check that lookup rather than relying on a general rule.

The ETA's developer FAQ adds two practical points for retailers: a receipt must be submitted "within the allowed duration (24 hours)", and the point-of-sale device itself must be registered on the platform.

A shop worker in an apron holds a receipt printer at the counter
Sales to consumers use the e-receipt, not the e-invoice. Each has its own phased decisions.

How an invoice is cleared

The ETA's software development kit (SDK) describes the technical path. In plain terms:

  1. Your system builds the invoice as structured data. The submission API "supports documents submitted using JSON and XML format".
  2. The invoice is signed. The SDK describes hashing the document and signing the hash "using CADES-BES signature" with the company's e-seal certificate, then attaching that signature to the document. The e-seal is a digital certificate belonging to the company, issued by a licensed certification provider and usually delivered on a USB token.
  3. The ETA validates it. The ETA's introductory guide for taxpayers (2023) says the platform runs nine types of checks on each document before it accepts it.
  4. The ETA returns an ID. A valid document receives a unique ID of 26 letters and numbers, and a longer 42-character ID that can be used to look the document up. Possible statuses are submitted, valid, invalid, rejected and cancelled.
  5. The buyer sees it on the platform and in their own system.

The document types in the SDK are invoice, credit note and debit note, plus export versions of each. One rule worth knowing early: a credit note cannot exceed the amounts on the invoice lines it corrects.

Registering on the ETA portal

Registration creates your company's identity on the platform and names a system administrator. You need three things before you start: a valid e-seal in the company's name, a Windows computer that can read the seal's USB token, and the company's tax registration number.

Registration is done on the ETA profile portal, separately for the test environment (preproduction) and the live environment (production). Our Arabic registration guide walks through the four screens and the common errors, based on the ETA's own readiness guide.

Two decisions to make at this stage:

  • Who is the administrator? That person invites users and registers your ERP. Choose someone from management, not an outside bookkeeper who may leave.
  • Test first. Issue several invoices on preproduction before you go live. Anything sent to production has tax effect.

Choosing how to issue: portal, ERP integration or a provider

There are three routes, and the ETA's rules are the same on all of them.

  • The ETA portal. You type each invoice by hand in a web application. This suits a company with a handful of B2B invoices a month. It does not scale, and it is easy to make typing mistakes.
  • Your ERP or accounting system, through the API. Your system signs and sends each invoice automatically. The ETA's getting-started page describes this as "System integration provides set of APIs". This is the right route once invoices are routine. Your system must be registered on the portal as an ERP, and it receives its own credentials.
  • A service provider. Article 35 of Law 206 allows a company to "contract with one of the companies licensed by the Minister to implement this electronic system". The provider handles the connection; you still own the data and the deadlines.

If you are choosing new software anyway, read our comparison of accounting software and ERP and our guide to Odoo in Egypt, which covers how one ERP connects to the ETA in practice.

Three ways to issue an e-invoice in Egypt An e-invoice can reach the Egyptian Tax Authority by being typed on the ETA portal, sent by your ERP or accounting system through the API, or submitted by a service provider. All three go through the same ETA validation. A valid document gets a unique ID; an invalid one is rejected, fixed and sent again. Three ways in, one check 1 ETA portalType each invoice by hand 2 Your ERP, by APISends signed JSON or XML 3 A service providerSubmits on your behalf ETA validatesnine types of checks per document Valid: gets a UUID Invalid: fix, resend The rules are the same on every route.
Portal, API or provider: the route changes the work on your side, not the rules. Every document goes through the same ETA validation.

Item coding: GS1 and EGS

Every line on an e-invoice must carry an item code, and the SDK is explicit: the item type "must be GS1 or EGS for this version".

  • GS1 codes are the international barcodes many manufacturers already print on packs.
  • EGS codes are Egypt-specific internal codes that a company creates for its own items and services, then submits for ETA approval.

Coding is usually the longest part of the project, because it forces you to clean your item list. Duplicate items, vague service names and products with no barcode all surface here. Start it in parallel with registration, not after.

A manager in a white shirt reviews the item list on a tablet in his office
Item coding with GS1 or EGS codes is usually the longest part of the project. Start it early.

Common rejection reasons

The ETA validates every document. The SDK's own rules point to the mistakes that stop a document most easily:

  • Missing or unapproved item codes. A GS1 or EGS code that is not active on the platform fails validation.
  • A date in the future. The SDK states that the issue date and time "cannot be in future". A server clock in the wrong time zone is enough to trigger this.
  • Totals that do not add up. Line values, discounts and taxes must reconcile exactly.
  • A credit note larger than the original invoice lines.
  • A missing or invalid signature, for example an expired e-seal. The SDK requires at least the issuer's signature on every document.

Two time limits also matter. A buyer can reject an invoice "only within limited time period", and only once; the SDK's sample configuration shows 72 hours, and vendor guides report the same figure. The issuer can cancel a document only within a period that the SDK calls configurable, without publishing a number. Treat both windows as short and fix errors on the same day.

Penalties and deadlines

The fines are in Law 206 of 2020 itself. Article 71 sets a fine of "not less than twenty thousand Egyptian pounds and not exceeding one hundred thousand Egyptian pounds" for anyone who breaches, among other articles, the first and second paragraphs of Article 35, which hold the e-invoice obligation. The same law sets separate fines for late tax returns (Articles 69 and 70).

The practical cost is often larger than the fine. Your customers may refuse paper invoices because they cannot deduct them, and government buyers stopped accepting them in 2021.

Frequently asked questions

Is e-invoicing mandatory for small companies in Egypt?

PwC's summary states that from July 2023 all taxpayers are required to implement the e-invoicing system. If you sell to other companies or to the government, plan on issuing e-invoices whatever your size.

What is the difference between an e-invoice and an e-receipt?

The e-invoice is for sales to companies and government bodies. The e-receipt is for sales to consumers, and it has its own phased decisions, its own platform and registered point-of-sale devices.

Do I need an e-seal to issue e-invoices?

Yes. Every document must be signed, and the ETA's SDK describes the signature as created with the company's e-seal certificate. You also need the seal to register.

Can a foreign-owned company use its group ERP?

Yes, if the ERP can produce ETA-compliant JSON or XML, sign it with the Egyptian entity's e-seal, and use GS1 or EGS item codes. Many groups add a local connector or use a licensed provider.

How long does a buyer have to reject an e-invoice?

The ETA's SDK limits rejection to a set period and allows it once per document. Its sample configuration and vendor guides show 72 hours.

Where can I read the official rules?

Start with the ETA's SDK site and the ETA's taxpayer guides listed below. Law 206 of 2020 holds the obligation and the fines.

Sources

Each source shows the date we read it. Facts last checked: .

  1. Law No. 206 of 2020, Unified Tax Procedures Law, English translation by Andersen Egypt (September 2025), Articles 30, 35, 37, 69 to 71 (read 20 November 2026): eg.andersen.com
  2. EY Global Tax News, "Egypt introduces Unified Tax Procedures Law" (publication date of Law 206/2020; read 20 November 2026): globaltaxnews.ey.com
  3. Egyptian Tax Authority, SDK, "Submit Documents" (JSON and XML, document IDs; read 20 November 2026): sdk.invoicing.eta.gov.eg
  4. Egyptian Tax Authority, SDK, "Signature Creation" (CAdES-BES, e-seal; read 20 November 2026): sdk.invoicing.eta.gov.eg
  5. Egyptian Tax Authority, SDK, "Document Types" (read 20 November 2026): sdk.invoicing.eta.gov.eg
  6. Egyptian Tax Authority, SDK, "Invoice v1.0" (GS1 or EGS, date rule; read 20 November 2026): sdk.invoicing.eta.gov.eg
  7. Egyptian Tax Authority, SDK, "Reject Document" and "Cancel Document" (read 20 November 2026): sdk.invoicing.eta.gov.eg
  8. Egyptian Tax Authority, SDK, "Getting started" (portal and API integration; read 20 November 2026): sdk.invoicing.eta.gov.eg
  9. Egyptian Tax Authority, SDK, "Receipt issuance FAQ" (24-hour submission, POS registration; read 20 November 2026): sdk.invoicing.eta.gov.eg
  10. Egyptian Tax Authority, Taxpayers Introductory Guide (Arabic, v2, 2023) (read 20 November 2026): eta.gov.eg
  11. Egyptian Tax Authority, Taxpayers Readiness Guide, part 1: registration (Arabic, v2, 2023) (link checked 20 November 2026): eta.gov.eg
  12. Egyptian Tax Authority, e-receipt services page (decisions and taxpayer lookup; read 20 November 2026): eta.gov.eg
  13. PwC Worldwide Tax Summaries, "Egypt: Other taxes" (last reviewed 17 August 2026; read 20 November 2026): taxsummaries.pwc.com
  14. Sovos, "Egypt's tax digitization continues" (8 December 2020; secondary source for the pilot dates; read 20 November 2026): sovos.com
  15. EDICOM, "Electronic invoicing in Egypt" (vendor page; secondary source for rollout dates and the 72-hour window; read 20 November 2026): edicomgroup.com
  16. Comarch, summary of Resolution 281 of 2025 on the e-receipt (20 August 2025; secondary; read 20 November 2026): comarch.com
  17. Banker.news, report on Decision 361 of 2025 (25 September 2025; secondary; read 20 November 2026): banker.news

Omega Trove Egypt editorial team

We write practical guides for companies doing business in Egypt. Every legal or tax fact in this article links to an official or named source above, checked on .

Practical ideas from Omega Trove Egypt

مقالات ذات صلةRelated articles

واتسابWhatsApp