Time to sandbox
Hours
Validate against your own systems and the Peppol test network.
Time to launch
Tage bis Wochen
Launch according to your integration and release process.
Rate limit
Agreed per partner
Capacity provisioned per partner.
Service Provider role
Qvalia
Qvalia operates the Access Point, SMP and network governance.
Technical support
Third line
Qvalia provides third-line technical support.
Built for
ERP providers · Invoicing and accounting software · CRM systems · VAN operators
B2B marketplaces · Accounting agencies · IT consultancies
Your product, our infrastructure
Partners build and own the user experience. Qvalia operates the Access Point, SMP and messaging infrastructure behind it, reached through one API.
You control the customer experience, contract and pricing. Qvalia operates the Peppol service behind your interface.

What we run, what you own
What Qvalia runs
- Access Point and SMP under Qvalia’s Peppol Service Provider role
- Message validation, format conversion and delivery across the network
- Participant registration and lookup
- Monitoring, updates and network compliance
What you own
- The interface your customers use, inside your own product
- The customer relationship, contract and pricing
- Your own onboarding and support flow
Partner API workflow
The Partner API covers system authentication, customer setup, document submission and inbound message handling. Qvalia operates Peppol transport, discovery, validation and certificate management.
1. Authenticate
Partner systems authenticate with an API key, or exchange it for a short-lived JWT. One credential covers the Transaction, Partner, Account and Enrichment APIs.
curl --location --globoff -X POST \
'https://api.qvalia.com/token' \
--data '{
"client_id": "{partnerRegNo}",
"client_secret": "{apiKey}"
}'
# Valid for one hour. Send it on every call:
# Authorization: Bearer <token>
2. Create the customer
Create the account and register its Peppol participant identifier. Qvalia manages participant registration and directory updates
curl --location --globoff -X POST \
'https://api.qvalia.com/partner/{partnerRegNo}/account' \
--header 'Authorization: Bearer <token>' \
--data '{
"accountRegNo": "5567321707",
"name": "Nordkap Logistik AB",
"address": "Wallingatan 33",
"postalCode": "111 24",
"country": "SE"
}'
curl --location --globoff -X PUT \
'https://api.qvalia.com/partner/{partnerRegNo}/account/5567321707/peppol/0007:5567321707' \
--header 'Authorization: Bearer <token>'
3. Send and receive messages
Documents are validated against the applicable Peppol specifications before transmission. Structured validation responses are returned to your system, and inbound messages are available through the same account.
curl --location --globoff -X POST \
'https://api.qvalia.com/partner/{partnerRegNo}/transaction/5567321707/invoices/outgoing' \
--header 'Authorization: Bearer <token>' \
--data '{ "Invoice": { } }'
# 200
# { "status": "success", "data": { "message": "invoice 12335675 sent" } }
4. Subscribe to events
Subscribe to document events with webhooks. Qvalia posts to your endpoint when a document arrives, when delivery status changes, and when delivery fails.
curl --location --globoff -X PUT \
'https://api.qvalia.com/partner/{partnerRegNo}/webhook/configure' \
--header 'Authorization: Bearer <token>' \
--data '{
"url": "https://your-platform.example/qvalia/events",
"events": ["new_document", "document_delivery", "document_error"]
}'
# Delivered as HTTPS POST with a JSON body.
# Respond 2xx within 10 seconds.
| Specification | Detail |
| Transport | Peppol AS4 transport, ebMS messaging and PKI certificate handling are operated by Qvalia. |
| Response time | API response time depends on payload size and connectivity. Peppol delivery is asynchronous and depends on the receiving Access Point. |
| Breaking changes | Breaking changes ship as a new API version with at least one month’s notice, normally longer |
Multi-tenant account models
Choose a consolidated setup or a separate account per customer, based on registration, data separation and user-management requirements.
| Consolidated | Account per tenant | |
| Peppol Registrierung | Shared setup managed by you | Own account and Peppol ID per end customer |
| Data and users | Managed together in your platform | Separate data, users and settings per tenant |
| Onboarding | Fastest way to add a customer | Participant registration and directory updates handled by Qvalia |
| Fit | Many small customers under one service you operate | Customers who need their own Peppol identity and audit trail |
You control the onboarding experience in both models. The account model determines participant registration and data separation.
Supported business documents
The same integration supports the available invoicing, ordering and related business document flows.
| Document | Peppol name | Detail |
| Invoice | Invoice | A demand for payment, with line items, tax and payment terms |
| Gutschrift | CreditNote | A correction or reversal of an invoice already sent |
| Self-billing invoice | SelfBillingInvoice | An invoice the buyer issues on the supplier’s behalf |
| Self-billing credit note | SelfBillingCreditNote | The matching credit note for a self-billed invoice |
| Order | Order | A purchase order from buyer to supplier |
| Order response | OrderResponse | Acceptance, rejection or amendment of an order |
| Order agreement | OrderAgreement | A framework agreement that later orders refer to |
| Order change | OrderChange | An amendment to an order already sent |
| Order cancellation | OrderCancellation | Cancellation of an order already sent |
| Versandhinweise | DespatchAdvice | What has actually shipped, against which order |
| Catalogue | Catalogue | Products, descriptions and agreed prices |
| Catalogue response | CatalogueResponse | Acceptance or rejection of a catalogue |
| Message level response | MessageLevelResponse | Technical acknowledgement or rejection of a message |
| Message level status | MessageLevelStatus | Processing status of a message on the network |
Punchout, PDF and EDI services can use the same account structure. Qvalia handles validation, routing, delivery and network-level error handling.
Structured transaction data
Documents are available as structured transaction data for reporting, analytics and accounting automation.
Invoice line, as received
ART 4471-B
Printing paper A4 80G 5X500
12 pcs 489,00 SEK
Same line, classified
| UNSPSC | 14111507 Copy paper |
| Kategorie | Office supplies |
| Unit | 12 × 2 500 sheets |
| Stückpreis | 40.75 SEK |
| Supplier | Matched to master data |
Line items can be structured and classified in real time, with master data connected to the transaction flow. This supports reporting, spend analytics and accounting automation in your product. OCR, automated accounting and classification enrichment are available as add-ons.
Peppol compliance responsibilities
Qvalia holds the Peppol Service Provider role for Embedded Peppol. The partner remains responsible for its customer relationship and commercial offering. Only active legal entities may be assigned a Peppol ID.
| Responsibility | Qvalia | You |
| Certified Peppol Service Provider role | Qvalia | |
| Access Point and SMP operation | Qvalia | |
| Peppol certification, audits and network governance | Qvalia | |
| ISO/IEC 27001:2022 and ISO 22301:2019 management systems | Qvalia | |
| Customer due diligence | Partner | |
| Confirming customers are not deregistered, insolvent or in breach of AML requirements | Partner | |
| End-customer contract, pricing and commercial relationship | Partner |
This applies to Embedded Peppol and to the white-label platform. Partners who need to hold the Peppol Service Provider role in their own name should look at Hosted Access Point instead.
Häufig gestellte Fragen
What does Embedded Peppol mean in practice?
You offer Peppol connectivity and compliant exchange of business messages to your own customers, embedded in your product through an API. Qvalia operates the Peppol infrastructure in the background. You own the customer relationship and the offering.
Do we need to manage Peppol compliance ourselves?
No. With Embedded Peppol, Qvalia holds the Peppol Service Provider role and operates the Access Point and SMP. Qvalia manages Peppol network governance and technical compliance for the service. You remain responsible for end-customer contracts, onboarding information, pricing and support. Partners that need to hold the Service Provider role in their own name should consider Hosted Access Point.
Wie unterstützen Sie Peppol-Setups mit mehreren Mandanten?
Qvalia supports both consolidated and multi-tenant models. You can manage multiple end customers in a shared setup, or provide separate accounts and Peppol IDs for each customer.
Which Peppol message types can we offer our users and end-customers?
Invoices, credit notes, orders, order responses, despatch advice, catalogues and related business messages, plus punchout. Qvalia handles validation, routing, delivery and error handling across the network. PDF and EDI run through the same account structure.
Wie werden Endkunden eingebunden und verwaltet?
End customers are assigned their own Peppol IDs and routing rules during onboarding. Qvalia manages participant registration, directory updates and network configuration behind the scenes, while you control the onboarding experience.
Do we have to poll for inbound documents?
No. Subscribe to webhook events and Qvalia posts to your endpoint when a Peppol message or document arrives, when its delivery status changes, and when delivery fails. Polling endpoints are available as an alternative.
Can we offer more than message exchange?
Yes. Every transaction is available as structured data with line-item classification, which is what lets you build reporting, spend analytics and automated accounting into your own product rather than only moving documents. OCR, automated accounting and classification enrichment are available as add-ons.
Are there rate limits?
Yes. Partner accounts are provisioned well above standard account limits, and the limit is adjusted for your expected volume. If you plan a large onboarding or a heavy month-end, contact us.
How quickly can we get started?
Sandbox access is typically available within hours. Production launch depends on integration, testing and your release process.
How is the integration built?
The platform is integrated through REST APIs. System authentication uses OAuth 2.0 client credentials. User SSO is configured separately through supported identity options. If you do not need the interface inside your product, the white-label platform provides Qvalia’s application under your brand.
Alternative solutions
Choose White-label platform for a complete application, or Hosted Access Point when your organisation needs to hold the Service Provider role.
You want the product, not the build
The white-label platform is Qvalia’s complete application under your brand, domain and pricing. It provides a full interface without a development project.
You need to be the provider, in your own name
Hosted Access Point makes you a certified Peppol Service Provider with your own Access Point identity and PKI certificate, on infrastructure Qvalia operates.
Lassen Sie uns reden
Tell us which product you are extending, the markets you support and your expected transaction volumes. We will define the account model, integration scope and launch plan.
Kontakt aufnehmen
Integrieren Sie mit Qvalia e-Invoicing, e-Ordering und Datenanreicherung in Ihre Plattform.
Mit unserer Partner-API, fortschrittlichen Verwaltungstools und White-Label-Lösungen können Sie Ihren Endbenutzern ein nahtloses Transaktionsmanagement anbieten.
Arbeiten Sie mit uns zusammen, um die Möglichkeiten Ihrer Plattform zu erweitern und die digitale Transformation voranzutreiben. Kontaktieren Sie uns, um mehr zu erfahren.
Austausch von Geschäftsdokumenten über Peppol, EDI und mehr
KI-gestützte Datenanreicherung auf Einzelpostenebene ermöglichen
Erweitern Sie Ihr Produktangebot und Ihre Benutzerfreundlichkeit