Peppol Network
Invostaq handles the complexity of the Peppol network so you don't have to. This page explains how the pieces fit together and what you need to know as an integrator.
What is Peppol?
Peppol (Pan-European Public Procurement Online) is an international e-invoicing network used across the EU, UAE, Singapore, Australia, and other countries. It defines:
- Document format: UBL 2.1 XML with the Peppol BIS Billing 3.0 profile
- Routing: Participant IDs in ISO 6523 format (e.g.,
0196:971501234567) - Delivery: Documents are routed through certified Access Points
How Invostaq fits in
Your System ──► Invostaq API ──► Peppol Access Point ──► Recipient
(JSON) (UBL XML) (AS4/AS2)
When you call POST /v2/invoices/send:
- You send JSON — structured invoice data with line items, totals, and participant IDs
- Invostaq validates — checks totals, participant ID format, and UBL compliance rules
- Invostaq builds UBL XML — generates a Peppol BIS Billing 3.0 compliant UBL 2.1 document
- The Access Point delivers — routes the document to the recipient's Access Point via AS4
- You receive a webhook —
transaction.sent(delivered) ortransaction.failed(rejected)
You never need to write UBL XML, manage certificates, or interact with the Peppol infrastructure directly.
Participant IDs
Every entity on the Peppol network is identified by an ISO 6523 participant ID:
{scheme}:{identifier}
| Scheme | Country / Standard | Example |
|---|---|---|
0196 | UAE (TRN) | 0196:971501234567 |
0235 | UAE (TIN) | 0235:1234567890 |
0088 | International (GLN) | 0088:1234567890123 |
0007 | Sweden (Org number) | 0007:1234567890 |
0106 | Netherlands (KVK) | 0106:12345678 |
0208 | Belgium (CBE) | 0208:0453054123 |
0231 | Saudi Arabia (TIN) | 0231:300000000000003 |
Use GET /v2/lookup to check if a participant ID is registered on the Peppol network before sending.
Supported document types
Invostaq currently supports:
| Document type | UBL identifier |
|---|---|
| Invoice | urn:oasis:names:specification:ubl:schema:xsd:Invoice-2 |
Credit note support is planned. Use the lookup endpoint to check which document types a specific recipient accepts.
Compliance
Invostaq generates documents compliant with:
- Peppol BIS Billing 3.0 — the standard profile for invoices on the Peppol network
- EN 16931 — the European e-invoicing standard
- UAE FTA Corner 5 — UAE Federal Tax Authority requirements
- ZATCA Phase 2 — Saudi Arabia e-invoicing requirements (planned)
The compliance validation happens automatically during the send flow. If your invoice data doesn't meet the requirements, you'll receive a validation-failed error with specific rule violations. See the Error Reference for details.
Sandbox vs. production network
| Environment | Peppol network | Key prefix |
|---|---|---|
| Sandbox | TEST | sk_test_ |
| Production | PROD | sk_live_ |
The test network mirrors production behavior but invoices never reach real recipients. Use it to validate your integration end-to-end before going live.
See Environments for more details.