Software on Peppol: which access point is your invoicing tool on?

Peppol network · billing & accounting software

Software on Peppol: who connects through what

Almost nobody joins Peppol directly. You buy invoicing or accounting software, and that software reaches the network through a certified access point — sometimes one it operates itself, more often one it rents from another company. This page names the operator behind each product, and shows the uptime we measure for it.

16 products · 12 access points · data as of 20 Sept 2026, 19:30 UTC

Language EN NL FR

Why it matters: when an invoice does not arrive, the problem is almost never the software you are looking at. It is the operator underneath it, and that is the thing you can neither see nor choose from inside the product. 16 products on this page resolve to just 12 operators; 5 of them hold a Peppol certificate of their own and the rest stand on somebody else's.

Each row names the operator a product's documents travel through. The participant figure is that operator's total, shared by every product on it — never a count of the product's customers. Uptime is our own 30-day measurement of the same operator's endpoints.

Belgium

Product Access point Participants on that AP (shared) 30-day uptime
Doccle rides another certificate Wolters Kluwer (Flowin) 634,885 100.00%
Billit own access point Billit 383,682 99.88%
Odoo own access point Odoo SA 85,938 99.73%
Falco rides another certificate Horus 118,351 49.97%
CodaBox rides another certificate Wolters Kluwer (Flowin) 634,885 100.00%
Billtobox rides another certificate Banqup SA 108,717 74.98%
Clearfacts rides another certificate Wolters Kluwer (Flowin) 634,885 100.00%
OkiOki rides another certificate Dokapi 126,868 99.99%
Octopus own access point Octopus NV 68,099 100.00%
Chuck rides another certificate Dokapi 126,868 99.99%
Mobeyond rides another certificate Renta Solutions NV 10 100.00%
Onfact own access point Infinwebs 35,379 100.00%
Scrada own access point Scrada BV 11,521 99.99%

Netherlands

Product Access point Participants on that AP (shared) 30-day uptime
Blue10 rides another certificate Tickstar 1,079,396 99.99%
Exact rides another certificate 4CEE 78,554 99.99%
Moneybird rides another certificate 4CEE 78,554 99.99%

Where these numbers come from

Both columns are ours. The participant figures are counted from the live registration data our crawlers resolve, and the uptime is measured continuously from probes in several regions — not taken from a status page an operator writes about itself. That makes the uptime column the closest thing there is to an answer for "why did my invoice not arrive".

We cannot split an operator's traffic by the software that fed it, so we never present a share of it as a product's own. On a narrow screen the shared participant column is dropped and the uptime kept, because uptime is the column you can act on; each product's own page carries both in full.

Why your software may not be listed

We only place a product on an access point when our own measurements or first-party documentation name it. In practice that means one of four things: the product is a certified provider in our provider directory, or it appears in our curated reseller fingerprint catalogue, or an access point we probe publishes an endpoint in the product's name, or the vendor's own site names its operator. A vendor saying "we support Peppol" is not one of those, because it does not say through whom.

These well-known products are still unplaced:

Lucy · Accountable · Yuki · WinAuditor · Dexxter · Zenfactuur · Cegid · Teamleader · EDIStech

Know the operator? Tell us — hello@peppolstatus.com.

We measure the network, we do not use these products: nothing here describes what one looks like from the inside, and for pricing, features or the steps to switch Peppol on you want the vendor's own documentation.

Look up a Peppol ID · Every Peppol access point, ranked by uptime · Is Peppol down?

Next: look up a single Peppol ID · every access point and SMP operator, ranked by uptime · what the e-invoicing mandate requires.