If you run your business on ERPNext, the UAE's mandatory e-invoicing mandate (phased from July 2026) is a problem ERPNext core does not solve. Out of the box, ERPNext produces a print-format PDF and can email it, but it has no concept of PINT AE — the UAE's Peppol-based invoice specification — no notion of the 51 mandatory FTA data fields, no EN 16931 semantic validation, and no way to transmit a structured invoice through an accredited Access Point on the Peppol network. A PDF or a plain UBL export is not a compliant e-invoice, and the 5-corner Decentralised Continuous Transaction Control model the FTA has adopted means your invoice has to be machine-validated and exchanged provider-to-provider, not just generated. This is exactly where a stock ERPNext instance runs out of road.

ECOSIRE builds a proper Frappe app — its own module with real DocTypes — that plugs into your existing Sales Invoice workflow. A hooks.py doc event (on_submit / on_update_after_submit) fires a server-side mapper that reads the submitted Sales Invoice, its Customer, Company, tax templates, and line items, and generates conformant PINT AE XML: the Peppol BIS Billing 3.0 UBL syntax bound to the UAE Data Dictionary. The mapper populates all 51 mandatory fields — seller and buyer TRN, Emirate-level addressing, scheme identifiers, tax category codes (standard/zero-rated/exempt/reverse-charge/out-of-scope), line-level and document-level allowances and charges, and currency handling — and stores each generated document as its own PINT AE Document DocType record with a status field, the raw XML, and a validation report attached, so every invoice has an auditable e-invoicing trail inside ERPNext.

Before anything leaves your system, the app runs the invoice through EN 16931 business-rule validation (the BR- and BR-AE- / UAE rule set) so structurally or semantically invalid invoices are caught and flagged against the originating Sales Invoice rather than silently rejected downstream. Valid documents are then handed to your accredited service provider (ASP) / Peppol Access Point over their API for signing and network delivery, and status callbacks (accepted, rejected, delivered) are written back onto the PINT AE Document record. A Frappe scheduler event polls or retries pending and failed transmissions, whitelisted REST methods expose submit/status/retry to integrations and the client script layer surfaces validation errors and transmission state directly on the Sales Invoice form. Both B2B and B2G flows are supported, and access is governed through dedicated roles and a role profile so only authorised users can transmit or reprocess invoices.

Because this is build-to-order, ECOSIRE tailors it to your Access Point of choice, your Company/branch and TRN setup, your tax templates, and your Chart of Accounts — there is no generic one-size download. After a short scoping call we confirm the exact fields, your ASP, and your ERPNext version (v15 or v16), then build, test on a staging clone of your instance, and hand over. Typical delivery is one working week from confirmed scope, and you receive the installable source, the git repository, documentation, training, and a post-go-live support window.