Egyptian businesses running ERPNext hit a hard wall the moment they fall under the ETA e-invoicing and e-receipt mandate. ERPNext core will happily produce a Sales Invoice and a POS transaction, but it has no concept of the Egyptian Tax Authority's document schema, no way to sign a document against your registered device or issuer, and no channel to submit and reconcile status with the ETA production and pre-production environments. Teams end up re-keying every invoice into the ETA portal by hand, which does not scale past a few dozen documents a day and leaves the accounting team blind to which invoices were accepted, rejected, or still pending clearance.

ECOSIRE builds a dedicated Frappe app that closes this gap end to end. The connector adds its own module, DocTypes (an ETA settings/configuration DocType, an EGS/GS1 item-code mapping DocType, and a submission-log DocType keyed to each Sales Invoice, POS Invoice, and credit/debit note), and a set of hooks.py document events. On on_submit of a Sales Invoice or POS Invoice, a server-side handler transforms the ERPNext document into the ETA-compliant invoice JSON (and the canonical signed structure the ETA requires), resolves each line's tax type, subtypes, and unit codes, maps your item to its registered EGS or GS1 code, computes the document totals exactly the way the ETA validator expects, and enqueues the submission through Frappe's background job queue so a slow ETA response never blocks the user in the UI.

Technically, the flow is grounded in real Frappe primitives rather than a black box. Authentication and token refresh against the ETA identity service run on a scheduler_events hook so your access token is always valid. Digital signing is handled through the ETA device/issuer onboarding you complete once, with the connector holding the credentials in a secured settings DocType and applying the cryptographic signature at submission time. Whitelisted Python methods (@frappe.whitelist()) expose safe, permission-checked actions — submit, re-submit, cancel, and refresh-status — that are wired to client scripts and custom buttons on the invoice form, so an accountant clicks one button and sees the returned ETA UUID, long-ID, and clearance status written straight back onto the document. A scheduled job also polls pending submissions and reconciles their final ETA status, and every attempt is recorded in the submission-log DocType with the full request/response payload for audit. E-receipt (POS) submission follows the parallel ETA e-receipt path with its own signing and batching rules, and role profiles/permissions keep submission and configuration rights scoped to the right users. Everything is exposed over the standard Frappe REST API and targets Frappe/ERPNext v15 and v16.

Because this is build-to-order, nothing ships as an instant download. After a short scoping call we confirm your exact ETA registration model (issuer, branches, activity codes, device vs. issuer signing), your invoice and POS volume, and any localization your chart of accounts and tax templates need. Typical delivery is 2–4 weeks from confirmed scope. We build against your real document types on a staging instance, run UAT with your accounting team using your own invoices in the ETA pre-production environment, and only then cut over to production with a rollback plan. You receive the full source, the git repository, documentation, training, and a post-go-live support window — you are never locked out of your own connector.