FR EN
Testing e-invoicing software: formats, flows and France's 2026 reform
4 October 2026 Oussama Belakhdar 7 min read

Testing e-invoicing software: formats, flows and France's 2026 reform

Since 1 September 2026, every company established in France must be able to receive electronic invoices. For a software vendor or a finance department, an invoice is no longer a PDF sent by email: it is a structured flow, with formats, statuses and rejections.

Key takeaways
  • The timeline: reception mandatory for all companies since 1 September 2026; issuing mandatory for large and mid-sized companies on the same date, and for SMEs and micro-businesses on 1 September 2027.
  • Three structured formats: Factur-X, UBL and CII, transmitted through an approved platform.
  • Calculation remains the core of testing: VAT, rounding, discounts, credit notes.
  • Rejections are tested as much as successes: a rejected invoice must be explained and correctable.

Oussama Belakhdar, QA architect and founder of AutomationDataCamp, has led testing projects on invoicing software. This page describes our priority checks for a software vendor, a platform or a finance department affected by the French reform. No client is named.

What do the reform figures say?

137 Approved platforms on the French tax administration's list for transmitting e-invoices. data.gouv.fr — DGFiP list of approved platforms 2026
€4.5 bn Expected productivity gains from e-invoicing for the 1.5 million SMEs that still use paper invoices. French Senate — 2026 finance bill report
€20–26 bn VAT missing from public finances every year, a gap the reform aims to reduce. French Senate — 2026 finance bill report

Figures published by the organisations cited, not results of our own engagements.

Why is an e-invoicing chain tricky to test?

  • An invoice exists in several forms that must say the same thing: the data in the software, the structured XML file and, for a hybrid format such as Factur-X, the readable PDF.
  • The flow goes through at least one approved platform, often two (the sender's and the recipient's), each with its own delays, checks and status messages.
  • Tax edge cases are numerous: several VAT rates on one invoice, reverse charge, exemptions, rounding per line or on the total, partial credit notes, currencies.
  • The roll-out is staggered: until 1 September 2027, an SME supplier may still issue outside the platforms, so the software has to handle both channels in parallel.

What we test first in invoicing software

  1. Amounts: VAT per rate, line and invoice-level discounts, fees, down payments, credit notes, rounding.
  2. Generating each format (Factur-X, UBL, CII) and validating it against its schema and business rules.
  3. Consistency between XML and PDF: same number, same amounts, same mandatory mentions.
  4. Mandatory mentions, including those added by the reform, for both sender and recipient.
  5. Life cycle: submitted, received, rejected, accepted, paid, and forbidden transitions (paid before received).
  6. Rejections and duplicates: number already used, recipient not found in the directory, non-compliant file; each rejection is explained and the invoice can be corrected.

Timeline, platforms, formats: the reform from a tester's point of view

The timeline. Since 1 September 2026, all companies established in France must be able to receive electronic invoices. Issuing and e-reporting became mandatory on that date for large and mid-sized companies, and will be for SMEs and micro-businesses on 1 September 2027. Testing follows this timeline: receiving for everyone, issuing according to company size.

Approved platforms. Invoices between companies go through a platform approved by the tax administration (formerly called PDP), whose list is published by the DGFiP. For a software vendor, each partner platform is an integration to test: authentication, submission, acknowledgements, statuses, errors.

Formats: Factur-X, UBL, CII and the EN 16931 standard. All three formats rely on the semantic model of the European standard EN 16931, drawn up following Directive 2014/55/EU on e-invoicing in public procurement. Factur-X, published by the French FNFE-MPE and its German counterpart, combines a readable PDF with an embedded XML file; UBL and CII are purely structured.

E-reporting. Transactions that do not give rise to an e-invoice between companies established in France, such as sales to consumers or international transactions, are reported to the tax administration as data. These flows are tested like invoices: completeness, amounts, rejections.

Test the file, not just how it looks

An invoice can display correctly and still be rejected by the platform. Our tests therefore target the file itself: validation against the XSD schema, then against the standard's business rules (often expressed in Schematron), then a field-by-field comparison with the expected data. A library of reference invoices (multiple rates, partial credit note, reverse charge, foreign currency invoice) is replayed in every release of the software.

An example test case: the cent that gets an invoice rejected. EN 16931 business rules are published as Schematron files by the European Commission, and three of them catch most calculation defects: BR-CO-10 (the sum of the line net amounts equals the invoice net total, BT-106), BR-CO-15 (the total with VAT, BT-112, equals the total without VAT, BT-109, plus the total VAT, BT-110) and BR-DEC-13 (the total VAT has at most two decimals). A typical test builds an invoice with several lines at 20% and 5.5% VAT, a line discount and amounts chosen so that rounding each line and rounding the total give results one cent apart. The software must produce a file that passes all three rules, and the PDF of a Factur-X invoice must show the same totals as the XML. This is the kind of defect that looks harmless on screen and only appears when the platform rejects the file.

The second part concerns the exchanges. The platform is simulated in automated tests to trigger a rejection, a delay or an unexpected status at will; an end-to-end test on the partner platform's acceptance environment, when it offers one, then validates the real integration before go-live.

How do we organise testing for invoicing software?

  1. Start from tax and cash risks. A VAT error or a blocked invoice costs more than a display defect: calculations, formats and statuses come first.
  2. Test flows at API level. Submission, statuses and rejections are checked with API tests; Playwright covers entering and viewing invoices, k6 covers month-end peaks, all triggered on every commit in your CI.
  3. Fictitious test invoices. Fictitious companies, identifiers and amounts, generated for every run.
  4. AI, with a review. An assistant helps produce invoice variants and rejection cases. The review follows our 7-question checklist. A concrete example is in our case study: from a PDF specification to Playwright tests.

Where should you start?

The first workstream is often the library of reference invoices: without it, every change to the software has to be retested by hand.

A QA audit reviews your application: a written assessment, a test strategy adapted to your industry and a costed action plan, in 5 days, for €1,000 excl. VAT as a fixed fee. Delivered remotely, in English or French, for companies in the US, the UK, Canada, Australia, Europe, the Gulf and the Nordics. The first scoping session is free.

See the QA audit at €1,000 excl. VAT

Frequently asked questions about e-invoicing testing

When does e-invoicing become mandatory in France?

Reception has been mandatory for all companies since 1 September 2026. Issuing is mandatory on the same date for large and mid-sized companies, and on 1 September 2027 for SMEs and micro-businesses.

What should be tested first in e-invoicing software?

Amount calculation (VAT, rounding, credit notes), generation and validation of each format, consistency between structured data and the readable invoice, and the handling of rejections.

Should each format, Factur-X, UBL and CII, be tested?

Yes, for every format your software issues or receives. All three rely on the same semantic model (EN 16931), but their syntax differs: a field that is correct in UBL can be misplaced in CII. Each format is validated against its schema and business rules.

How can you test without sending real invoices?

By simulating the approved platform in automated tests, then using the partner platform's acceptance environment, when it offers one, for end-to-end tests, with fictitious companies and amounts.

How much does a QA audit cost at AutomationDataCamp?

The QA audit and diagnosis costs €1,000 excl. VAT as a fixed fee, over 5 days: a written assessment, a test strategy and a costed action plan. The first scoping session is free.

Other industries: Healthcare · Finance · Blockchain · Logistics · E-commerce · Document management. All industries.

Page signed by Oussama Belakhdar, written with the help of AI. Regulatory references link to the official sources above; they are not legal advice.

Related articles