Belgium E-Invoicing Requirements 2026: Peppol Compliance Guide

Belgium mandated B2B e-invoicing for all domestic transactions between VAT-registered businesses from January 1, 2026. Every invoice exchanged between Belgian VAT-registered entities must now comply with Peppol BIS Billing 3.0 (UBL 2.1) or Factur-X at EN 16931 profile. Businesses that fail to comply face penalties starting at EUR 1,500 per offense, with escalation to 60–100% of the VAT amount due for repeated or deliberate non-compliance.

The legal basis was published on February 6, 2024, modifying the Belgian VAT code to require structured electronic invoicing for all domestic B2B transactions. A three-month tolerance period gave businesses until March 2026 to finalize their setups. That grace window has closed, and the Belgian Federal Public Service Finance is now actively enforcing penalties.

The scope is precise: the mandate covers domestic B2B transactions only. If both parties are VAT-registered in Belgium, the invoice must be a structured electronic document transmitted through the Peppol network or as a compliant Factur-X file. Cross-border invoices, whether intra-EU or extra-EU, remain outside the current mandate. Plain PDFs without embedded structured XML no longer qualify as legally valid invoices for covered transactions.

The scale of this shift is substantial. Approximately 1 billion invoices are exchanged annually in Belgium, and according to the European Commission's eInvoicing country profile for Belgium, the Belgian federal government estimated EUR 3.37 billion per year in expected economic benefits from nationwide e-invoicing adoption. Those savings come from eliminated manual processing, faster payment cycles, and reduced error rates across the entire invoicing chain.

Yet most guides to Belgium's e-invoicing requirements stop at the legal checklist. For Belgian finance teams, the harder questions are operational. How does receiving structured Peppol XML instead of PDF invoices change your accounts payable extraction workflow? How do you handle the hybrid environment where domestic invoices arrive as Peppol messages but cross-border suppliers still send PDFs? And how can you use the 120% tax deduction for e-invoicing software investments to fund the compliance tooling you need? This guide covers all of it.

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. This is the format transmitted across the Peppol network, and it is the default choice for businesses without pre-existing electronic invoicing infrastructure. When regulators and software vendors refer to "Belgium Peppol e-invoicing," they mean invoices issued and received in this format.

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.

How Peppol XML Transforms AP Data Extraction

The shift to mandatory Peppol e-invoicing changes something fundamental about how invoice data enters your accounting system. Before January 2026, every domestic B2B invoice arrived as a PDF or paper document. Extracting structured data from those formats required OCR, manual keying, or AI-based extraction tools that interpreted visual layouts to identify fields. With Peppol BIS 3.0, compliant domestic invoices arrive as structured UBL 2.1 XML delivered through the Peppol network via your Access Point. The data is already machine-readable.

This is not a minor workflow tweak. Invoice number, issue date, due date, line items, VAT breakdowns, payment references, supplier details, and buyer details all arrive as tagged semantic elements. Your systems can read them programmatically without any interpretation step. For these invoices, OCR becomes entirely unnecessary. There is no image to scan, no field recognition to configure, no extraction confidence score to evaluate. The data simply exists in defined, predictable fields.

UBL 2.1 Field Mapping for Accounting Systems

Understanding which UBL elements carry which data helps AP teams configure their import processes and verify that nothing gets lost in translation. The key mappings between Peppol invoice XML and your accounting system fields are:

cbc:ID maps to your invoice number field
cbc:IssueDate maps to invoice date; cbc:DueDate maps to payment due date
cac:AccountingSupplierParty contains vendor name, address, and VAT number
cac:AccountingCustomerParty contains your company's details as the buyer
cac:InvoiceLine contains individual line items with descriptions, quantities, unit prices, and item-level tax classifications
cac:TaxTotal and its nested cac:TaxSubtotal elements break down VAT amounts by rate category
cac:LegalMonetaryTotal provides the net amount, tax-exclusive total, tax-inclusive total, and payable amount
cac:PaymentMeans carries payment method, bank account (IBAN), and payment reference

These elements follow a standardized structure across every Peppol invoice. Unlike PDF extraction, where field positions vary by supplier template, XML parsing uses the same element paths regardless of who sent the invoice. The most common mapping issues Belgian businesses encounter involve payment reference fields not aligning automatically with the OGM-VCS format and VAT rate categories requiring manual configuration to match Belgian VAT codes in the receiving ERP.

What Actually Changes in Your Daily Workflow

