E-Invoicing in Europe 2026: The Manufacturer's Guide to Mandates, Peppol, and What's Next
Lennard Kooy
·
13 min read
Four EU countries switch on mandatory B2B e-invoicing in 2026. Here's what every European manufacturer needs to know by country: formats, dates, what ViDA changes in 2030, and what to do in your ERP now.
E-Invoicing in Europe 2026: The Manufacturer's Guide to Mandates, Peppol, and What's Next
2026 is the year European B2B e-invoicing stops being optional. Four EU member states switch on mandatory structured e-invoicing for domestic B2B transactions this year. One more phases in receiver obligations. The EU's own harmonising framework, ViDA, is adopted, with its cross-border mandate scheduled for 2030. For European manufacturers that issue and receive invoices across multiple jurisdictions, the picture is no longer abstract. It is a compliance calendar with hard dates.
This guide is written for operations and finance leaders at European manufacturers that want one document explaining what is actually mandatory in 2026, in which country, in which format, for which company size, and what to do about it.
Automated e-invoicing inside your ERP is the operational answer. The regulatory answer is country by country, format by format, and we walk through every live mandate below.
How Lleverage Handles E-Invoicing Inside Your ERP
Lleverage is the invisible AI layer in your ERP. For e-invoicing specifically, we handle both sides of the flow, issuing structured outbound e-invoices to customers in the format each jurisdiction requires (Peppol BIS, XRechnung, ZUGFeRD, KSeF, Factur-X, SdI), and capturing structured inbound e-invoices from suppliers straight into Business Central, SAP, Exact Online, AFAS, or NetSuite. The AP team sees the exceptions; the rest posts automatically.
This is why Dutch wholesalers and manufacturers choose Lleverage over standalone Peppol Access Points or bolt-on e-invoicing tools. The AI captures invoices arriving in any format the customer actually sends today, PDFs, emailed scans, portal exports, EDI, Peppol, and it also issues outbound invoices in the structured format each receiving jurisdiction mandates. No new interface for the finance team. No data migration. No chart-of-accounts change.
For the ERP architecture detail across Business Central, SAP, AFAS, and Navision, see our ERP + AI integration guide. For a real Dutch wholesaler case (Topa Bathroom Products, +90% automation, 3.8 FTEs redeployed, 30-second invoice confirmation inside Business Central), see Invoice Automation in Business Central for Dutch Wholesalers.
→ See it work on your own invoices.
The 2026 EU E-Invoicing Timeline at a Glance
Five jurisdictions have live or phasing-in B2B e-invoicing mandates that European manufacturers have to think about in 2026:
Belgium, mandatory B2B e-invoicing via Peppol BIS, effective 1 January 2026 (three-month tolerance period until 31 March).
Poland, KSeF mandatory for large taxpayers (annual turnover above PLN 200 million) from 1 February 2026, extended to all remaining taxpayers from 1 April 2026, with micro-enterprises joining 1 January 2027.
France, mandatory B2B e-invoicing for large and mid-size companies from 1 September 2026 (issuance), and mandatory receipt for all companies from the same date. SMEs and micro-enterprises join on 1 September 2027.
Germany, all businesses must be able to receive EN 16931-compliant e-invoices from 1 January 2025; businesses with turnover above EUR 800,000 can no longer issue paper or unstructured invoices from 1 January 2027; full mandatory issuance for all businesses from 1 January 2028.
Italy, domestic B2B e-invoicing via the SdI (Sistema di Interscambio) has been mandatory since 2019, with the scope extended in steps since.
Netherlands, domestic B2B e-invoicing is voluntary today; the Dutch Ministry of Finance submitted its ViDA response to Parliament on 10 March 2026, with a Peppol-based domestic mandate projected for January 2030.
The per-country detail below explains what each rule actually requires, what format it uses, and what a manufacturer has to do to comply.
Country-by-Country E-Invoicing Mandates for Manufacturers
Belgium: 1 January 2026 (Peppol BIS, Mandatory)
From 1 January 2026, all VAT-registered Belgian businesses must issue and receive structured electronic invoices for domestic B2B transactions. The required format is Peppol BIS Billing (EN 16931-compliant), and invoices must be transmitted through the Peppol network. Paper invoices and unstructured PDFs are no longer valid for B2B.
The Belgian tax administration has confirmed a three-month tolerance period: no sanctions will be imposed for e-invoicing-specific infringements between 1 January and 31 March 2026, provided the taxpayer can show reasonable, timely compliance steps. From 1 January 2028, Belgium adds near-real-time e-reporting to the tax authority via a Peppol five-corner model, replacing the annual customer listing.
What manufacturers need to do: connect to a certified Peppol Access Point, configure outbound Peppol BIS issuance from the ERP, and ensure inbound Peppol capture lands in the AP system. If the Belgian entity is a branch or subsidiary of a larger European group, alignment with the group's Peppol and ERP stack matters more than a stand-alone solution.
Poland: 1 February 2026 (KSeF, Large Taxpayers); 1 April 2026 (All Other Taxpayers)
Poland's Krajowy System e-Faktur (KSeF) is a government-operated clearance-model e-invoicing system. From 1 February 2026, KSeF is mandatory for large taxpayers, roughly 4,200 companies with annual turnover above PLN 200 million. From 1 April 2026, the obligation extends to all remaining Polish taxpayers except micro-enterprises, which join on 1 January 2027. Penalties for non-compliance are largely deferred until 1 January 2027, giving a one-year stabilisation window.
Unlike Belgium's Peppol-based decentralised model, KSeF is centralised: every B2B invoice must be submitted in structured XML to the Polish Ministry of Finance's platform, which validates the content and assigns a unique KSeF identifier. Only after validation is the invoice considered officially issued.
What manufacturers need to do: integrate the ERP with KSeF, map outbound invoice data to the required XML schema, and build in KSeF ID handling for payment references. For manufacturers with Polish customers but no Polish entity, inbound capture of KSeF invoices is the relevant concern.
France: 1 September 2026 (Issuance for Large and Mid-Size; Receipt for All)
The French B2B e-invoicing reform applies to all domestic transactions between VAT-registered French entities. From 1 September 2026, large and mid-size companies are required to issue electronic invoices and report transaction data through certified platforms (Plateformes de Dématérialisation Partenaires, PDPs). From the same date, all French VAT-registered companies, regardless of size, must be able to receive electronic invoices. SMEs and micro-enterprises become obligated to issue electronic invoices from 1 September 2027.
France uses a four-corner (soon five-corner) model built around PDPs and a public portal. Accepted formats include UBL, CII, and Factur-X (the French ZUGFeRD equivalent: a hybrid PDF/XML format). The reform also introduces e-reporting obligations for B2C and cross-border transactions.
What manufacturers need to do: select a certified PDP, map outbound invoices to the required structured format, and prepare for the additional mandatory invoice fields that come into effect from 1 September 2026. Large and mid-size manufacturers should plan a parallel-run period starting at least three months before the deadline.
Germany: Phased 2025 → 2028 (XRechnung, ZUGFeRD, EN 16931)
Germany's B2B e-invoicing mandate, introduced via the Growth Opportunities Act of March 2024, follows a three-phase rollout:
From 1 January 2025, all German businesses must be able to receive EN 16931-compliant electronic invoices.
From 1 January 2027, businesses with annual turnover above EUR 800,000 can no longer issue paper or unstructured electronic invoices (PDFs without structured XML).
From 1 January 2028, the mandatory issuance obligation extends to all German businesses.
Germany accepts multiple EN 16931-compliant formats. XRechnung is the national CIUS (Core Invoice Usage Specification) used for public-sector invoicing and widely adopted for B2B. ZUGFeRD 2.1 is an accepted hybrid format that embeds a structured XML inside a PDF, which is convenient for recipients who need a human-readable view. Germany currently operates a post-audit model: there is no central clearance platform, and invoices are exchanged directly between businesses rather than through a government portal.
What manufacturers need to do in 2026: the immediate Phase 1 receipt obligation already applies. If German turnover is above EUR 800,000, prepare outbound issuance for the 1 January 2027 deadline, map ERP output to XRechnung or ZUGFeRD 2.1 and pilot with friendly customers during 2026.
Italy: Already Mandatory via SdI
Italy mandated domestic B2B e-invoicing via the Sistema di Interscambio (SdI) in 2019 and has expanded scope since. All domestic B2B invoices must be submitted in FatturaPA XML format through SdI, which validates and forwards the invoice to the recipient. For manufacturers with Italian operations or Italian customers, SdI integration is table stakes. For European manufacturers extending into Italy, SdI integration is the first hard gate. There is no paper fallback.
Netherlands: Voluntary in 2026, Mandate Targeted for January 2030
As of April 2026, the Netherlands has no mandatory B2B e-invoicing. B2B e-invoicing is voluntary and most commonly exchanged via Peppol by businesses that choose to adopt it. B2G (invoicing to Dutch public authorities) has been voluntary via Peppol for years.
On 10 March 2026, the Dutch Secretary of Finance submitted a formal response to Parliament on implementing the EU's ViDA package. Per VATupdate and RTC Suite summaries of the Ministry of Finance position, the Netherlands is oriented toward a broad Peppol-based domestic B2B e-invoicing mandate. A definitive government position is expected in summer 2026, draft legislation is expected in Q4 2026 for public consultation, final legislation in mid-2028, and the domestic B2B e-invoicing mandate is projected to take effect in January 2030, aligned with the EU ViDA cross-border mandate that goes live on 1 July 2030.
What Dutch manufacturers should do in 2026: start on the voluntary Peppol rail now, while adoption is elective and costs are modest. Arriving at a 2030 mandate with Peppol-based outbound issuance already stable is structurally cheaper than a forced migration in the final months.
The ViDA Directive: EU-Wide Harmonisation from 2030
VAT in the Digital Age (ViDA) is the EU's framework directive, adopted in March 2025, to harmonise e-invoicing and digital reporting across all member states. Its most consequential dates for manufacturers are:
From 1 July 2030: cross-border intra-EU B2B transactions must use EN 16931-compliant structured electronic invoices, issued within 10 days of the taxable event, with near-real-time digital reporting to member-state tax authorities.
Member states retain discretion to introduce domestic B2B mandates before 2030 without prior EU approval (the national mandates above exist under this discretion).
The common technical denominator across member states is EN 16931, the European semantic data model for electronic invoices. Country-specific Core Invoice Usage Specifications (CIUS) such as XRechnung, Peppol BIS Billing, Factur-X, and FatturaPA are all EN 16931-compatible.
The practical implication for a European manufacturer running a single ERP across multiple jurisdictions is that by 2030, cross-border B2B flows between EU member states will all operate on EN 16931-compliant structured invoicing with near-real-time reporting. The infrastructure put in place to comply with the earliest national mandates (Belgium, Poland, France, Germany) is also the infrastructure that will handle ViDA in 2030.
What Manufacturers Should Actually Do in 2026
1. Inventory where you issue and receive invoices, per country
For each EU member state where the manufacturer has a legal entity or a significant customer base, record which mandate is live, when it switches on, what format it uses, and whether issuance, receipt, or both apply. The country-by-country summary above is the starting point.
2. Pick Peppol as the default transport layer where possible
Belgium, France (partially), the Netherlands (voluntary, future mandate), Germany (accepted but not mandated), and several Nordic countries converge on Peppol as the exchange network. Poland (KSeF) and Italy (SdI) use country-specific clearance platforms. A Peppol-first posture handles the majority of jurisdictions with a single integration; KSeF and SdI add country-specific adapters.
3. Map ERP output once per format, not once per customer
EN 16931 is the common semantic layer. XRechnung, ZUGFeRD, Peppol BIS, and Factur-X are syntax variations over the same data model. Configuring the ERP to produce a canonical EN 16931-compliant invoice and transforming to the specific syntax at the exit point is more maintainable than customer-by-customer templates.
4. Treat inbound capture as a separate problem
Receiving structured e-invoices from suppliers is not the same job as issuing them. Inbound capture needs to match the invoice against the purchase order and goods receipt, validate pricing and tax treatment against master data, and post a clean record into the AP module. This is the three-way matching use case; a capture tool that speaks Peppol but cannot reconcile against the ERP is only half the solution.
5. Start parallel-run before the deadline
For the September 2026 French mandate and the January 2026 Belgian mandate, a two-to-four-week parallel-run against a subset of friendly customers surfaces the integration issues that do not show up in test environments. The earlier deadlines are the cheapest to hit; compliance timelines compress as the deadline approaches.
How E-Invoicing Connects to Your ERP and AP Workflow
For manufacturers, the operational story is not "replace the invoicing process." It is "fit structured e-invoicing into the existing order-to-cash and procure-to-pay flows without disrupting production planning."
Outbound: customer orders are captured (from email, PDF, EDI, or portal) into the sales-order module of the ERP; production and fulfilment execute; the ERP issues a commercial invoice, which Lleverage transforms into the structured syntax required by the customer's jurisdiction (Peppol BIS for a Belgian customer, Factur-X for a French mid-cap, XRechnung for a German public-sector buyer, FatturaPA for an Italian entity via SdI, KSeF-XML submitted to the Polish portal). Each transformation happens at the exit point; the ERP's own invoice record stays canonical.
Inbound: suppliers send e-invoices into the manufacturer's Peppol Access Point or equivalent national channel. Lleverage captures the structured data, matches it against the purchase order and goods receipt, applies your approval rules, and posts a clean AP record into Business Central, SAP, Exact Online, AFAS, or NetSuite. Exceptions are routed to a human. For the detailed three-way matching logic, see Invoice Processing Automation: Cut AP Processing Time by 70%.
The same AI layer also handles order-processing automation, see AI Order Processing: How Manufacturers Eliminate Manual Order Entry, because the structural problem is the same: unstructured inbound content becoming structured, validated ERP records without a human keying every field.
Frequently Asked Questions
Is a PDF attached to an email an e-invoice?
Not under the 2026 EU mandates. All the live national mandates (Belgium, Poland, France, and the German receipt obligation) require structured electronic invoicing, either EN 16931-compliant XML transmitted through a specified network (Peppol, KSeF, PDP, SdI), or a hybrid format such as ZUGFeRD or Factur-X that embeds a structured XML inside the PDF. A plain PDF without structured data does not satisfy the mandate in any of the 2026 jurisdictions.
What is the difference between Peppol BIS, XRechnung, ZUGFeRD, Factur-X, KSeF, and SdI?
They are different transport networks and syntaxes, most sitting on top of the same semantic data model (EN 16931). Peppol is a four-corner exchange network used by Belgium, parts of France, and the Nordics, with Peppol BIS Billing as its invoice format. XRechnung is Germany's national Core Invoice Usage Specification for EN 16931. ZUGFeRD and Factur-X are hybrid formats (PDF with embedded XML), ZUGFeRD in Germany, Factur-X in France. KSeF is the centralised Polish government clearance platform. SdI is the centralised Italian clearance platform. A manufacturer operating across jurisdictions generally needs Peppol plus country-specific adapters for KSeF and SdI.
Do we need a Peppol Access Point, or will our ERP handle it?
Most ERPs do not ship with native Peppol Access Point functionality. A certified Peppol Access Point (operated by a service provider) sits between the ERP and the Peppol network and handles message routing, format validation, and delivery confirmation. The integration between the ERP and the Access Point is the practical unit of work. Lleverage handles the Peppol integration inside the ERP so the finance team does not adopt a separate tool.
What happens if we miss a national deadline?
Sanctions vary by country. Belgium has confirmed a three-month tolerance period from 1 January to 31 March 2026 during which no penalties apply to e-invoicing-specific infringements. Poland has deferred most KSeF penalties until 1 January 2027. France and Germany apply their general tax-compliance penalty regimes to e-invoicing failures once the mandate is live. Italy has enforced SdI compliance since 2019 and does not operate a grace period for new entrants.
How does e-invoicing affect three-way matching and AP processing?
Positively, if the infrastructure is right. A structured inbound e-invoice is orders of magnitude easier to match against the purchase order and goods receipt than a scanned PDF, because the line-item data, tax treatment, and supplier identifier are already machine-readable. The operational saving comes not from the Peppol transmission itself but from the downstream automation that becomes possible once the inbound record is structured, automated three-way matching, exception-only review, and straight-through posting into the ERP.
Is the Netherlands a 2026 e-invoicing jurisdiction?
No, not in the mandatory sense. The Dutch B2B e-invoicing mandate is currently projected for January 2030. In 2026, Dutch manufacturers are in a preparation window, the Ministry of Finance is consulting on the design, and draft legislation is expected in Q4 2026. Manufacturers with Dutch operations and non-Dutch customers still face the Belgian, Polish, French, and German mandates in 2026 for those cross-border flows.
See Lleverage Work on Your Own E-Invoicing Flows
Lleverage runs e-invoicing automation inside the ERP your finance team already uses, Business Central, SAP, Exact Online, AFAS, Infor, or NetSuite. Outbound invoices go out in the format each receiving jurisdiction mandates. Inbound invoices arrive as structured records inside your AP module, matched against purchase orders and goods receipts. The finance team only touches exceptions. No new interface. No data migration. No chart-of-accounts change.
Further reading on our blog:
Invoice Automation in Business Central for Dutch Wholesalers
Invoice Processing Automation: Cut AP Processing Time by 70%
ERP + AI Integration Guide: Business Central, SAP, AFAS, Navision
AI Order Processing: How Manufacturers Eliminate Manual Order Entry
Explore solution pages: