France's PPF goes down from 10 September. Here's what actually stops.

France’s public invoicing portal goes into a maintenance window tomorrow. From 13:00 CEST on 10 September 2026 (12:00 BST) the PPF production environment takes a certificate update, and no file transfers to or from PPF production are to occur while it runs.

Note what has not been said. The notice is scheduled against 13:00 CEST on 11 September, but the authorities have not confirmed an exact end time, and the platforms relaying it say they will pass on confirmation when they get it. Treat the end as unknown rather than as a 24-hour bound you can plan a batch window around.

Nine days after the reception obligation went live, that is a bracing piece of scheduling.

Before anyone reaches for the contingency plan, it is worth being precise about what this touches. It is less than the headline suggests, and it is not confined to one provider’s customers.

This is State infrastructure, not a vendor outage

The PPF is run for the French State. Every approved platform connects to the same production environment, so a window on that environment is a window for all of them. If you are in scope in France, this applies to you whichever platform you signed with.

What it does not mean is that French invoicing stops for a day.

The PPF you may still have in your head, the one that carried invoices between businesses, was cancelled in October 2024. AIFE now describes the portal’s job as “la fonction d’annuaire, permettant le routage des factures, et de celle de concentrateur pour la transmission des données”: a directory that makes routing possible, and a concentrator that carries data to the administration.

Read that carefully. The directory makes routing possible. It does not perform it. Under article 289 bis of the CGI, invoices are issued, transmitted and received through approved platforms, and they travel platform to platform. They do not transit the PPF.

So the invoice you send to a French customer tomorrow afternoon has no reason to stop moving.

What actually pauses

The traffic that pauses is the traffic between the platforms and the State:

• Directory synchronisation. The annuaire is fed by the platforms and published back to them. That exchange is what stops.
• The concentrator. Invoice data destined for DGFiP, and the e-reporting flows for transaction and payment data, queue up rather than land.

Everything downstream of that stays where it was. Your invoice is still valid, your customer still owes you, and your VAT deduction is unaffected. DGFiP says so directly: a temporary e-reporting difficulty “ne remet pas en cause la validité des factures, le paiement des opérations concernées ou la poursuite de l’activité”.

DGFiP already wrote the runbook

This is the part most teams have not read. When DGFiP published its guide pratique de démarrage au 1er septembre 2026, it included a question that anticipates precisely this situation: what to do when the failing component is a tool provided by the State, naming the directory and the concentrator.

The answer is unusually candid. The system is built so that a temporary directory outage does not, on its own, block invoicing. Platforms may fall back on directory data they retrieved earlier and on the technical addresses already in use for exchanges, Peppol addresses included where they are available and relevant.

On data that cannot be transmitted, the instruction is to hold it rather than drop it. Keep the data, document the incident, transmit as soon as the difficulty is lifted, and regularise the gap. DGFiP is explicit that the business is not expected to fix a public tool itself. It is expected to show it noticed, that it limited the damage, and that it did not use the outage as cover for drifting out of the regime.

That last clause is the one to take seriously. The tolerance approach DGFiP announced in July rests on demonstrable good faith, and the penalties for the reception obligation carry no first-offence relief. Evidence is the currency. A dated note in your incident log costs nothing tomorrow and is worth a great deal in eighteen months.

What to check in Dynamics 365 F&O

The practical exposure in an F&O estate is not the invoice. It is the queue.

Check how your integration handles a channel that accepts nothing for an open-ended stretch. If submissions to your platform’s PPF-bound flows fail, do they retry with backoff, or do they exhaust their attempts overnight and land in a failed state nobody reviews on a Friday? A batch job that burns through its retries against a scheduled outage produces a pile of manual reprocessing, and it produces it silently.

The absent end time makes this sharper. A retry policy sized to a known 24-hour window is a guess, and it fails closed if the certificate work overruns.

Three things worth doing before 13:00 tomorrow:

1. Confirm with your platform whether its PPF-bound flows queue or reject during the window, and whether your B2G traffic is in scope.
2. Look at retry and timeout behaviour on the relevant batch jobs. Widen the retry window rather than let it expire inside the outage.
3. Note the window in your compliance log, with the times and the notice you acted on.

One more thing, about how you found out

I went looking for this window on impots.gouv.fr and on the AIFE site. It is not there. It reached the market through operational notices from approved platforms to their own customers.

For a shared piece of national infrastructure nine days into a mandate, that is a thin channel. It also tells you something structural about the reform: your platform is now your early warning system as well as your transmission route. If it is quiet during an incident, you are blind to it.

Ask your provider how they notify you of PPF incidents, and whether you are on that list. Then confirm the window above with them directly, because a relayed notice is not a primary source, and I would not want you to treat this article as one either.

If you want the wider picture of where each mandate stands, our France mandate page and the 31-country mandate checker both carry sourced dates.