ERPNext Egypt E-Invoicing & E-Receipt Connector

Key Features

Custom Frappe app with its own module, packaging ETA settings, EGS/GS1 mapping, and submission-log DocTypes rather than bolting fields onto core

`hooks.py` doc events on Sales Invoice and POS Invoice `on_submit`/`on_cancel` that build and enqueue the ETA payload without blocking the UI

ETA-compliant invoice document generation in the required JSON/canonical signed structure, with correct taxTotals, taxType/subType and unit codes

Digital signing tied to your ETA device or issuer onboarding, with signing credentials held in a secured, permission-scoped settings DocType

E-receipt (POS) submission on the ETA e-receipt path, including receipt batching and its distinct signing rules

EGS / GS1 item code mapping DocType so every ERPNext Item resolves to its registered product code at submission time

OAuth token acquisition and automatic refresh against the ETA identity service via a `scheduler_events` job so tokens never expire mid-run

Whitelisted (`@frappe.whitelist()`) submit / re-submit / cancel / refresh-status methods, permission-checked, callable from the form and the Frappe REST API

Client scripts adding one-click submit and status buttons to the invoice form, writing the returned ETA UUID, long-ID, and clearance status back to the document

Submission-log DocType per document storing the full request/response, error codes, and retry history for a defensible audit trail

Scheduled reconciliation job that polls pending submissions and updates their final ETA accepted/rejected/valid status automatically

Credit note and debit note handling mapped to the ETA reference-document rules for returns and adjustments

Configurable pre-production vs. production ETA environment switch so UAT runs safely before go-live

Role profiles and DocType permissions separating who can configure the connector from who can submit invoices, plus Error Log integration for failed submissions

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your ERPNext.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

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.

What you get

Installable source code for your commissioned version of the Frappe app, pinned to your Frappe/ERPNext v15 or v16 instance

Installation and configuration on your staging environment, including ETA settings, signing credentials, and EGS/GS1 mapping setup

Technical documentation covering DocTypes, hooks, whitelisted methods, scheduler events, and the ETA integration architecture

End-user guide plus a live training session for your accounting and POS teams on submitting and reconciling documents

UAT on a staging instance against your real invoices in the ETA pre-production environment, with a documented go-live and rollback plan

Post-go-live support window for bug fixes and ETA acceptance issues after production cutover

Full git repository handover so you own the code and can maintain or extend it independently

Who this is for

Egyptian SME on ERPNext under the ETA mandate

Finance owner at a small or mid-size Egyptian company whose ERPNext already runs sales and accounting, now legally required to clear every invoice through the ETA and unwilling to keep re-keying documents into the tax portal by hand.

Retail / F&B operator needing e-receipt (POS) compliance

Multi-branch retailer or restaurant using ERPNext POS that must submit e-receipts to the ETA. Needs signed, batched receipt submission and per-branch status visibility without slowing down the checkout counter.

ERPNext functional consultant or partner

Implementation partner who owns a client's ERPNext rollout and needs a reliable, source-available ETA connector they can hand over, document, and support rather than building the tax integration from scratch under deadline.

Finance controller / tax manager

Accountant responsible for compliance who needs a defensible audit trail — every submission logged with the ETA UUID, long-ID, and clearance status — and clear reconciliation of which invoices were accepted, rejected, or still pending.

How ERPNext Egypt E-Invoicing & E-Receipt Connector Compares

Criterion	ECOSIRE	Custom Build	Competitor
ETA e-invoice + e-receipt support	Both paths built in, signed and reconciled	Whatever you scope and can finish	Often e-invoice only, e-receipt partial
Fit to your instance	Built against your DocTypes, taxes, and item codes	Fully bespoke if you have the team	Generic; you bend your setup to fit it
Digital signing & device onboarding	Guided onboarding, credentials in secured settings DocType	You implement the crypto and key handling	Varies; signing model may be opaque
Submission tracking & audit trail	Per-doc submission-log with UUID, long-ID, full payload	Only what you build	Basic status field, limited logging
Failure handling & reconciliation	Queued jobs, scheduled re-poll, Error Log integration	Depends on your engineering	Manual retry common
Source code ownership	Full source + git repo handover	You own it by definition	Usually closed/licensed, no source
Delivery model	Build-to-order, 2–4 weeks, UAT + rollback	Unpredictable; hiring and ramp-up	Instant install but generic
Ongoing compliance updates	Support window + update engagements as ETA changes	Your team tracks ETA schema changes	Vendor roadmap, not your priorities

Frequently Asked Questions about ERPNext Egypt E-Invoicing & E-Receipt Connector

Is this a ready-made app I can download and install today?

No. This is build-to-order. ECOSIRE builds the connector against your specific ERPNext instance, ETA registration model, and item catalog, then installs and configures it for you. There is no instant download — the value is a connector that matches your real documents and passes ETA validation, not a generic zip file.

How long does delivery take?

Typical delivery is 2–4 weeks from confirmed scope. The timeline starts once we have agreed the exact requirements in a scoping call — your ETA issuer/device model, branches and activity codes, invoice and POS volume, and any localization your tax templates need. Complex multi-branch or high-volume e-receipt setups sit at the longer end of that range.

Which Frappe / ERPNext versions do you support?

We target Frappe/ERPNext v15 and v16. We build and test against your actual version and site configuration so the app installs cleanly with `bench get-app` / `bench install-app` on your instance, and we confirm compatibility with your custom fields and tax templates during scoping.

How does the digital signing and ETA device onboarding work?

The ETA requires each issuer or device to be onboarded and each document to be cryptographically signed. We help you complete that onboarding, and the connector stores the signing credentials in a secured, permission-scoped settings DocType and applies the signature at submission time — for both e-invoices and POS e-receipts, which follow the ETA's distinct signing paths.

What happens if the ETA rejects an invoice or the service is down?

Submissions run through Frappe's background job queue, so a slow or failed ETA response never blocks the user. Every attempt is written to a submission-log DocType with the full response and error codes, failures surface in the ERPNext Error Log, and a scheduled reconciliation job re-polls pending documents. Rejected invoices are flagged with the ETA reason so your team can correct and re-submit with one click.

Do we own the code, and how do updates and support work?

Yes — you receive the full source and a git repository handover, so you are never locked in. Delivery includes a post-go-live support window for bug fixes and ETA acceptance issues. Beyond that window, or when the ETA changes its schema or signing rules, we offer ongoing support and update engagements to keep you compliant.

Can it handle e-receipts from ERPNext POS as well as standard sales invoices?

Yes. The connector covers both the ETA e-invoice path for Sales Invoices and credit/debit notes, and the separate ETA e-receipt path for ERPNext POS transactions, including receipt batching and the e-receipt signing rules. Configuration and status visibility can be scoped per branch.