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.
- 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 worked on software testing projects in this industry. This page sums up what we check first. Our clients are not named.
Industry figures
Figures published by the organisations cited, not results of our own engagements.
What makes testing hard
- The same invoice exists in several forms (data, PDF, XML) that must stay consistent.
- Exchanges go through third parties (approved platforms) with their own delays and statuses.
- Edge cases are numerous: multiple VAT rates, rounding per line or per total, partial credit notes, currencies.
The scenarios we test first
- Amount calculation: VAT per rate, rounding, discounts, fees, credit notes.
- Generating each format and validating it against its schema.
- Consistency between the structured data and the human-readable invoice.
- Lifecycle and statuses: submitted, received, rejected, accepted, paid.
- Rejections: missing mandatory information, duplicate number, unknown recipient.
The framework to know
France's e-invoicing reform. Reception mandatory for all companies since 1 September 2026. Issuing and e-reporting mandatory on that date for large and mid-sized companies, and on 1 September 2027 for SMEs and micro-businesses.
Approved platforms. Business-to-business invoices go through an approved platform, in a structured format (Factur-X, UBL or CII).
Our method
- Start from the risks. We rank features by the impact and likelihood of a defect, then test first what would cost the most.
- Automate what comes back in every release. API tests for rules and integrations, Playwright for user journeys, k6 for load, all wired into your CI.
- Controlled test data. Fictitious data sets, created for each run, never copied from production.
- AI with a review. An assistant speeds up writing scenarios and tests; every generated test is reviewed against our 7-question checklist. See our case study: from a PDF specification to Playwright tests.
Start with an audit
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
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.
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

AI & ML for test automation
What AI concretely changes in test automation.
Read more : AI and ML for test automation
Integrating Automation into CI/CD
Jenkins, GitLab CI, GitHub Actions — practical examples.
Read more : Integrating Automation into CI/CD