France E-Invoicing Lifecycle Statuses in 2026: What ERP Teams Should Log Before Cutover
Published August 2026 by Solarc Labs
Invoice payloads are only one side of the production conversation
DGFiP lists XP Z12-012 among the currently applicable standards for the French reform. The standard covers both invoice message formats and lifecycle-status messages in the minimum framework. That means an ERP cutover cannot be tested only by generating a UBL, CII or Factur-X file and observing that an upload endpoint accepted it. The integration also needs to consume, correlate and preserve the lifecycle information returned through the regulated ecosystem.
Treat CDAR lifecycle messages as business evidence, not debug noise
XP Z12-012 defines the lifecycle-status message in the UN/CEFACT CDAR syntax. An integration team should decide where the raw status message is preserved, how it is normalized into the application state model, and which identifiers connect it back to the exact invoice and source transaction. If status data exists only in transient logs, finance and support teams will struggle to reconstruct what happened when a production invoice takes an unexpected path.
Do not collapse transport acknowledgement into business acceptance
A successful API call, a received file and a downstream invoice lifecycle state answer different questions. Design the state model so a transport-level success cannot silently become a final business outcome. Preserve the upstream invoice identifier, platform tracking reference, status code, event time and the original message or evidence needed for later review. This separation is especially important during cutover because a technically successful exchange can still expose a business-rule, recipient or workflow exception later in the lifecycle.
Test negative paths and out-of-order events before production
Happy-path testing should be the smallest part of lifecycle QA. Use a bounded test matrix that includes a rejected or failed path, repeated delivery, delayed status arrival, replay after a temporary integration failure and reconciliation when the source application missed an event. The exact behavior depends on the chosen Plateforme Agréée and implementation. The useful engineering question is whether your source system can recover a truthful state without inventing success or losing the evidence that explains the exception.
Corpus preflight can prepare invoice data, but it cannot certify PA lifecycle behavior
InvoiceBatch FR is not a Plateforme Agréée and does not transmit invoices or lifecycle messages. It can help isolate upstream source-data and structured-invoice defects before those files enter the regulated exchange, but lifecycle delivery, processing and recipient-side outcomes remain properties of the actual PA and production integration. Use the preflight evidence to reduce source uncertainty, then verify lifecycle behavior in the real integration environment with the selected platform.
Primary sources
Sources used for this article
Continue the job