Egypt's mandatory electronic invoicing programme, enforced by the Egyptian Tax Authority (ETA), requires every VAT-registered taxpayer to issue, digitally sign, and submit all B2B invoices and B2C receipts through the ETA's centralised e-invoice platform in real time. For businesses running Foodics POS, Odoo ERP, SAP, or any enterprise accounting system, this creates an immediate operational challenge: every invoice generated in the source system must be transformed into ETA's UBL 2.1 JSON format, signed with the company's registered digital certificate, and submitted before the transaction closes.
The Compliance Challenge
Manual processes fail at scale. A restaurant chain processing 2,000 receipts per day cannot manually re-enter each one into the ETA portal. An Odoo-based distributor cannot have its finance team manually export, sign, and upload invoices one at a time. The compliance risk, the operational overhead, and the exposure to ETA penalties for late or missing submissions make automation the only viable path forward — not a future consideration, but an immediate operational requirement.
The ETA Enterprise Connector
The Cloudypedia ETA Enterprise Connector is a purpose-built integration layer that sits between any enterprise application and Egypt's ETA e-invoice platform. It intercepts invoice and receipt events from the source system, transforms them into ETA's required UBL 2.1 format, applies a cryptographic signature using the company's registered certificate, and submits the document — all within seconds of the originating transaction. Upon ETA acceptance, the connector writes the ETA-assigned UUID back to the source system, closing the compliance loop without any human intervention.
The connector is not a SaaS portal and not a manual upload tool. It is a silent, always-on middleware component that makes compliance invisible to the business — every invoice is compliant by default, from the moment it is created.
How It Works
When a Foodics order is completed, an Odoo invoice is confirmed, or any configured event fires in the source system, the connector receives it via API call, database trigger, or webhook. The Document Transformer maps the source fields — buyer TIN, seller TIN, line items, tax codes, totals, currency — to ETA's exact UBL 2.1 schema and validates the output. The Digital Signature Engine applies the required CAdES-BES cryptographic signature using the company's USB token, HSM, or cloud HSM. The signed document is submitted to ETA's API. ETA's response — accepted, rejected, or pending — is captured, logged, and the ETA UUID is written back to the originating record in the source system.
Rejections are not silently dropped. The connector parses the ETA error code, logs the reason with the full ETA response payload, and triggers a configurable re-submission or alert workflow so the finance team can resolve and resubmit within the compliance window.
Source System Adapters
The connector ships with pre-built adapters for Foodics (via the Foodics F&B API), Odoo 16 and 17 (via XML-RPC and the Odoo external API), and a generic REST/webhook adapter for any other source system. For SAP, Oracle Financials, or custom ERP systems, the adapter layer is extended during the implementation engagement. No changes are required to the source application — the connector listens at the event layer without touching core application logic or database schemas.
Full Compliance Scope
The connector handles both document types mandated by the ETA programme: B2B Electronic Invoices with full UBL 2.1 structure, buyer and seller TIN, line-item tax breakdown, and cryptographic signature; and B2C Electronic Receipts in ETA e-receipt format for retail and F&B point-of-sale transactions. Credit notes, debit notes, and invoice cancellations are handled natively. Every document submitted is stored in an immutable audit log with its ETA UUID, submission timestamp, ETA response payload, and document hash — providing the complete evidence trail required for tax authority inspections and financial audits.