What is a Peppol access point?

A Peppol access point is the network service that sends and receives structured invoice documents on the Peppol network. If a business wants to exchange invoices through Peppol, the access point is the transport layer that connects the sender or receiver to the rest of the network.

Tooltensor is not a Peppol access point. Tooltensor helps one step before or around that transport layer: identify invoice files, open XML in plain language, review invoice fields, and precheck business identifiers before the document moves into another system.

Tooltensor editorial note: This page was checked for workflow scope and terminology. Last updated: July 7, 2026.

What a Peppol access point actually does

A Peppol access point handles document delivery on the network. In practical terms, it helps route invoice data from one party to another using the Peppol framework. That usually includes technical onboarding, document transport, and network-level message exchange. It does not exist to explain a raw XML file to a human reader.

Why people search for access points

Many users search for a Peppol access point when their real problem is more basic. They may have received a UBL or Peppol XML file and simply want to know what it is, whether the participant ID looks usable, or whether the invoice can be reviewed before it goes into accounting software. That is why transport tools and inspection tools are often confused.

What an access point does not replace

An access point does not replace invoice review, participant checks, VAT checks, or payment checks. A business can still need to inspect the invoice content, read supplier and buyer fields, confirm totals, and validate key identifiers before the invoice is accepted into another workflow.

Peppol access point vs Peppol participant

A participant is the sender or receiver identifier used on the network. An access point is the service that helps that participant exchange documents on the network. These are different things. If the question is whether a participant ID looks correct or resolves on a live lookup, that is a participant-check problem, not an access-point problem.

When you need an access point

You need a Peppol access point when your business wants to actually send or receive structured invoices through the Peppol network. That is an operational transport decision. It usually matters when onboarding to e-invoicing, connecting ERP or billing software, or complying with country-specific e-invoicing rules.

When you do not need one yet

You may not need an access point yet if your immediate problem is understanding a file already in front of you. If someone emailed or exported a structured invoice file and the main question is what the XML contains, whether the format is UBL, or whether the identifiers look usable, inspection and validation tools are the right first step.

A practical example

If an accountant receives an attachment called invoice.xml and cannot tell whether it is a real Peppol invoice, the first bottleneck is not transport. The first bottleneck is identification and readable review. In that case, a detector and viewer solve the immediate problem faster than an access-point discussion.

Where Tooltensor fits in the workflow

Tooltensor fits before transport and alongside operational checks. Use the format detector when you do not know what file you received. Use the UBL viewer when you want to read supplier, buyer, totals, and line items in plain language. Use the participant checker when the open question is whether a Peppol participant ID resolves on a live production lookup.