How to Comply with Peppol in the EU: Connect, Validate, and Send Your First Invoice (2026)

To comply with Peppol in the EU, register through a certified Peppol Access Point, obtain a Peppol Participant Identifier in the SMP/SML directory, emit invoices in Peppol BIS Billing 3.0 (UBL 2.1 customisation of EN 16931), pass the official Schematron validation, and exchange documents AP-to-AP over AS4 with signed receipts. Belgium has mandated this for B2B since 1 January 2026; Germany requires B2B receipt since 1 January 2025; France switches on receipt for all businesses on 1 September 2026.

Why Peppol matters now

Peppol is the de facto EU rail for both e-invoicing for the EU and a growing list of national B2B mandates.

Peppol is the de facto EU rail for both e-invoicing for the EU and a growing list of national B2B mandates. Directive 2014/55/EU obliges every EU contracting authority to receive EN 16931 invoices — almost all do so via Peppol. The VAT in the Digital Age (ViDA) package, adopted by the Council on 11 March 2025, entered into force on 14 April 2025 and lets member states impose mandatory e-invoicing without prior derogation. That has unlocked the wave of national B2B mandates landing through 2026–2028.

Prerequisites before you onboard

Prerequisites before you onboard includes: A registered legal entity with a national identifier the Peppol Policy for Identifiers recognises (VAT number, national company number, GLN/0088, LEI/0199). Buyer master data: each buyer's Peppol Participant Identifier (scheme::value) or enough information for an SMP lookup.

• A registered legal entity with a national identifier the Peppol Policy for Identifiers recognises (VAT number, national company number, GLN/0088, LEI/0199).
• Buyer master data: each buyer's Peppol Participant Identifier (scheme::value) or enough information for an SMP lookup.
• An invoicing platform that emits UBL 2.1 in the Peppol BIS Billing 3.0 customisation and routes through a certified Access Point.
• If you also archive on-platform, a tamper-resistant store that meets your jurisdiction's retention period (10 years in Belgium, France and Germany; 7 in the Netherlands; see local rules).

Step 1 — Choose a certified Peppol Access Point

You never connect to Peppol directly. You connect through a certified Peppol Access Point ("AP") that speaks AS4 to every other AP on the network.

You never connect to Peppol directly. You connect through a certified Peppol Access Point ("AP") that speaks AS4 to every other AP on the network. Invoicemonk operates as an AP for customers in scope, so the AP step is bundled when you turn Peppol on inside the product.

What should I check on a candidate AP?

Confirm active OpenPeppol certification, supported document types (at minimum BIS Billing 3. 0 Invoice and Credit Note), supported jurisdictions, AS4 conformance to Peppol AS4 Profile v2.

Confirm active OpenPeppol certification, supported document types (at minimum BIS Billing 3.0 Invoice and Credit Note), supported jurisdictions, AS4 conformance to Peppol AS4 Profile v2.0.3, and whether validation, MLR handling and archiving are bundled.

Should I run my own Access Point?

Only at very high volume or if you resell Peppol connectivity. Running an AP requires OpenPeppol certification, ongoing infrastructure, and continuous tracking of network policy changes through the OpenPeppol eDEC.

Only at very high volume or if you resell Peppol connectivity. Running an AP requires OpenPeppol certification, ongoing infrastructure, and continuous tracking of network policy changes through the OpenPeppol eDEC.

Step 2 — Register your Peppol Participant Identifier

Your AP registers you in the Peppol SMP (Service Metadata Publisher) and the SML (Service Metadata Locator) so other senders can resolve you. The Participant ID follows scheme::value.

Your AP registers you in the Peppol SMP (Service Metadata Publisher) and the SML (Service Metadata Locator) so other senders can resolve you. The Participant ID follows scheme::value. Common schemes: 0208 Belgian Crossroads Bank for Enterprises (CBE), 0184 Danish CVR, 0192 Norwegian Organisation Number, 0204 German LeitwegID for public buyers, 9925 Belgian VAT, 9930 German VAT.

SML vs SMP — what is the difference?

The SML is the DNS-backed root directory pointing to the SMP that holds a participant's metadata. The SMP holds the endpoint URL, certificate, and accepted document types.

The SML is the DNS-backed root directory pointing to the SMP that holds a participant's metadata. The SMP holds the endpoint URL, certificate, and accepted document types. The combination means any sender's AP can route to any receiver without bilateral setup.

Step 3 — Declare the document types you accept