The extraction step changes dramatically, but the surrounding AP workflow does not disappear. You still need to validate that invoice details match purchase orders or contracts. You still need to route invoices through approval chains. You still need to post them to the correct general ledger accounts and cost centers. What changes is that the data feeding those downstream steps arrives clean and structured instead of requiring cleanup after extraction.

One practical pain point that catches AP teams off guard: some Peppol senders transmit only the XML without an attached PDF representation. This means your staff cannot visually review the invoice in a familiar format unless your system can render the XML into a human-readable view. If your team relies on seeing a formatted invoice before approving it, you need software that can display Peppol XML as a readable document.

ERP Compatibility Gaps

Not every Belgian accounting package handles Peppol XML natively yet. Major platforms like WinBooks, BOB50, Sage BOB, and Exact Online have released updates to accept Peppol imports, but businesses running older software versions may face a gap. The invoice arrives at your Access Point in structured XML, but your ERP cannot import it without a manual conversion step or a middleware connector. Before assuming your system is ready, verify that your specific version supports UBL 2.1 invoice import and that the field mapping aligns with your chart of accounts.

This creates a dual reality for AP teams: structured Peppol XML covers domestic Belgian B2B invoices, but cross-border invoices from EU and international suppliers, invoices from exempt entities, and legacy PDFs still arrive as unstructured documents. Your extraction capabilities do not become obsolete. They shift to handling the non-Peppol portion of your invoice volume, and platforms using AI extraction engines, like Invoice Data Extraction, remain essential for the PDF and image-based invoices that continue flowing in from outside the Peppol network.

Managing the Dual Peppol and PDF Invoice Workflow

The compliance shift is clear, but the operational challenge is where most Belgian businesses struggle. Domestic invoices now arrive as structured Peppol XML, while cross-border invoices (intra-EU, extra-EU), B2C transactions, and invoices from exempted sectors continue to arrive as PDF via email or supplier portals.

Running both processing tracks simultaneously doubles your intake complexity. Finance teams must identify the format on arrival, route each invoice to the correct processing method, normalize the output into a consistent data structure, and consolidate everything into a single approval and posting workflow. Without deliberate process design, this leads to duplicated effort, inconsistent data quality between domestic and international invoices, and bottlenecks at the consolidation step.

Avoiding Duplicate Peppol Registrations

If your business is registered under multiple Peppol identifiers (different CBE number formats, registrations through multiple access point providers), incoming invoices may be delivered to the wrong endpoint or received twice. Audit your Peppol registrations through your Access Point provider, consolidate to a single canonical identifier, and deregister any duplicates. This is a one-time cleanup task, but skipping it creates persistent data quality issues that compound over time.

Converging Both Tracks Into One Workflow

The most effective approach to the dual-format environment is to eliminate the branching logic entirely. Rather than maintaining separate processing pipelines for Peppol XML and PDF, businesses should target a single intake workflow where both formats produce identical structured output.

For the PDF side of this equation, AI-powered extraction tools close the gap. A platform that lets you automate invoice data extraction across document formats handles the cross-border PDF invoices that Peppol does not cover, processing mixed batches of supplier PDFs and scanned documents into structured Excel, CSV, or JSON output with the same field-level accuracy you get from parsed Peppol XML. The result is one consolidated data stream feeding your accounting system, regardless of whether the source was a Belgian domestic e-invoice or a PDF from an Italian supplier.

This matters most for businesses processing invoices from dozens of international suppliers. A Belgian importer might receive invoices in Dutch, French, German, and English across entirely different PDF layouts. The extraction challenge is format diversity, not volume, and AI-based tools that interpret document context across languages and structures handle the long tail of non-standard invoices that would otherwise require manual data entry.

The EU's VAT in the Digital Age (ViDA) initiative will eventually extend structured e-invoicing to cross-border B2B transactions (expected around 2030), but the hybrid processing environment will persist for years as extra-EU invoices and legacy formats remain PDF-based. Investing in tools and workflows that handle both structured and unstructured documents is not a temporary bridge; it is the operational foundation for the foreseeable future of AP processing.

Claiming the 120% Tax Deduction for E-Invoicing Software

Belgium's e-invoicing mandate comes with a financial incentive that most businesses overlook. The federal government offers a 120% tax deduction on investments in e-invoicing software, meaning the deductible amount on your corporate tax return actually exceeds what you spent. A EUR 10,000 investment in qualifying software generates a EUR 12,000 deduction, effectively subsidizing your compliance effort.

