What French Accountants Will Actually Do All Day Under the E-Invoicing Mandate

France’s e-invoicing reform is built around the ideal case: a supplier sends a valid Factur-X, it travels through a Plateforme Agréée (PA), and it arrives in the buyer’s accounting system. The tax data is reported on the way. From September 2026, most French B2B invoices will follow this path.

But everyone who works in accounts payable or in a cabinet comptable knows where the working hours really go: not to the 95 percent of invoices that flow through, but to the 5 percent that do not. With a large invoice volume, 5 percent is a daily queue of problems.

The platforms are built for the normal flow. The problem cases land on a human.

What the problem cases look like

They fall into a few recurring situations:

A rejected outgoing invoice. The file bounces back with an error code (for example, BR-CO-15, a VAT category problem, or a wrong date format). The payment run is tomorrow, and the person who can regenerate the invoice from the source system is on holiday. The PA reports the rejection; it does not repair the file.

A suspicious incoming invoice. In a Factur-X, the embedded XML is the legally valid part, not the PDF that a human reads. If the totals or dates differ between the two, the accounting system books the XML. Someone has to see both layers before approving the payment.

A format mismatch. EN 16931 invoices exist in two syntaxes: CII (inside Factur-X) and UBL (used on Peppol). Real business mixes them. A client’s Belgian buyer wants UBL, but the file is CII. Or a UBL file must become a Factur-X.

A document the platform does not handle. The reform covers invoices. But large buyers are starting to ask for structured purchase orders too, in the Order-X format (the purchase-order version of Factur-X). Many platforms do not support these documents yet.

None of this is rare. Multiply it by the invoice volume of a mid-sized company, or of an accounting firm with many clients, and it becomes daily work.

Fix the file, do not regenerate it

The most expensive habit is treating every broken file as a round trip: send it back to the supplier, wait, receive it again, check it again. In most rejections, the real problem is one single field.

This is why file editing is the most useful new development in browser tools. An online Factur-X editor opens a rejected invoice as a simple form. You correct the wrong field (the VAT category, the missing buyer reference, the date), and download a valid, revalidated file. No XML editing, no round trip to the supplier.

Combined with a validator that runs the official EN 16931 and French rules, the workflow becomes short: validate, read the errors in plain language, fix the field, download. For the team handling these cases, this is the difference between a queue that empties every day and one that keeps growing.

The same browser tools cover the other daily tasks the platforms leave to you: converting between CII and UBL, displaying machine-only XML as a readable invoice, extracting attachments, and creating credit notes that correctly reference the original invoice.

The Order-X gap

The purchase-order request deserves a special mention, because it surprises many teams. Order-X uses the same idea as Factur-X: a readable PDF with structured XML inside. Some large buyers already require it from suppliers, before most platforms support it. But purchase orders are outside the regulated invoice flow anyway, so no platform is needed: a browser-based Order-X creator, with matching validation, answers the request today.

A workbench in front of the pipeline

Regulated transmission of domestic French B2B invoices runs through accredited platforms, and businesses in scope will contract with one. Around that pipeline, a second layer is emerging: a workbench where files are checked, repaired, converted and created, before and after they enter the exchange network. The two layers do different jobs, and heavy users need both.

This layer is also becoming conversational. An AI assistant accepts the whole range of tasks in plain language: “validate this file against the French rules”, “fix the VAT breakdown and give me a valid version”, “convert this to UBL”. One instruction replaces a dozen tools, which matters most for heavy users who see a different problem every hour.

The reform will automate the normal flow. The professionals who win in 2026 and 2027 will be the ones who also automated the exceptions.

---

---