Egypt ETA Electronic Invoice & Receipt

Name: Egypt ETA Electronic Invoice & Receipt
Brand: ECOSIRE
SKU: egypt-eta-einvoice

اہم خصوصیات

ETA-compliant JSON document generation for invoices, bills, credit notes and debit notes, matching the current ETA e-invoice schema (documentType I/C/D, internalID, taxpayer activity code, item and tax structures)

Digital signature of the canonical JSON via USB token or HSM (CAdES-BES), with a signing bridge/agent that ECOSIRE configures against your certificate provider

Direct submission to ETA e-invoice and e-receipt REST endpoints, storing the returned document UUID, submission UUID and long-ID back on the account.move / pos.order record

E-receipt (POS) submission support with documentType RECEIPT for retail and near-real-time store clearance from the Odoo POS session

GS1 and EGS product code mapping: an extra field on product.template that maps each product to its GS1 GTIN or ETA EGS code, validated before submission

Automatic tax and total recomputation via @api.depends compute methods so ETA line totals, discounts and tax subtotals always reconcile to the Odoo journal entry

Full lifecycle state machine (draft → signed → submitted → valid / rejected / cancelled) tracked on the record with ETA error messages surfaced inline for fix-and-resubmit

QR code and ETA identifiers embedded on the customer invoice through a customized QWeb report, so printed and PDF invoices carry the compliant markings

Scheduled bulk submission and automatic retry using ir.cron, plus a manual 'Submit to ETA' action on invoice list and form views

Cancellation and rejection handling that keeps the ETA document status in sync with Odoo credit-note and reversal workflows

Company-scoped configuration (client ID/secret, activity code, environment: preview vs production) with credentials stored in res.company settings, isolated per company for multi-company databases

Security via ir.model.access.csv and record rules so only authorized accounting roles can view, sign, submit or cancel ETA documents

Chatter and audit logging of every ETA API request/response for traceability during ETA audits

XML-RPC / JSON-RPC exposure of the eta.document model so external systems can trigger or read submission status programmatically

Preview/sandbox environment toggle so you can validate against ETA's test system before going live

Bilingual (Arabic / English) labels on views and QWeb output to match ETA and local accounting expectations

آرڈر پر تیار، مکمل طور پر آپ کے لیے

خود سیٹ اپ کی ضرورت نہیں — ایک کام کرنے والی ایپ جو ECOSIRE بناتا، انسٹال اور سپورٹ کرتا ہے۔

آپ آرڈر دیتے ہیں

ایک بار کی تعمیر کی قیمت سے آغاز کریں۔ آغاز پر ہم آپ کے ساتھ مل کر دائرہ کار طے کرتے ہیں۔

ہم بناتے اور انسٹال کرتے ہیں

ECOSIRE اسے آپ کے Odoo پر بناتا، ترتیب دیتا اور انسٹال کرتا ہے۔

لائیو + معاونت

آپ تقریباً 2–4 ہفتوں میں لائیو ہو جاتے ہیں، لانچ کے بعد معاونت کی مدت کے ساتھ۔

اس مصنوع کے بارے میں

Egypt's Tax Authority (ETA) mandate requires every taxable business to clear invoices and receipts electronically before they are legally valid — a workflow Odoo core has no concept of. This is a build-to-order Odoo module that ECOSIRE designs, builds, installs and supports specifically for your chart of accounts, tax setup and product catalog. It is not an off-the-shelf apps.odoo.com download; we scope your ETA registration details, GS1/EGS coding scheme and signature hardware, then deliver a tested module against Odoo 17, 18 or 19 (Community or Enterprise) within a 2–4 week lead time.

Under the hood the module extends account.move and pos.order with ETA-specific fields and a new eta.document model that serializes each posted invoice, bill, credit note or debit note into the exact ETA JSON schema (documentType, taxpayerActivityCode, internalID, itemCode, unitType, taxable/discount lines and tax totals). Amounts, tax breakdowns and totals are recomputed with @api.depends compute methods so they always reconcile to the Odoo journal entry rather than being re-keyed. Documents are cryptographically signed using your USB token or HSM (CAdES-BES signature over the canonical JSON), then transmitted to the ETA e-invoice and e-receipt endpoints via their REST API, with the returned UUID, submission UUID and long-ID written straight back onto the Odoo record and shown on the customer QWeb invoice as a QR code.

Every state transition — draft, signed, submitted, valid, rejected, cancelled — is tracked on the Odoo record with the ETA error messages surfaced inline so your accountants can fix and resubmit without leaving Odoo. Bulk submission and automatic retry run as scheduled actions (ir.cron), access is locked down through ir.model.access.csv plus record rules scoped by company, and the whole flow is auditable in the chatter. For retail, the same engine handles POS e-receipts (documentType RECEIPT) so store sales clear against ETA in near real time. ECOSIRE hands over the source, the configuration, documentation, admin training and a support window — and keeps the connector current as ETA revises its schema.

What you get

Complete, commented Odoo module source (models, views, security, QWeb report, ir.cron actions) delivered as a versioned Git repository targeting your Odoo 17, 18 or 19 edition

