Belgium E-Invoicing Requirements 2026: Peppol Compliance Guide

Belgium's B2B e-invoicing mandate has applied to domestic transactions between VAT-registered businesses since January 1, 2026. Covered invoices must now use Peppol BIS Billing 3.0 (UBL 2.1) or Factur-X at EN 16931 profile. Non-compliance starts at EUR 1,500 per offense and can escalate to 60-100% of the VAT amount due for repeated or deliberate violations.

The mandate covers domestic B2B transactions only. Cross-border invoices, B2C invoices, and transactions with non-VAT-registered entities remain outside the current scope. The European Commission's verified 2025 Belgium eInvoicing country sheet says Belgium's Peppol-based model applies to roughly 1.2 million entities, with Peppol BIS Billing 3.0 as the mandatory EN 16931 support path.

For Belgian finance teams, compliance is only the starting point. The practical work is connecting Peppol XML to accounting systems, keeping PDF workflows for cross-border and exempt invoices, and using the 120% deduction where the software investment qualifies.

Required Formats: Peppol BIS 3.0, Factur-X, and Existing EDI

Belgium's mandate does not require a single proprietary format. It requires compliance with EN 16931, the European standard for semantic data models in electronic invoicing. In practice, three paths satisfy this requirement, each with specific conditions.

Peppol BIS Billing 3.0 is the primary format. Built on UBL 2.1, it defines a structured XML schema that carries every field a Belgian B2B invoice needs: supplier and buyer identification, line items, VAT breakdowns, payment terms, and routing metadata. For most Belgian businesses, Peppol BIS Billing 3.0 is the default route for issuing and receiving compliant structured invoices.

To send or receive Peppol BIS 3.0 invoices, your business connects to the Peppol network through a certified Peppol Access Point. The access point provider handles the technical exchange: formatting, validation, encryption, and delivery. You register as a Peppol participant through your chosen provider, which assigns your business a Peppol identifier linked to your VAT number. Your accounting or ERP system then transmits invoice data to the access point, which routes it to the recipient's access point. You do not need to manage the network infrastructure yourself.

Factur-X qualifies as a compliant alternative, but only under strict conditions. Factur-X is a hybrid format that embeds structured XML data inside a PDF/A-3 document. It comes in multiple profiles ranging from Minimum to Extended. For the Belgian mandate, only the EN 16931 profile satisfies compliance. This is the most complete profile, carrying the full set of structured fields required by the European standard. A Factur-X invoice using the Basic or Minimum profile does not meet the mandate, because those profiles omit fields that EN 16931 requires. If your invoicing software generates Factur-X, verify which profile it produces before assuming compliance.

Existing EDI connections receive a grandfathering provision. Businesses that already exchange invoices electronically through established EDI channels (EDIFACT, for example) can continue doing so, provided two conditions are met: both trading partners explicitly agree to maintain the EDI arrangement, and the invoices carry data that complies with EN 16931 semantics. This is not a blanket exemption. It is a practical allowance for large enterprises with deeply integrated supply chain systems where migrating to Peppol would be disruptive without clear benefit. If you onboard a new trading partner, the default expectation is Peppol BIS 3.0.

Two technical details affect format compliance regardless of which path you choose. First, Belgian e-invoices typically include structured payment references following Belgium's OGM-VCS structured payment reference system. The Belgium Peppol BIS 3.0 format accommodates these references in dedicated fields, and your invoicing system should populate them correctly to ensure recipients can automate payment matching. Second, VAT rounding must occur at the total per VAT rate, not per invoice line. Rounding line-by-line and then summing produces different totals than summing exact amounts and rounding once. The mandate enforces the latter. This is a configuration detail that accounting systems often handle differently by default, and getting it wrong will cause validation failures at the access point level.

Who Is Exempt and What Are the Penalties?

Not every Belgian business faces the mandate on day one. Several categories remain outside the scope of mandatory B2B e-invoicing, though the window of exemption is narrower than many assume.

Exempt sectors include businesses whose activities fall under specific VAT exemptions: medical and paramedical services, social and cultural institutions, and educational organizations. These exemptions align with Article 44 of the Belgian VAT Code and apply regardless of business size.

Businesses operating under the flat-rate VAT scheme (forfaitaire regeling / régime forfaitaire) are also currently exempt. However, this exemption has an expiration date. The flat-rate scheme itself is being phased out by 2028, meaning businesses relying on this carve-out will eventually need to comply with structured e-invoicing requirements. Treating this as a permanent exemption is a planning mistake.

Entities in bankruptcy proceedings round out the exempt categories.

Beyond exemptions, certain transaction types fall entirely outside the mandate's scope:

B2C transactions: invoices to private consumers are not covered
Cross-border transactions: both intra-EU and extra-EU sales remain outside the Belgian mandate (though separate EU-level e-invoicing rules are advancing)
Transactions with non-VAT-registered entities: no structured e-invoice obligation applies

