Belgium E-Invoicing 2026: What the B2B Mandate Means for Your Pipeline

Since January 1, 2026, every VAT-registered business in Belgium must send and receive structured electronic invoices for domestic B2B transactions. PDF invoices via email are no longer valid. The format is Peppol BIS Billing 3.0 — a UBL 2.1-based structured XML standard compliant with EN 16931.

There's a three-month grace period running until March 31, 2026. After that, penalties start at €1,500 per offence.

If you're an ERP vendor with Belgian customers, this affects your export pipeline directly.

What Changed on January 1

Belgium joined the growing list of EU member states mandating structured e-invoicing for B2B. The rules are straightforward:

Every domestic B2B invoice between Belgian VAT-registered businesses must be a structured electronic invoice. "Structured" means machine-readable XML — not a PDF, not a scan, not an email attachment with a PDF. The government's preferred channel is the Peppol network, using the Peppol BIS Billing 3.0 format.

Alternative transmission methods are allowed only if both parties explicitly agree and the invoice still complies with the EN 16931 standard. But there's a catch: every Belgian business must be reachable via Peppol regardless of whatever alternative arrangements they make for specific trading partners.

The practical result: if your ERP generates invoices for Belgian companies, those invoices need to be valid Peppol BIS 3.0 XML. No exceptions.

Scope and Exemptions

The mandate applies to all domestic B2B transactions between Belgian VAT-registered entities. "Domestic" is the key word.

In Scope

All domestic B2B transactions between Belgian VAT-registered businesses
Foreign suppliers invoicing Belgian buyers for VAT-taxable supplies in Belgium
Credit notes and corrective invoices (same structured format requirements)

Out of Scope

B2C transactions (invoices to consumers)
Intra-community supplies of goods (cross-border within EU)
Services taxed in another EU member state under reverse charge
Supplies exempt under Article 44 of the Belgian VAT Code

A common mistake: assuming cross-border invoices to Belgian buyers are exempt. They're not — if the supply is taxable in Belgium, the mandate applies.

The Grace Period Ends March 31

The FPS Finance confirmed a three-month tolerance period from January 1 through March 31, 2026. During this window, no sanctions will be imposed for non-compliance with the e-invoicing obligation.

The grace period is not automatic. You must demonstrate "reasonable and timely steps" toward compliance. A company that made no effort to implement Peppol by March 31 cannot claim tolerance.

After April 1, penalties apply:

| Offence | Fine | |---------|------| | First violation | €1,500 | | Second violation | €3,000 | | Third and subsequent | €5,000 each |

Violations are counted per three-month period. Miss compliance in Q2 2026 — that's your first offence. Miss it again in Q3 — second offence. The fines escalate quickly for businesses that delay.

VAT Rounding Changes

Belgium introduced a new rounding rule that applies exclusively to structured e-invoices. This is technical, but it matters for your validation pipeline.

Old rule: rounding was allowed at the line level (per invoice line). New rule: rounding is only permitted on the total amount per VAT rate. Line-by-line rounding is no longer valid.

This is a common source of validation failures. If your ERP calculates VAT per line and rounds at the line level, the totals won't match what the Belgian rules expect. The errors you'll see:

BR-CO-10 — Sum of line net amounts doesn't match the invoice total
BR-DEC-* rules — Decimal precision violations on amounts

ERP vendors: check how your system handles VAT calculation and rounding. This is the #1 cause of Belgian invoice rejections we're seeing.

Technical Requirements

Format

Peppol BIS Billing 3.0, which is UBL 2.1 under the hood. Your invoices must pass four layers of validation:

Layer 1

XML Schema

Well-formed UBL 2.1 XML with correct namespaces and structure

Layer 2

EN 16931 Business Rules

BR-01 through BR-65 — the European base rules for e-invoice content

Layer 3

Peppol Rules

PEPPOL-EN16931-R001 through R080 — additional rules for Peppol network delivery

Layer 4

Belgian Rules

Belgium-specific validations including KBO/BCE number format and VAT rounding requirements

Required Identifiers

Belgian businesses are identified by their KBO/BCE enterprise number (Kruispuntbank van Ondernemingen / Banque-Carrefour des Entreprises). In Peppol, this maps to scheme ID 0208.

<cbc:EndpointID schemeID="0208">0123456789</cbc:EndpointID>

If you're building Peppol integration for Belgian customers, the KBO/BCE number is the primary identifier. Not the VAT number — the enterprise number.

Related glossary entries: KBO/BCE enterprise number, Scheme ID, Endpoint ID.

