Egypt ETA E-Invoicing Compliance

This is a build-to-order extension, not an instant AppSource install. After a short scoping call we typically build, install and validate it in your sandbox within 2 to 4 weeks depending on the complexity of your tax setup, item catalog and signing method. ECOSIRE deploys it as a per-tenant AL extension into your Business Central environment and runs full sandbox testing against the ETA before production go-live.

The ETA specification, code tables and validation rules change over time. Under your support agreement ECOSIRE maintains the extension against ETA spec updates, fixes issues, and assists with Business Central version upgrades so your submissions keep clearing. Support covers configuration changes, new item-code mappings and help reconciling rejected documents.

Yes. ETA requires each document to be signed (CAdES). The extension integrates with your signing method — USB cryptographic token, HSM, or a signing service — and invokes the signing step automatically before submission, so users do not handle the cryptography manually.

Yes. It submits e-invoices and credit notes from Posted Sales documents and e-receipts from POS/retail documents, mapping each to the correct ETA document structure, with status tracking on both paths. The exact POS integration is scoped to your Business Central retail/POS configuration during the build.

Yes. It is delivered as an AL extension compatible with both Business Central online (SaaS) and on-premises deployments. Signing hardware and outbound connectivity to the ETA API are configured to suit your deployment model — for SaaS, signing typically routes through a service endpoint since SaaS cannot access local USB tokens directly.

Yes. A maintainable mapping table links each Business Central item to its ETA-registered EGS or GS1 product code, and we populate it for your active catalog during delivery. New items can be mapped by your team afterward, with validation that flags any unmapped item before submission.