Reseller programme

Overview

The e-invoice.be reseller programme is for SaaS companies, software vendors and service providers that want to add Peppol e-invoicing to their products and services. A reseller gets an organisation API key for the Admin API and manages one tenant for each customer. A tenant is a company that a reseller manages.

Who the programme is for

SaaS platforms (accounting, ERP, CRM and invoicing software)
Software vendors that sell business management products
Managed service providers that serve many clients
Industry platforms (for example construction, healthcare and logistics)
Accounting and bookkeeping firms that manage the invoicing of their clients

Benefits

White-label integration

Your customers use your interface. Your platform calls the e-invoice.be API in the background.

Multi-tenant support

Manage all your customers through one integration, with one tenant and one API key for each customer.

Technical support

Technical support during the integration and after it.

Volume pricing

Pricing that depends on the volume, for resellers and service providers.

How it works

Partnership setup

Send an email to support@e-invoice.be to discuss:

your use case and your customers
the integration requirements
the expected transaction volumes
pricing and commercial terms

Technical integration

Integrate the API into your product:

API access: all e-invoice.be API endpoints, with the API key of each tenant.
Admin API: create and manage tenants and their API keys with your organisation API key. See the Admin API.
Webhooks: each tenant has its own webhooks. Create them with the API key of the tenant. See Webhooks.
Testing: use test-mode tenants. Their sends go to email and they cause no Peppol traffic. See Test mode and sandbox companies.

Go live

Start e-invoicing for your customers:

Customer onboarding: create the tenant, the API key and the Peppol registration through the Admin API.
Billing: consolidated billing or billing for each customer, as agreed in your contract. To read the usage of each tenant for re-invoicing, see Usage statistics and credits.
Support: e-invoice.be handles technical Peppol problems; you give support to your customers.

Use cases

SaaS accounting platform

A cloud accounting platform adds Peppol e-invoicing for its customers. For each new customer, the platform creates a tenant and an API key with the organisation API key (E_INVOICE_ORG_API_KEY):

# 1. Create a tenant for the new customer (Admin API, organisation API key)
curl -X POST "https://api.e-invoice.be/api/admin/tenants" \
     -H "Authorization: Bearer $E_INVOICE_ORG_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{
       "name": "e-invoice-bv",
       "description": "E-INVOICE BV",
       "company_tax_id": "BE1018265814",
       "peppol_ids": ["0208:1018265814"]
     }'

{
  "id": "ten-9k2m4p7q3w5x8r",
  "name": "e-invoice-bv",
  "description": "E-INVOICE BV",
  "company_tax_id": "BE1018265814",
  "peppol_ids": ["0208:1018265814"],
  "plan": "enterprise",
  "credit_balance": 999999999,
  "created_at": "2026-04-16T10:00:00.000000Z",
  "updated_at": "2026-04-16T10:00:00.000000Z"
}

The response is shortened; see Create a tenant for all fields.

# 2. Create an API key for the tenant (use the tenant id from step 1)
curl -X POST "https://api.e-invoice.be/api/admin/tenants/ten-9k2m4p7q3w5x8r/api-keys" \
     -H "Authorization: Bearer $E_INVOICE_ORG_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{"name": "production-key"}'

{
  "id": "api-3h8f5j2k9l4m7n6p1q5r8s2t4v6w9x3y",
  "tenant_id": "ten-9k2m4p7q3w5x8r",
  "name": "production-key",
  "description": null,
  "created_at": "2026-04-16T10:00:00.000000Z",
  "updated_at": "2026-04-16T10:00:00.000000Z",
  "is_deleted": false
}

The id of the API key is the bearer token of the tenant. The platform stores it and uses it for all invoice operations of this customer. The API finds the tenant from the key, so the request body does not contain a tenant ID. Set E_INVOICE_API_KEY to the id of the API key of the tenant. For example, to list the documents that the customer sent:

# 3. Call the standard API with the tenant API key
curl -X GET "https://api.e-invoice.be/api/outbox/" \
     -H "Authorization: Bearer $E_INVOICE_API_KEY"

To create and send an invoice with this key, see Create e-invoices.

ERP system integration

An ERP vendor builds e-invoicing into the product:

