# Peppol sending for Belgian companies

Source: https://veriport.io/docs/peppol-sending (published 2026-10-24)

Registers a Belgian company as a sender at Veriport's Peppol access point, under your account: one key can onboard many companies (software vendors). Give its enterprise number (any usual form; checked against its mod-97 digits), name, address and, optionally, its VAT number (BE + the enterprise number) and a contact e-mail (passed to the access point for the identity check, not stored by Veriport). The company is registered as a **sender only**: it is not published as a receiver, so wherever it receives its Peppol documents today stays unchanged.

**The mandate.** `mandate` records that the company authorises the sending: `accepted: true`, the version in force (`2026-11-17`), the name of the person accepting and their capacity (director, power_of_attorney). The record keeps the version, the SHA-256 of its exact text, the time, the key and a salted hash of the address, signed with an HMAC (`mandate.signature`, your receipt). The text:

> The company identified in this onboarding (the Company) authorises Janolab Studio LLC, which operates Veriport (https://veriport.io), and the certified Peppol access point Veriport uses as its subcontractor, to:
>
> 1. register the Company with that access point as a sender on the Peppol network under its Belgian enterprise number (scheme 0208), without publishing it as a receiver, so that its current way of receiving documents is not changed;
>
> 2. transmit over Peppol, in the Company's name, the invoices and credit notes submitted to Veriport for the Company under the API account that recorded this mandate;
>
> 3. have the access point verify the identity of the Company's representative, as the access point requires before a company may send.
>
> The person accepting declares that they may bind the Company (as a director or under a power of attorney) and that the data given for the Company is correct. The Company remains responsible for the content of each document it sends.
>
> The Company may withdraw this mandate at any time, through the API (DELETE /peppol/companies/{id}) or by writing to hello@veriport.io; documents already transmitted remain transmitted. This mandate is governed by the terms of service at https://veriport.io/terms.

**The identity check.** The access point verifies the company's representative before it may send (matched against the Belgian company register): the answer is `pending_verification` with `verificationUrl`, which the representative opens; the company becomes `active` when the access point confirms it (read it again, or wait for the next send). Onboarding the same enterprise number again on the same account answers the existing company (200); a company onboarded by another account is 409 `peppol_company_taken`. Not counted; prepaid credits or the monthly plan.

## POST https://veriport.io/api/v1/peppol/companies

Registers a Belgian company as a sender at Veriport's Peppol access point, under your account: one key can onboard many companies (software vendors). Give its enterprise number (any usual form; checked against its mod-97 digits), name, address and, optionally, its VAT number (BE + the enterprise number) and a contact e-mail (passed to the access point for the identity check, not stored by Veriport). The company is registered as a **sender only**: it is not published as a receiver, so wherever it receives its Peppol documents today stays unchanged.

**The mandate.** `mandate` records that the company authorises the sending: `accepted: true`, the version in force (`2026-11-17`), the name of the person accepting and their capacity (director, power_of_attorney). The record keeps the version, the SHA-256 of its exact text, the time, the key and a salted hash of the address, signed with an HMAC (`mandate.signature`, your receipt). The text:

> The company identified in this onboarding (the Company) authorises Janolab Studio LLC, which operates Veriport (https://veriport.io), and the certified Peppol access point Veriport uses as its subcontractor, to:
>
> 1. register the Company with that access point as a sender on the Peppol network under its Belgian enterprise number (scheme 0208), without publishing it as a receiver, so that its current way of receiving documents is not changed;
>
> 2. transmit over Peppol, in the Company's name, the invoices and credit notes submitted to Veriport for the Company under the API account that recorded this mandate;
>
> 3. have the access point verify the identity of the Company's representative, as the access point requires before a company may send.
>
> The person accepting declares that they may bind the Company (as a director or under a power of attorney) and that the data given for the Company is correct. The Company remains responsible for the content of each document it sends.
>
> The Company may withdraw this mandate at any time, through the API (DELETE /peppol/companies/{id}) or by writing to hello@veriport.io; documents already transmitted remain transmitted. This mandate is governed by the terms of service at https://veriport.io/terms.

**The identity check.** The access point verifies the company's representative before it may send (matched against the Belgian company register): the answer is `pending_verification` with `verificationUrl`, which the representative opens; the company becomes `active` when the access point confirms it (read it again, or wait for the next send). Onboarding the same enterprise number again on the same account answers the existing company (200); a company onboarded by another account is 409 `peppol_company_taken`. Not counted; prepaid credits or the monthly plan.

Tiers: credits, plan. Cost: free.

## GET https://veriport.io/api/v1/peppol/companies

The companies onboarded on your account, newest first, withdrawn ones included. Any key; not counted.

Tiers: free, credits, plan. Cost: free.

## GET https://veriport.io/api/v1/peppol/companies/{id}

One company of your account; while its identity check is pending, the access point is asked whether it completed. Any key; not counted.

Tiers: free, credits, plan. Cost: free.

- `id` (path, required): The company id (`pc_…`).

## DELETE https://veriport.io/api/v1/peppol/companies/{id}

Ends the mandate: nothing more is sent for the company (`withdrawn`); documents already handed to the access point still settle and stay readable. The company can be onboarded again with a new mandate. Any key; not counted.

Tiers: free, credits, plan. Cost: free.

- `id` (path, required): The company id (`pc_…`).

## POST https://veriport.io/api/v1/peppol/companies/{id}/verification

For a company still `pending_verification`: asks the access point for a new `verificationUrl` (links can expire). An active company is answered as it is. Any key; not counted.

Tiers: free, credits, plan. Cost: free.

- `id` (path, required): The company id (`pc_…`).

## POST https://veriport.io/api/v1/peppol/documents

Sends a Peppol BIS Billing 3.0 invoice or credit note for an `active` company of your account. The body is `companyId` and `invoice`, the same InvoiceInput as /einvoice/create (`format` peppol-bis, the default). In order, before anything leaves: the file is built and checked like /einvoice/create (schema, CEN and Peppol rules, the Belgian rules; 400 / 422 as there); the seller's electronic address must be the company (0208 + its enterprise number, the default); the buyer's electronic address is the receiver, looked up on the Peppol network (422 `peppol_receiver_unreachable` when it is not registered or does not receive this document type); a number the company already sent (and that did not fail) is 409 `peppol_duplicate_document`. Then 100 calls are reserved and the file is handed to the access point.

**Idempotency-Key is required**: a document sent twice reaches the buyer twice. The same key answers the same document at any later time (200, `Idempotent-Replayed: true`), with another body 409. **Billing:** 100 calls a document, once, when the access point confirms delivery to the receiver's access point (`delivered`); a refused, failed or never-confirmed document costs nothing, and its reserved calls are released.

**Answers:** 201 `delivered` (the receiver's access point acknowledged it) or `pending` (acknowledgement awaited: read it with GET /peppol/documents/{id}); 202 `unconfirmed` when the access point did not answer: Veriport then asks it for the exact file (its SHA-256) and settles the document within minutes, never sending it twice (a document the access point does not hold after 15 minutes becomes `failed`); 422 `peppol_send_failed` (with `documentId`) when the access point refused or could not deliver it. Only the metadata and the file's SHA-256 are kept (10 years), never the file.

Tiers: credits, plan. Cost: 100 calls per delivered document, billed on delivery; 0 for a refused, failed or replayed request.

- `Idempotency-Key` (header, required): Your identifier for this document (1–128 letters, digits, `-`, `_`, `.`, `:`), such as your invoice id.

## GET https://veriport.io/api/v1/peppol/documents

Your account’s documents, newest first, optionally one company’s. Any key; not counted.

Tiers: free, credits, plan. Cost: free.

- `companyId` (query): Only this company’s documents (`pc_…`).
- `limit` (query): Documents per page.
- `cursor` (query): The `nextCursor` of the previous page.

## GET https://veriport.io/api/v1/peppol/documents/{id}

One document of your account; while it is `pending` or `unconfirmed`, the access point is asked for its current state first (and a delivery found is billed then, once). Any key; not counted.

Tiers: free, credits, plan. Cost: free.

- `id` (path, required): The document id (`pd_…`).

## Read next

- [Belgium’s e-invoicing mandate: the Peppol checks](https://veriport.io/guides/belgium-peppol-e-invoicing-mandate)
- [Free Peppol participant lookup](https://veriport.io/tools/peppol-participant-lookup)
- [Product page: the e-invoice API](https://veriport.io/einvoice-api)
