Mandatory Einvoicing in Belgium (2026): What Businesses Must Do, Compliance, Contracts & M&A

Since 1 January 2026, mandatory eInvoicing in Belgium 2026 has required every Belgian VAT-registered business to issue and accept structured electronic invoices for domestic B2B transactions. The obligation, rooted in amendments to the Belgian VAT Code and implemented through a long-awaited Royal Decree, represents the most significant change to commercial invoicing practice in a generation. Beyond tax compliance, the mandate forces immediate updates to supply and distribution agreements, master service contracts and procurement frameworks, while creating a new layer of due-diligence risk for M&A transactions and transfers of undertakings. This guide provides the practical compliance roadmap, model contract clauses and transaction-focused checklists that general counsels, CFOs and deal teams need right now.

• Immediate action 1: Confirm your Peppol Access Point registration and test structured invoice exchange with your top ten trading partners.
• Immediate action 2: Review and amend all active commercial contracts to include an eInvoicing clause that allocates format obligations, costs and breach remedies.
• Immediate action 3: For any live or planned M&A transaction, add eInvoicing compliance to your due-diligence checklist alongside VAT and ERP verification items.

Legal Background: The Law, Royal Decree and Code of Economic Law Amendments (2026)

Belgium’s mandatory B2B eInvoicing obligation was enacted through the Programme Law of 22 December 2023, which amended Article 53, §2 of the Belgian VAT Code. That legislative change established the principle that taxable persons established in Belgium must issue structured electronic invoices for domestic B2B supplies of goods and services. The implementing Royal Decree, published in the Moniteur Belge (Belgian Official Gazette), set out the detailed technical specifications, transitional arrangements and the tolerance period that governs early enforcement. Industry observers note that together these instruments also intersect with relevant provisions of the Code of Economic Law governing electronic commercial communications and document-retention requirements.

The practical effect is that a PDF attached to an email no longer qualifies as a compliant invoice for domestic B2B purposes. Only a structured electronic invoice, machine-readable and transmitted through an approved channel, satisfies the mandate. Businesses that previously relied on paper, PDF or unstructured electronic formats must migrate to Peppol-based exchange or an equivalent compliant infrastructure.

Key Legislative Dates

Who Is Covered and Who Is Excluded, Scope of B2B eInvoicing Belgium

The mandatory eInvoicing obligation applies to all taxable persons established in Belgium and registered for Belgian VAT who carry out domestic B2B supplies of goods or services. This covers the vast majority of Belgian companies, partnerships, sole traders operating through a VAT-registered enterprise, and Belgian permanent establishments of foreign entities.

Understanding who falls inside and outside the mandate is critical for both eInvoicing compliance 2026 planning and for contract counterparty assessments. The scope can be summarised as follows:

• Covered: Any Belgian VAT-registered taxable person issuing an invoice for a domestic B2B transaction (i.e., both supplier and customer are established in Belgium).
• Receiving obligation: The mandate is bilateral, businesses must be able to both issue and receive structured eInvoices.
• B2C transactions: Not covered by the B2B mandate. Consumer-facing invoices remain outside scope, though businesses should monitor future EU developments under the ViDA (VAT in the Digital Age) initiative.

Exclusions and Edge Cases

For businesses with complex group structures, the key test is whether both parties to the transaction are established in Belgium and VAT-registered. Intercompany invoices between a Belgian parent and its Belgian subsidiary fall squarely within scope, whereas invoices to a sister company established solely in another EU Member State do not, under the current domestic mandate.

Technical and Procedural Requirements: eInvoice Format Belgium, Peppol and Standards

Belgium’s mandate requires that all in-scope invoices be issued as structured electronic invoices conforming to the European standard EN 16931. In practice, this means a machine-readable XML document, not a PDF, scanned image or unstructured email attachment. The Peppol network has been designated as the default interoperability framework for transmitting these invoices.

• Format: Invoices must comply with EN 16931 and use either UBL 2.1 (Universal Business Language) or CII (Cross Industry Invoice) syntax, the two syntaxes recognised under the European standard.
• Transport: The Peppol eDelivery network, via a certified Peppol Access Point, is the primary transport mechanism. Businesses connect to Peppol either through their ERP vendor, a dedicated service provider or a government-approved platform.
• Identification: Each business must be registered in the Peppol directory with its Belgian enterprise number (KBO/BCE number) as the participant identifier.

Peppol vs Other Formats

While Peppol is the designated framework, the Royal Decree allows for the use of other structured electronic formats provided they comply with EN 16931 and both trading partners agree. However, early indications suggest that the overwhelming majority of Belgian businesses are adopting Peppol as the standard channel, driven by its existing use in government procurement, the availability of certified Access Points and interoperability with other EU Member States.

Businesses that previously used EDI (Electronic Data Interchange) connections with major trading partners should assess whether their existing EDI formats satisfy EN 16931 requirements. In many cases, legacy EDI setups will require mapping or conversion layers to achieve compliance.

