Connect your software to Peppol
Two ways, one result. Pick the connection that best fits how your software already works today.
REST API
Your software sends the UBL document to PepTalk in one call and gets an answer straight away.
- Immediate validation and error message
- Own API key per company
- Status tracking per document
Choose this if you build a web application or SaaS, or already work with REST services.
FTP
Your software writes the UBL file to a folder on our FTP server and we pick it up.
- No code for HTTP calls needed
- Fits scheduled exports and batches
- Results visible in the portal
Choose this if your software can already export or write files.
From first conversation to live
1. Introduction
Together we look at how your software creates invoices and choose the connection.
2. Test environment
You get access to the portal in test mode and send your first test documents.
3. Registration
Your company (or your customers) are registered on the Peppol network with the right document types.
4. Live
When everything is right, we switch each company from test to live.
What you can send and receive
| Document type | Used for | Direction |
|---|---|---|
| Invoice | Standard sales invoice, Peppol BIS Billing 3.0 | Send & receive |
| Credit note | Correction or refund of an invoice | Send & receive |
| Invoice response | Status message from the buyer: received, accepted, disputed | Send & receive |
| Self-billing invoice | Invoice created by the buyer on behalf of the supplier | Send & receive |
| Self-billing credit note | Credit note created by the buyer | Send & receive |
Need another document type? Let us know.
What PepTalk handles for you
Validation
Every document is checked before it leaves. If there is a problem you get the reason, not a vague error code.
Recipient lookup
PepTalk looks up your customer's address and supported document types in the Peppol address book.
Sending
Automatic, or with manual approval if you prefer to check first.
Receiving
Incoming documents are processed, stored and can be forwarded by e-mail.
Archiving
Everything is archived automatically, incoming and outgoing, searchable and downloadable per month as a ZIP.
Notifications
Errors, warnings and deliveries are collected in the portal, with reports by e-mail.
Technical documentation and examples
After the first conversation you receive the API description, FTP instructions and example UBL files for your test environment.
Request a test environment