Register as a Peppol access point participant for e-invoicing
domain: peppol.eu · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Choose a certified Peppol Access Point provider from the official OpenPeppol member list and complete their onboarding to obtain a Peppol participant identifier (typically formatted as scheme:identifier, e.g., 0088:GLN or country-specific scheme)
Register your participant ID in a Peppol Service Metadata Publisher (SMP) by providing the document types you will send and receive (such as BIS Billing 3.0 invoice and credit note)
Configure your ERP or invoicing system to generate UBL 2.1 or CII XML invoices conforming to the EN 16931 European standard, including mandatory fields such as buyer reference and VAT breakdown
Test end-to-end invoice delivery using the Peppol test network (pilot environment) by sending a test invoice to a known test participant endpoint
In production, send invoices by submitting the UBL XML to your Access Point's API or SFTP endpoint; the Access Point routes the document to the recipient's Access Point via the four-corner model
Known gotchas
Each country may overlay additional mandatory fields on top of the EN 16931 base standard (e.g., Italy requires specific tax regime codes, Australia/NZ PINT requires additional fields); using the base standard alone may cause rejection
Peppol participant IDs are not email addresses and must be looked up in the SMP/SML before sending; sending to a non-registered ID will result in a routing failure with no delivery confirmation
Peppol itself has no legal archiving mechanism — you are responsible for storing signed invoice XML for the retention period required by each jurisdiction (often 7-10 years)
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?