Skip to content

Best Peppol API for a multi-tenant SaaS in 2026

For a multi-tenant SaaS platform, the right Peppol API is the one that matches how you onboard and manage customer legal entities — not a universal winner.

Short answer

Platform fit
Choose getpeppr when one master API key must manage many customer Legal Entities, you want a TypeScript SDK and CLI, and getpeppr's published country coverage matches your rollout.
Alternative fit
Choose another provider when you need broader direct infrastructure, a full SDK in a language other than TypeScript, fully API-bootstrapped onboarding, or enterprise AP automation. The verified comparison below names the trade-offs.

Ordinary Peppol invoicing from France works today; French regulated CTC is not yet open in production.

Peppol API providers, side by side

getpepprBuilt for SaaS platforms

Built for:
SaaS platforms embedding Peppol (multi-tenant)
SDKs:
TypeScript + CLI + PHP package for sending UBL + hosted MCP server (sandbox)
Pricing:
Business from EUR 49/mo + usage; Platform: one plan at EUR 99/mo + usage, 50 Legal Entities included, no per-customer minimum
Self-serve:
Sandbox self-serve; Platform production contract-gated
Market focus:
Belgium + France + Ireland + UK + Netherlands + Denmark + Germany + Sweden + Norway + Estonia + Iceland self-serve · French regulated CTC not yet open in production
Evaluation path:
Free sandbox + offline CLI + AI assistant via hosted MCP

peppol.sh

Built for:
Developers, AI agents & embedded SaaS
SDKs:
REST/OpenAPI + code samples; TypeScript SDK published on npm (0.1.0), Python and PHP announced as coming soon
Pricing:
Personal EUR 0.20/document; Connect EUR 0.16→0.10 (EUR 250 top-up)
Self-serve:
Yes (API-created sandbox)
Market focus:
Developer- and agent-first Peppol
Evaluation path:
Instant API-created sandbox

e-invoice.be

Built for:
SaaS, ERPs & managed-service partners
SDKs:
5 languages (TS, Python, PHP, Ruby, Java) + MCP
Pricing:
From EUR 0.25/invoice; Enterprise from EUR 0.18
Self-serve:
Yes
Market focus:
Belgian certified AP; claims 30+ reachable countries
Evaluation path:
Free sandbox, no sales call

Storecove

Built for:
ERP integrators & platforms
SDKs:
RESTful JSON API
Pricing:
Quote required
Self-serve:
30-day test account by request
Market focus:
31-country compliance; Peppol + DBNAlliance
Evaluation path:
Requested 30-day sandbox

Basware

Built for:
Enterprise e-invoicing & AP automation
SDKs:
Network REST API + XML integrations
Pricing:
Subscription; contact Basware
Self-serve:
Support-provisioned test account
Market focus:
Global network
Evaluation path:
Testing account via Basware Support

"Market focus" reflects each provider's published positioning and country-framework coverage. It does not prove that every sender can onboard or that every national tax flow is supported. Details verified against the linked official sources on 2026-09-19; re-check before deciding.

Comparing getpeppr and peppol.sh specifically? See the head-to-head

Still deciding whether to become an access point at all? Compare the three ways

How to add Peppol e-invoicing to your software without becoming an access point

They all end on the same network. What changes is how much of it your team has to build and keep up to date.

Short answer

You don't need to become a Peppol access point. Map your invoices to JSON and call a Peppol API; a certified access point carries them across the network. If you send on behalf of your customers, pick a provider with a real multi-tenant sender model. getpeppr manages many customer legal entities under one master API key per environment, each identity-verified and authorised by the customer before it can send live invoices, with a TypeScript SDK and a free sandbox.

Option 1

Become an access point yourself

  • Join OpenPeppol and sign the Service Provider Agreement with your Peppol Authority, or with OpenPeppol where your country has none
  • Run the network stack: an AS4 implementation and Peppol PKI certificates, plus SMP registration for the customers you receive for
  • Pass OpenPeppol's AS4 onboarding test before you get a production certificate
  • Generate and validate UBL, and stay compliant with the BIS specifications your service uses as they are released

Fits when e-invoicing is your product, not a feature of it.

Option 2

Integrate an access point's API directly

  • No accreditation on your side — the provider holds it
  • You map your invoices to the provider's document model
  • You build customer onboarding, identity handling and status reconciliation

Fits when you need broad direct infrastructure and have the team to build the layer above it.

Where most software vendors landOption 3

Use a Peppol API built for software vendors

  • Send JSON; validated UBL is generated and delivered for you
  • Customer legal entities are created through the API; each customer authorises on a hosted page
  • Status webhooks and a sandbox to test before anything is live

Fits when invoicing is a feature of your product. getpeppr, e-invoice.be and peppol.sh work this way.

Peppol accreditation

Option 1 Yours to obtain and keep

