# E-Invoicing in Egypt: What Does It Require? *An e-invoice for companies and an e-receipt for consumers — and the line between portal and system is two hundred invoices a month* > **In short:** An explainer of Egypt's e-invoicing per the Egyptian Tax Authority: who must issue e-invoices versus e-receipts. - **URL:** https://www.snad.io/en/blog/fatura-electroniya-misr-dalil - **Arabic original:** https://www.snad.io/blog/fatura-electroniya-misr-dalil - **Category:** Guides — Regional Tax - **Tags:** Egypt, Invoicing, Digital Transformation, Small Business, Snad - **Published:** 2026-08-24 - **Updated:** 2026-08-24 - **Publisher:** Snad (snad.io) The Egyptian Tax Authority has moved invoicing from paper in drawers to a digital system that receives the documents — and made the obligation serious: non-compliance "constitutes a tax evasion crime" in its own words (eta.gov.eg, accessed August 2026). The basic split is simple: dealing with **companies** obliges an **electronic invoice**; dealing with a **final consumer** obliges an **electronic receipt** — and whoever deals with both answers to both systems. This is an explainer: it covers the structure and the practical decisions, with the Authority's publications and your tax adviser as the final references. ## Two systems, not one: invoice and receipt Per the Egyptian Tax Authority (August 2026): | Your dealings | Your obligation | The system | |---|---|---| | With companies (B2B) | Issue electronic invoices | The e-invoicing system | | With final consumers (B2C) | Issue electronic receipts | The e-receipt system | | With both | Both obligations — each in its system | Both systems | Joining starts from the **digital signature**: an e-seal certificate carrying the tax registration number, with sign-up through the Authority's tax-profile portal. The point many miss is the third row: a shop selling to individuals while supplying companies lives in both systems — an invoice for the corporate supply and a receipt for the walk-in sale, each under its own rules. Knowing your row in this table is step zero before any technical decision. ## Portal or ERP? The two-hundred line The Authority provides an **issuing portal** for small invoicing volumes, and has drawn the line clearly (per its site — August 2026): - **Fewer than 200 invoices a month**: you may request to use the issuing portal and stay on it. - **More than 200 invoices a month**: the portal is available **as a six-month grace period only** — while the business adopts an ERP system to issue its invoices. Reading the line managerially matters more than technically: - The grace period is an explicit message: the portal is a **bridge** for transition, not a residence for anyone above the line. - Manual portal entry is duplicated work: the invoice is created in your books and then entered again — an error door that widens with every additional invoice. - Whoever is approaching the line from below should plan before reaching it: adopting a system under the pressure of an expiring grace period is the worst way to adopt one. Which system is a decision governed by the Authority's technical integration requirements — specifications to be reviewed from official sources at selection time. ## What changes in the working day The system's daily effect goes beyond the invoice's format: 1. **Customer data became a condition of issuing**: a company invoice needs its tax particulars correct — an organised customer file with their details is no longer a nicety but an operating requirement. 2. **Item description became codified**: the system relies on unified goods-and-services codes, so coding your items correctly once spares you on every invoice after. 3. **Timing became part of the obligation**: the electronic document is transmitted under the system's rules, not when an employee finds time — batched invoicing "entered at the weekend" stopped being a viable working style. 4. **The document acquired a life cycle**: issue, acceptance and cancellation through defined procedures — no more "tear up the paper and write another". The connecting thread: the system assumes the invoice **comes out of a disciplined system**, not a carbon-copy book — which is exactly why the two-hundred line and the six-month grace period of the previous section exist. ## Bookkeeping readiness before technology Effective preparation starts in the books, not the technology: 1. **Clean the customer file**: complete, correct tax particulars for corporate customers — the most painful invoice rejections come from data errors an unhurried week could have fixed. 2. **Unify your items**: one item list with disciplined names and codes, not the same item under three names — unified coding builds on a clean list. 3. **Discipline the invoice sequence**: sequential numbering and a defined path for cancellation and amendment through notes, not strike-outs. 4. **Let the invoice be born from the books**: a system where the invoice arises from the sale's own data closes the re-entry door — the first source of gaps between what was transmitted and what your books say. 5. **Consult before adopting**: the technical integration requirements and the obligation's details are reviewed from the Authority's publications and with a specialist. In that context, said plainly: **Snad** runs the invoicing, accounting and inventory cycle with sequential numbering and an exportable archive — while **direct integration with a government invoicing portal is available inside Saudi Arabia only**, so connecting to the Egyptian Authority's system and its requirements is a matter for specialists and official sources. ## Frequently asked questions ### Who must issue electronic invoices in Egypt? Per the Egyptian Tax Authority (August 2026): whoever deals with companies must issue electronic invoices on the e-invoicing system, whoever deals with final consumers must issue electronic receipts on the e-receipt system — and whoever deals with both answers to both. Non-compliance constitutes a tax evasion crime in the Authority's own words. ### Do I need an ERP, or does the issuing portal suffice? Per the Authority (August 2026): under 200 invoices a month you may request the issuing portal and stay on it; above 200 the portal is available for a six-month grace period while an ERP is adopted. In practice, duplicated manual entry makes a system cheaper in effort and error even before the line is reached. ### What should I prepare before joining the system? A digital signature with an e-seal certificate carrying your tax registration number; a customer file with complete tax particulars for corporate customers; a unified, codable item list; and a disciplined invoice sequence with a clear cancellation path — then review the technical integration requirements from the Authority's publications. ### Does Snad integrate with Egypt's e-invoicing system? Direct integration with a government invoicing portal is available inside Saudi Arabia only. Snad runs the invoicing, accounting and inventory cycle with sequential numbering and an archive exportable in standard formats — connecting to the Egyptian Authority's system and its technical requirements is a matter for specialists and official sources. --- ## About the publisher **Snad (سند)** — a private Saudi software company based in Riyadh, founded 2025. Legal form: Sole proprietorship. Commercial registration: 7038154642 VAT number: 310959226500003 Only official domain: snad.io > Snad is a private commercial business-management platform. It is not a > government body, not a bank, and not a government services portal, and it > is not affiliated with any government entity. Any site or app with a > similar name is unrelated to Snad.