What Is a Peppol Access Point? A Plain-Language Guide

If you're trying to comply with e-invoicing mandates in Belgium, Germany, Norway, Singapore, or any of the other 30+ countries running on the Peppol network, you'll encounter the term "Access Point" early in the process. This guide explains what it is, what it does, and what to look for when choosing one.

The short answer

A Peppol Access Point (AP) is a certified service that connects your business to the Peppol network. When you send an e-invoice through Peppol, it doesn't go directly to your buyer — it goes from your Access Point, through the Peppol routing infrastructure, to your buyer's Access Point, and then to your buyer.

Think of it like email but for legally compliant structured invoices: you need a mail server (Access Point) to send and receive, and the network routes messages between servers.

How the Peppol network works

Peppol uses a "four-corner model":

Corner 1          Corner 2          Corner 3          Corner 4
[Supplier] ──→ [Your Access Point] ──→ [Buyer's Access Point] ──→ [Buyer]

Corner 1 — Your business: generates the invoice in your ERP or billing system.

Corner 2 — Your Access Point: validates the invoice format, packages it as an AS4 message, and delivers it to the buyer's Access Point.

Corner 3 — The buyer's Access Point: receives the AS4 message, extracts the invoice, and delivers it to the buyer.

Corner 4 — Your buyer: receives a structured XML invoice in their system.

The routing between corners 2 and 3 happens through the Peppol SML/SMP infrastructure — a distributed directory that maps participant IDs (such as a VAT number or company registration number) to their registered Access Point.

What an Access Point actually does

When you submit an invoice via an Access Point, it handles:

Format validation — checks that your invoice XML conforms to the relevant Peppol profile (BIS Billing 3.0 for EU markets, PINT for APAC markets, etc.) before attempting delivery. Errors are caught before they hit the buyer.

Participant lookup — queries the Peppol SMP to find the buyer's registered Access Point endpoint. This lookup happens automatically per invoice.

AS4 message packaging — wraps the invoice XML in an AS4 MIME envelope with the required headers, signatures, and timestamps for Peppol transport.

Delivery — transmits the AS4 message to the buyer's Access Point over HTTPS using mutual TLS.

MDN receipt — collects the Message Disposition Notification from the buyer's Access Point, confirming delivery. This is your proof that the invoice was delivered to the correct endpoint.

Error reporting — if delivery fails (buyer not registered, network timeout, format rejection), the Access Point surfaces the error with enough detail to diagnose and retry.

Who needs an Access Point

You need an Access Point if you are:

• A business required to issue Peppol e-invoices — Belgium's B2B mandate (live since January 2026), Norway's B2G mandate, Singapore's InvoiceNow B2G requirement, and others all require Peppol delivery
• A supplier to government bodies in any Peppol-connected country — most EU B2G mandates run on Peppol
• A software vendor building e-invoicing compliance into your product for customers in Peppol markets

You do not need to run your own Access Point. You use one operated by an accredited provider.

How Access Points are accredited

OpenPeppol — the non-profit organisation that governs the Peppol network — operates an accreditation programme for Access Point providers. To become accredited, a provider must:

• Pass OpenPeppol's conformance test suite (covering AS4 transport, SMP registration, and BIS 3.0 document handling)
• Sign the OpenPeppol Service Provider Agreement
• Maintain compliance with network policy updates

You can verify any Access Point's registration via a live SMP lookup on the Peppol production network. Clearvo's AP identifier is PIE001162, registered on the production network and visible via standard SMP lookup.

Choosing an Access Point: what to look for

1. Direct delivery vs. reseller Some providers are registered Access Points themselves. Others are resellers that route through a third-party AP with a separate SLA. Direct APs have full visibility into delivery status and faster error resolution.

2. Country coverage Peppol BIS Billing 3.0 is the EU standard, but APAC markets (Australia, New Zealand, Japan, Singapore) use PINT profiles with country-specific CIUS extensions. Confirm the AP handles the specific profiles you need, not just "Peppol" in general.

3. API vs. portal If you're integrating programmatically — connecting your ERP, billing platform, or SaaS product — you need an AP with a clean REST API, not just a web portal for manual uploads.

4. Schema version tracking Peppol BIS Billing 3.0 has had multiple minor updates, and country-specific CIUS documents are updated when national legislation changes. Ask how quickly the provider updates their validation when OpenPeppol or a national authority publishes a new schema version.

5. Status and MDN handling Delivery status (MDN receipt, delivery confirmation) should be surfaced via webhook or polling API, not just visible in a portal dashboard. For automated invoice workflows, you need machine-readable status.

Peppol Access Point vs. clearance model

It's worth understanding the distinction between Peppol (a decentralised network) and clearance models like Italy's SDI or Poland's KSeF:

France is a hybrid: it uses PDPs (similar role to an Access Point) but with a centralised government directory and clearance-style routing.

How Clearvo works as a Peppol Access Point

Clearvo is a registered Peppol Access Point (AP ID: PIE001162) and handles the full delivery lifecycle — SMP lookup, AS4 packaging, delivery, MDN receipt, and error normalisation — through a single REST API.

You submit a structured JSON invoice. Clearvo selects the correct Peppol profile based on the country field, validates against the relevant schematron, and routes the invoice to the buyer's registered Access Point. Delivery receipts and rejection notices are returned via webhook.

The same API call works across all 31 supported countries — whether the destination uses Peppol BIS 3.0, a PINT profile, or a country-specific CIUS extension.

Supported Peppol markets include Belgium, Netherlands, Germany, Norway, Sweden, Denmark, Finland, Ireland, Australia, New Zealand, Singapore, Japan, and more.