Installation and configuration on your environment: ETA client credentials, taxpayer activity code, signing hardware bridge and preview-vs-production environment wiring

GS1/EGS product coding mapping set up and validated for your live product catalog, with a documented process for adding new products

Customized QWeb invoice report carrying the ETA QR code and document identifiers, matched to your branding

Administrator and accountant documentation covering day-to-day submission, error resolution, resubmission and cancellation flows

Live hands-on training session for your finance/accounting team plus a recording

Sandbox validation report showing successful ETA preview-environment submissions before go-live

A defined post-go-live support window with SLA-backed response times for issues and configuration questions

Who this is for

Egyptian SME finance manager under the ETA mandate

Runs accounting on Odoo and must clear every invoice and receipt through ETA before it is legally valid. Needs submission, signing and error handling to happen inside Odoo rather than re-keying data into the ETA portal.

MENA Odoo implementation partner

Delivers Odoo to Egyptian clients and needs a proven, supported ETA connector to bundle into projects across Odoo 17/18/19 — with source, documentation and a maintenance path instead of building and maintaining the integration in-house.

Retail / multi-branch operator using Odoo POS

Sells through physical stores and must submit ETA e-receipts for point-of-sale transactions. Needs POS e-receipt clearance and GS1/EGS product coding wired into the existing POS and inventory setup.

Group CFO / multi-company controller

Oversees several Egyptian entities in one Odoo database and needs company-scoped ETA credentials, record rules and consolidated visibility into submission status and rejections across all companies.

How Egypt ETA Electronic Invoice & Receipt Compares

Criterion	ECOSIRE	Custom Build	Competitor
ETA-compliant JSON, signing and submission out of the box	Included	Partial support	Partial support
E-receipt (POS) clearance to ETA	Included	Partial support	Not included
GS1 / EGS product code mapping and validation	Included	Partial support	Partial support
USB token / HSM digital signature integration	Included	Partial support	Partial support
Tailored to your chart of accounts, taxes and catalog	Included	Included	Not included
Source code handed over with documentation and training	Included	Included	Partial support
Ongoing patching for ETA schema/endpoint changes	Included	Not included	Partial support
Supported across Odoo 17, 18 and 19 (Community & Enterprise)	Included	Partial support	Partial support

Frequently Asked Questions about Egypt ETA Electronic Invoice & Receipt

How long until the module is delivered and live?

This is a build-to-order module, not an instant download. After a short scoping call to confirm your Odoo version and edition, ETA registration and taxpayer activity code, signing hardware (USB token or HSM) and product coding scheme, typical delivery is 2–4 weeks. That includes development, sandbox validation against ETA's preview environment, installation on your server, and team training before go-live.

What support and updates are included after go-live?

Every engagement includes a defined post-go-live support window with SLA-backed response times for bugs, submission errors and configuration questions. Because ETA periodically revises its JSON schema, endpoints and rules, we patch and re-test the connector for those changes during your support window so submissions keep clearing. Extended support and maintenance can be renewed after the initial window.

Does it support e-receipts for POS, or only invoices?

Both. The same engine handles ETA invoices, credit notes and debit notes from account.move, and e-receipts (documentType RECEIPT) from Odoo POS orders, so retail point-of-sale sales are cleared with ETA in near real time alongside your standard invoicing.

Which Odoo versions and editions does it work with?

We build against Odoo 17, 18 or 19 — you tell us which. It works on both Community and Enterprise; ETA compliance lives in the accounting and POS layers we extend (account.move, pos.order) rather than depending on Enterprise-only features. If you later upgrade Odoo, we migrate the module as part of a follow-on engagement.

How does digital signing and the USB token / HSM work?

ETA requires each document to be cryptographically signed with your registered certificate. We configure a signing bridge that produces a CAdES-BES signature over the canonical ETA JSON using your USB token or HSM, then submit the signed payload to ETA. We scope your specific certificate provider and signing hardware during onboarding and handle the integration.

Will my product data and taxes actually match what ETA expects?

Yes. Product lines carry a GS1 GTIN or ETA EGS code via a mapping field on product.template that is validated before submission, and all totals, discounts and tax subtotals are recomputed with @api.depends compute methods so the ETA document reconciles exactly to the Odoo journal entry — no manual re-keying and no drift between what Odoo shows and what ETA receives.

Is it secure and auditable?

Access is controlled through ir.model.access.csv and record rules scoped per company, so only authorized accounting roles can sign, submit or cancel ETA documents. Every ETA API request and response is logged to the record's chatter for full traceability during an ETA audit, and credentials are stored per company in Odoo settings.

Egypt ETA Electronic Invoice & Receipt

Sync Odoo invoices, bills and credit/debit notes with Egypt's ETA e-invoice system, plus POS e-receipts. Built, installed and supported by ECOSIRE.

Digital signature of the canonical JSON via USB token or HSM (CAdES-BES), with a signing bridge/agent that ECOSIRE configures against your certificate provider

Direct submission to ETA e-invoice and e-receipt REST endpoints, storing the returned document UUID, submission UUID and long-ID back on the account.move / pos.order record

E-receipt (POS) submission support with documentType RECEIPT for retail and near-real-time store clearance from the Odoo POS session

اہم خصوصیات