EU e-invoicing has stopped being optional. Between existing national mandates (Italy's SdI, France's mandate rollout, Poland's KSeF, Belgium's 2026 B2B requirement) and the incoming VAT in the Digital Age (ViDA) framework, businesses running ERPNext are increasingly required to issue structured, machine-readable invoices — not PDFs — and to route them over the Peppol network. ERPNext core does an excellent job of the accounting: it produces a clean Sales Invoice, taxes, and print formats. What it does not do out of the box is emit a valid EN 16931 UBL document, apply the country-specific CIUS/national rules, look up a recipient's Peppol Participant ID, or hand the document to a certified Access Point for delivery. That gap is exactly where teams get stuck weeks before a deadline.

ECOSIRE builds a proper Frappe app — a dedicated module with its own DocTypes, hooks.py doc events, server scripts, and scheduler entries — that plugs into your existing ERPNext without forking core. On Sales Invoice submit (via a doc_events hook), the app maps ERPNext fields to a Peppol BIS Billing 3.0 payload and generates syntactically valid EN 16931 UBL 2.1 XML. Before anything leaves your system it is validated against the EN 16931 schematron and the applicable CIUS profile, so structural or VAT-rule errors surface inside ERPNext — on a linked Peppol Document DocType with a clear status and a human-readable error report — rather than as an opaque rejection from a downstream authority. Master data is handled properly too: Customer and Company gain Peppol identifiers (electronic address scheme + participant ID), and a Participant Directory lookup confirms the recipient is registered and reachable on the network before you send.

Transmission runs through your chosen certified Peppol Access Point. We integrate the AP's API for outbound send and for inbound receive (mapping incoming supplier UBL back into ERPNext Purchase Invoice drafts), track the message and its acknowledgements against the Peppol Document record, and use Frappe scheduler_events to poll delivery status and retry transient failures with backoff. Whitelisted Frappe REST methods expose send/status/lookup actions so your own automations or a client-side script button on the invoice can trigger and monitor transmission. Role profiles and DocType permissions keep e-invoicing operations scoped to the right users, and every action is written to the Frappe audit trail. The design targets ViDA readiness — continuous transaction controls and near-real-time reporting — so the same pipeline extends as the digital reporting requirements land.

Because this is build-to-order, nothing is guessed. We start with a short scoping call to confirm your EU country/countries, the specific CIUS/national profile(s) you need, your Access Point provider, and your ERPNext version (v15 or v16). We build against a copy of your data on a staging bench, run UAT with real invoices end-to-end (generate → validate → send → acknowledge), and only then install on production behind a rollback plan. Typical delivery is one working week from confirmed scope. You receive the full app source and its git repository, so you are never locked to us — though a post-go-live support window is included for the settling-in period.