France, Poland, and Germany are mandating e-invoicing - each in a completely different way.

See what each country requires Calculate your team's cost
4–7+
e-invoicing regulatory updates per year across a typical 4-6 country EU footprint
Vertex Regulatory Tracker Q4 2025
85%
of finance team time during an active rollout goes to coordination and triage, not execution
Accenture 2024
15–25%
of invoices fail validation in the first 30 days after go-live when preparation was unstructured
IOFM / SoftCo 2026
270–430h
internal preparation hours per mandate per entity, before ERP configuration begins
Ardent Partners / Gartner 2024-26
Internal preparation cost

How much does getting ready actually cost your team?

Select your countries, ERP, and team rate. The calculator estimates the internal preparation work your team will absorb before any external vendor or consulting costs.

1
Nobody budgets for this. Everyone pays it.
Mandate readiness doesn't disappear when it's unplanned - it gets absorbed as coordination, research and post-go-live firefighting.
-- Structured
-- Reactive
Grey bar: full cost spectrum  ·  Blue band: your team's estimated range  ·  Hover to read values
Your internal cost (typical midpoint) --
Estimated readiness hours
--
Select a mandate above

We track the entire European mandate landscape and translate it into what it means for your team.

France: legislation
France: official portals
Poland: legislation
  • Act of 9 May 2024, Dz.U. 2024 poz. 852 - KSeF mandatory phases (Feb and Apr 2026)
  • VAT Act Art. 106ga - B2B e-invoicing scope and exclusions
  • VAT Act Art. 106j - correction invoice (Faktura korygujaca) rules
  • VAT Act Art. 106na - KSeF platform legal basis
  • VAT Act Art. 106ni - penalty provisions (up to 100% of VAT)
  • VAT Act Art. 106nn - archiving obligations within KSeF (10 years)
  • Council Implementing Decision (EU) 2022/1003 - EU derogation permitting KSeF ahead of ViDA
Poland: official portals
Germany: legislation
Germany: official sources
Format and interchange standards
  • EN 16931-1 - European e-invoice semantic data model (CEN/TC 434)
  • XRechnung - German CIUS on EN 16931 (KoSIT, IT Planning Council)
  • Factur-X - Franco-German hybrid PDF/XML format (FNFE-MPE, AFNOR, FeRD)
  • FA (Faktura) schema v3 - KSeF proprietary XML, Polish Ministry of Finance
  • UBL 2.1 - OASIS Universal Business Language standard
  • Peppol BIS Billing 3.0 - OpenPEPPOL business interoperability specification
Cross-referencing platforms and registries
Industry research
  • Vertex Regulatory Tracker, Q4 2025 - mandate change frequency analysis
  • Accenture: The Finance Function Transformation, 2024 - coordination and triage time benchmarks
  • IOFM / SoftCo: AP Processing Benchmark Survey, 2026 - go-live exception rate data
  • Ardent Partners: AP Metrics That Matter, 2024-26 - ERP implementation hour benchmarks
  • Gartner: ERP Complexity Benchmarks, 2024-26 - ERP implementation multipliers
Belgium, Romania, Italy, Denmark, Netherlands, Sweden, Spain, and Finland are covered with equivalent primary legislation and official portal sources in their individual compliance map entries.

What getting ready actually requires.

France: new vendor to onboard, master data to clean, September 2026

+
  • Selecting a certified PDP platform is a full vendor procurement - plan 6-12 weeks through InfoSec and legal before integration can even begin
  • Your ERP connector must be built and validated against the PDP API; the standard "send invoice" process does not work until this is done
  • SIRET master data for every French establishment must be verified and corrected - often months of cleanup work
  • Finance Systems, Tax, and Finance Ops each have distinct preparation tasks with no natural coordinator between them

Poland: government API already live, penalties from August 2026

+
  • KSeF uses FA-3, a government-specific XML schema - no standard ERP connector covers it out of the box, custom mapping required
  • Every invoice is validated in real time by the government platform; a rejection means the invoice does not legally exist yet
  • Your ERP needs a dedicated API connection per company NIP, authenticated with OAuth2 to the KSeF system
  • If your Polish entity is not yet connected and tested, the penalty window opens in August 2026

Germany: two separate obligations, ERP output often not yet correct

