Peppol delivery / certified-provider boundary
Connect validated invoices to a certified Peppol access point
Keep invoice validation and mapping under your control while a certified provider operates Peppol PKI, discovery and AS4 network transport.
Direct answer
Direct answer
A Peppol access point integration must provide the sender and receiver participant identifiers, document type identifier, process identifier and exact validated XML to a certified network provider. Shipment Sentry supplies an authenticated, idempotent access-point adapter and requires a provider receipt before recording delivery. It does not claim to be a Peppol-certified access point: Peppol PKI, SMP/SML discovery and AS4 conformance remain the configured provider’s responsibility.
Why a parser is not enough
Peppol is more than an invoice XML format. BIS business rules, participant addressing, dynamic capability discovery, certificate trust and AS4 delivery each answer a different question. A defensible system names the boundary instead of treating a valid UBL file as proof of network eligibility.
What the control should check
- 01Validate UBL or CII business content before network submission.
- 02Require sender and receiver participant identifiers.
- 03Bind the current document type and process identifier to the partner route.
- 04Use a certified access point with authenticated credentials.
- 05Retry only transient HTTP outcomes and preserve a stable idempotency key.
- 06Store the access-point receipt separately from downstream business acceptance.
Working example
sender: 0088:5790000435969
receiver: 0208:123456789
document: urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##...
process: urn:fdc:peppol.eu:2017:poacc:billing:01:1.0
transport: peppol-transport-as4-v2_0Identifier values and capabilities are examples only; the certified access point and current participant metadata remain controlling.
Failure modes worth catching
- A syntactically valid invoice targets an unregistered participant.
- A document type is valid but unsupported by the receiver capability record.
- An uncertified in-house endpoint is presented as a Peppol access point.
- A provider HTTP response is stored without its receipt identifier.
Put it into the dispatch workflow
- 1Choose the Peppol billing profile and validate the invoice.
- 2Map tenant and partner identities to participant identifiers.
- 3Configure a certified access-point endpoint and token.
- 4Submit exact bytes with document and process identity.
- 5Require and record the provider receipt.
- 6Correlate later status or business responses without rewriting delivery history.
Questions
Implementation answers
Is Shipment Sentry itself a certified Peppol access point?
No. It integrates with the certified access point you configure and keeps that provider boundary explicit.
Does it perform SMP and SML discovery?
The certified provider owns dynamic discovery and Peppol PKI. Shipment Sentry sends the identifiers it needs to perform that work.
Can I validate the invoice before delivery?
Yes. The Peppol validator checks the supported public-rule surface before exact bytes enter the access-point adapter.
Sources and limits
Reviewed 2026-07-20. Public references cannot establish every partner-specific rule. Current implementation guides and agreements remain controlling.
Keep investigating