ERPNext UAE E-Invoicing (Peppol) Connector

ECOSIRE builds a proper Frappe app — installed on your own bench as an app alongside erpnext — rather than a set of loose customizations. The connector adds its own module with DocTypes such as E-Invoice, E-Invoice Log, and Peppol Settings (single DocType for ASP credentials, participant IDs, and environment toggles). A hooks.py doc event on Sales Invoice.on_submit builds the PINT-AE UBL 2.1 XML from the submitted invoice, runs it through UAE schema and schematron validation, and — on success — hands it to your chosen Peppol Access Point / ASP for transmission, recording the response, message ID, and status back onto the linked E-Invoice record. Buyer and supplier participant resolution (endpoint/SML lookup) is wired in so documents route to the correct recipient, and a scheduler event polls for delivery acknowledgements and clearance status.

Under the hood it uses the tools ERPNext developers expect: server scripts and Python controllers for the mapping logic, whitelisted methods exposed over the Frappe REST API (/api/method/...) so you can trigger or re-transmit an e-invoice programmatically, a client script that surfaces validation errors and a "Send to Access Point" action right on the Sales Invoice form, and role profiles / permission rules so only an authorized "E-Invoicing Manager" can edit credentials or force-resend. Failed transmissions are retried and logged, never silently dropped, and every payload is stored for the statutory retention period. Where your Access Point/ESP provider (or the FTA reporting hook) has its own API, we integrate against it directly; where you have custom item categories, free zones, or reverse-charge scenarios, we map them into the correct PINT-AE tax categories during the scoping phase.

Because this is build-to-order, nothing is downloaded and dropped on your system blind. We start with a short scoping call to confirm your ERPNext version (v15 or v16), your chosen Access Point/ASP, your tax and free-zone setup, and your go-live deadline. We then build against your actual invoice data on a staging bench, run UAT with your finance team, and only after sign-off do we install into production with a documented rollback plan. Typical delivery is 2 to 4 weeks from confirmed scope, and you receive the full source in a git repository you own.