# PEPPOL e-invoicing + Krokul CRM

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.

**Status:** Via API and webhooks.

## What your team gets

### Issued invoice delivered over Peppol

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.

### Buyer participant ID on the client company

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.

### Validation before the invoice leaves

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.

### Delivery status on the invoice

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.

### Belgian B2B invoices from 2026

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.

## What moves between PEPPOL and Krokul

| Peppol provider (Access Point) | Krokul | Direction | When |
|---|---|---|---|
| BIS Billing 3.0 invoice (UBL 2.1) | Invoice (document) with lines | Krokul → provider | The invoice is issued |
| Buyer party: legal name, VAT number, address | Client company | Krokul → provider | Built into each invoice |
| Participant identifier (SMP lookup) | Peppol ID of the client company | Krokul ↔ provider | Checked before sending |
| Provider document ID | External key of the invoice | Provider → Krokul | Right after sending |
| Delivery or rejection status | Invoice status and a deal activity | Provider → Krokul | Provider callback or scheduled check |

## How to connect today

### Custom flow through the Krokul API and webhooks

1. Sign a contract with a Peppol Access Point provider, register your company as a sender there, and create a Krokul API key that reads documents and client companies and writes activities.
2. Subscribe a Krokul webhook (`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`.
3. Send the document to the API of your provider, first to its test environment, and save the provider document ID with `externalRef/api-set`.
4. Record each delivery or rejection reported by the provider on the deal with `activity/api-create`.

### For integrators

In the Peppol four-corner model, sender and receiver each connect through an Access Point, an SMP publishes what a receiver accepts, and the SML tells Access Points which SMP to ask. Krokul sits before corner one as the source system. Krokul webhooks are signed with HMAC-SHA256, failed deliveries can be replayed with `webhook/api-redeliver`, and `x-crm-delivery` lets your service pass each invoice to the provider only once.

[API documentation](https://app.krokul.com/api/v1/docs)

## Questions and answers

### Is Krokul a Peppol Access Point?

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.

### Which Peppol format does Krokul produce?

Krokul builds invoices as Peppol BIS Billing 3.0 in UBL 2.1 syntax. Your provider then delivers them to the buyer Access Point.

### Can Krokul receive supplier invoices from Peppol?

No. Krokul handles the deals, quotes and invoices you issue. Incoming purchase invoices stay with your accounting system or Access Point provider.

### Is there a ready Peppol module on automation platforms?

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.

## Limits

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.

## Related services

- [Avalara](https://krokul.com/en/integrations/avalara/index.md)
- [Xero](https://krokul.com/en/integrations/xero/index.md)
- [QuickBooks Online](https://krokul.com/en/integrations/quickbooks-online/index.md)
- [Sage Accounting](https://krokul.com/en/integrations/sage-accounting/index.md)
- [Business Central](https://krokul.com/en/integrations/dynamics-365-business-central/index.md)

[Tax and e-invoicing](https://krokul.com/en/integrations/category/tax-einvoicing/index.md)

Peppol is a trademark of OpenPeppol AISBL. Krokul is not affiliated with OpenPeppol and is not a Peppol service provider.

Updated: 2026-10-12

---

App: https://app.krokul.com/ · API: https://app.krokul.com/api/v1/docs