Belgium B2B E-Invoicing in 2026: What Small SaaS and Service Teams Need to Change

Belgian B2B e-invoicing changes how small SaaS, marketplaces, agencies, and subscription products should collect billing data. It is not enough to email a PDF after payment. The product flow must know whether the buyer is a business, capture legal buyer details, and route the invoice through a Peppol-capable accounting or access-point setup.

What changed

Belgium's B2B mandate applies to VAT-liable operations between VAT-liable entities from 1 January 2026. The European Commission country profile also states that B2C is not mandated, while B2B and B2G flows must support EN 16931/Peppol-compatible structured invoices.

For software teams this means the checkout cannot treat every customer as just an email address. A corporate buyer needs a billing profile: legal name, VAT or company number, country, address, billing email, and, where known, the Peppol endpoint.

Product checklist

1. Separate B2C and B2B checkout paths.
2. Require VAT/company number for business package sales.
3. Store legal billing address separately from user profile data.
4. Keep invoice drafts reviewable before enabling auto-send.
5. Sync payment status from Stripe or the app store separately from Peppol delivery status.
6. Build an admin view for failed, pending, sent, and paid states.

Stripe and Peppol

Stripe can collect tax IDs and addresses, but Stripe itself is not the Peppol network. If Billit, Odoo, or another accounting provider imports Stripe invoices, keep auto-send disabled until the first real invoice for that buyer country has been reviewed.

Implementation pattern

The safest architecture is: checkout creates a paid order, the backend creates an invoice draft, accounting or Billit/Odoo validates the Peppol-ready payload, and only then the invoice is sent or marked for manual review.

Sources

• European Commission, eInvoicing in Belgium: https://ec.europa.eu/digital-building-blocks/sites/spaces/DIGITAL/pages/467108877/eInvoicing%2Bin%2BBelgium