Most EU finance teams running ERPNext hit the same wall as ViDA and national e-invoicing mandates approach: ERPNext core produces a PDF Sales Invoice and a print format, but nothing that speaks Peppol. There is no native UBL 2.1 generation, no EN16931 semantic validation, no Access Point transport, and no inbound e-document lane. That leaves teams re-keying invoices into a government or provider portal, or running a spreadsheet-to-portal shuffle that breaks the moment volume, entity count or cross-border traffic grows. Once a tax authority or a large customer requires structured e-invoicing, a PDF is no longer a legal invoice — and ERPNext, out of the box, cannot produce the structured document the network expects.

ECOSIRE builds a proper Frappe app — its own module, DocTypes, roles and permissions — that lives inside your ERPNext bench rather than beside it. The core is a UBL 2.1 generator that maps the ERPNext Sales Invoice and credit notes to a compliant Peppol BIS Billing 3.0 document: seller and buyer Party blocks with the correct Peppol participant IDs and scheme identifiers (0088 GLN, 0192 org number, VAT-based schemes), InvoiceLine rows carrying EN16931 tax categories, allowances and charges, rounding and the mandated code lists. Every document is run through EN16931 / BIS 3.0 schematron validation before it is allowed to leave the system, so malformed documents are caught at source instead of being rejected days later by the receiver's Access Point.

Technically, generation and dispatch hook into the ERPNext document lifecycle. hooks.py doc events on Sales Invoice (on_submit, on_cancel) trigger UBL build and transmission; a dedicated Peppol Document DocType stores the generated XML, the transmission ID, participant details and a status field, giving finance a clean audit trail. Outbound transmission calls your chosen Peppol Access Point service provider's API — we integrate with the provider you already use or help you select one; ECOSIRE does not become the Access Point itself. Inbound documents are polled on a scheduler_events cron, parsed from UBL back into ERPNext, and matched against open Purchase Order / Purchase Invoice records with clear exception handling when a match is uncertain. Participant lookup and validation (SML/SMP-style resolution via the provider) is exposed as a whitelisted method so users can verify a counterparty is Peppol-reachable before sending. A client script surfaces send status, validation errors and a "resend" action directly on the invoice form, and role profiles keep e-invoicing actions scoped to finance staff.

Because this is build-to-order, nothing is a black box. After a short scoping call we confirm your legal entities, VAT scheme identifiers, Access Point provider, the document types in scope (invoice, credit note, self-billing) and any country-specific CIUS profiles you need. ECOSIRE then builds against your Frappe/ERPNext v15 or v16 bench, validates on a staging copy of your data through real UAT with your finance team, and installs to 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 — so the app is yours to run, extend and audit, not a subscription you rent.