+
  • The receiving obligation has been live since January 2025 - many ERP systems were never configured to ingest structured XML from suppliers
  • Outbound XRechnung or ZUGFeRD output is required by January 2027 - this is an ERP output configuration change, not a platform selection
  • There is no central platform: exchange is peer-to-peer, which means every counterparty relationship relies on your ERP being configured correctly
  • Many teams discover their current setup outputs a PDF attachment - not a machine-readable XML - only when a customer rejects an invoice
See the full breakdown for each country
Our services

One track, two stages. Your team gets to ready - and stays there.

Our service is a structured engagement. We enable your finance teams so you meet e-invoicing mandates - continuously as mandates develop.

→
→
Example scope

France PDP Readiness Sprint

France PDP  ·  September 2026 (large companies and ETIs)  ·  one legal entity

Finance Systems Owner

What your ERP needs to produce and accept, which master data fields need to be corrected before go-live, what to require from your platform vendor, and a week-by-week action sequence from now to the deadline.

Tax / Compliance

Which entities and transactions are in scope, what the format requirements mean for your VAT reporting, how corrections and cancellations work, and what needs to be retained for audit.

Finance Ops

What to expect in the first 30 days after go-live, how to handle invoices that fail validation, who escalates what, and how to monitor for exceptions before they become a backlog.

Local Partner Accountability

A structured question set for your accounting partners in each country, what they need to confirm and by when, and a clear record that it was done - not an email chain.

Fixed scope Fixed fee 50% on start · 50% on delivery Source-linked with snapshot dates
Learn more about our services
Who is this service for?

You're holding the full picture. Nobody else is.

Getting ready for an e-invoicing mandate is not one task. It is six parallel workstreams, across every entity in your footprint, each requiring time and internal effort to coordinate.

VP Finance Ops  /  Group Controller E-invoice compliance orchestration
↕
Finance
Systems
↕
Tax /
Compliance
↕
AP /
Inbound
↕
AR /
Outbound
↕
Archiving
& Audit
↕
Local
Partners
France entity Poland entity Germany entity + every other entity in scope

Finance Systems configures the ERP. Tax interprets the mandate. Finance Ops handles go-live exceptions. AP and AR change how invoices move. Archiving must store them correctly. And in each country, the local accounting partner has it covered - on whose timeline, confirmed how? You are the one who needs to turn all of that into a single shared plan before the deadline.

Tell us about your mandate footprint. We come back with a frank read of where you stand.

Get in touch
FAQ

Questions we hear most.

Not answered here? Email directly.

Several EU countries have passed laws requiring companies to use structured electronic invoice formats instead of PDF. The specifics vary significantly by country. France and Poland use clearance platforms: invoices must be validated by a government or certified platform before they reach the recipient, so any data error stops the invoice from going through. Germany and Belgium require structured formats exchanged directly between trading partners, with no central government platform. Each country has its own technical format, its own registration requirements, and its own timeline for when companies must start receiving and when they must start issuing. France, Poland, Germany, Belgium, Romania, and Italy all have active or imminent mandates affecting B2B transactions.
No. einvoiceops provides operational readiness support - structured work packets and action sequences for internal preparation. We do not interpret tax law, give compliance opinions, or confirm that your organisation is compliant. All work packets are source-linked to official sources and include a clear disclaimer. For tax or legal interpretation, engage a qualified advisor.
A work packet per function in your finance team - Finance Systems Owner, Tax/Compliance, Finance Ops. Each covers: what the mandate means operationally, a T-minus action sequence to the deadline, which systems and fields are affected, what you need from other teams, and a partner accountability module for your local accounting partners. Everything is source-linked with a snapshot date.
Your platform vendor handles the connection to the government network and the technical exchange format. They do not configure your ERP to produce compliant output, clean your master data, coordinate the preparation work across your internal teams, or confirm that your local accounting partners are ready. Those are internal tasks your vendor cannot do for you. They are what breaks at go-live when they have not been done.
Both the sprint and the ongoing coverage are fixed fee - no day rates, no hourly billing. The sprint is scoped to your EU entity footprint and priced per the number of countries and entities in scope. Coverage is billed quarterly. Get in touch with your countries and ERP and we will come back with a clear number upfront.

Tell us your footprint. Get back a frank read of where you stand.

Share your countries, your ERP, and where you stand. We come back with a clear picture of what your situation requires - in writing, within 48 hours.

einvoiceops provides operational readiness support and is not a tax advisor, legal advisor, or compliance authority. All work packets are informational and operational planning aids only. Customers remain responsible for all compliance decisions and their execution. Confirm regulatory applicability with a qualified advisor where required.