Peppol Participant Onboarding
Prepare SMP & SML registration payloads so your Access Point can put your participants on the Peppol network
What this module does
Before you can receive Peppol documents, your participant
identifier and its capabilities must be published on a
Service Metadata Publisher (SMP) and a
discovery record must exist in the
Service Metadata Locator (SML). This module
turns your participant data into the exact
OASIS BDXR SMP 1.0 REST registration payloads
your Access Point or SMP operator executes — the
ServiceGroup that creates the participant, one
ServiceMetadata per document type capability, and
the derived SML DNS record.
It is a payload preparer: it generates the registration format and a copy-paste runbook. Transmission to your SMP is performed by your own Access Point with your own credentials and certificate (bring-your-own-key). This module is not an SMP, an SML or a certified Access Point.
Participant identifiers, validated
Parse and validate Peppol participant identifiers in both the
full iso6523-actorid-upis::0192:991825827 form and
the bare value form. The 4-digit ISO 6523 ICD is checked against
the published Peppol participant code list (Norwegian Org no.,
Belgian CBE, German VAT, Italian Partita IVA and dozens more),
with clear warnings for unknown schemes.
SMP registration payloads
Build the canonical ServiceGroup and
ServiceMetadata XML bodies exactly as the OASIS
BDXR SMP 1.0 REST binding requires, including the correct
percent-encoded PUT URLs, the AS4 transport profile
(peppol-transport-as4-v2_0), your endpoint URL and
your embedded AP certificate.
SML DNS record derivation
Compute the discovery DNS name
B-<md5>.<scheme>.<sml-zone> for
the production (edelivery.tech.ec.europa.eu) or
test (acc.edelivery.tech.ec.europa.eu) network, and
the CNAME target pointing at your SMP host.
Copy-paste runbook & export
Every onboarding produces an ordered runbook —
PUT ServiceGroup, then one
PUT ServiceMetadata per capability, then the SML
DNS step — that you can download as a text file and hand to
your Access Point.
Supported document type capabilities
| Capability | Peppol document type |
|---|---|
| Invoice | Peppol BIS Billing 3.0 Invoice |
| Credit Note | Peppol BIS Billing 3.0 Credit Note |
| Order | Peppol BIS Ordering 3.0 Order |
| Order Response | Peppol BIS Ordering 3.0 Order Response |
| Despatch Advice | Peppol BIS Despatch Advice 3.0 |
| Catalogue | Peppol BIS Catalogue 3.0 |
| Invoice Response | Peppol BIS Invoice Response 3.0 |
| Message Level Response | Peppol MLR |
How it works
- Capture the participant identifier on the contact, or create an onboarding request directly.
- Add the document type capabilities the participant will receive.
- Set the SMP base URL, AS4 endpoint and AP certificate (defaults come from company settings — BYOK).
- Validate, then generate the SMP registration payloads and the SML runbook.
- Hand the runbook to your Access Point, who executes the PUTs against the SMP with their own credentials.
Standards & boundary
Implements the OpenPEPPOL Policy for use of Identifiers, the Peppol Code Lists (participant ICD codes, document type and process identifiers), the OASIS BDXR Service Metadata Publishing (SMP) 1.0 REST binding and the SML DNS derivation. All identifiers and zones used are the published Peppol values.
Boundary: this module prepares the registration format only. Your Access Point performs the SMP PUTs and the SML registration using your own credentials and certificate. No data leaves your database during preparation.
We deliver the software only (BYOK — the SMP/SML registration runs under your own access point and credentials). We are not a Peppol access point, SMP, SML or integrator. Support is provided and your purchase is refundable.
Screenshots
Settings
Onboarding Requests
Update date: 2026-07-02