🚧

Caution

You must use the Vertex e-Invoicing Messaging API to use this feature. This API is explained in the Vertex e-Invoicing Messaging API: Overview section.

Mandate

France's electronic invoicing reform requires every domestic B2B and B2G structured invoice to be accompanied by standardized lifecycle events. These events are transmitted as CDAR messages (Cross Domain Acknowledgement and Response). CDAR messages provide complete traceability from invoice submission, through routing and processing, to final payment.

The AFNOR XP Z12-012 standard defines all lifecycle status codes, sequencing rules, and actor responsibilities.

Key Actors in the French Lifecycle Exchange Model

PA-E - Issuer's Accredited Platform

The platform used by the seller (issuer).
PA-E is responsible for:

• Performing issuer side checks, creating in case of error the 213 - Rejected status
• Confirming the correct submission of the invoice generating the 200 - Submitted status
• Forwarding the invoice to PA-R via Flux 2
• Transmitting VAT relevant invoice data (Flux 1) to the PPF
• Relaying seller side processing statuses to PA-R
• Transmitting mandatory lifecycle statuses to the PPF

PA-R - Receiver's Accredited Platform

The platform used by the buyer (recipient).
PA-R is responsible for:

• Receipt side validations, creating in case of error the 213 - Rejected status
• Creating statuses such as 202 - Received or 203 - Made Available to confirm the correct reception of the invoice and the provision of the invoice to the buyer
• Delivering the invoice (Flux 2) to the buyer
• Relaying buyer side processing statuses back to PA-E
• Transmitting mandatory lifecycle statuses to the PPF

CDAR - The Official Lifecycle Message Format

By default, lifecycle messages are transmitted using the CDAR format, which:

• Uses UN/CEFACT CII syntax
• Forms part of the minimum mandatory structure for lifecycle reporting
• Is defined in XP Z12-012_Annexe_A_2026_V1.3, in the sheet titled "CDV FE - CDAR"

VRBL Requirement for Lifecycle Messages

To simplify development, you will submit lifecycle using the VRBL format to construct lifecycle messages submitted to Vertex e-Invoicing.

VRBL lifecycle payloads are transformed into fully compliant CDAR CII messages as defined in XP Z12-012.

Additionally:
Any transmission or processing phase lifecycle statuses received from PA-E, PA-R, or the PPF will also be made available in VRBL format, ensuring that inbound and outbound status data shares the same structure.

Two Lifecycle Phases

Transmission Phase

Created only by PA-E or PA-R.

These statuses describe the technical routing of the invoice between platforms.

Processing Phase

Triggered by actions conducted by the buyer or by the seller.

These statuses describe business handling and commercial decisions.

Mandatory, Optional, and Conditional Statuses

XP Z12-012 standard identifies four statuses that may be required by the State (PPF).

Two of these are directly handled by PA-E and/or PA-R:

• 200 - Submitted confirming the correct reception of the invoice by PA-E
• 213 - Rejected in case of the invoice didn't go through the official validations defined

Two of these are conditional:

• 210 - Refused is mandatory only when the buyer actually refuses a received invoice. To note that the refusal of an invoice corresponds to its cancellation, which means that the seller will have to issue an internal credit note and then a new invoice.
• 212 - Payment Received is mandatory only when VAT becomes due at the time of payment/on collection.

Complete CDAR Lifecycle Status Table

(Codes, covering actor, phase, and mandatory logic - derived from AFNOR standard XP Z12-012)

Processing Phase Statuses (Buyer, Seller, PA-E, or PA-R)

Details

Restrictions

You must use the Vertex e-Invoicing Messaging API to use this country, format and Document Type. More information about the API is provided in the Vertex e-Invoicing Messaging API: Overview section.

In this section