Peppol e-invoicing API in just two calls

A weekend for a tracer-bullet send-and-receive integration; one to two weeks for a production-ready ERP integration with reconciliation and error handling.

The API hides the BIS schemas, schematron, and Access Point onboarding, so most of the work is on your side: mapping ERP fields to our flat JSON and wiring up the inbound webhook.

No. e-invoice.be is the compliance layer that snaps onto your existing stack. Your ERP, accounting suite, or billing system keeps producing invoices the way it always has. The Peppol formatting, validation, routing, and archiving happen below the surface.

We are infrastructure, not an invoicing app.

Pro

from €0.25 per invoice

Enterprise

from €0.18 per invoice (volume-negotiated)

Account, Peppol ID, sandbox

free

Both sending and receiving are billed per invoice. No setup fees, no monthly minimums.

Yes. Open an account, get a test API key in 30 seconds, and send invoices that get validated and serialized exactly like production but emailed back to you instead of routed over the Peppol network. The same code goes to production by flipping an env var. No sales call required.

Inbound is webhook-driven. Subscribe once, receive a signed POST whenever a Peppol invoice arrives for your participant ID, and fetch the full document via the API.

Polling endpoints are also available if you can't expose a webhook endpoint.

Every country reachable on the Peppol network. One integration covers:

• •Belgium (B2B mandate, 2026)
• •France (mandate phasing in from 2026)
• •Germany (B2B mandate, 2027)
• •Poland, Romania, Spain and the rest of the EU under ViDA
• •UK, Australia, New Zealand, Singapore and other Peppol-connected geographies

Country-specific BIS profiles and schematron rules are handled in the mapping; you don't manage them.

Yes. Manage tenants through one integration: provision accounts, mint and rotate per-tenant API keys, and register your customers on the Peppol network programmatically. Built for ERPs, SaaS platforms, and managed-service partners running invoicing for many companies.

Upload the PDF, the API extracts the data, validates against Peppol BIS 3.0, and ships a compliant UBL invoice. Useful when the ERP can't be persuaded to emit structured invoice data on day one.

Sandbox / lookups

no KYC

Send over Peppol

KYC required (24–48h)

KYC is a one-time wire-transfer verification. It keeps spammers off the network and protects deliverability for every legitimate sender.

A Peppol e-invoice is a structured electronic document exchanged over the Peppol network. It follows the EN16931 European standard and uses UBL 2.1 XML (Peppol BIS 3.0). Unlike a PDF, a Peppol e-invoice is machine-readable from the start, so it can be processed automatically by any receiving system without manual data entry.

Yes. Since January 2026, all Belgian B2B transactions must use structured e-invoicing via the Peppol network. This applies to every VAT-registered business in Belgium. The mandate covers domestic B2B invoices. B2G (business-to-government) e-invoicing was already mandatory before this.

Peppol (Pan-European Public Procurement OnLine) is a network and set of standards for exchanging electronic business documents. For e-invoicing, it provides a four-corner model: the sender's Access Point transmits the invoice to the receiver's Access Point over a secure AS4 channel, with routing handled by SML and SMP lookups. This means any two businesses on the Peppol network can exchange invoices without bilateral integration.

Over 30 countries are connected to the Peppol network. This includes Belgium, the Netherlands, Germany, France, Italy, Sweden, Norway, Denmark, Finland, Ireland, Poland, Singapore, Australia, New Zealand, Japan, and the UK. The EU ViDA regulation will extend mandatory e-invoicing across the bloc by 2030. e-invoice.be reaches all Peppol-connected countries through a single API integration.

Peppol uses a four-corner model:

1. Corner 1: the sender (your business)
2. Corner 2: the sender's Access Point (e-invoice.be)
3. Corner 3: the receiver's Access Point
4. Corner 4: the receiver

When you send an invoice via the API, e-invoice.be validates it against BIS 3.0, serialises it to UBL XML, looks up the receiver's Access Point via SMP, and transmits the document over a secure AS4 channel.

Create an account on e-invoice.be, complete the one-time KYC verification (24-48h), and we register your business as a Peppol participant. You get a Peppol ID and can start sending and receiving invoices immediately. No need to become a certified Access Point yourself. The API and SDKs handle all the protocol-level complexity.

The account, Peppol ID registration, and sandbox are free. Production usage is pay-per-invoice:

Pro

from €0.25 per invoice

Enterprise

from €0.18 per invoice

Both sending and receiving are billed. No setup fees, no monthly minimums.

Yes. Upload a PDF invoice to the API, and it extracts the structured data using OCR and field recognition, validates the result against Peppol BIS 3.0, and produces a compliant UBL 2.1 XML document. You can then send it over Peppol or download the UBL for archival. You can also validate and inspect invoices using the free Peppol Invoice Viewer tool.

The API is ERP-agnostic. It works with SAP, Oracle, Microsoft Dynamics 365, NetSuite, Odoo, Sage, Exact, Twinfield, Yuki, and any custom ERP that can make HTTP calls. You map your ERP fields to our flat JSON schema. No plug-ins or middleware required. SDKs are available for Python, TypeScript, Java, PHP, and Ruby.

Yes. The API supports invoices, credit notes, debit notes, self-billing invoices, and self-billing credit notes as first-class document types. Each uses the same POST endpoint with a document_type field. Self-billing lets you issue invoices on behalf of your supplier, which is common in logistics, staffing, and marketplace scenarios.

Peppol BIS 3.0 (Business Interoperability Specification) is the current invoicing specification on the Peppol network. It defines the UBL 2.1 XML structure, validation rules (schematron), and business rules that every Peppol invoice must follow. BIS 3.0 implements the European EN16931 standard. The e-invoice.be API handles BIS 3.0 compliance automatically: you post JSON, and the API serialises and validates to BIS 3.0.

The Peppol MCP (Model Context Protocol) server lets AI agents and LLM-powered tools interact with the e-invoice.be API programmatically. It exposes 12 read-only tools for looking up Peppol participants, validating invoices, and querying invoice data. Install it with npx e-invoice-api-mcp@latest or connect via the streamable HTTP endpoint at api.e-invoice.be/mcp.