Since the Egyptian Tax Authority (ETA) mandate rolled out across VAT-registered businesses, any company crossing the EGP 250,000 registration threshold has to issue structured, cryptographically signed electronic documents — not PDFs — and get each one accepted by ETA in near real time. Miss a submission window, send a malformed taxItem block, or use the wrong TaxType/TaxSubtype code and you face rejections, reconciliation headaches, and penalties. ERPNext gives you clean Sales Invoices, Item masters, and Tax Templates out of the box, but it has no concept of ETA's document envelope, its UUID/hash chain, the certified e-signature step, or the submit-and-poll status lifecycle. That is exactly where core ERPNext runs out of road.

ECOSIRE builds a proper Frappe app — installed on your bench alongside ERPNext — that closes that gap end to end. The app ships new DocTypes (an ETA Settings single for credentials, environment, and issuer data; an ETA Submission log linked one-to-one with each Sales Invoice and POS Invoice; and mapping DocTypes for ETA code lists). A hooks.py doc-event handler fires on invoice submit to serialize the document into ETA's exact JSON schema, resolve every line to a validated TaxType/TaxSubtype pair, apply the certified electronic signature, and either submit immediately or queue it for interval-based batch submission via a Frappe scheduler event. Whitelisted server methods expose the submit, cancel, and status-refresh actions to the desk and to the Frappe REST API, so your own systems can trigger them too.

Once a document is accepted, ETA returns a long UUID, a submission UUID, and a status that changes asynchronously (Submitted → Valid, or Invalid/Rejected with reasons). A scheduled background job polls ETA and writes the current state, the public-share QR/URL, and any rejection reason back onto the linked invoice, so your finance team sees the truth inside ERPNext without logging into the ETA portal. For retail and B2C, the same engine handles the E-Receipt flow: POS transactions are packaged, signed, and submitted on the receipt cadence ETA expects, with the receipt reference stored back on the POS Invoice. Client scripts add status badges and a "Resubmit to ETA" button on the invoice form, and a dedicated role profile keeps signing credentials and submission controls limited to authorized finance users.

Because this is build-to-order, nothing is a black box. We start with a scoping call to confirm your ERPNext version (v15 or v16), your tax setup, which document types are in scope (B2B e-invoice, B2C e-receipt, or both), and your ETA credentials and environment (preprod vs production). We then build against your actual chart of accounts and tax templates, test the full submit/poll/cancel lifecycle on a staging bench, run UAT with your team, and cut over to production with a rollback plan. Typical delivery is one working week from confirmed scope. You receive the full source code and git repository so you are never locked to us — though most clients keep us on for the post-go-live support window and ETA schema updates.