From 2026, structured electronic invoicing via the Peppol network becomes mandatory for B2B transactions in Belgium. If your practice or business still sends and receives invoices as PDFs or paper, this changes what "sending an invoice" means — not just the format, but the entire process.

What the mandate actually requires

Peppol (Pan-European Public Procurement Online) is a network and a structured data format (UBL/XML) for exchanging invoices directly between accounting systems — not email, not PDF attachments. An invoice sent via Peppol arrives as structured data your accounting software can read and book automatically, not a document someone has to open and re-key.

For accountants managing multiple clients, this means every client relationship needs a way to send and receive Peppol-format invoices — and someone has to actually build that capability before the mandate takes effect, not after.

Why this is more than a software checkbox

Peppol compliance touches the same three stages every invoice already passes through in your practice:

  • Receiving. Incoming Peppol invoices need to be picked up from the network and matched against the right client and ledger — automatically, not manually downloaded and re-entered.
  • Sending. Outgoing invoices need to be generated in valid UBL/XML and transmitted through the network correctly, not just formatted to look right.
  • Booking. Once received or sent, the invoice still needs to land in the actual ledger — Peppol solves transmission, not bookkeeping.

A tool that only handles the transmission piece still leaves the booking and matching work manual — which is exactly the work most accounting practices are already short-staffed for.

The Accounting Bundle handles all three stages as one connected process: Peppol invoices are received, validated, and booked directly into Odoo — incoming and outgoing, without a separate tool or manual re-entry.

How the automation layer handles it

OpenClaw and n8n sit between the Peppol network and your books, handling the parts that would otherwise be manual:

  • Incoming Peppol invoices are validated against the current UBL schema automatically before they reach the ledger
  • Matching against purchase orders or client records happens without a bookkeeper re-typing anything
  • Outgoing invoices generated in Odoo are converted and transmitted in valid Peppol format
  • Errors or mismatches are flagged for a human to review — not silently dropped or silently accepted

The goal isn't to remove the accountant from the process — it's to remove the manual re-keying so the accountant's time goes to reviewing exceptions, not processing routine invoices one by one.

See the platform

The Accounting Bundle runs as three dedicated, EU-hosted servers per customer, with Peppol handling built in from day one — not bolted on separately.

Explore the Accounting Bundle