Port Cloud Pro.
Integration

EU E-Invoicing Mandates and Your Procure-to-Pay Software: A Country-by-Country Guide

Germany, France, Poland, Belgium and Italy now require structured B2B invoices, and no two do it the same way. Here's what each mandate demands of your P2P software, what the add-ons typically cost and which gaps to close first.

Port Cloud Pro editorial team · November 2026 · 11 min read

The Four Questions Your P2P Vendor Must Answer for Each Country

If you run payables or receivables for legal entities in Germany, France, Poland, Belgium or Italy, a PDF-and-OCR invoice process is either already non-compliant or close to it. All five countries have made structured electronic invoices mandatory for domestic B2B trade, or have a mandate phasing in. They use different formats and different transmission networks. The difference that matters most is whether the tax authority sees the invoice before your customer does.

That's why "we support e-invoicing" tells you nothing when you evaluate e-invoicing procure to pay software. You need a separate answer for each country to four questions:

  • Can it receive and validate the mandated structured format as data, without turning it into an image?
  • Can it send that format through the required channel?
  • Does it process the status messages the government or network sends back?
  • Does it archive the legally valid original for the local retention period?

Below you'll find each country's obligations, the software requirements they create and indicative add-on costs. One caveat applies to all of it. These timelines have shifted repeatedly and implementing rules keep arriving, so use the dates here as a planning baseline. Before you commit to a go-live date, get a qualified tax adviser to confirm the current position for each entity.

Advertisement

Clearance Versus Post-Audit: The Distinction That Drives Your Architecture

Europe's mandates follow two broad models. The model you're dealing with matters more than the file format.

Post-audit models (Germany, Belgium) require a structured invoice, but it goes straight from supplier to buyer. The tax authority checks it later, during an audit. Your P2P system has to produce and consume compliant XML and archive it correctly. It never has to wait for government permission.

Clearance or continuous transaction control (CTC) models (Italy, Poland, and France in a decentralized form) put a government platform or a government-certified intermediary in the path of every invoice. In Italy and Poland, an invoice doesn't legally exist until the platform accepts it. The consequences are operational. Outbound billing needs real-time integration and a way to handle rejections. Inbound AP may have to pull invoices from a government system instead of an email inbox. And your three-way match has to work with a government-issued identifier.

The practical rule: in a post-audit country you're running a format-and-connectivity project. In a clearance country you're redesigning a process, so budget and staff it that way.

Five Mandates Compared: Model, Format, Channel and Phasing

CountryModelRequired formatChannelKey phases (confirm with adviser)
GermanyPost-auditEN 16931 formats: XRechnung, or ZUGFeRD/Factur-X from version 2.0.1 (MINIMUM and BASIC-WL profiles excluded)Any agreed channel: email, Peppol, EDI, portalReceive: since January 2025 (all businesses). Issue: from January 2027 if prior-year turnover exceeds EUR 800,000; from January 2028 for everyone
FranceDecentralized CTC plus e-reportingUBL, UN/CEFACT CII, Factur-XCertified platforms (Plateformes Agréées), interconnectedReceive: since September 2026 (all). Issue: since September 2026 for large and mid-size companies; September 2027 for SMEs and micro-businesses
PolandClearanceKSeF structured XML (FA(3) schema)National KSeF platform via APIPhased through 2026, starting with the largest taxpayers in February; relief for the smallest businesses into 2027; penalties deferred during the transition
BelgiumPost-audit (e-reporting planned from 2028)Peppol BIS Billing 3.0 by defaultPeppol networkJanuary 2026 for B2B between Belgian-established VAT businesses
ItalyClearanceFatturaPA XMLSistema di Interscambio (SdI)Live for B2B since 2019; cross-border transaction data reported through SdI since 2022

Multinationals often get the scoping wrong. These mandates generally cover domestic transactions between businesses established in the country. A parent in the US, India or Singapore invoicing a German subsidiary from abroad is usually outside the German domestic mandate. The German subsidiary invoicing a German customer is inside it. Map obligations by legal entity and establishment, not by where headquarters sits.

Germany and Belgium: Format and Network Projects

Germany

Technically, the Germany e-invoicing mandate is the lightest of the five. That's also why companies underestimate it. Since January 2025, every German business has had to be able to receive EN 16931-compliant e-invoices. A plain PDF no longer qualifies as an e-invoice. A ZUGFeRD hybrid PDF does, but only because of its embedded XML, and the XML is the legal record.

Look out for AP tools that accept a ZUGFeRD file, run OCR on the visual layer and throw away the XML. That fails twice: you lose structured data you already had, and you may not be archiving the legally valid version. Ask vendors to demonstrate XRechnung and ZUGFeRD validation against the national CIUS business rules, and storage of the original XML in line with GoBD archiving requirements.

