Electronic invoicing is no longer optional in Europe. Country by country, governments are mandating structured formats, official transmission platforms, and tightening deadlines. For businesses running an ERP, the question is no longer whether they will need to adapt, but when — and more importantly, how.
The stakes are real: by the end of 2027, virtually every European business will be required to issue and receive compliant electronic invoices. Companies whose ERP is not ready face tax penalties, invoice rejections, and cash-flow disruption.
This guide covers the regulatory timeline by country, compares technical standards, benchmarks ERP compliance by tier, and provides an actionable checklist to prepare your organisation for the transition.
The Regulatory Calendar 2024–2028: Who Mandates What and When
E-invoicing mandates are rolling out at different speeds across Europe. Here is the current landscape of key deadlines.
| Country | Standard | B2G (public sector) | B2B mandatory | Platform |
|---|---|---|---|---|
| Italy | FatturaPA / SDI | ✅ 2014 | ✅ 2019 | SDI (Sistema di Interscambio) |
| France | Factur-X / UBL | ✅ 2020 (Chorus Pro) | Sept 2026 (reception), Sept 2027 (issuance SME/VSE) | Chorus Pro + accredited PDPs |
| Germany | XRechnung / ZUGFeRD | ✅ 2020 | Jan 2025 (reception), Jan 2027 (issuance) | Peppol + Länder portals |
| Belgium | Peppol BIS | ✅ 2024 | Jan 2026 | Peppol |
| Spain | Facturae / TicketBAI | ✅ 2015 | 2026–2027 (Ley Crea y Crece) | SII + regional platforms |
| Poland | KSeF | ✅ 2024 | Feb 2026 | KSeF (Krajowy System e-Faktur) |
| Nordics | Peppol BIS | ✅ 2018–2020 | Widely adopted (not always legally mandatory B2B) | Peppol |
The ViDA Directive (VAT in the Digital Age): the European Commission is targeting a harmonised EU-wide B2B e-invoicing framework by 2030, with near-real-time VAT reporting. Until then, member states are advancing independently.
What These Deadlines Mean for Your ERP Concretely
Each deadline means your management system must be able to:
- Generate invoices in the required structured format (XML UBL, CII, Factur-X, etc.)
- Transmit via the official platform or an accredited clearance operator
- Receive and automatically integrate incoming structured invoices
- Archive with legal evidential value for the statutory retention period (6 to 10 years depending on the country)
- Report VAT data in real-time or near-real-time as required by the relevant jurisdiction
An ERP that does not cover all five functions before the deadline exposes the business to financial penalties and the inability to invoice B2B customers.
France: Chorus Pro and the Progressive Mandate
France has chosen a phased rollout that has left many businesses uncertain about what they need to do and by when.
The French Timeline in Detail
September 2026: every business must be able to receive electronic invoices, regardless of size. This is the most immediate deadline — and the most underestimated.
September 2027: obligation to issue electronic invoices extended to SMEs and micro-businesses (after large enterprises and mid-market companies in 2026).
The Chorus Pro and PDP Ecosystem
The French model is built around a Y-model architecture:
- Chorus Pro: the free public platform, the central routing hub
- PDPs (Plateformes de Dématérialisation Partenaires): private operators accredited by the tax authority, offering value-added services (validation, enrichment, archiving)
- ODs (Opérateurs de Dématérialisation): technical service providers that convert formats but must route through Chorus Pro or a PDP
The Factur-X format is the French standard: a human-readable PDF embedding a structured XML file (CII profile). This hybrid format eases the transition for smaller businesses — the invoice remains “readable” while being machine-processable.
ERP Impact in France
To be compliant, an ERP must:
- Generate Factur-X (minimum, basic, EN16931 or extended profiles depending on requirements)
- Connect to at least one accredited PDP or directly to Chorus Pro via API
- Manage the full invoice lifecycle: issuance, status tracking, acknowledgement, rejection
- Include mandatory fields (SIREN, address, intra-community VAT number)
- Support e-reporting: transmitting transaction data to the tax authority for transactions outside the e-invoicing scope (B2C, cross-border)
French-origin ERPs (Sage, Cegid, Divalto) have a natural advantage: they know French tax law and ship native PDP connectors. International ERPs (SAP, Oracle, NetSuite) often require an additional module or specialist partner.
Germany: XRechnung, ZUGFeRD, and German Pragmatism
Germany has chosen a dual approach that reflects its federal structure.
XRechnung: the Public Sector Standard
XRechnung is the mandatory XML format for invoicing federal public administrations and most Länder since 2020. It is a profile compliant with European standard EN 16931, based on UBL 2.1 or CII.
A key complexity: each Land may have its own receiving portal (ZRE for the federal level, OZG-RE for some Länder), which complicates integration for businesses operating across multiple regions.
ZUGFeRD: the Hybrid Format for B2B
ZUGFeRD (Zentraler User Guide des Forums elektronische Rechnung Deutschland) is the German equivalent of France’s Factur-X — technically, the two share the same CII specification. ZUGFeRD 2.x and Factur-X are fully interoperable.
Since January 2025, all German businesses must be able to receive structured electronic invoices. The obligation to issue follows in January 2027 for businesses above €800,000 in turnover.
ERP Requirements in Germany
- Native XRechnung support (UBL 2.1 or CII) for B2G
- ZUGFeRD 2.x generation for B2B
- GoBD compliance (full digital fiscal audit trail: every entry traced, immutable)
- Transmission via Peppol (the preferred network for B2G and increasingly B2B)
- Handelsgesetzbuch (HGB) accounting rules
German-native ERPs (SAP, proALPHA, ABAS, Haufe X360) are naturally ahead. Non-German ERPs — whether from other European countries or global vendors — should verify GoBD compatibility, which is often the blocking point.
Italy: Lessons from SDI Since 2019
Italy is Europe’s e-invoicing pioneer. Its system, mandatory for B2B since 2019, has delivered invaluable lessons for the rest of the continent.
The SDI Model (Sistema di Interscambio)
The SDI is the central platform run by the Agenzia delle Entrate (Italian tax authority). Every B2B and B2C invoice must pass through the SDI in FatturaPA format (XML conforming to the Italian schema).
The flow is straightforward but rigid:
- The issuer sends the XML invoice to the SDI (via PEC, web portal, FTP, or API)
- The SDI validates the format, fiscal content, and recipient
- On successful validation, the SDI routes the invoice to the recipient and notifies the issuer
- On rejection, the issuer receives a detailed error notification
Key Lessons from Italy for the Rest of Europe
VAT gap reduction: Italy recorded a €3.5 billion reduction in its VAT gap in the first two years of mandatory e-invoicing. This result convinced other European governments to accelerate their own programmes.
Adaptation timeline: Italian SMEs took an average of 6 to 12 months to adapt their processes. Businesses that waited until the last moment experienced significant cash-flow disruption.
Data quality imperative: the move to SDI forced a major clean-up of supplier and customer master data. Companies whose ERP held incorrect records (tax codes, addresses) found themselves blocked from invoicing.
Impact for Multi-Country ERPs
Any business operating in Italy must ensure its ERP:
- Generates compliant FatturaPA (specific XML schema, different from UBL)
- Manages the codice destinatario (7-character routing code) for each customer
- Processes SDI notifications (acceptance, rejection, mancata consegna)
- Supports the esterometro for cross-border transactions
Italian-origin ERPs (Zucchetti, TeamSystem, Passepartout) handle SDI natively. International ERPs require a certified SDI connector or an intermediary service.
Nordics: Peppol as the De Facto Standard
The Nordic countries (Sweden, Norway, Denmark, Finland) are Europe’s e-invoicing champions, with B2B adoption rates exceeding 80% in some sectors.
Peppol: the Pan-European Network
Peppol (Pan-European Public Procurement Online) is both a transport network and a set of specifications (Peppol BIS Billing 3.0). Its 4-corner model (sender → sender access point → receiver access point → receiver) guarantees interoperability across countries and systems.
Key advantage: a business connected to Peppol can send and receive invoices from any other Peppol participant in Europe, regardless of country or ERP.
Adoption by Nordic Country
- Norway: SAF-T mandatory for tax audits, Peppol near-universal for B2G and B2B. EHF (Electronic Handelsformat) as the local profile.
- Sweden: Peppol mandatory for B2G since 2019, strong voluntary B2B adoption. Svefaktura has migrated to Peppol BIS.
- Denmark: a historical pioneer with NemHandel (a Peppol precursor), now fully Peppol-integrated.
- Finland: Finvoice as the domestic format, with a Peppol gateway for cross-border interoperability.
ERP Impact
The good news: Peppol is the most ERP-friendly standard in Europe. Its UBL 2.1 specification is widely supported, and Peppol access points offer modern APIs.
A Peppol-compliant ERP must:
- Generate Peppol BIS Billing 3.0 (UBL 2.1)
- Connect to a certified Peppol access point
- Handle the Peppol Directory (automatic recipient lookup)
- Support SAF-T for Norway (standardised tax audit format)
Nordic ERPs (Visma, Fortnox, Monitor ERP) are natively connected. International ERPs benefit from the broad availability of Peppol access points as SaaS services.
Which ERPs Are Ready? A Comparison by Tier
E-invoicing compliance varies significantly depending on ERP tier and market of origin.
Tier 1: SAP S/4HANA
Compliance level: Excellent (native multi-country)
SAP S/4HANA includes SAP Document Compliance, a comprehensive solution covering:
- France (Chorus Pro, Factur-X, PDP connectivity)
- Germany (XRechnung, ZUGFeRD, GoBD)
- Italy (SDI, FatturaPA)
- Nordics (Peppol BIS)
- 60+ additional countries
Strength: SAP maintains continuous regulatory monitoring and deploys compliance updates through regular SAP Notes.
Weakness: configuration is complex and costly. Budget 3 to 6 months of project work and €50,000–€150,000 to activate multi-country compliance.
Verdict: essential for mid-market and enterprise groups operating in multiple countries; over-engineered for a single-country SME.
Tier 3: Sage 100 and Odoo Enterprise
Sage 100 — Compliance: Very good (France, solid in Europe)
Sage 100 is a leading ERP for European SMEs. Its e-invoicing compliance:
- France: native Chorus Pro connector, Factur-X generation, PDP partnerships (Sage itself is a PDP candidate)
- Germany: ZUGFeRD via add-on module
- International: coverage via Sage Network (document exchange platform)
Strength: the transition is nearly transparent for existing Sage 100 users — a software update plus module activation.
Weakness: coverage outside France requires additional paid modules.
Odoo Enterprise — Compliance: Good (modular, improving)
Odoo Enterprise addresses e-invoicing via country-specific modules:
- France: Factur-X module (PDF/A-3 + CII XML), Chorus Pro connector via partners
- Germany: XRechnung module, ZUGFeRD supported
- Italy: FatturaPA module with SDI integration
- Peppol: connector available via community apps and partners
Strength: the modular approach lets you activate only the countries you need. Cost is controlled (included in the Enterprise subscription for official modules).
Weakness: quality varies between official and community modules. Regulatory updates can lag behind specialist publishers.
Tier 4: Dolibarr and Axelor
Dolibarr — Compliance: Adequate (France, basic elsewhere)
Dolibarr, the most popular open-source ERP among European micro-businesses:
- France: Factur-X module available (community), Chorus Pro integration under development
- International: limited coverage, depends on third-party modules
Strength: near-zero cost for micro-businesses. The community is active on e-invoicing.
Weakness: no integrated multi-country coverage. Technical support relies on the community or local integrators.
Axelor — Compliance: Good (France, expanding)
Axelor, the French open-source low-code ERP:
- France: native Factur-X, Chorus Pro connector in development
- International: modular architecture enabling country-specific connectors to be added
- Peppol: on the roadmap
Strength: the low-code approach accelerates adaptation to new regulations. The publisher is responsive to French compliance requirements.
Weakness: less mature than Sage or Odoo for multi-country coverage.
Compliance Summary Table
| ERP | France | Germany | Italy | Peppol | Multi-country | Activation effort |
|---|---|---|---|---|---|---|
| SAP S/4HANA | ★★★ | ★★★ | ★★★ | ★★★ | ★★★ | High (3–6 months) |
| Sage 100 | ★★★ | ★★☆ | ★★☆ | ★★☆ | ★★☆ | Medium (1–2 months) |
| Odoo Enterprise | ★★★ | ★★★ | ★★★ | ★★☆ | ★★★ | Medium (1–3 months) |
| Dolibarr | ★★☆ | ★☆☆ | ★☆☆ | ★☆☆ | ★☆☆ | Low (weeks) |
| Axelor | ★★★ | ★☆☆ | ★☆☆ | ★☆☆ | ★★☆ | Medium (1–2 months) |
E-Invoicing Compliance Checklist for CIOs
Here are the concrete steps to prepare your ERP for mandatory e-invoicing.
Phase 1: Audit (3–6 months before the deadline)
- Map your invoice flows: how many invoices issued and received per month, which countries, which types (B2B, B2G, B2C)
- Check your ERP version: contact your vendor to identify the minimum version required for e-invoicing compliance
- Audit your data quality: VAT numbers, company registration numbers, addresses — e-invoicing rejects incorrect data
- Identify your obligations by country: if you invoice across multiple European countries, each has its own requirements
- Assess your connectivity: can your ERP connect to an accredited PDP (France), to the SDI (Italy), or to a Peppol access point?
Phase 2: Selection and Configuration (2–4 months before)
- Choose your PDP or clearance operator: compare at least 3 providers on cost, country coverage, and native ERP integration
- Activate e-invoicing modules in your ERP: Factur-X, XRechnung, FatturaPA depending on your markets
- Configure output formats: verify that your invoice templates generate XML conforming to the required profile
- Set up e-reporting (France): B2C and cross-border transactions must also be reported
- Update customer and supplier records: codice destinatario (Italy), GLN or Peppol ID (Nordics), SIREN/SIRET (France)
Phase 3: Testing and Deployment (1–2 months before)
- Test in a qualification environment: submit test invoices via the platform’s sandbox (Chorus Pro offers a test portal)
- Validate the full cycle: issuance → transmission → acknowledgement → accounting → archiving
- Train accounting teams: new workflows change established habits (no more PDFs sent by email)
- Prepare a fallback plan: what happens if the platform is unavailable? Is archiving guaranteed? What is your operator SLA?
- Document your compliance: the tax authority can request evidence of a compliant process at any time
Phase 4: Post-Deployment Monitoring
- Monitor rejection rates: a rate above 2% signals a data or configuration issue
- Track regulatory changes: specifications evolve (new mandatory fields, new Factur-X profiles)
- Plan ahead for upcoming deadlines: if you are compliant in one country, start preparing for the next
FAQ: Common Questions on the E-Invoicing Transition
My current ERP doesn’t support e-invoicing. Do I need to change it?
Not necessarily. Most modern ERPs offer e-invoicing modules or connectors. The first step is to contact your vendor and ask about their roadmap. If your ERP is end-of-life (no longer receiving updates) or if the e-invoicing module cost is disproportionate to the system’s overall value, this may be the right moment to consider a migration to a compliant ERP.
What does compliance cost?
Costs vary widely depending on your situation:
- Micro-business on Dolibarr: €500–€2,000 (community module + configuration)
- SME on Sage/Odoo: €5,000–€20,000 (module licence + integrator + PDP)
- Mid-market on SAP: €50,000–€150,000 (configuration project + multi-country connectors)
Add recurring operator or PDP costs (averaging €0.10–€0.50 per transmitted invoice). See our ERP implementation cost guide to put these figures in context.
Are Factur-X and ZUGFeRD the same format?
Yes, technically. Factur-X (France) and ZUGFeRD 2.x (Germany) share the same technical specification based on the Cross Industry Invoice (CII) standard from UN/CEFACT, embedded in a PDF/A-3 file. A valid Factur-X invoice is also a valid ZUGFeRD invoice, and vice versa. This Franco-German interoperability is a significant advantage for cross-border businesses.
Will Peppol replace all other standards?
That is the underlying direction. The EU’s ViDA directive is pushing towards harmonisation around Peppol as the transport network and EN 16931 as the semantic standard. However, national specifics (SDI in Italy, Chorus Pro in France) will persist at least until 2030. The safest strategy: choose an ERP that supports both Peppol and national formats.
How does e-invoicing interact with GDPR?
Invoices contain personal data (names, addresses, VAT numbers). Their transmission through third-party platforms (PDPs, SDI, Peppol) must respect GDPR. Your ERP must ensure that invoicing data transits through secure channels and that archiving complies with statutory retention periods without exceeding GDPR retention limits. For more on this topic, see our guide on ERP and GDPR compliance.
Conclusion: Act Now or Struggle Later
Mandatory e-invoicing is not an isolated IT project — it is a transformation of financial processes touching accounting, procurement, treasury, and tax compliance across the organisation.
Businesses that prepare early gain real advantages: faster payment cycles (structured invoices are processed more quickly), fewer manual entry errors, real-time cash-flow visibility, and proactive rather than reactive compliance.
Three priority actions for your CIO:
- Assess your ERP’s compliance today — contact your vendor, identify which modules need to be activated
- Select your PDP or operator before the rush — accredited operators in France have limited onboarding capacity and queues are growing
- Run a pilot on a limited scope (one country, one invoice type) to validate the full workflow before organisation-wide rollout
The September 2026 reception deadline in France is months away. For SMEs that have not yet started, now is the time to review our 2026 ERP comparison guide and select a compliant solution.