For all of these, PDF invoices remain perfectly acceptable.

Penalty Structure

The consequences of non-compliance are specific and escalating. A first offense carries a fine of EUR 1,500 per invoice. Repeat violations increase the penalty, with the maximum reaching 60% to 100% of the VAT amount due on the non-compliant invoice. For high-value invoices, this penalty range can dwarf the initial flat fine, making habitual non-compliance a genuinely expensive proposition.

Credit Notes and Self-Billing: The Compliance Traps

Two edge cases catch businesses off guard more than any other aspect of the mandate.

Credit notes must match the format of the original invoice. If you issued a structured e-invoice through Peppol, the corresponding credit note must also be a structured e-invoice. Issuing a PDF credit note against a Peppol invoice is a compliance violation. Finance teams that process credit notes through a separate workflow from their invoicing system need to verify both paths support structured formats.

Self-billing arrangements require explicit Peppol registration on the supplier side. In a self-billing setup, the buyer issues the invoice on behalf of the supplier. Under the mandate, the supplier must be registered for self-billing on the Peppol network. Existing self-billing agreements that predate January 2026 do not automatically carry over. If your supplier has not completed a separate Peppol registration step for self-billing, the arrangement is non-compliant regardless of how long it has been in place. The supplier's Access Point provider can register them for the Peppol Self-Billing document type, which is a distinct registration from standard invoice reception.

CBE Number and Peppol Identifier Pitfalls

Belgian businesses are identified on the Peppol network using their CBE number (Crossroads Bank for Enterprises) under the 0208 identifier scheme. In practice, this creates two common problems.

First, registration confusion. Some businesses register through multiple access points or service providers without realizing each registration creates a separate Peppol endpoint. When a business holds duplicate Peppol identifiers, incoming invoices may be delivered to the wrong endpoint or received twice, creating reconciliation headaches in accounts payable.

Second, businesses with multiple VAT units or branches sometimes assume each unit needs its own Peppol identifier. The correct approach depends on your organizational structure, but getting it wrong means invoices arrive at endpoints your AP team does not monitor.

One final detail that catches multinational teams off guard: Belgian invoice language rules do not disappear just because the invoice is now a structured XML file. The language requirements tied to the registered office location of the buyer still apply to the content fields within the e-invoice. For a full breakdown of these obligations, see the Belgian invoice language compliance rules.

What Changes in AP: Peppol XML, PDFs, and ERP Imports

Peppol changes how domestic Belgian invoice data enters the AP workflow. Covered invoices arrive as structured UBL 2.1 XML through an Access Point, so invoice numbers, dates, line items, VAT breakdowns, payment references, supplier details, and buyer details are already tagged in machine-readable fields. For those invoices, OCR is no longer the extraction step.

The main UBL mappings AP teams need to verify are:

cbc:ID for invoice number
cbc:IssueDate and cbc:DueDate for invoice and payment dates
cac:AccountingSupplierParty and cac:AccountingCustomerParty for supplier and buyer details
cac:InvoiceLine for line descriptions, quantities, unit prices, and item-level tax classifications
cac:TaxTotal and cac:TaxSubtotal for VAT amounts by rate category
cac:LegalMonetaryTotal for net amount, tax-exclusive total, tax-inclusive total, and payable amount
cac:PaymentMeans for IBAN and payment reference

The surrounding AP controls still matter. You still need to validate invoices against purchase orders or contracts, route exceptions for approval, and post costs to the right GL accounts and cost centers. The common configuration issues are Belgian payment references not aligning with OGM-VCS fields and VAT categories not mapping cleanly to Belgian VAT codes in the receiving ERP — construction AP teams in particular need to separate reverse-charge subcontractor invoices from standard 21% VAT and map them to grids 87, 56, and 59 of the VAT return, whether the invoice arrives as Peppol XML or PDF. Fleet-heavy AP teams face a related mapping problem with Belgian fuel and charge card monthly invoices that drive the 50% VAT deduction under Article 45 and rooster 59 entries for company cars.

Two operational gaps deserve early testing. First, some Peppol senders transmit XML without an attached PDF rendering, so approvers need software that can display the XML as a readable invoice. Second, not every accounting package handles Peppol imports on older versions. WinBooks users handling both Peppol XML and legacy PDFs should understand how built-in OCR and invoice scanning workflows fit beside structured Peppol data.

The mandate also creates a durable dual intake model. Domestic Belgian B2B invoices move through Peppol, while cross-border suppliers, exempt entities, and legacy portals still send PDFs. A single intake workflow should normalize both sources into the same approval and posting process. On the PDF side, platforms that automate invoice data extraction across document formats handle invoices Peppol does not cover, and teams that need to convert PDF invoices into Peppol and UBL-ready e-invoice data can use the same extraction-first workflow before validation and delivery.

