Peppol E-Invoicing Network Connector

Key Features

Peppol BIS Billing 3.0 (EN 16931) UBL 2.1 XML generation from submitted ERPNext `Sales Invoice` records via a `hooks.py` `on_submit` doc event

Schematron validation against the EN 16931 and Peppol BIS rule sets before transmission, with the full validation report stored on the document

Certified Access Point connectivity abstracted behind an adapter so your provider's AS4/REST API (and credentials) is configured, not hardcoded

Inbound document ingestion via a `scheduler_events` poll or a whitelisted webhook endpoint the Access Point pushes to

Automatic mapping of received UBL to a draft `Purchase Invoice`, matched to `Supplier` by Peppol participant ID

Participant (SMP) lookup exposed as a whitelisted method and a client-script button to confirm a partner is reachable and which document types they accept

Dedicated `Peppol Document` DocType capturing message ID, direction, status, raw UBL payload, and transmission log for audit

Status workflow (`Draft` → `Validated` → `Sent` → `Delivered` / `Rejected`) with automatic retry and error surfacing on failed transmissions

Country-profile / CIUS support (national BIS variants and rules such as German, Belgian, or Nordic customizations) configured to your entity

Endpoint scheme handling (GLN, VAT, national registry IDs) with a `Peppol Settings` single DocType for sender identity and endpoint IDs

`Peppol Manager` role profile and per-DocType permissions controlling who can transmit, retry, and view raw payloads

Tax mapping from ERPNext `Sales Taxes and Charges Template` / `Tax Category` to the correct UBL tax scheme, category codes, and exemption reasons

Frappe REST API access to all connector data plus whitelisted actions (`send`, `retry`, `lookup_participant`) for integration and scripted use

Structured error logging to the ERPNext `Error Log` and optional email/notification alerts on rejected or undeliverable documents

Built and tested for Frappe/ERPNext v15 and v16, packaged as an installable versioned Frappe app

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your ERPNext.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

EU and international businesses are increasingly mandated to send and receive structured e-invoices over the Peppol network, but ERPNext core stops at a PDF Sales Invoice print format. There is no native BIS Billing 3.0 UBL generation, no Access Point connectivity, no participant (SMP) lookup, and no way to ingest an inbound supplier invoice as a validated Purchase Invoice. Teams end up rekeying invoices into a portal or paying per-document fees to a disconnected middleware tool that never reconciles back to ERPNext. That gap is exactly what this connector closes.

ECOSIRE builds a proper Frappe app (for example peppol_connector) with its own module, DocTypes, and hooks.py doc events rather than a pile of loose customizations. Outbound, a doc_events hook on Sales Invoice on_submit renders a Peppol BIS Billing 3.0 UBL 2.1 XML document from the submitted invoice — mapping company and customer Address/Tax ID, item lines, UOM, tax templates and Tax Category to the correct UBL elements — validates it against the Peppol EN 16931 and BIS schematrons, and transmits it to your chosen certified Access Point over its API (AS4/REST, depending on provider). A dedicated Peppol Document DocType stores the transmission state, message ID, validation report, and the raw UBL for audit, with a status workflow (Draft → Validated → Sent → Delivered / Rejected).

Inbound is handled by a Frappe scheduler event (scheduler_events in hooks.py) that polls the Access Point for new documents, or a whitelisted REST endpoint the AP can push to as a webhook. Received UBL is parsed, schematron-validated, mapped to a draft Purchase Invoice (or held as a Peppol Document for review), and linked to the matching Supplier by their Peppol participant ID. Participant (SMP) lookup — confirming a trading partner is reachable on the network and which document types they accept — is exposed as a whitelisted method callable from a client script button on the invoice, so users verify a recipient before they hit submit. Everything is governed by ERPNext's permission model: a Peppol Manager role profile and per-DocType permissions control who can transmit, retry, or view raw payloads.

Because this is build-to-order, nothing ships as a blind download. We start with a scoping call to confirm your legal entity, country profile (BIS variants and any national CIUS such as the German or Belgian rules), your Access Point provider and credentials, and the exact Sales/Purchase Invoice fields to map. We build against a staging copy of your ERPNext v15 or v16 instance, run UAT with your real invoice data and sandbox Access Point, and only then install to production with a documented rollback. Typical delivery is 2–4 weeks from confirmed scope. You receive the full source as a versioned Frappe app in a git repository you own, along with a post-go-live support window.

What you get

Installable source code for your build — a versioned Frappe app (module, DocTypes, hooks, scripts) targeting your ERPNext v15/v16

