Europe's e-invoicing mandates: navigating multiple models

Disclaimer: This article reflects mandate status, dates, and official guidance available as of 7 September 2026. E-invoicing and digital reporting rules continue to evolve across Europe. Verify the current requirements for the relevant entity and transaction before implementation. This article is general information and is not tax or legal advice.

A multinational can run one ERP, one finance organisation, and one AP model across Europe, while the legal route of an invoice changes completely from country to country. In Poland, the supplier submits the invoice to KSeF and the buyer accesses it there. In Italy, SdI checks the invoice and routes it onward. In France, accredited private platforms exchange the invoice while required data is reported to the tax administration. In Belgium, the invoice moves between the supplier's and buyer's Peppol providers, with no tax authority in the exchange today. Germany requires structured e-invoicing but leaves the delivery channel to the trading parties. The direction is common; the operating models are not.

Poland, Italy, France, Belgium, and Germany are useful to look at together because they make several of the main European architectures visible within one multinational footprint: a central government platform, a central validation and routing gateway, regulated private platforms combined with e-reporting, a four-corner Peppol exchange moving towards a reporting layer, and structured e-invoicing without a government platform in the invoice route. These five markets illustrate the main patterns rather than the full set; several other European countries use further variations.

Some of these architectures are described as Continuous Transaction Controls, or CTCs. In simple terms, a CTC means that invoice or transaction data is shared electronically with the tax authority as part of, or very close to, the transaction process. E-invoicing and CTC are not the same thing. Depending on the country, the tax authority may sit directly in the invoice journey, receive selected data separately through e-reporting, or not be involved in the invoice exchange at all. That distinction changes what finance, AR, AP, and the underlying systems need to support.

The country mandates also sit in a wider European context. The regimes below are national frameworks and, in these examples, mainly determine how domestic B2B invoices are issued and exchanged. Some countries go further: France, for example, combines domestic B2B e-invoicing with separate e-reporting for specified B2C and cross-border transactions, together with payment reporting where applicable. VAT in the Digital Age (ViDA) adds an EU layer rather than replacing national models with one European platform. From 1 July 2030, cross-border B2B transactions will be subject to Digital Reporting Requirements based on mandatory e-invoicing. Domestic real-time reporting systems will increasingly converge with that framework, with final alignment required by 1 January 2035.

Follow the invoice: five countries, five different journeys

The clearest way to understand the difference is to follow the invoice. Across the five markets, the key questions are where the invoice goes, whether the tax authority validates it or receives data from it, what the buyer receives, who is in scope, and what reporting sits around the invoice.

Poland: KSeF puts the government platform in the invoice flow

Poland sits at the most centralised end of this comparison. An in-scope supplier sends the structured invoice to KSeF, the government system, and the domestic buyer receives it through KSeF. In the standard online flow, KSeF statuses and identifiers become part of the legal and accounting process. Mandatory issuance started on 1 February 2026 for taxpayers whose 2024 gross sales exceeded PLN 200 million and on 1 April 2026 for other in-scope taxpayers. Taxpayers whose monthly gross invoiced sales do not exceed PLN 10,000 can remain outside mandatory issuance until 1 January 2027. Mandatory receipt through KSeF started on 1 February 2026, and KSeF-specific financial penalties apply from 1 January 2027. Mandatory issuance generally depends on a Polish establishment or a Polish fixed establishment participating in the transaction rather than VAT registration alone. For finance, the consequence is clear: the ERP process has to manage submission, system statuses, identifiers, reconciliation, and contingency scenarios, which is a considerably larger job than generating an XML file.

Italy: SdI validates and routes the invoice

Italy also places a government-managed system in the invoice route, but the role is different. In-scope invoices are created in FatturaPA XML and sent to the Sistema di Interscambio, or SdI. SdI performs technical checks and, if the file passes, routes the invoice onward to the recipient's nominated delivery channel. SdI rejects files that fail the checks; the supplier then corrects and retransmits them. The broad B2B and B2C model has been in place since 2019 and generally applies to operators resident or established in Italy rather than non-established businesses that are merely VAT registered. Poland and Italy can both be described as central models, but the platform role, format, routing, statuses, corrections, and integrations are still country-specific.

