Peppol for your ERP, without rebuilding your ERP.
Push invoices in through the API, pull inbound documents out — PeppolNavigator handles the network.
Larger companies rarely want another invoicing screen. They want their ERP to keep doing its job while someone else handles Peppol formats, validation, delivery and inbound normalisation. That is what the PeppolNavigator API is for.
Your ERP was not built for Peppol.
Formats, validation rules and inbound variants keep changing. You want them handled outside your core system.
A Peppol layer with a clean API.
PeppolNavigator sits between your systems and the Peppol network.
- 01REST API documented with OpenAPI / Swagger and a Postman collection
- 02Create draft invoices by API and send them over Peppol
- 03Upload your own UBL, optionally with your PDF embedded
- 04Inbound polling with peek-then-acknowledge: at-least-once delivery, nothing lost
- 05CII and hybrid-PDF invoices normalised to UBL before you receive them
- 06Dead-letter queue with retry for failed deliveries
What you gain
Frequently asked questions
01Do you have a connector for SAP, Dynamics or Oracle?
We do not ship ready-made ERP connectors. Integration goes through the REST API, which most ERPs and integration platforms can call. We can help you plan the integration.
02How do we receive inbound invoices in our ERP?
Your system polls the documents endpoint, takes the new documents and acknowledges them. Until a document is acknowledged it stays available, so a failed run never loses an invoice.
03Can we keep our own invoice layout?
Yes. You can upload your own HTML/CSS template, or send your own PDF and let PeppolNavigator embed it in the UBL.
04Is there a test environment?
Yes, there is a sandbox environment next to production for integration testing.