Yes. Krokul CRM integrates with PEPPOL and sends invoices over the network through your Peppol Access Point provider. It builds the invoice as a Peppol BIS Billing 3.0 document in UBL 2.1 syntax, the provider delivers it to the buyer Access Point, and the delivery status returns to the invoice. Krokul acts as the source system, and the Access Point role stays with your provider. The link runs through the provider API together with the Krokul API and webhooks.
When an invoice is issued for a buyer that receives via Peppol, Krokul builds a BIS Billing 3.0 invoice in UBL 2.1 with the seller and buyer parties, lines, VAT breakdown and payment terms, and hands it to the provider API. The provider looks up the receiver through the SMP and delivers the document.
Every receiver on the network has a participant identifier. Krokul keeps it on the client company and checks through the provider whether the buyer is registered before sending, so the manager knows in advance whether the invoice goes by Peppol.
Peppol BIS Billing 3.0 is a core invoice usage specification of EN 16931, so a valid document meets the European standard and the Peppol rules on top. Krokul checks the invoice against those rules first, and a missing VAT number or postal code shows on the invoice before it is sent.
The provider returns its document ID, which Krokul stores as an external key on the invoice. When the provider reports delivery or rejection, the status appears on the invoice and in the deal timeline.
OpenPeppol notes that Belgium requires structured e-invoicing for nearly all transactions between Belgian VAT-registered businesses from 1 January 2026, with Peppol as the recommended network. A Belgian company that issues invoices in Krokul sends them through its Access Point provider with the same connector.
| Peppol provider (Access Point) | Direction | Krokul | When |
|---|---|---|---|
| BIS Billing 3.0 invoice (UBL 2.1) | Krokul → provider | Invoice (document) with lines | The invoice is issued |
| Buyer party: legal name, VAT number, address | Krokul → provider | Client company | Built into each invoice |
| Participant identifier (SMP lookup) | Krokul ↔ provider | Peppol ID of the client company | Checked before sending |
| Provider document ID | Provider → Krokul | External key of the invoice | Right after sending |
| Delivery or rejection status | Provider → Krokul | Invoice status and a deal activity | Provider callback or scheduled check |
webhook/api-upsert) to document.created, check the x-crm-signature header, then read the invoice with document/api-read and the buyer with clientCompany/api-read.externalRef/api-set.activity/api-create.No. Krokul does not connect to the Peppol network itself and holds no Peppol certification. Your certified Access Point provider sends the invoice, and Krokul prepares it and tracks its status.
Krokul builds invoices as Peppol BIS Billing 3.0 in UBL 2.1 syntax. Your provider then delivers them to the buyer Access Point.
No. Krokul handles the deals, quotes and invoices you issue. Incoming purchase invoices stay with your accounting system or Access Point provider.
No. Peppol is a network of providers, so the flow talks to the API of the provider you choose, and the Krokul API with webhooks supplies the invoices and takes back the status.
Krokul holds no Peppol certification, and the connection to the network belongs to your Access Point provider. Incoming purchase invoices stay with your accounting system or provider, because Krokul covers the sales side.
Tell us which service you use and what should move between it and Krokul. We reply with the way to do it and when it will be ready.
Request received. We reply to your email.
Peppol is a trademark of OpenPeppol AISBL. Krokul is not affiliated with OpenPeppol and is not a Peppol service provider.