Germany doesn't require Peppol, but it's gaining ground as a scalable channel, especially among organizations that already invoice the public sector. Larger German suppliers lose their PDF fallback in January 2027, so outbound billing should be tested and ready well before year-end.

Belgium

Belgium made Peppol the default channel from January 2026. That makes it the clearest case for Peppol procure to pay capability. Every Belgian-established VAT entity needs a Peppol access point (in practice, a certified service provider), a listing in the Peppol directory, and the ability to send and receive Peppol BIS Billing 3.0. The authorities announced a short initial tolerance period, but fines rise with repeat offenses. Don't plan on leniency.

For P2P, Belgium is mostly a supplier master data problem. You need each counterparty's Peppol participant identifier, and your system should look it up in the directory automatically instead of relying on manual entry. Belgium also plans near-real-time e-reporting from 2028, so pick a provider that can add reporting without a second integration.

France, Poland and Italy: When the Tax Authority Sits in the Middle

France

The France e-invoicing reform sends invoices through certified private platforms (Plateformes Agréées), which exchange invoices with each other and pass data to the tax administration. Since September 2026, every French business has had to be able to receive e-invoices, and large and mid-size companies have had to issue them. SMEs follow in September 2027.

Two obligations go beyond the invoice. The first is e-reporting: transaction data for B2C and international sales, plus payment data for services. The second is a set of mandatory lifecycle statuses, including submitted, rejected, refused and, for services, collected. Your P2P system has to send those statuses back, so approval and payment events must flow out of AP as well as invoices flowing in. Your ERP alone won't make you compliant in France. You need a contract with a certified platform. Your P2P suite either is one, partners with one, or leaves you to integrate one yourself.

Poland

Poland KSeF is pure clearance. When the national platform accepts a structured invoice it assigns a KSeF number, and that number is the invoice's legal identity. On the AP side, purchase invoices from Polish suppliers arrive from KSeF, not by email. Your system needs authenticated API access to fetch them, de-duplication against the PDF courtesy copies some suppliers will keep sending, and matching on the KSeF number. KSeF has defined offline and outage procedures, and your vendor has to support them. A billing run that stops during a KSeF outage is a cash-flow problem.

Italy

Italy's SdI has handled B2B clearance since 2019, so mature vendors should manage it without trouble. The usual gap is cross-border AP. Purchases from foreign suppliers that fall under reverse charge have to be reported to SdI as integration or self-billing documents (document types TD17 to TD19). If your P2P suite processes an invoice from a German supplier and nothing triggers the SdI document, the Italian entity has a reporting gap even though AP looks clean.

P2P Requirements Checklist for Vendor Demos

Use this as a scoring sheet. Have the vendor show each item live for every country you operate in. Slides don't count.

  1. Native structured intake. The system receives XRechnung, ZUGFeRD, Peppol BIS 3.0, FatturaPA, KSeF XML and the French base formats as data, with no OCR. It validates against EN 16931 and the national rules and returns a reason code on rejection.
  2. Channel coverage. A certified Peppol access point, a KSeF API connector, an SdI connection, and either a French Plateforme Agréée or an integration with one. Find out which are native, which come through a partner and which you'd have to build.
  3. Status round-tripping. Clearance acceptances and rejections, plus French lifecycle statuses, update the invoice record and trigger workflow. A rejected outbound invoice must never post to the ledger as issued.
  4. Government identifiers in matching. KSeF numbers, SdI identifiers and Peppol IDs are stored, searchable and carried through to payment.
  5. Supplier and customer master data. Fields for Peppol participant IDs, SdI destination codes, French SIREN and routing data, and Polish tax IDs, with directory lookups.
  6. Compliant archiving. The legal original is kept for the local retention period, which runs from roughly five to ten years depending on country and document type, with audit trails that meet local rules.
  7. Cross-border triggers. Italian integration documents for foreign purchases, and French e-reporting for transactions outside the e-invoicing scope.
  8. Vendor-owned regulatory change. A contractual commitment to update schemas and rules when authorities publish new versions, with a defined notice period.

Item 8 is where buyers get burned. KSeF schemas, French specifications and XRechnung versions all change regularly. If the vendor bills each regulatory update as a project, your compliance cost has no ceiling.

What the Add-Ons Typically Cost