An AP publishes the document types your endpoint receives — typically urn:cen. eu:en16931:2017 (the BIS Billing 3.

An AP publishes the document types your endpoint receives — typically urn:cen.eu:en16931:2017 (the BIS Billing 3.0 Invoice) and the corresponding Credit Note. Senders' APs check this list before they transmit; an undeclared type comes back as an SMP lookup error rather than a delivery.

Step 4 — Map your invoice to BIS Billing 3.0

Peppol BIS Billing 3. 0 is a Core Invoice Usage Specification (CIUS) of EN 16931, expressed in UBL 2.

Peppol BIS Billing 3.0 is a Core Invoice Usage Specification (CIUS) of EN 16931, expressed in UBL 2.1. The mapping that catches most teams:

• Party identification: seller and buyer with Peppol-compatible scheme IDs.
• Line items: classified with UNSPSC or CPV (UNCL 7143).
• Unit codes: UN/ECE Recommendation 20 (EA, HUR, KGM…).
• Tax category: UNCL 5305 (S standard, Z zero, E exempt, AE reverse charge, K intra-EU).
• Payment means: UNCL 4461 (30 credit transfer, 58 SEPA credit transfer, 59 SEPA direct debit).
• Currency: ISO 4217, with optional tax accounting currency for non-EUR taxable supplies in EUR-denominated jurisdictions.

Step 5 — Validate against the Schematron rule set

Run every outgoing document through the Peppol BIS Billing 3.

Run every outgoing document through the Peppol BIS Billing 3.0 Schematron at docs.peppol.eu/poacc/billing/3.0/rules/. Documents that fail validation are rejected at the receiving AP. Blocking sends until validation passes is the cheapest control you can put in place. The validator returns rule codes prefixed BR- (business rules from EN 16931), BR-CO- (calculation rules), BR-S- (VAT category rules), and PEPPOL- (Peppol-specific rules).

Step 6 — Send your first live invoice

Step 6 — Send your first live invoice includes: Create the invoice as normal in your invoicing system. The platform renders UBL 2.

1. Create the invoice as normal in your invoicing system.
2. The platform renders UBL 2.1 in the BIS Billing 3.0 customisation.
3. Your AP looks up the buyer's endpoint via SMP/SML.
4. The document is transmitted to the buyer's AP over AS4, with non-repudiation receipts signed by both APs.
5. The buyer's AP delivers it to the buyer's ERP or accounts payable system.

Step 7 — Handle MLR responses and rejections

Buyers may return a Message Level Response (MLR) acknowledging or rejecting the document. Treat MLR rejects the same way you would treat a bounced email — surface them in the invoice timeline, store the rejection reason code, and re-issue once corrected.

Buyers may return a Message Level Response (MLR) acknowledging or rejecting the document. Treat MLR rejects the same way you would treat a bounced email — surface them in the invoice timeline, store the rejection reason code, and re-issue once corrected. Typical reasons: unknown buyer reference, missing purchase order number, tax category mismatch, or party identifier mismatch.

Country-specific obligations on top of Peppol

Country-specific obligations on top of Peppol — Belgium: B2B mandatory since 01 Jan 2026; grace period ended 27 Mar 2026 — Peppol BIS Billing 3. 0.

Pre-go-live compliance checklist

Pre-go-live compliance checklist includes: ☐ Participant ID registered in SMP + visible in SML. ☐ Document type declarations include BIS Billing 3.

• ☐ Participant ID registered in SMP + visible in SML.
• ☐ Document type declarations include BIS Billing 3.0 Invoice + Credit Note.
• ☐ Schematron validation runs on every outgoing document.
• ☐ AS4 receipts archived alongside the signed invoice.
• ☐ MLR processing wired to the invoice timeline.
• ☐ Country-specific overlays (XRechnung Leitweg ID, French PPF endpoint, Polish KSeF gateway) configured for your buyers.
• ☐ Retention store proven against your longest jurisdiction (10 years for Belgium, France, Germany).

Key takeaways

Key takeaways includes: Peppol compliance = AP + Participant ID + BIS Billing 3. 0 + Schematron + AS4 + MLR handling.

• Peppol compliance = AP + Participant ID + BIS Billing 3.0 + Schematron + AS4 + MLR handling.
• Belgium, Germany and France are the immediate forcing functions for B2B in 2025–2027.
• ViDA does not mandate Peppol but its DRR (digital reporting requirements) effectively standardise on EN 16931 syntaxes.
• Run validation upstream of the AP — every Schematron error caught locally saves a network round-trip.

Related reading

Start at the e-invoicing pillar, then the Peppol EU mandate page. For background, read Peppol EU explained: scope, country mandates, and what changes in 2026.

Start at the e-invoicing pillar, then the Peppol EU mandate page. For background, read Peppol EU explained: scope, country mandates, and what changes in 2026. To compare to clearance regimes, read Peppol vs national portals. For deep dives on the building blocks: what is a Peppol Access Point, UBL 2.1 explained, and XAdES digital signatures.

Sources

• OpenPeppol — Peppol BIS Billing 3.0 (November 2025 Release)
• OpenPeppol — Peppol AS4 Profile v2.0.3
• Directive 2014/55/EU on electronic invoicing in public procurement
• European Commission — VAT in the Digital Age (ViDA)
• European Commission — eInvoicing in Belgium country factsheet
• Bundesfinanzministerium — E-Rechnung FAQ (Germany)
• Service-Public — France e-invoicing reform timetable