Checklist for connecting an ERP to Belgian Peppol e-invoicing: scope, VAT data, Peppol BIS, access point, testing, archive and 2026 readiness.
List domestic Belgian B2B invoices between VAT-liable businesses, supplier invoices, credit notes, self-billing cases, exempt Article 44 flows, B2C transactions and non-established VAT registrations. Belgian official guidance says structured e-invoices become mandatory from 1 January 2026 for transactions between Belgian VAT-registered companies, with limited exceptions, so the ERP scope must be decided before connector selection.
Peppol is not only a transport network. The invoice must contain structured data that can be processed automatically. Check Belgian VAT number, legal name, address, buyer reference, purchase order, VAT category, payment terms, bank account, line descriptions, discounts, delivery charges and credit-note references against Peppol BIS and EN 16931 expectations.
Some ERPs connect through a certified Peppol access point, some through accounting software, and some through integration middleware. Ask who registers the Peppol participant, who monitors delivery, how status messages are shown, whether inbound supplier invoices return to the ERP, and how support is split between ERP vendor, access point and accountant.
A useful demo should include a normal sales invoice, a credit note, an invoice with discount and shipping, an inbound supplier invoice, a wrong VAT number, a rejected file, a retry and an archive search. If the ERP only proves one happy-path invoice, the business has not tested daily operations.
ERP Peppol integration touches master data, order-to-cash, procure-to-pay, tax configuration, customer onboarding and support. Assign an owner for rejected invoices, customer Peppol identifiers, access point incidents, field mapping changes, supplier onboarding and accountant review.
Belgian businesses still need reliable invoice evidence. Store the original structured file, readable view, Peppol delivery information, validation results, accounting posting, correction links and user logs. Make sure finance can search by invoice number, VAT number, KBO/BCE identifier, customer name and Peppol status.
The accountant can confirm whether ERP output can be booked, reconciled and checked without manual PDF handling. Ask them to review VAT categories, credit notes, inbound invoices, month-end cut-off, exceptions and what evidence they need during VAT review.
Do not assume a PDF email remains enough, buy an access point without inbound workflow, ignore supplier invoices, leave Belgian VAT master data dirty, forget credit notes, split responsibility across vendors without escalation rules or treat Peppol as only an IT switch. This is practical information, not legal or tax advice.
Prefer vendors that can show Belgian Peppol production references, Peppol BIS validation, inbound and outbound workflow, clear support hours, readable error messages, API logs, accountant export, user permissions and transparent pricing for invoice volume and access point services.
Create one ERP test pack with ten invoices and supplier examples, then ask every ERP, accounting software or access point provider to run the same pack. Compare failures, status visibility, support response and archive evidence before committing.
Classify Belgian VAT B2B, B2C, exempt and foreign-registration flows
Clean VAT, KBO/BCE, customer and supplier master data
Map ERP fields to Peppol BIS and EN 16931
Select access point, middleware or accounting-software route
Test outbound invoices, inbound invoices, credit notes and rejections
Define error ownership across finance, IT, vendor and accountant
Store original structured files, Peppol statuses and logs
Review pricing, support, volume limits and go-live evidence
For most transactions between Belgian VAT-liable businesses, official Belgian guidance points to structured electronic invoices from 1 January 2026 and systematic exchange via Peppol. Check exceptions and your exact VAT position before relying on a generic answer.
No for in-scope Belgian B2B transactions. Belgian guidance distinguishes classic electronic invoices from structured electronic invoices and says PDF by email or platform will not be enough for the mandate.
Sometimes. It can work when accounting software has complete invoice data and controls the workflow. If verkoop, orders, pricing or approvals live in the ERP, you must test whether the accounting route preserves field quality, status visibility and corrections.
Ask for outbound invoice, inbound supplier invoice, credit note, wrong VAT number, rejected file, retry, Peppol status, archive search, accounting posting and user-permission examples. Use real Belgian master-data cases, not only a vendor sample.
Belgian VAT numbers, KBO/BCE identifiers, legal names, addresses, VAT category codes, line descriptions, discount/shipping lines, payment terms and credit-note references commonly expose ERP master-data or mapping issues.
Decide before go-live. Some errors belong to sales or master data, some to finance tax settings, some to the ERP integrator, and some to the access point. The process should name owner, response time and evidence for every error type.
Yes. Receiving structured supplier invoices affects approval, booking, matching, archive search and accountant review. A send-only integration can leave half the operating model unfinished.
No. It is a practical readiness guide. Confirm regulated details with Belgian official sources, FPS Finance guidance and qualified advisers.
Use the country hub to see every related deadline, checklist, format guide and software comparison for this market.
We prioritize official government and EU sources where available and keep last-checked dates visible for mandate-sensitive pages.
E-Invoice Finder
