Do I need a Peppol access point?

You need a Peppol access point when your business must actually send or receive invoices through the Peppol network. You do not need one just because you received an XML invoice file and want to open it, inspect it, or understand what is inside it.

You probably do need one if

Your business must exchange invoices through Peppol as part of a live operational workflow, onboarding requirement, ERP integration, or country-specific e-invoicing mandate. In that situation, an access point becomes part of your transport infrastructure.

You may not need one yet if

Your immediate problem is that you have an invoice file in front of you and do not know what it is, cannot read the XML clearly, or need to check whether participant or supplier identifiers look usable before the workflow continues.

Common confusion

Many users search for a Peppol access point when the real issue is earlier in the chain. They may need a viewer, format detector, or participant check first. Transport matters, but not before you understand what file you have and whether the important business data inside it makes sense.

What problem are you actually solving?

If the problem is sending or receiving through the network, you are in access-point territory. If the problem is reading invoice XML, checking a participant ID, reviewing totals, or seeing whether a PDF hides machine-readable XML, you are still in the inspection and validation layer.

Good first question to ask internally

Ask whether your team is blocked by network delivery or by file clarity. If the team cannot even identify the invoice format, participant data, or core fields, an access point is probably not the first thing to fix.

Where Tooltensor fits

Tooltensor helps with invoice inspection, first-pass validation, participant checks, and file understanding. It is useful before onboarding a transport provider and also after onboarding, when teams still need to inspect real invoice files that move through the network.