Few P2P suites cover all five countries natively. Most buyers end up combining one of three things. The first is a P2P platform such as Coupa, SAP Ariba, Basware or Ivalua. The second is an ERP tax-compliance module, such as SAP Document and Reporting Compliance or Oracle's localization features. The third is a dedicated compliance network such as Sovos, Pagero, Comarch, Edicom, Avalara or Unifiedpost. The figures below are typical 2026 market ranges. They vary widely by contract, volume and region, so confirm current pricing with each vendor.

Cost componentTypical 2026 range (USD)What drives it
Per-document transaction fees$0.10 to $1.00 per invoiceVolume tier, inbound vs. outbound, clearance vs. Peppol
Platform or country subscription$3,000 to $25,000 per country per yearNumber of entities, e-reporting scope, SLA level
Small-business Peppol access point$30 to $400 per monthDocument bundle size, whether an ERP connector is included
ERP and P2P integration (one-time)$15,000 to $100,000+ per countryERP customization, number of instances, clearance complexity
Archiving add-on$2,000 to $15,000 per yearRetention period, storage volume, jurisdictions

Hypothetical worked example: a distributor has entities in Germany, Poland and Belgium, runs a single SAP S/4HANA instance, and handles 60,000 inbound and 40,000 outbound invoices a year. At about $0.30 per document, transaction fees come to roughly $30,000 a year. Three country subscriptions at $8,000 to $15,000 each add $24,000 to $45,000. One-time integration might run $40,000 to $120,000, with Poland taking the largest share because KSeF retrieval and outage handling are the most work. That puts a realistic first-year budget at about $95,000 to $195,000, with ongoing costs of roughly $55,000 to $75,000 a year before archiving. Adding France or Italy would push both figures up.

The biggest hidden cost is running several providers. A different vendor in each country can look cheaper on the price sheet, but you pay for it in extra integrations, contracts and status-mapping logic. If your group has three or more mandated countries, a single multi-country network usually comes out ahead on total cost.

ViDA, Wider Mandates and the Decision Rule for Your Shortlist

The EU's VAT in the Digital Age (ViDA) package, adopted in 2025, is the main reason to treat this as a platform decision rather than a string of country patches. Under the ViDA e-invoicing rules, member states can introduce domestic mandates without first seeking EU approval, and more of them are expected to. From July 2030, intra-EU B2B supplies will require structured e-invoices based on EN 16931, with near-real-time digital reporting. Domestic systems are expected to converge on that model over the following years. Spain, Croatia and Greece are among the countries already moving. Outside the EU, India, Saudi Arabia, Malaysia, Mexico and others run or are rolling out their own programs, so a provider with only European coverage may not be enough for a global group.

Red flags in a vendor response:

  • Compliance delivered by OCR of PDFs, or a "structured" option that turns out to be a PDF with metadata.
  • No certified Peppol access point and no named, contracted partner.
  • Regulatory updates priced as change requests.
  • No live demo of a clearance rejection flowing back into AP or AR workflow.
  • A France answer that doesn't name a specific Plateforme Agréée.

The decision rule: if you operate in one post-audit country only, a Peppol-capable P2P suite or a low-cost access point is enough. If you have any clearance country, or three or more mandated countries, shortlist providers that cover all of them on one network with status round-tripping, and score them against the checklist above. Start by listing every legal entity with its establishment status and invoice volumes. Then have your tax adviser confirm the current deadlines for each one before you issue an RFP.

Frequently asked questions

Can we keep emailing PDF invoices to customers in Germany?

For now, in some cases. The transition rules generally allow other invoice formats through the end of 2026 for most businesses, and through the end of 2027 for businesses with prior-year turnover at or below EUR 800,000. After that, domestic B2B invoices must be structured EN 16931 e-invoices such as XRechnung or ZUGFeRD. A German tax adviser can confirm how the rules apply to your entity.

Do we need Peppol for every EU country?

No. Belgium uses Peppol as its default channel, and some German businesses use it by choice. Poland requires its national KSeF platform, Italy requires SdI, and France routes invoices through certified platforms that connect to each other. A multi-country provider should cover all of these, with Peppol as one channel among several.

Is our non-EU parent company affected by these mandates?

Usually not directly for invoices it issues from abroad, because the domestic mandates generally apply to businesses established in the country concerned. Your EU subsidiaries almost certainly are affected, and ViDA brings intra-EU B2B supplies into scope from 2030. Have a tax adviser confirm establishment status and obligations for each legal entity.

Which country should we tackle first if we operate in several?

Start with any clearance country where you issue invoices, such as Poland or Italy. A rejected or blocked invoice there stops billing outright. France comes next because of its platform contract and lifecycle-status requirements. Post-audit countries like Germany and Belgium are mostly format and connectivity work, but they still have fixed deadlines and should be scheduled, not left until last by default.

Written by the Port Cloud Pro editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.