< Compliance />

Send invoices electronically.
Receive them too.

PEPPOL e-invoicing inside ERPNext. Mandatory for Dutch B2G. Increasingly expected in B2B. We make it the default, not an upgrade.

Book a free consultation

PEPPOL Invoice

SINV-2026-00417.xml

<cbc:CustomizationID>

peppol:billing:3.0

<cbc:ID>SINV-2026-00417</cbc:ID>

<cbc:IssueDate>2026-05-11</cbc:IssueDate>

<cac:AccountingSupplierParty>

...

</Invoice>

Schematron validated

Why now

Your customers’ countries are switching.

PEPPOL is mandatory in the Netherlands for B2G already, and the EU is moving fast. Here’s when each market locks in.

NL · Netherlands

LIVE

B2G mandatory

All suppliers to the Dutch government must send PEPPOL invoices since 2017.

BE · Belgium

Jan 1, 2026

B2B mandatory

Every Belgian B2B invoice must be a structured e-invoice from 2026.

DE · Germany

Jan 1, 2027

B2B sending (large firms)

Receiving already mandatory since Jan 2025. Large firms (>€800k turnover) must send from 2027; SMEs from 2028.

FR · France

Sept 1, 2026

B2B (receive)

All French businesses must accept e-invoices by Sept 2026. Sending phases in afterwards.

Paper invoices. PDFs in email. That door is closing.

Dutch B2G already requires PEPPOL for many transactions. B2B is heading the same way. Without an integration, your finance team is manually matching supplier PDFs to purchase orders — and your customers are waiting for invoices that should land in their ERP automatically.

What you get

PEPPOL invoices, end-to-end inside ERPNext.

Send PEPPOL invoices on submit

ERPNext produces a UBL 2.1 XML the moment you submit a Sales Invoice. PEPPOL BIS 3.0 compliant, validated against the official spec.

Receive invoices automatically

Drop an incoming PEPPOL XML and a Purchase Invoice is created. Supplier, items, and purchase order matched to your existing master data.

Catch errors before they leave

XSD + Schematron validation runs every invoice through the PEPPOL ruleset. Bad invoices never reach the network — they block submission.

Human-readable XML preview

Open any PEPPOL XML and see a formatted preview from the official PEPPOL stylesheet. No more squinting at raw markup.

Auto-match suppliers and items

Incoming invoices match against your existing suppliers, items, and POs. Mismatches surface a dialog for one-click resolution.

Profile architecture

PEPPOL today. XRechnung, Italian SDI, French Factur-X are next. A new standard means a new profile, not a rewrite.

How it works

Submit. Validate. Send. Or: receive, match, post.

Submit invoice

Submit a Sales Invoice in ERPNext as you normally would.

XML generated

ERPNext produces a UBL 2.1 XML automatically. PEPPOL BIS 3.0 compliant.

Validated

XSD + Schematron checks run. Bad invoices block submission with a clear error.

Sent or received

On the way out: delivered via PEPPOL. On the way in: matched and turned into a Purchase Invoice.

Built for

Who actually needs this.

Suppliers to the Dutch public sector

PEPPOL is already mandatory for many B2G transactions. Compliance becomes a single setting in ERPNext, not a separate workflow.

B2B sellers in regulated industries

Customers in healthcare, logistics, and government supply chains expect PEPPOL. Send straight from ERPNext — no paper, no PDF email.

Buyers receiving PEPPOL invoices

Suppliers sending you PEPPOL XML? Receive, validate, match, and post — all without leaving ERPNext.

Built on the standard

No homemade XML.

We use the official PEPPOL BIS Billing 3.0 spec, UBL 2.1 schemas, and Schematron rulesets straight from peppol.eu — no interpretation, no shortcuts. A profile architecture means the same code path will handle XRechnung, Italian SDI, and Factur-X. The code is open source. You can audit the validation rules yourself.

Send invoices electronically.Receive them too.