Option 2 The provider's

Option 3 The provider's

UBL generation and validation

Option 1 You build it

Option 2 Shared with the provider

Option 3 Handled by the provider

Onboarding each customer company

Option 1 You build it

Option 2 You build it

Option 3 API, plus a hosted customer authorisation

Keeping up with rulebook updates

Option 1 Your team

Option 2 Shared with the provider

Option 3 The provider

First decision: who is the sender?

This one question decides which option fits. Answer it before comparing providers.

Your own invoices

Your company sends

You bill your customers as one legal entity. One verified sender, one API key, many recipients. Every option above handles this.

On behalf of customers

Each customer sends under its own name

Each customer is a separate legal entity on the network. You need consent, identity checks and an explicit sender per invoice. Ask each provider how it does this before promising it to your customers.

Why "multi-tenant" changes the question

A normal Peppol integration assumes one company sending its own invoices. A SaaS platform is different: each customer is a separate legal entity on the network. These are the criteria that actually matter.
Tenant model
One company sending its own invoices is easy. A SaaS platform needs one integration with N legal entities underneath it — each customer is a separate Peppol participant — not one account per customer.
Programmatic onboarding
Can you register a tenant and mint its per-tenant credentials via API, or does every new customer need a manual setup or a sales call?
JSON in, no XML
You send your data shape; UBL / Peppol BIS Billing 3.0 is generated, validated, and transmitted for you. No XML schemas in your codebase.
Try before you buy
Can you evaluate without a signup wall or a demo call? Offline validation and instant sandboxes shorten the path from curiosity to first invoice.
Certified Access Point backing
A certified Peppol Access Point handles network transport, certificates, and Peppol rules. Fiscal compliance, invoice content, sender onboarding, and national tax flows still need to be checked separately.
Mandate roadmap & pricing model
Check which country-specific layers are live, which are piloted, and whether adding tenants or volume changes the contract, monthly fee, or per-document price.

The providers, fairly

No single provider wins on every axis. Here's where each one is strongest — facts verified on 2026-09-19.
getpeppr (opens in a new tab)
A TypeScript-first Peppol SDK built for SaaS platforms. Its Platform API uses one master API key to manage multiple customer Legal Entities, with per-tenant authorisation and webhooks. The CLI can validate and convert invoices offline without an account, and a PHP package sends UBL that PHP software already generates. Sandbox access is self-serve; Platform production access requires an Order Form and DPA. Customers are self-serve in France, Belgium, Ireland, the United Kingdom, the Netherlands, Denmark, Germany, Sweden, Norway, Estonia and Iceland. Ordinary Peppol invoicing from France works today; the regulated CTC flow for the September 2026 mandate is not yet open in production. Consider getpeppr when that tenant model, the TypeScript tooling, and the published country coverage match your rollout.
Storecove (opens in a new tab)
A certified Peppol Access Point with a RESTful JSON API and published compliance coverage in 31 countries. Storecove positions the product for ERP integrators and platforms, offers a requested 30-day test account, and activates production after contract. Pricing is quoted per integrator: the published route is a consultation or a test-account request rather than a rate card. Consider it when direct Access Point infrastructure and broader country-framework coverage matter more than a self-serve product path.
e-invoice.be (opens in a new tab)
A certified Belgian Access Point offering JSON-to-UBL, a free sandbox, multi-tenant account management, SDKs in TypeScript, Python, PHP, Ruby and Java, plus an MCP server. Published pricing starts at EUR 0.25 per invoice, with Enterprise from EUR 0.18 and no monthly minimum. Production follows KYC. Consider it when multiple SDK languages and a per-document model fit your platform.
peppol.sh (opens in a new tab)
A developer- and agent-centric REST API that accepts JSON, produces Peppol BIS 3.0 UBL, and supports one Company per tenant through its Connect model. Sandbox signup, keys and KYC are API-driven; published pricing has no monthly or per-tenant fee. It publishes a TypeScript SDK on npm; Python and PHP are announced as coming soon. Consider peppol.sh when API bootstrapping and agent-driven workflows are the priority.
Basware (opens in a new tab)
An enterprise e-invoicing network and AP automation platform with Network REST APIs plus documented XML integration paths. A subscription is required, pricing is provided by Basware, and a free testing account is provisioned through Basware Support. Consider it when enterprise AP automation and global network breadth are the primary requirements.

Which should you choose?

Match the provider to your situation.
Multi-tenant SaaS that wants a premium TypeScript SDK + help embedding Peppol
getpeppr
Raw certified Access Point infrastructure + broad coverage, build-your-own layer
Storecove
Five SDK languages + MCP with published per-document pricing
e-invoice.be
Lean / agent-first team, no monthly fee at all
peppol.sh
Enterprise AP automation + global network
Basware

Why getpeppr for multi-tenant SaaS