Key Invoice Data Elements

Finance and IT teams should conduct a field-by-field mapping exercise between their current ERP invoice template and the EN 16931 data model. Gaps, particularly around tax category codes, unit-of-measure standards and buyer reference fields, are the most common source of rejection by Peppol Access Points during testing.

Compliance Roadmap: 30/60/90-Day Action Plan for eInvoicing Compliance 2026

Achieving and maintaining compliance with mandatory eInvoicing Belgium 2026 requires coordinated action across finance, IT, legal and procurement functions. The following roadmap provides a structured approach, whether a business is still in early-stage preparation or finalising its rollout.

The likely practical effect of delaying this roadmap is significant. Businesses that have not completed Peppol registration and testing by the end of the tolerance period risk invoice rejections, payment delays and, ultimately, administrative penalties. Procurement teams should pay particular attention to smaller suppliers who may lack the resources or awareness to comply independently; proactive outreach and even shared-platform solutions can prevent supply-chain disruption.

Commercial Contracts: What to Change and Model eInvoicing Clauses

The introduction of mandatory eInvoicing Belgium 2026 renders most standard invoicing clauses in Belgian commercial contracts outdated. Clauses that simply require invoices to be “sent by email” or “delivered in PDF format” no longer reflect legal reality. Every supply agreement, distribution contract, master service agreement and framework purchasing agreement should be reviewed and, where necessary, amended.

The following areas require attention in a commercial contract eInvoicing clause review:

• Format obligation: Specify that invoices must be issued as structured electronic invoices compliant with EN 16931, transmitted via the Peppol network.
• Receiving obligation: Confirm that both parties are registered on Peppol and commit to maintaining their registration for the duration of the agreement.
• Cost allocation: Address which party bears the cost of Peppol Access Point subscriptions, ERP integration and any middleware or conversion services.
• Breach and remedies: Define what happens if a party fails to issue or accept compliant eInvoices, including the right to withhold payment, claim damages or terminate.
• Technical failure protocol: Establish a fallback procedure for temporary Peppol outages or Access Point failures, including notification obligations and maximum resolution timeframes.

Model eInvoicing Clause (Short Form)

Suitable for straightforward supply or service agreements between established trading partners:

“All invoices issued under this Agreement shall be structured electronic invoices compliant with the European standard EN 16931 and transmitted via the Peppol eDelivery network. Each Party shall maintain an active Peppol registration using its Belgian enterprise number (KBO/BCE) for the duration of this Agreement. An invoice that does not comply with this clause shall not be deemed validly issued, and payment terms shall not commence until a compliant invoice is received.”

Model eInvoicing Clause (Detailed, With Options)

Suitable for master agreements, distribution contracts and higher-value commercial relationships:

“1. Format and Transmission. The Supplier shall issue all invoices as structured electronic invoices conforming to EN 16931 (UBL 2.1 or CII syntax), transmitted exclusively via the Peppol eDelivery network to the Buyer’s registered Peppol endpoint. A PDF or other non-structured format attached to an email shall not constitute a valid invoice for the purposes of this Agreement.

2. Registration and Maintenance. Each Party warrants that it is, and shall remain, registered as a Peppol participant using its KBO/BCE enterprise number throughout the term of this Agreement. A Party shall notify the other within five (5) business days of any change to its Peppol Access Point or participant identifier.

3. Implementation Costs. Unless otherwise agreed in writing, each Party shall bear its own costs of Peppol registration, Access Point subscription and ERP integration. [Option: The Buyer shall reimburse the Supplier for documented one-time integration costs up to EUR [●], payable within thirty (30) days of invoice.]

4. Non-Compliance. If the Supplier issues an invoice in a non-compliant format, the Buyer may reject such invoice by written notice within ten (10) business days. Payment terms shall recommence from the date a compliant replacement invoice is received. Persistent non-compliance (three or more rejected invoices within any six-month period) shall constitute a material breach entitling the Buyer to terminate this Agreement upon thirty (30) days’ written notice.

5. Technical Failure. In the event of a Peppol network outage or Access Point failure lasting more than forty-eight (48) hours, the affected Party shall promptly notify the other and the Parties shall cooperate to transmit the invoice via an alternative EN 16931-compliant channel. Such temporary alternative transmission shall not constitute a breach of this clause.”

Liability Cap and Indemnity Considerations

For high-volume commercial relationships, industry observers expect negotiation around indemnities for losses caused by eInvoicing failures, such as delayed VAT recovery, late-payment interest or supply-chain disruption. A balanced approach is to cap eInvoicing-related indemnity at the direct losses suffered, excluding consequential damages, and to require the claiming party to demonstrate reasonable mitigation efforts. Sellers should resist open-ended indemnities that effectively make them insurers of the buyer’s own systems readiness.

