Discover a trading partner's Peppol access point and supported document capabilities before transmitting an e-invoice
domain: docs.peppol.eu · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Determine the recipient's Peppol Participant ID, typically a scheme-prefixed identifier such as a national company registration number
Use the Peppol dynamic discovery process, as defined in the OpenPeppol Service Metadata Locator (SML) specification, to have your Access Point resolve which SMP currently hosts that participant's metadata
Query the resolved SMP for the participant's published service metadata to confirm which document types and process profiles they can receive
Alternatively, use a public OpenPeppol lookup tool to manually confirm a participant is registered and review their capabilities before building the automated flow
Only transmit a document type and process profile that the recipient's SMP metadata actually lists as supported
Known gotchas
SML/SMP resolution is dynamic; a participant's SMP host can change over time, so cache lookups conservatively and re-resolve periodically rather than hardcoding an SMP address
Appearing in a public Peppol directory listing is not the same as supporting every document type; always check the specific document type and process profile in the SMP response before sending
This discovery step is distinct from registering your own business as a Peppol access point participant; it addresses finding and validating a counterparty, not your own onboarding
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?