Despite appearing in nearly every summary of the 2026 mandate, this incentive rarely receives the detailed treatment it deserves. The result is that many SMEs either assume they do not qualify or fail to claim the full amount they are entitled to.

How the 120% Deduction Mechanism Works

The enhanced deduction functions as a super-deduction under Belgian corporate tax law. Rather than deducting 100% of the cost of qualifying digital investments from your taxable base, you deduct 120%. The additional 20% reduces your taxable income beyond the actual expense, lowering your effective tax liability.

For a company subject to the standard 25% corporate tax rate, a EUR 10,000 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

For businesses investing EUR 50,000 or more in their e-invoicing infrastructure, the additional savings become material.

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

This breadth matters for accounts payable teams. If you invest in software that extracts data from incoming Peppol XML invoices and maps it to your general ledger, that investment qualifies. Tools like Invoice Data Extraction, which convert financial documents into structured Excel, CSV, or JSON output, fall within the scope of eligible software when used as part of an e-invoicing compliance workflow. With a permanent free tier covering up to 50 pages per month and pay-as-you-go pricing above that threshold, such tools give SMEs a low-cost entry point where qualified costs remain eligible for the enhanced deduction.

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

A common question is whether the deduction applies only to outright software purchases or also to recurring subscriptions. 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.

Sunset Considerations

The 120% super-deduction for digital investments was introduced as a temporary fiscal incentive to accelerate adoption of the e-invoicing mandate. Belgian tax incentives of this nature are typically reviewed and renewed on a periodic basis. Businesses planning their compliance investments should confirm the current status of the incentive for their specific tax year, as the enhancement could be modified or allowed to expire in future legislative cycles. Acting sooner rather than later ensures you capture the full benefit while the rate remains at 120%.

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

The 2026 mandate covers how invoices are exchanged between businesses. The next phase, Belgium e-reporting 2028, adds a fundamentally different layer: automatic reporting of invoice data to the Belgian tax authority as part of every Peppol transaction.

Understanding the distinction is critical. E-invoicing governs the format and delivery of invoices between trading partners. E-reporting governs the visibility the government has into those transactions. With e-reporting, the tax authority receives structured invoice data in near real-time, without requiring businesses to compile and submit it separately.

From 4 Corners to 5

Today's Peppol infrastructure follows a 4-corner model: the sender transmits an invoice through their Access Point, which routes it to the receiver's Access Point, which delivers it to the receiver. The government is not part of this chain.

The 5-corner model introduces the tax authority as an additional node. When an invoice passes through the Peppol network, a copy of the transaction data is automatically routed to the Belgian government. This creates a system of continuous transaction controls where the tax authority maintains a real-time view of B2B commercial activity without requiring manual filings for those transactions.

What This Means for VAT Compliance

The most significant practical consequence: once e-reporting is fully operational, businesses will no longer need to file separate VAT returns for B2B transactions that are already captured through the Peppol reporting layer. The tax authority will already have the invoice data it needs. For finance teams that currently spend considerable effort reconciling and filing periodic VAT returns, this represents a genuine reduction in administrative burden.

This does not happen overnight. The transition will be gradual, and details around implementation timelines and technical specifications are still being finalized. But the direction is clear: manual VAT reporting for domestic B2B transactions is being replaced by automated data flows.

Belgium's Place in the EU's ViDA Directive

Belgium's 2028 e-reporting timeline aligns with the broader EU VAT in the Digital Age (ViDA) directive, which aims to establish real-time digital reporting across all member states. ViDA is expected to mandate structured e-invoicing for cross-border transactions by approximately 2030, gradually eliminating the need for PDF invoices in intra-EU trade.

For Belgian businesses, this reinforces the trajectory: structured invoicing will gradually expand beyond domestic borders.

Why Your 2026 Investment Carries Forward

Businesses that have onboarded to Peppol for the 2026 mandate are already positioned for what comes next. The 5-corner model builds on the same Peppol infrastructure, the same Access Points, and the same invoice formats. There is no parallel system to adopt.

The one preparation step worth taking now: confirm with your Peppol Access Point provider that they will support the 5-corner model when Belgium activates e-reporting. Providers that are actively involved in the Peppol community and Belgian regulatory working groups are more likely to offer a smooth transition. Asking this question during your current vendor evaluation or renewal saves you from a second migration later.