Peppol Registration

Every business needs a Peppol ID, registered through a certified Peppol Access Point. The Access Point handles the actual message transport on the Peppol network.

For ERP vendors, the question is whether you operate your own Access Point or route through a provider. Most mid-market ERPs use a third-party Access Point and focus their integration on generating valid invoices.

That's where pre-submission validation matters. An invoice that gets rejected at the Access Point or by the receiver's system creates a support ticket, a payment delay, and a frustrated customer.

Common Belgian Validation Errors

Based on what we see in production pipelines:

BR-CO-10 — VAT rounding mismatch (see rounding section above)
PEPPOL-EN16931-R010 — Missing or invalid buyer reference
BR-CO-09 — VAT identifier doesn't start with country code prefix
Scheme ID 0208 formatting — KBO/BCE number with incorrect length or format
BR-16 — Missing order reference when required

Most of these are structural issues — fixable before submission if you validate early enough in the pipeline.

For ERP Vendors

Your Belgian customers are asking one question: "Can your software send compliant Peppol invoices?"

If the answer involves manual exports, PDF conversions, or "we're working on it" — you're losing deals. The mandate is live.

Integration Approaches

Option 1: Native Peppol support. Your ERP generates Peppol BIS 3.0 XML natively and connects to an Access Point. Full control, significant development investment.

Option 2: Middleware / compliance gateway. Your ERP generates structured data, a middleware layer converts to Peppol BIS 3.0 and handles submission. Less ERP development, dependency on the gateway.

Option 3: Pre-submission validation API. Your existing export is close but not always compliant. A compliance safety layer validates each invoice, safely remediates structural issues, and revalidates before release. No changes to your ERP export template — the compliance gate catches what slips through.

For ERP-specific implementation guidance:

E-Reporting: What's Coming in 2028

Belgium has also confirmed mandatory near real-time e-Reporting starting January 1, 2028. This is separate from e-invoicing — it requires businesses to report transaction data to the tax authority in near real-time.

The 2026 e-invoicing mandate is the foundation. Getting Peppol infrastructure right now means you're architecturally prepared for the e-Reporting layer that follows. Businesses that rushed to comply with e-invoicing at the last minute will face the same scramble again in 2028.

The smart move: treat 2026 compliance as building infrastructure, not checking a box.

Compliance Checklist

This checklist assumes you're an ERP vendor or technical team implementing Belgian e-invoicing compliance. For a general business overview, see our Belgium country page.

Register a Peppol ID for your organization via a certified Access Point (or ensure your customers have one)
Update your ERP export to generate Peppol BIS Billing 3.0 (UBL 2.1) XML
Fix VAT rounding logic — move from line-level to VAT-rate-level rounding
Map Belgian identifiers — use KBO/BCE (scheme 0208) as the primary business identifier
Validate before submission — run every invoice through schema + EN 16931 + Peppol + Belgian rules. Test with Invoice Navigator →
Handle credit notes — same format requirements apply to credit notes and corrective invoices
Inform your trading partners — both sender and receiver need Peppol capability
Monitor rejections — track Access Point rejections and fix root causes in your export templates

FAQ

Is the Belgium e-invoicing mandate already in effect?

Yes. The mandate took effect January 1, 2026. There's a grace period until March 31, 2026 — but only for businesses that can demonstrate they took reasonable steps to comply. After April 1, penalties apply.

What format does Belgium require?

Peppol BIS Billing 3.0, which is based on UBL 2.1 and compliant with the EN 16931 European standard. Alternative formats are allowed if both parties agree, but every business must still be reachable via Peppol.

Do I need to register for Peppol?

Yes. Every Belgian VAT-registered business must be reachable on the Peppol network. Registration happens through a certified Peppol Access Point provider.

What are the penalties for non-compliance?

€1,500 for a first offence, €3,000 for a second, €5,000 for each subsequent violation. Offences are counted in three-month periods.

Does this apply to cross-border invoices?

The mandate covers domestic B2B transactions. However, if a foreign supplier makes a VAT-taxable supply in Belgium, that transaction is in scope. Intra-community supplies and reverse-charge services taxed in other EU states are exempt.

What about B2C invoices?

B2C transactions are out of scope. The mandate applies only to B2B transactions between VAT-registered businesses.

How does Invoice Navigator help with Belgian compliance?

Invoice Navigator validates your invoices against all four rule layers (XML schema, EN 16931, Peppol, Belgian-specific rules), safely remediates structural issues without touching financial fields, revalidates via KoSIT, and generates an evidence pack proving compliance. Try the free validator →