Is ETA e-invoicing the same as e-receipt?

No — they are two parallel systems on the same platform. E-invoice covers B2B and B2G transactions; e-receipt covers B2C retail. Both go through the ETA, both require digital signatures and clearance, but the formats and the workflows differ.

What is an eSeal and why do I need one?

An eSeal is a digital certificate issued by a certified authority (such as Egypt Trust). It is used to digitally sign every invoice before it is submitted to the ETA. Without an eSeal, your invoices will not be accepted by the platform. You apply for one as soon as you start the ETA enrollment.

How long does ETA enrollment + integration usually take?

For a small business with one location: 5 to 10 business days for the technical integration once your eSeal is in hand. The longest single step is usually waiting for the eSeal itself (a few days) and for ETA-side enrollment to clear, not the integration code.

Do I need to map every product to an EGS code?

Yes — every invoice line must reference an EGS or GS1 code. If your catalog has 50 SKUs this takes an afternoon; if it has 5,000 it takes weeks. Start the catalog mapping the moment the integration kicks off, in parallel with the technical work.

What if the ETA platform is down when I need to issue an invoice?

Your finance team needs a written paper-rollback procedure. In practice, brief outages are rare and your ERP queues the submission until the platform is back. For longer outages, the ETA publishes guidance on temporary paper invoices that must then be electronically reissued retroactively.

Can I integrate ETA e-invoicing without replacing my current accounting system?

Yes — Path B (a middleware layer on top of your existing system) is built for exactly this. As long as your current software can export invoices in a structured format (XML, CSV, or via an API), a middleware layer can submit them to the ETA on your behalf. BSE delivers both Path A and Path B.

What happens if I cross the VAT threshold mid-year?

You are required to register within 30 days of crossing the threshold (on a trailing 12-month basis), and from that moment every invoice must be on the ETA platform. For SMBs that crossed the new EGP 250 000 line in early 2026, see our VAT threshold catch-up guide.

ETA e-invoicing in Egypt — complete guide | BSE

What ETA e-invoicing actually is

ETA e-invoicing is the Egyptian Tax Authority's digital invoice clearance system. Instead of issuing paper or PDF invoices and trusting that they reach the buyer and the tax record, every invoice from a registered business is submitted to the ETA platform, validated, signed, archived, and assigned a UUID before it has legal force.

The system was launched in November 2020 for large taxpayers and has expanded in phases ever since. By 2026 it covers effectively every VAT-registered business in Egypt.

Who is required to use it

Anyone VAT-registered with the ETA must issue invoices through the platform. Since the threshold dropped from EGP 500 000 to EGP 250 000 on 31 March 2026 (see our catch-up guide), this now reaches the vast majority of Egyptian SMBs.

It applies to:

B2B sales between registered businesses
B2G sales to government bodies
B2C sales (via the parallel e-receipt system, which feeds into the same ETA infrastructure)

If you are issuing invoices in Egypt and not on the ETA platform, you are likely out of compliance.

How the rollout has unfolded

The ETA mandate has been rolled out in waves so that the platform and integrators could scale without overwhelming anyone:

November 2020 — Phase 1: 134 large taxpayers
2021 — Phases 2 and 3: progressive expansion to the top several hundred companies
2022–2023 — Mid-sized companies brought in, and the e-receipt system launched for B2C
2024–2025 — Smaller VAT-registered firms enrolled
31 March 2026 — Registration threshold drops to EGP 250 000, pulling in tens of thousands of SMBs

Each wave has tightened the technical requirements: digital signatures, GS1/EGS coding, real-time clearance. A business enrolling for the first time in 2026 is meeting the latest, strictest version of the spec.

What changes day-to-day

Five things genuinely change once you are on the platform:

Every invoice line item needs an EGS or GS1 product code. You cannot ship a free-text "consulting services" line; you map your catalog to the official coding system once, then it flows automatically.
You need an eSeal certificate. The certificate is issued by an authority like Egypt Trust and used to digitally sign every invoice before submission.
Invoices clear in near-real-time. You submit to the ETA; it returns a UUID and QR code within seconds; only then is the invoice legally valid.
You file monthly VAT returns that reconcile against what the ETA already has on record — discrepancies trigger flags.
Your customers can pull your invoices directly from the platform, which means clean accounts-receivable reconciliation but also no more "I never got your invoice" disputes either way.

Integration approaches

There are three practical paths:

Path A — Native ERP integration. Your ERP already speaks ETA. You configure your eSeal, your EGS codes, and you are done. Best fit for businesses that are choosing or replacing their ERP this year anyway. SafeERP and a handful of local packages support this directly.

Path B — Middleware layer. Your existing accounting software does not speak ETA, but it can export invoices in a structured format. A middleware layer reads those exports, normalizes them, signs and submits them to the ETA, and writes the UUID back. Best fit for businesses on legacy systems they cannot replace yet.

Path C — Portal-only. You enter invoices directly on the ETA portal one at a time. Works for very low volume (under 20 invoices a month). Beyond that, the time cost stops being worth it.

Common rollout mistakes

Five mistakes we see SMBs make on first rollout:

Underestimating the EGS coding work. Mapping your entire catalog takes longer than the technical integration. Start early.
Ordering the eSeal certificate last. Issuance can take days. Order it the moment registration starts.
Treating it as an IT project. It is a finance + IT project. The CFO and the accountant must be in the room.
Skipping the first-month close rehearsal. The first ETA-reconciled VAT return is where surprises surface.
Going live without a paper rollback plan. If the ETA platform has a brief outage, your team needs a procedure.

Where BSE fits in

BSE has integrated ETA e-invoicing for over 500 businesses since the mandate first launched in 2020. For SMBs newly required to enroll, we typically deliver either Path A (SafeERP with native ETA) or Path B (middleware on top of your existing system) in 5 to 10 business days for single-location operations. The technical work is the small part; the value comes from the scoping conversation that picks the right path for your catalog, your volume, and your accountant's workflow.

Talk to us if you want a quote scoped to your situation.

ETA e-invoicing in Egypt — the complete guide to compliance, integration, and rollout