France: private platforms exchange the invoice, while the tax administration receives the data

France changes the architecture more fundamentally. Rather than requiring every domestic B2B invoice to pass through one central government exchange, the reform relies on accredited private platforms, Plateformes Agréées or PAs, to exchange invoices between businesses and transmit required data to the tax administration. The public infrastructure supports the central directory and data-concentration functions rather than acting as a free public invoice-exchange platform. Since 1 September 2026, all businesses established in France that fall within the reform's scope must be able to receive e-invoices through a PA. Large enterprises and entreprises de taille intermédiaire (ETIs), France's mid-sized enterprise category, must also issue e-invoices and transmit the required transaction and payment data; smaller in-scope businesses follow for issuance and e-reporting on 1 September 2027. Domestic B2B transactions between established businesses generally fall into e-invoicing, while specified B2C and cross-border transactions fall into e-reporting, together with payment reporting where applicable. The French government confirmed that no business will be sanctioned during 2026 while the reform is being brought into operation. France therefore requires invoice exchange and tax reporting to be designed together, even though the tax authority is not the platform exchanging the commercial invoice.

Belgium: Peppol connects supplier and buyer today, with e-reporting coming next

Belgium moves the invoice exchange further away from the tax authority. Since 1 January 2026, structured e-invoicing is mandatory for nearly all in-scope domestic B2B transactions between Belgian-established taxable persons. The invoice is normally exchanged over the decentralised Peppol network in a four-corner model: the supplier connects through its service provider, the buyer through its own provider, and the invoice moves between those providers. The Belgian tax authority does not sit between supplier and buyer and, in this first phase, invoice data is not sent to the administration as part of the exchange. Peppol BIS is the default business interoperability specification. Parties can agree on another exchange method and another format, provided it complies with EN 16931, the European standard that defines the semantic content of an electronic invoice. Belgium is also preparing the next phase: near-real-time bilateral e-reporting is targeted for 2028, and the Council of Ministers approved a preliminary draft law on 18 July 2026. The final legal and technical design is still developing. Peppol readiness therefore solves today's exchange layer, while the reporting and reconciliation layer arriving with the next phase remains open.

Germany: structured e-invoicing without a central government platform

Germany sits at the other end of the comparison. Businesses must be able to receive structured e-invoices, but the invoice does not have to pass through a central government platform or one mandatory network. Domestic businesses have had to be able to receive e-invoices since 1 January 2025. For issuance, all businesses can rely on the statutory transition until the end of 2026; businesses with prior-year turnover of no more than EUR 800,000 can continue under the transition until the end of 2027, and certain existing EDI arrangements can also continue through 2027. Once the relevant transition ends, in-scope domestic B2B invoices must meet the structured e-invoice requirements. The implementation focus is therefore on structured data, receipt capability, and buyer integration rather than government clearance or transaction-level reporting of each invoice.

The five models side by side

Placed side by side, the difference is clear. Poland makes KSeF the central platform through which the invoice is submitted and made available to the buyer. Italy keeps a government gateway in the middle, but SdI validates and routes the file onward. France moves the commercial exchange to accredited private platforms and adds e-reporting to the tax administration. Belgium uses a four-corner Peppol exchange today, with a separate bilateral reporting layer planned next. Germany leaves the tax authority outside the invoice exchange. A common move towards structured e-invoicing does not create one common compliance architecture.

Note on terminology: The CTC and operating-model labels in the table are practical architecture descriptions, not statutory terms used identically by every jurisdiction. Germany does not operate transaction-level CTC in the B2B invoice flow today. Belgium's 2026 mandate is a four-corner Peppol e-invoicing model without invoice-data reporting to the administration; the expected five-corner evolution from 2028 remains subject to final legislation and technical design.

Scope starts with the entity and transaction, not the VAT number

Understanding the architecture is only half the exercise. The next question is whether your entities and transactions are actually in scope. A foreign-headquartered group can still fall inside a local mandate, and a local VAT number on its own can still leave it outside one. Never use a VAT registration list as your e-invoicing scope map.