Claiming the 120% Tax Deduction for E-Invoicing Software

Belgium's e-invoicing mandate includes a 120% tax deduction for qualifying e-invoicing software investments. A EUR 10,000 qualifying cost can produce a EUR 12,000 deduction, so the additional 20% reduces taxable income beyond the actual expense.

How the 120% Deduction Mechanism Works

For a company subject to the standard 25% corporate tax rate, a EUR 10,000 qualifying software investment works out as follows:

Standard deduction (100%): EUR 10,000 deducted, saving EUR 2,500 in tax
Enhanced deduction (120%): EUR 12,000 deducted, saving EUR 3,000 in tax

What Software Qualifies

The deduction is not limited to tools that create or send e-invoices. It covers the full spectrum of software involved in structured e-invoice processing:

Invoice creation and dispatch software that generates Peppol BIS 3.0 or UBL-compliant invoices
Receiving and processing platforms connected to the Peppol network via an access point
Data extraction and automation tools that convert structured e-invoice data into accounting-ready formats
ERP modules and integrations specifically acquired or upgraded to handle the Belgian e-invoicing mandate

Tools that convert Peppol XML, PDF invoices, and scanned documents into accounting-ready Excel, CSV, or JSON output may qualify when they are part of the e-invoicing compliance workflow. Keep vendor invoices and implementation records that show the link to structured invoice processing.

Eligibility Criteria for Belgian SMEs

The 120% deduction targets small and medium-sized enterprises as defined under Belgian tax law. To qualify, your company must meet at least two of the following three criteria for the relevant tax year:

Annual average workforce of no more than 50 employees
Annual turnover (excluding VAT) not exceeding EUR 9,000,000
Balance sheet total not exceeding EUR 4,500,000

Companies linked to a larger group that collectively exceed these thresholds may be excluded. Sole proprietors and freelancers operating under the personal income tax regime should verify with their accountant whether the deduction applies under their specific filing structure, as the mechanism is primarily designed for corporate taxpayers.

Subscriptions, One-Time Purchases, and Implementation Costs

Under current Belgian tax rules:

Subscription-based software (SaaS): Monthly or annual subscription fees for qualifying e-invoicing software are deductible as operating expenses, and the 120% enhancement applies to these recurring costs for each tax year they are incurred.
One-time license purchases: Capital expenditures on software licenses qualify and are typically spread over the depreciation period, with the 120% rate applying to each year's depreciation amount.
Implementation and consulting costs: Professional services directly tied to deploying e-invoicing software, such as configuration, data migration, and integration work, generally qualify when they are inseparable from the software investment itself. General IT consulting or broader digital transformation projects that are not specifically tied to e-invoicing compliance do not qualify.

How to Claim the Deduction

The enhanced deduction is claimed on your corporate tax return (form 275.1) for the tax year in which the expense was incurred or the depreciation is recorded. You will need:

Invoices from your software vendor clearly describing the e-invoicing functionality purchased
Proof of payment corresponding to the claimed amounts
Documentation linking the software to e-invoicing compliance, particularly if the tool serves multiple functions beyond structured invoice processing

Your accountant or tax advisor should record the additional 20% as a separate line item in the tax calculation, distinct from the base deduction. There is no pre-approval process or separate application; the deduction is applied directly when filing.

Confirm the incentive status for the specific tax year you are filing, because temporary digital-investment incentives can be modified or allowed to expire.

What Comes Next: Belgium's 2028 E-Reporting and the 5-Corner Model

The 2026 mandate covers invoice exchange between businesses. Belgium's planned 2028 e-reporting layer would add tax-authority reporting to the Peppol flow.

Today's Peppol infrastructure uses a 4-corner model: sender, sender Access Point, receiver Access Point, and receiver. The planned 5-corner model adds the tax authority as another participant, so structured invoice data can be reported as the transaction moves through the network.

Once e-reporting is fully operational, Belgium expects invoice data captured through Peppol to replace some separate reporting obligations, including the annual sales listing. Until that change lands, French-speaking finance teams still need to compile the annual VAT client listing from a year of sales invoices — aggregating by customer VAT number, applying the EUR 250 threshold, and filing through Intervat by 31 March. Businesses should not assume periodic VAT returns disappear until the Belgian tax authority publishes the final operating rules.

Belgium's timeline also sits within the EU's broader VAT in the Digital Age (ViDA) direction. For teams comparing neighboring markets, this overview of Dutch Peppol and NLCIUS e-invoicing rules shows how the Netherlands currently handles B2G, B2B, and B2C requirements.

The practical preparation step is simple: confirm with your Peppol Access Point provider that it plans to support Belgium's 5-corner model when e-reporting goes live.