Impact of eInvoicing on M&A: Due Diligence, Warranties and Transfer of Undertakings

Mandatory eInvoicing Belgium 2026 introduces a new, and frequently overlooked, layer of risk in mergers, acquisitions and transfers of undertakings. A target company’s failure to comply creates potential VAT liabilities, operational disruption and contractual exposure that directly affect enterprise value. Both buy-side and sell-side advisers should integrate eInvoicing verification into standard due-diligence workflows.

The impact of eInvoicing on M&A manifests in several areas:

• Historical compliance: Were invoices issued in compliant structured format from 1 January 2026? Non-compliant invoices may trigger the right of the tax authority to challenge VAT deductions claimed by the target’s customers.
• System readiness: Does the target have a functioning Peppol connection, or is it relying on manual workarounds that will not scale?
• Contractual exposure: Have the target’s commercial contracts been updated with eInvoicing clauses? Outdated contracts create breach risk and potential payment disputes post-closing.
• Integration cost: If the acquirer operates a different ERP or Peppol Access Point, post-closing integration may require additional investment.

M&A Due-Diligence Checklist

SPA Clause Examples: Representations on eInvoicing Compliance

Transaction lawyers should consider including specific representations and warranties in the share purchase agreement or asset purchase agreement. A sample representation clause might read:

“The Company warrants that, since 1 January 2026, all invoices issued for domestic B2B transactions have been structured electronic invoices compliant with EN 16931, transmitted via the Peppol eDelivery network, and archived in their original structured format. The Company is not aware of any pending or threatened challenge by the Belgian tax administration relating to the format or validity of invoices issued or received since that date.”

For transfers of undertakings and transfer of undertakings eInvoicing scenarios, including family business successions, the acquiring party should additionally verify that the transferred business’s Peppol participant identifier can be migrated or re-registered without disruption, and that all ongoing commercial contracts contain adequate eInvoicing clauses that will survive the change of control.

Enforcement, Penalties and the Transitional Grace Period

The Belgian tax administration (FOD Financiën) is responsible for enforcing the mandatory eInvoicing obligation. A three-month administrative tolerance period, running from 1 January 2026 through 31 March 2026, was announced to allow businesses additional time to finalise technical implementation without facing immediate sanctions. This tolerance period was widely reported by professional-services firms and confirmed in guidance associated with the Royal Decree.

After the tolerance period expires, non-compliant businesses face administrative penalties. The likely practical effect is that the FOD Financiën will focus initial enforcement on persistent non-compliance rather than isolated technical errors, though businesses should not treat this expectation as a guarantee. The nature and scale of penalties are governed by the general Belgian VAT penalty framework, which provides for fixed fines per infringement and proportional penalties in cases of intent or repeated violation.

How to Manage Counterparties During the Tolerance Period

• Document good-faith efforts: Maintain written evidence of Peppol registration applications, Access Point contracts and testing correspondence with trading partners. This creates a compliance paper trail if the FOD Financiën queries your status.
• Dual-channel approach: During the tolerance window, consider issuing both a structured eInvoice via Peppol and a parallel PDF to counterparties who confirm they are not yet technically ready to receive structured invoices. The structured invoice remains the legally valid document.
• Escalation clause: In amended contracts, include a provision requiring counterparties to achieve full Peppol compliance by a specified date (no later than 31 March 2026) and reserving remedies if they fail to do so.
• Monitor official guidance: The tolerance period parameters may be adjusted. Regularly check the official einvoice.belgium.be portal and FOD Financiën announcements for updates.

Conclusion: Preparing Your Business for Mandatory eInvoicing Belgium 2026

Mandatory eInvoicing Belgium 2026 is not merely a tax-technology project, it is a commercial and transactional imperative that touches every active business relationship. The businesses that treat this mandate solely as an IT upgrade risk contractual disputes, M&A liability exposure and regulatory penalties. Those that approach it as a cross-functional compliance programme, updating contracts, strengthening due-diligence processes and building robust technical infrastructure, will be best positioned.

The key takeaways are clear: register on Peppol and test thoroughly; amend commercial contracts with specific eInvoicing clauses that allocate obligations and costs; integrate eInvoicing compliance into every live or planned transaction’s due-diligence checklist; and monitor the official einvoice.belgium.be portal for regulatory updates. For businesses navigating complex commercial relationships, multi-entity structures or active M&A pipelines, early engagement with experienced Belgian commercial lawyers is the most effective way to mitigate risk and ensure full compliance.

Sources

1. E-invoice Belgium, Official Government Portal
2. European Commission, eInvoicing in Belgium Overview
3. FOD Financiën / Belgian Tax Administration, eInvoice Partner Page
4. Loyens & Loeff, eInvoicing in Belgium: Key Provisions of the Royal Decree
5. BDO Belgium, Mandatory eInvoicing 2026: Three-Month Tolerance Period
6. PwC Belgium, Newsflash: eInvoicing in Belgium