Every VAT-registered company in Egypt issues B2B invoices through the ETA portal, and e-receipts are rolling out for sales to consumers. Odoo has a standard Egyptian e-invoicing module, but most problems come from data, not from the connection.
FlexCode Middle East is part of FlexCode Systems GmbH, an Odoo Silver Partner. We implement Odoo, and our own apps are mentioned where they fit.
Key points
- Standard module. Odoo's Egyptian localization sends signed invoices to the ETA portal.
- Codes first. Every product needs a registered EGS or GS1 item code before you invoice it.
- Sign with your token. Invoices are signed with the company e-signature token before they are sent.
- Fix, then resend. A rejected invoice is corrected in Odoo and sent again, not edited on the portal.
Integrates with

What you need before the first invoice
- Your ETA portal registration, with the API client ID and secret for your ERP system.
- A valid e-signature token for the company.
- Your activity code and the branch details exactly as registered with the authority.
- Item codes for every product and service you sell, registered on the portal.
Setting it up in Odoo
- Install the Egyptian accounting localization and the ETA e-invoicing module.
- Enter the API credentials and choose the test (preproduction) environment first.
- Fill in the company branch, activity code and tax ID.
- Add the ETA item code to every product, and the correct tax types to your taxes.
- Send test invoices and credit notes, then switch to production.
- Confirm the invoice
- Sign with the e-signature token
- Send to the ETA portal
- Valid, or rejected with a reason
- Fix the data and resend
The rejections we see most often

| Error | Usual cause | Fix |
|---|---|---|
| Item code not valid | Code not registered or not yet approved | Register it on the portal, wait for approval, resend |
| Receiver data missing | No tax ID for a company, or no national ID above the value limit for individuals | Complete the customer record in Odoo |
| Tax type mismatch | Tax in Odoo not mapped to the right ETA type and subtype | Correct the tax configuration |
| Issuer address invalid | Branch address differs from the registration | Copy the registered address exactly |
| Signature error | Token not connected or expired | Reconnect or renew the token |
Credit notes and cancellations
Once an invoice is accepted, correct it with a credit note that references the original. The portal also allows a cancellation request within a limited window, and the buyer can reject an invoice. Agree internally who watches for rejected and cancelled documents.
What about e-receipts?
The e-receipt system covers sales to consumers, usually from shops and point of sale. It has its own registration and device setup, separate from e-invoicing. If you sell to consumers, check your phase with the authority and plan the point of sale setup together with your Odoo project.
FlexCode connects Odoo to the ETA
We register item codes, configure taxes, connect the token and test with you before go-live.
Frequently asked questions
Does Odoo support ETA e-invoicing as standard?
Yes. The Egyptian localization includes an e-invoicing module that signs and submits invoices and credit notes.
Can I edit an invoice after the ETA accepted it?
No. Issue a credit note, or request a cancellation within the allowed window.
How long does the setup take?
Usually one to three weeks. Registering item codes is often the longest part.
Talk to us about how Odoo fits your business. Book a free call
This article explains the rules in general terms and is not tax or legal advice. Check the details for your company with your tax adviser.
Run invoicing, stock and accounts from one system.
FlexCode Middle East implements Odoo in Arabic and English, with e-invoicing set up for Egypt, Saudi Arabia and the UAE.