A VAT registration is not the same as an establishment. Scope tests also remain country-specific. Poland, Italy, Belgium, France, and Germany generally place significant weight on local establishment or, where relevant, a fixed establishment participating in the transaction rather than VAT registration alone. France also applies separate e-reporting obligations to specified B2C, cross-border, and certain non-established flows. The same legal entity can therefore face different obligations depending on which establishment participates and what type of transaction is performed.

Your practical starting point is to map legal entities, business establishments, branches or fixed establishments, and VAT registrations separately, then overlay your material domestic, cross-border, B2B, and B2C transaction flows. That determines whether the obligation is to issue, receive, report, or potentially fall outside a particular local mandate for that flow.

What these differences mean for finance

Once the country and scope are known, the operational consequence becomes clearer. Finance cannot treat e-invoicing as an outbound format change. The invoice route affects customer and supplier master data, delivery statuses, exception handling, AP processing, archiving, and the evidence needed to reconcile the invoice back to the accounting and VAT record.

The incoming side matters just as much as issuance. If a supplier invoice is rejected, arrives through the wrong channel, or cannot be linked to the accounting record, posting, matching, approval, and payment can stall. Depending on the facts and country, the timing or evidence supporting input VAT recovery can also be affected. E-invoicing therefore lands on finance controls and working capital as heavily as it lands on the sales-invoice process.

Employee expenses sit beside that AP process but are not automatically subject to the same legal invoice route. A supplier invoice addressed to the company may have to arrive through KSeF, a French PA, or Peppol, while a receipt issued to an employee can remain subject to different invoicing and evidence rules. Supplier invoices, employee expenses, VAT evidence, approvals, and archiving still need to come together within a controlled spend process.

For an expense platform such as Rydoo, that boundary matters. E-invoicing does not turn every employee expense into an e-invoice, but the expense process still has to remain aligned with new AP invoice channels and local evidence requirements.

Peppol can connect markets, but it does not harmonise the law

After five different invoice journeys, there is still room for reuse. Peppol is one important interoperability layer, but its role needs to be precise. Peppol is not an invoice format and it is not a government clearance platform. It is a network and rulebook that allows businesses to exchange structured documents through certified service providers. In the standard four-corner model, supplier and buyer can each use their own provider while remaining connected through the same network.

That flexibility is valuable, but it does not create one European compliance model. Belgium uses Peppol as its default B2B exchange route. French accredited platforms can use it for interoperability. Germany can use it as one delivery channel without mandating it. Poland and Italy continue to rely on their statutory central systems. Peppol can standardise parts of connectivity, addressing, and document exchange; it does not decide local scope, tax-authority reporting, correction rules, or contingency procedures.

Start with the footprint, then decide what should be common

You can still build around a common foundation, provided you are explicit about where local law requires a different route. Your common layer can include the entity and transaction map, source-data model, master-data ownership, lifecycle statuses, monitoring, minimum evidence, and governance. Country-specific layers then sit around that foundation where a mandated platform, format, reporting flow, or local exception requires them.

Before choosing a platform or provider, build a country-by-country view of how your group actually operates. For each legal entity and material transaction flow, capture the scope trigger, invoice route, required format, tax-authority touchpoint, reporting obligation, go-live date, and process owner. Add the incoming side as well: where supplier invoices arrive, how they are matched and approved, and where employee expenses sit alongside them.

That gives your finance and tax teams a stable foundation for the next country without pretending that every market should use the same tooling or legal process.

The next challenge is delivery

The five countries in this article are only a cross-section. Other markets combine e-invoicing, clearance, private-platform exchange, and reporting differently, and the number of mandates keeps growing through new legislation and later phases of existing regimes. The first task is understanding the country architecture and scope. Once that is clear, a different challenge starts: how to deliver several of those mandates through the same finance organisation without creating disconnected providers, integrations, controls, and exception processes.

For teams maintaining the underlying country view, the Rydoo Compliance Centre complements official sources with country-by-country e-invoicing and related spend-compliance guidance, including VAT, paperless documentation, per diem, and mileage.