getpeppr is designed for SaaS and ERP platforms that embed Peppol for their customers. It is a fit when its Platform tenant model, TypeScript tooling, and published country coverage match your rollout — not a universal winner on every axis.
Native multi-tenant
One master API key, N legal entities, per-tenant authorisation built in — not one account per customer.
Identity verification (Trust Layer)
Legal entities follow the applicable automatic or manual verification path before they can send. Current availability stays on the country coverage page.
TypeScript SDK + CLI
Full type safety, and offline validation from the terminal with no account required — try before you sign up.
Published Platform pricing
One Platform plan: a monthly fee, per-document usage, 50 customer Legal Entities included, and no per-customer minimum.
Certified Access Point underneath
Storecove handles Peppol network transport and certificates. National tax-flow support remains country-specific and is published separately.

Sources and methodology

Each provider row was checked against the provider's own public pages on 2026-09-19. We compare published tenant model, tooling, pricing, onboarding and market positioning. A sandbox claim is not treated as a measured production-delivery time, and Peppol connectivity is not treated as proof of every national tax flow. Re-check the linked source before making a buying decision.

Access point and Belgian mandate

Checked against these primary sources on 2026-09-18. Mandates change — re-check the linked source before making a decision.

Frequently asked questions

What is the best Peppol API for a multi-tenant SaaS?

For SaaS platforms sending invoices on behalf of many customers, the deciding factor is a native multi-tenant model — one API key, many legal entities, with per-tenant onboarding via API. getpeppr is purpose-built for that case; peppol.sh and e-invoice.be also support multi-tenant setups, and Storecove provides the underlying Access Point infrastructure.

Do I have to deal with UBL or XML myself?

No. With API-first providers like getpeppr, peppol.sh, and e-invoice.be you send JSON (or your own data shape) and the provider generates, validates, and transmits the Peppol BIS Billing 3.0 UBL for you.

Can I try a Peppol API before signing up or talking to sales?

Yes, but the path differs. getpeppr offers offline CLI validation, a hosted MCP server whose public tools Claude Code and Codex can use without an account, and a self-serve sandbox; e-invoice.be offers a free sandbox; peppol.sh can create a sandbox account through its API. Storecove offers a 30-day test account by request, and Basware provisions a free testing account through Support.

How can I check whether a company is already on the Peppol network?

Use the free Peppol participant lookup at getpeppr.dev/peppol-lookup — no signup needed. Enter a company's VAT or registration number and its scheme to see whether it is registered on Peppol and which documents (invoice, credit note) it can receive.

Which countries does the EU e-invoicing mandate cover, and when?

Belgium mandated B2B e-invoicing from 1 January 2026. Germany has phased requirements underway. France's rollout began on 1 September 2026. The EU's ViDA package extends digital reporting requirements for cross-border B2B by 1 July 2030. Peppol connectivity does not by itself prove national tax-flow coverage, so check each provider's published country capabilities.

What does "multi-tenant" mean for Peppol e-invoicing?

Each of your customers is a separate participant on the Peppol network with its own identity. A multi-tenant Peppol API lets your platform register and send for all of them through a single integration, instead of standing up a separate account per customer.

Do I need to become a Peppol access point to send e-invoices from my software?

No. You can connect through a certified access point, either by integrating its API directly or by using an API built for software vendors. Becoming an access point yourself means joining OpenPeppol, signing a Service Provider Agreement with your national Peppol Authority, running an AS4 implementation with Peppol PKI certificates and passing OpenPeppol's onboarding test — worth it when e-invoicing is your core product, rarely otherwise.

Can my SaaS send Peppol invoices on behalf of my customers?

Yes, if your provider supports a platform sender model: each customer is registered as its own legal entity, identity-verified, and authorises you to send in its name before any live invoice goes out. With getpeppr you create those legal entities through the API under one master key per environment; each customer then confirms on a getpeppr-hosted page, co-branded with your name, and a live send is refused until it has. The Platform plan includes 50 customer legal entities.

Is Peppol e-invoicing mandatory in Belgium?

Since 1 January 2026, Belgian VAT-taxable businesses must in principle issue structured electronic invoices to each other, under the law of 6 February 2024 (Moniteur belge, 20 February 2024), which added Article 53 §2bis to the VAT Code. The scope has exceptions — among them businesses without a Belgian establishment and those carrying out only Article 44 exempt supplies — and the law of 10 February 2026 narrowed it further and added a case where the recipient cannot technically receive a structured invoice. The default exchange is Peppol BIS over the Peppol network; another format is possible by mutual agreement and must still meet EN 16931. Check your own position against the sources on this page rather than treating this as advice.

Ready to send your first Peppol invoice?

Validate locally or create a free sandbox. No credit card, full SDK access.

npm install @getpeppr/sdk

Free sandbox, no time limit. Production access follows the plan you choose.