Large UAE taxpayers running ERPNext are facing the FTA e-invoicing mandate rolling out from 2027, and the standard Sales Invoice DocType simply doesn't speak the required language. ERPNext core can print a PDF and post GL entries, but it has no concept of PINT AE (the UAE's Peppol BIS 3.0 specialization), no UBL 2.1 syntax binding, no Accredited Service Provider (ASP) connection, and no way to track a clearance response from the FTA. Finance teams are left staring at a compliance deadline with a system that stops exactly where the regulation begins.

ECOSIRE builds a dedicated Frappe app — a proper module with its own DocTypes, not a pile of print-format hacks — that turns each posted Sales Invoice into a validated PINT AE XML document and moves it across the Peppol 5-corner model to your buyer via your chosen ASP. On on_submit of a Sales Invoice, a hooks.py doc event maps your ERPNext data (company TRN, customer TRN, AED currency and exchange rate, item-level VAT rate mapping to the correct UAE tax categories) into UBL 2.1, runs Schematron-style validation against the PINT AE rules, and hands the payload to an ASP connector. A new E-Invoice Log DocType stores the generated XML, the ASP transmission id, the clearance status, and every FTA API response so your tax team has a full audit trail inside ERPNext.

Technically, the app exposes whitelisted methods over the Frappe REST API for on-demand generation and re-submission, uses scheduler events to poll or reconcile pending transmissions, and processes inbound ASP webhooks to flip invoice status (cleared, rejected, delivered) as the corners report back. Role profiles and DocType permissions restrict who can transmit, cancel, or view raw XML, and client scripts surface a clear status indicator and action buttons directly on the Sales Invoice form so accountants never leave the screen they already work in. The ASP layer is built as a connector interface so your specific Accredited Service Provider — chosen from the FTA's accredited list — is the one we wire in and certify against.

Because this is build-to-order, nothing is a generic download. We start from a scoping call to confirm your ASP, your entity structure, your VAT category mix, and your Frappe/ERPNext version (v15 or v16). We build against your exact chart of accounts and tax templates, validate on a staging bench, run UAT with your finance team, and then install into production with a rollback plan. You receive the full source, a git repository handover, technical and user documentation, a training session, and a post-go-live support window. Typical delivery is one working week from confirmed scope, depending on ASP onboarding lead times, which are outside our control.