Key takeaways
- France's PPF recorded a 43.5% invoice rejection rate on 10 September 2026 — driven by data quality failures, not format issues
- Poland's centralised KSeF experienced phantom invoices and authentication errors during peak loads
- Both mandates prove that e-invoicing success depends on master data quality, ERP integration depth, and edge-case process design — not format compliance alone
- Poland's penalty grace period ends 1 January 2027 under current law (draft bill UD477 proposes deferral to 2028)
- Organisations preparing for upcoming mandates should audit master data and test full invoice lifecycle handling before go-live
The Numbers From France's First Month
France's e-invoicing mandate went live on 1 September 2026 for large and intermediate-sized enterprises. The scale was clear from day one — but so were the problems.
On 10 September 2026, the Public Invoicing Portal (PPF) received 924,040 invoice flows in a single day. Of those, 402,423 were flagged as non-compliant. That is a 43.5% rejection rate — the highest daily figure since the mandate began. The source is AIFE's official monitoring data.
By mid-October, most approved platforms (Plateformes Agréées) had pushed their compliance rates above 90%. The gap closed fast — but only after real invoices failed in production. By 4 October, 75% of VAT-declaring businesses had designated a receiving platform. The French Ministry of the Economy reported more than 20 million e-invoices exchanged worth over €70 billion in the first month. And Minister David Amiel confirmed no sanctions would be imposed on businesses during 2026.
That grace period bought breathing room. The underlying data problems, however, were entirely real.
Why the Rejections Happened (It Wasn't Format)
The natural assumption is that a 43.5% rejection rate on go-live means businesses got the XML wrong. They didn't. Format compliance was not the primary problem. Data quality was.
Here's what actually caused the failures:
Incomplete PPF directory at go-live. Trading partners had not yet registered or designated a receiving platform. Invoices were technically valid but had nowhere to route. This is a master data problem, not a format problem.
Missing SIREN numbers. French business identifiers were absent from invoice payloads. The PPF requires these for routing — without them, the invoice is rejected regardless of its structural compliance.
Invoice lifecycle status misuse. Businesses and platforms misused the Refusée (rejected) status code, treating it as a correction mechanism rather than a genuine refusal. This polluted status tracking and caused downstream reconciliation failures.
Missing mandatory fields. Transaction type codes, delivery addresses, and other mandatory data elements were absent. These fields exist in the specification — but many ERP configurations simply didn't populate them.
The lesson is uncomfortable: France's format specification (Factur-X, based on EN 16931) was well documented and widely implemented. The failures came from the data that feeds the format, not the format itself.
Poland's Different Architecture, Same Underlying Problem
Poland's KSeF (Krajowy System e-Faktur) went live on 1 February 2026 for large taxpayers with annual turnover exceeding PLN 200 million. Phase 2 followed on 1 April 2026, extending the mandate to all remaining VAT-registered taxpayers.
Where France uses a decentralised Y-model — the supplier sends through a Plateforme Agréée, the PPF validates and forwards to the buyer's platform — Poland built a fully centralised hub. Every invoice passes through KSeF. There are no intermediary platforms. The Ministry of Finance operates the entire infrastructure.
Different architecture, same category of problem:
Phantom invoices. Invoices received a valid KSeF number but remained invisible to the buyer. The invoice existed in the system — it just never appeared in the buyer's ERP. This is an integration failure, not a submission failure.
ERP authentication failures during peak load. Businesses reported 401 and 504 errors when their ERP systems attempted to authenticate with KSeF during high-volume periods. If your ERP can't authenticate, it can't submit — and you have no invoice.
Incorrect buyer VAT ID. In Poland's centralised model, an incorrect buyer VAT ID doesn't just cause a routing error. It requires a full correction cycle — a formal correcting invoice, not a simple amendment. This is an expensive mistake in a high-volume environment.
Under current law, Poland's penalty grace period ends on 1 January 2027. However, the Ministry of Finance has published draft bill UD477 (22 September 2026) proposing to defer penalties to 1 January 2028. That bill has not yet been enacted — the legislative process is ongoing. If your planning assumes penalties start in 2027, you're aligned with the law as it stands today.
The Real Lesson — E-Invoicing Is an ERP Integration Project
Both mandates went live successfully. Both produced high failure rates in the first weeks. And in both cases, the failures had almost nothing to do with the format specification.
Four things actually determine whether your e-invoicing implementation succeeds:
Master data quality. Business identifiers, trading partner registrations, platform designations. If your master data is incomplete, your invoices fail before they're validated.
ERP integration depth. A bolt-on that generates compliant XML is not enough. Your ERP needs to handle submission, receipt of status updates, error responses, and correction cycles — all automatically.
Invoice lifecycle status handling. Every e-invoicing regime defines a set of statuses (sent, received, accepted, rejected, corrected). Your ERP must map these to its own workflow. Misuse of a single status code — as France demonstrated — cascades into reconciliation failures.
Edge-case process design. What happens when a buyer hasn't registered? When authentication fails during a batch run? When a correction requires a full re-issuance? These scenarios don't appear on format specifications. They appear in production.
None of these appear on a format specification. All of them are ERP integration work.
What This Means for Your Organisation Right Now
If your organisation is preparing for an upcoming e-invoicing mandate — Germany from January 2027, the UAE, Saudi Arabia, or any of the deadlines landing in 2027 — the France and Poland experience offers a clear action list:
Audit your master data before you audit your format. Business identifiers, platform registrations, and trading partner records are where the failures happen. Start there.
Map invoice flows, not just invoice templates. Submission is one step. Receipt confirmation, status tracking, rejection handling, and correction cycles are the rest. If your ERP only does the first step, it's not ready.
Test invoice status handling in your ERP. Simulate the full lifecycle: sent → received → accepted. Sent → rejected → corrected → resubmitted. Sent → pending → timed out. If your ERP doesn't handle all three paths, you will discover this in production.
Taxually e-Invoicing handles the submission, confirmation, error response, and correction cycle — so your ERP doesn't have to build it from scratch. Request a demo to see how it works with your systems.
Facts verified as of 16 November 2026. This article is for informational purposes only and does not constitute legal or tax advice.
Read the full November 2026 indirect tax briefing
How Taxually Handles This
Taxually e-Invoicing automates the full invoice lifecycle — submission, status tracking, error handling, and corrections — across France, Poland, Germany, and 50+ other jurisdictions. One integration, every mandate.
Frequently asked questions
Is France's e-invoicing mandate fully enforced from 1 September 2026?
The mandate is live and legally binding for large and intermediate-sized enterprises from 1 September 2026. However, the French government has confirmed that no penalties will be imposed on businesses during 2026. SMEs and micro-enterprises must begin issuing e-invoices from 1 September 2027.
Do penalties apply for KSeF non-compliance in 2026?
No. Under current law, penalties for KSeF non-compliance begin on 1 January 2027. A draft bill (UD477, published 22 September 2026) proposes deferring penalties to 1 January 2028, but this has not yet been enacted.
Does the France mandate apply to foreign companies selling to French buyers?
Yes. Any business established in France or with a French VAT registration that issues B2B invoices to French buyers must comply. Foreign businesses selling into France may need to designate a Plateforme Agréée for receiving invoices.
What is the difference between France's decentralised model and Poland's centralised model?
France uses a Y-model: invoices flow from supplier through a Plateforme Agréée to the PPF and on to the buyer's platform. Poland uses a centralised hub where every invoice passes through KSeF, operated by the Ministry of Finance.
Which format does Germany use for mandatory e-invoicing from 2027?
Germany accepts XRechnung (pure XML) and ZUGFeRD (hybrid PDF/XML), both compliant with EN 16931. Businesses with 2026 turnover exceeding €800,000 must issue e-invoices from 1 January 2027.