Installation and configuration on your instance, including `Peppol Settings`, Access Point credentials, and country/CIUS profile

Technical documentation: DocType schema, `hooks.py` events, whitelisted methods, scheduler jobs, and the Access Point adapter

User guide plus a live training session for your finance/AP team covering send, receive, lookup, and error handling

UAT on a staging instance with your real invoice data against a sandbox Access Point, plus a documented rollback plan

Post-go-live support window for defect fixes and configuration adjustments after production cutover

Git repository handover — you own the full source history and can maintain or extend it independently

Onboarding checklist for registering your endpoint on the Peppol network via your Access Point provider

Who this is for

EU finance / AP lead under an e-invoicing mandate

Runs ERPNext for a business subject to Peppol or national e-invoicing rules and needs compliant BIS 3.0 send/receive inside ERPNext, not a separate portal, before the mandate deadline.

Cross-border seller trading across the EU and beyond

Sells into multiple countries and must exchange structured invoices with public-sector and enterprise buyers who only accept Peppol, needing correct country CIUS handling and participant verification.

ERPNext system administrator / integrator

Owns the ERPNext instance and wants a clean, upgrade-safe Frappe app with documented DocTypes, hooks, and whitelisted methods — plus git source they can maintain — rather than brittle server-script hacks.

Finance operations manager tracking compliance and audit

Needs every outbound and inbound document, its validation report, and its delivery status stored and searchable in ERPNext for audit, with role-based control over who can transmit or retry.

How Peppol E-Invoicing Network Connector Compares

Criterion	ECOSIRE	Custom Build	Competitor
Peppol BIS 3.0 send/receive in ERPNext	Built in, both directions, via doc events and scheduler	Possible but must be designed from scratch	Send often covered; receive frequently missing
Fit to your entity and country CIUS	Scoped and validated to your profile before build	Whatever you specify to your developers	Generic profiles; national variants may cost extra
Access Point integration	Adapter to your certified provider, credentials configured	You build and maintain the integration	Often locked to the vendor's own AP
Source code ownership	Full Frappe app in a git repo you own	You own it, but you built and must maintain it	Usually closed or licence-restricted
Audit trail and validation reports	`Peppol Document` DocType stores UBL, status, reports	Only if you design and build it	Varies; often outside ERPNext
Upgrade safety on v15/v16	Clean app with hooks, tested per version	Depends on developer discipline	Depends on vendor's ERPNext compatibility
Delivery model	Build-to-order, 2–4 weeks, UAT + rollback	Full project timeline and management on you	Instant install but generic and unsupported for your case
Support after go-live	Support window plus optional ongoing packages	Your own team or contractor	Per-vendor SLA, often per-document fees

Frequently Asked Questions about Peppol E-Invoicing Network Connector

Is this a ready-made app I can download and install today?

No. It is build-to-order. ECOSIRE scopes it to your legal entity, country profile, and Access Point, builds it against a staging copy of your ERPNext, runs UAT, then installs to production. You are not buying a blind download — you are commissioning a tested, owned Frappe app.

How long does delivery take?

Typically 2–4 weeks from confirmed scope. The clock starts once we have agreed the field mapping, your country CIUS variant, and your Access Point credentials on the scoping call. Complex multi-entity or multi-country setups can run longer and we will say so up front.

Do you provide the Peppol Access Point, or do I need my own?

Peppol requires a certified Access Point provider to transmit on the network — that is a separate service you contract. Our connector integrates with your chosen provider's API. If you do not have one yet, we will advise on selection and help register your endpoint during onboarding.

Which ERPNext versions are supported?

We build and test for Frappe/ERPNext v15 and v16, packaged as a standard installable Frappe app. Tell us your exact version and hosting (Frappe Cloud, self-hosted, or bench) on the scoping call and we build against that.

What about support and updates after go-live?

Every build includes a post-go-live support window for defect fixes and configuration adjustments. Because you receive the full git repository, your team can maintain and extend it. ECOSIRE also offers ongoing support and schematron/BIS-version update packages as your compliance requirements evolve.

Can it receive supplier invoices, not just send?

Yes. A scheduler event polls your Access Point (or a whitelisted webhook receives pushes), validates the inbound UBL, and maps it to a draft `Purchase Invoice` linked to the supplier by their Peppol participant ID for your team to review and submit.

How do you handle my country's specific invoicing rules?

Peppol BIS has national CIUS variants and additional rules. On scoping we confirm your country profile and validate against the correct schematron set, so documents pass both the EN 16931 core and your jurisdiction's specific requirements.