ETA e-invoice and e-receipt: what your business needs
Egypt's Tax Authority (ETA) requires many businesses to issue tax documents electronically through its system. The rules roll out in phases, so the first job is to find out whether your business is already in scope. This guide explains the two documents and how to pick software without being misled by marketing.
This guide is general information, not legal or tax advice.
E-invoice and e-receipt in plain terms
- E-invoice (الفاتورة الإلكترونية): the tax invoice you issue to another business or to a government body. It is sent to the ETA system and validated before it is final [1][2].
- E-receipt (الإيصال الإلكتروني): the receipt for a sale to an individual consumer, mostly retail and point-of-sale. It follows a separate ETA process and its own rollout schedule [1][3].
- Both are submitted from your own software to the ETA through its integration interface. You do not type them into a government form one by one, except through the ETA portal for small volumes [2].
Who must comply
The ETA announces who enters the system in waves, usually by taxpayer category and activity. Your obligation depends on your registration, your activity and the wave you fall into, so read the current announcements on the ETA site [1] instead of relying on a blog post, including this one.
A practical way to check: ask your accountant whether your tax file is registered for e-invoicing, and whether the ETA has contacted you about e-receipts. If you sell to consumers from a shop, café or clinic, assume e-receipts will reach you and plan for it.
How the connection works
Technical detail lives in the ETA's SDK documentation [3]. Your software vendor should handle it. You mainly need to know who holds the credentials and what happens when a document is rejected.
- Your business registers on the ETA portal and creates a taxpayer profile [2].
- You register the software (ERP, accounting or POS) you will use. The ETA issues credentials that identify your system.
- Your software signs each document and submits it through the ETA interface [3].
- The ETA validates it and returns a status. Rejected documents must be fixed and sent again.
Software that states ETA e-invoice integration
Computed live from our data. In our research we did not find an official ETA list of certified software providers, so integration statements are what each vendor says on its own site. Treat them as claims to verify, not as certification.
Software that states e-receipt support
E-receipt support is rarer and more tied to point-of-sale systems. If you run a shop, start here.
How to choose software
- Ask the vendor in writing whether it submits e-invoices, e-receipts or both, and since when.
- Ask for a customer in your sector that already issues documents through the ETA with it.
- Check what happens on rejection: do you see the ETA error message in Arabic or English, and can your team fix it without calling support?
- Compare the real price: monthly or annual plan, invoice limits, per-invoice overage, setup fee, and extra charges for branches or users.
- Check that it fits the rest of your work: inventory, point of sale, VAT reports, multiple branches, and an Arabic interface for your staff.
- Use the free trial. Issue a few test documents in the ETA pre-production environment before you switch real sales over [3].
Checklist for the month you start
- Confirm with your accountant whether you are in scope and from when.
- Register on the ETA portal and keep the credentials with a named owner [2].
- Clean your item list and customer tax numbers. Wrong codes cause rejections.
- Choose software and run a pilot week in parallel with your current process.
- Train the staff who issue documents, especially for cancellations and credit notes.
- Set a monthly check that submitted documents match your sales records.
Common mistakes
- Assuming a vendor is certified because it says it is integrated.
- Not storing the credentials safely, then losing access when one person leaves.
- Starting on the deadline instead of weeks before it.
- Ignoring VAT treatment of each item. The software cannot guess it.
Quick answers
- Do I need a developer? Usually not. Your software vendor handles the connection. You need someone to own the credentials and fix rejected documents.
- Is a PDF invoice enough? A PDF alone is not an ETA e-invoice. The document must be submitted and validated through the ETA system.
- Can my accountant do it? Often yes, if your software supports it. Ask them early.
- What about small volumes? The ETA portal offers a way to issue documents manually [2]. Check whether it fits your volume.
Questions to ask a software vendor
- Is your integration live with the ETA production system, not only the test environment?
- Who updates the software when the ETA changes its rules, and is it included in the price?
- Can I export all my submitted documents if I leave?
- How are item codes and customer tax numbers managed?
Sources
- Egyptian Tax Authority (ETA), official site
- ETA e-invoicing portal
- ETA e-invoicing and e-receipt SDK documentation
This guide is general information, not legal or tax advice.
Compare e-invoicing & accounting