Users send invoices from the ERP interface.
The ERP calls the e-invoice.be API in the background.
The ERP gets status changes through webhooks.
Users do not need a second login.

Managed service provider

A managed service provider handles the invoicing of 50 or more clients:

One API integration for all clients.
One tenant, with its own Peppol ID, for each client.
One API key for each client, which the provider can rotate and revoke through the Admin API.

Technical requirements

What your system must do

Send authenticated HTTPS requests.
Parse and generate JSON.
Host a webhook endpoint to receive notifications.
Handle errors and repeat failed requests.

Security

Store API keys in a secure location.
Keep a separate credential for each tenant.
Verify the signature of each webhook.
Keep an audit log.

Pricing

Reseller pricing depends on:

Volume: the number of invoices for each month
Number of customers: the number of tenants
Support level
Contract term

Send an email to support@e-invoice.be for a quotation.

How to become a reseller

Contact e-invoice.be

Send an email to support@e-invoice.be with:

your company background
a description of your use case
the expected volumes
your schedule

Commercial discussion

In a call, e-invoice.be and you discuss:

your requirements
the pricing options
the integration approach

Technical onboarding

After the agreement:

you receive an organisation API key for the Admin API
you read the Admin API page
you build and test the integration with test-mode tenants

Launch

Go live with your integration:

create production tenants
onboard your customers
get continued support

Support

A reseller gets:

Technical support: help with the API integration and with troubleshooting, through support@e-invoice.be
Admin API access: an organisation API key to manage tenants. See the Admin API.

Frequently asked questions

Can I white-label the service?

Yes. Your end users do not see the API integration. They use your interface, and your platform calls the e-invoice.be API in the background.

How are customers billed?

The billing model is part of your contract. Possible models are:

consolidated billing to you (you bill your customers)
billing for each tenant (e-invoice.be bills each customer)
a mix of the two

Who gives support to end customers?

You give first-line support to your customers. e-invoice.be gives:

technical support to you for API problems
communication about Peppol network status and incidents
documentation that you can share

Can customers exchange documents with users of other Peppol access points?

Yes. Peppol is an interoperable network. Your customers can exchange invoices with all participants on the Peppol network, whatever their access point provider.

What compliance is necessary?

e-invoice.be handles:

Peppol compliance and certification
validation against Peppol BIS Billing 3.0
the connection to the network

You handle:

customer onboarding (know-your-customer checks, if applicable)
data privacy (GDPR compliance)
the security of your application

Is there a minimum commitment?

The agreement depends on your situation. Send an email to support@e-invoice.be to discuss the options for your business model.

Contact

To become a reseller, send an email to support@e-invoice.be.

Next Steps

Admin API

Create tenants, issue API keys and register tenants on Peppol.

Create e-invoices

Create and send invoices with the API key of a tenant.

Webhooks

Receive status changes for the documents of each tenant.

Test mode and sandbox companies

Test your integration with no Peppol traffic.

Getting started

Send documents

Receive and manage

Other input formats

Integrate

SDKs and tools

Resellers

Reference

Overview

Who the programme is for

Benefits

White-label integration

Multi-tenant support

Technical support

Volume pricing

How it works

Use cases

SaaS accounting platform

ERP system integration

Managed service provider

Technical requirements

What your system must do

Security

Pricing

How to become a reseller

Support

Frequently asked questions

Contact

Next Steps

Admin API

Create e-invoices

Webhooks

Test mode and sandbox companies

​Overview

​Who the programme is for

​Benefits

White-label integration

Multi-tenant support

Technical support

Volume pricing

​How it works

​Use cases

​SaaS accounting platform

​ERP system integration

​Managed service provider

​Technical requirements

​What your system must do

​Security

​Pricing

​How to become a reseller

​Support

​Frequently asked questions

​Contact

​Next Steps

Admin API

Create e-invoices

Webhooks

Test mode and sandbox companies

Overview

Who the programme is for

Benefits

How it works

Use cases

SaaS accounting platform

ERP system integration

Managed service provider

Technical requirements

What your system must do

Security

Pricing

How to become a reseller

Support

Frequently asked questions

Contact

Next Steps