EU and international firms are increasingly obliged to exchange invoices as structured EN 16931 documents over the Peppol network rather than as PDFs or emails. ERPNext core can produce a print-format invoice and a generic e-invoicing export, but it has no concept of a Peppol participant, no SMP/SML lookup, no Access Point transport, and no BIS Billing 3.0 UBL that will pass Schematron validation at the receiver. Teams end up bridging the gap with a manual portal, a third-party SaaS with per-document fees, or a spreadsheet export — none of which keep the audit trail inside ERPNext where finance actually works.

ECOSIRE builds a proper Frappe application (its own module, DocTypes, and hooks.py) that turns your ERPNext into a first-class Peppol endpoint. We map Sales Invoice (and, where in scope, credit notes and Purchase Invoice) to Peppol BIS Billing 3.0 UBL, run EN 16931 business-rule and Schematron validation before anything leaves the system, resolve the recipient's Access Point through SMP/SML participant lookup, and hand the signed payload to your chosen Access Point over AS4. A dedicated Peppol Document DocType stores the outbound/inbound payload, transmission status, message ID, and validation report, so every exchange is traceable from the invoice it belongs to.

Technically, submission is wired through on_submit doc events in hooks.py so an invoice can be queued to Peppol the moment it is submitted, with a Peppol Settings single DocType holding your participant ID, Access Point credentials, endpoint scheme, and default profile. A scheduler event polls the Access Point for inbound documents and creates draft Purchase Invoice or Peppol Document records from received UBL, mapping supplier, tax, and line data back into ERPNext. Whitelisted methods exposed over the Frappe REST API let you trigger send, re-validate, or fetch transmission status programmatically, and client scripts add a "Send to Peppol" action plus a live status indicator on the invoice form. Country-specific and PINT profiles (e.g. national CIUS layers on top of BIS) are configured per company, and role profiles / permissions restrict who can transmit or view raw payloads. It targets ERPNext and Frappe v15 and v16.

Because this is build-to-order, it starts with a scoping call, not a download. We confirm your target countries and Peppol profiles, your Access Point provider (or advise on one), the document types in scope, and your ERPNext version, then quote a fixed build. Typical delivery is 2–4 weeks from confirmed scope. You receive the installable source for your version, installation and configuration on your environment, UAT on a staging bench with a rollback plan, documentation, a training session, and a post-go-live support window. The git repository is handed over so the code is yours to keep and extend.