Peppol e-invoicing in Belgium: step-by-step setup for contractors
Follow five practical steps for Belgian Peppol B2B e-invoicing: check scope, clean KBO data, test sending and receiving, and handle credit notes.
Since 1 January 2026, Belgian VAT-registered businesses have been legally required to exchange structured electronic invoices for domestic B2B transactions. For contractors, subcontractors, architects and suppliers working in Belgium, an emailed PDF invoice is no longer sufficient on its own: the legal invoice travels as a structured UBL file (Peppol BIS, compliant with European standard EN 16931) across the Peppol network.
You never have to read or edit XML code yourself. Modern invoicing software builds the structured UBL file automatically from your quote, work order or progress statement and delivers it straight into your client's accounting system. What does need attention is your operational setup — because bad customer data or unclear correction rules still stall payments.
The five operational steps to keep Peppol B2B e-invoicing running cleanly across quotes, sites and accounting.
Confirm which invoices fall under the Belgian Peppol rule
Start from the client and transaction type rather than your company size. Even a sole trader working mainly for homeowners still has Peppol obligations on the purchasing side.
| Transaction type | Peppol required? | Operational note |
|---|---|---|
| Belgian contractor invoicing a Belgian business (B2B) | Yes | Mandatory since 1 January 2026; emailed PDF alone is invalid |
| Subcontractor billing a main contractor (B2B) | Yes | Include reverse-charge co-contractor VAT wording inside the UBL |
| Belgian business invoicing a Belgian public body (B2G) | Yes | Already mandatory via Peppol / Mercurius |
| Contractor invoicing a private homeowner (B2C) | No | Outgoing B2C invoices stay PDF/paper, though structured copies are allowed |
| B2C contractor buying from Belgian suppliers | Receive only | Must be registered on Peppol to receive supplier UBL invoices |
Narrow statutory exemptions exist (for instance, certain VAT-exempt activities under Article 44 of the VAT Code or specific bankruptcies). Never assume an exemption applies because you invoice infrequently. Verify unusual cases against the official Belgian e-invoicing scope guidance or with your accountant.
For deeper background on the legal framework and formats, see our overview of mandatory Peppol in Belgium and how UBL invoices work.
Step 1: activate both sending and receiving
Check that your software covers both halves of the Peppol exchange:
- Outbound sales invoices: Look up the customer's Belgian enterprise number (KBO/BCE) in the Peppol directory, generate the Peppol BIS UBL file and transmit it with an embedded visual PDF copy.
- Inbound supplier invoices: Register your own KBO/BCE number with a single Peppol Access Point so invoices from timber merchants, electrical wholesalers and subcontractors land directly in your purchase inbox.
Avoid registering the same enterprise number on two competing Peppol Access Points at once, as that causes routing conflicts. Agree with your accountant who owns the Peppol receiving registration and how invoices flow into the bookkeeping package — automatic sync, scheduled export or direct workspace access — so nothing gets booked twice.
Step 2: clean your KBO, VAT and project master data
Peppol rejects or misroutes invoices when master data is sloppy. Before sending your next batch, audit three sets of fields:
- Your own company profile: Official legal name, enterprise number (
0xxx.xxx.xxx), VAT number (BE0xxx.xxx.xxx), registered address and IBAN. - Regular business customers: Merge duplicate records, replace outdated addresses and confirm each customer's active KBO/BCE number.
- Site and procurement references: Record the client's purchase order number, site code or progress-claim reference on the project file so it flows into the structured header fields. Many larger Belgian main contractors reject Peppol invoices automatically if the PO reference is missing.
Whenever a sending check flags bad customer data, fix the master customer record immediately rather than patching only that one invoice.
Step 3: separate technical checks from VAT and site checks
Passing technical Peppol schema validation only means the XML syntax is well-formed. It does not verify that your VAT rate or invoiced quantities are right. Keep a two-step check before hitting send:
- Site or project review: Confirm executed quantities, approved change order tickets or signed progress billing lines.
- Administrative review: Verify whether the invoice requires co-contractor reverse-charge VAT, 21% standard VAT, or specific contractual attachments (such as a signed delivery note or measurement sheet embedded inside the UBL package).
Also keep an eye on your quarterly VAT reporting calendar: under Belgium's 2025 VAT chain reform, quarterly returns are due by the 25th of the month following the quarter, making timely Peppol booking of both sales and purchase invoices much easier to keep on schedule.
Step 4: test one real outbound and one inbound invoice
Before rolling out across every active site, run a full dry run with a cooperative business customer and your accountant:
- Build a real invoice directly from an approved quote or work order, send it over Peppol and check the transmission confirmation.
- Ask the customer to confirm the invoice arrived cleanly in their accounting software with lines, VAT code and attachments intact.
- Have a supplier send one live purchase invoice to your Peppol ID, match it to the right project cost line and verify your accountant sees the UBL file and visual PDF.
Track delivery statuses every week after go-live. A "delivered" Peppol status only proves the file reached the recipient's Access Point — it does not mean the site manager or accounts payable team approved the amount for payment.
Step 5: handle errors and technical fallbacks cleanly
Never silently overwrite or delete a Peppol invoice once issued. If a quantity, price or VAT code was wrong, issue a structured credit note referencing the original invoice number and send a corrected new invoice. Keep both documents and their Peppol statuses linked to the project file for your statutory archive.
If a Belgian business recipient genuinely cannot receive a structured invoice due to a documented technical fault, Belgian transition guidance allows sending a temporary alternative (such as a PDF) so invoicing is not blocked, while the recipient remains responsible for fixing its Peppol reception. Log the failed lookup or error message and switch back to Peppol once resolved.
Connect Peppol directly to quotes and site records
When quotes, site records, advances and progress claims sit in the same construction software, Peppol stops being a separate portal. Enfin links quote-to-invoice workflows directly to Peppol sending and receiving, while pricing stays straightforward for small and growing Belgian contracting teams.
Official Belgian sources
- Belgian authorities: structured B2B e-invoices mandatory since 2026
- Belgian authorities: who must use e-invoicing
- Belgian authorities: what is an electronic invoice
- Belgian authorities: VAT measures effective from 1 January 2026
General operational information for Belgian businesses. Confirm sector-specific VAT rules or exemptions with your accountant.
Streamlined invoicing for construction contractors and their accountants
Practical guidance on streamlined invoicing for construction contractors and their accountants for Belgian construction SMEs, with a clear workflow, useful checks.
Common Invoicing Mistakes Contractors Should Avoid
Practical guidance for Belgian construction SMEs to prevent costly invoicing errors, with checklists and a structured workflow.
Mandatory Peppol e-invoicing in Belgium (2026): scope, rules and exceptions
Belgium's B2B Peppol e-invoicing mandate has been live since 1 January 2026. Check who is in scope, which exceptions apply and how contractors stay compliant.