France CIUS UBL

Official external specifications for the French e-invoicing reform. (opens new window)

As part of the French e-invoicing reform, domestic B2B invoices are exchanged through accredited platforms (Plateformes Agréées, PA). The French standard XP Z12-012 defines how these invoices are structured, based on the European norm EN 16931.

The France CIUS profile uses the standard EN 16931 specification identifier (BT-24):

urn:cen.eu:en16931:2017

The examples below come from XP Z12-012 Annexe B (v1.3) and contain French comments that map each element to its EN 16931 business term (BT). Next to the regular invoice, the examples show two use cases with an important structural difference:

• Credit note (avoir): uses the UBL CreditNote schema and references the initial invoice.
• Corrective invoice (facture rectificative): an invoice with type code 384 that corrects and references the initial invoice.

Submitting Peppol BIS Billing 3.0

Partners that already generate Peppol BIS Billing 3.0 invoices can keep doing so for regulated French domestic B2B invoices. eConnect accepts the Peppol BIS 3.0 document for inbound submission and transforms it to France CIUS UBL for outbound delivery to the receiving Plateforme Agréée (PA).

This transformation is only possible when all values required by the French CTC rules are present in the submitted document. eConnect cannot derive or supplement missing mandatory content; an incomplete document will result in an InvoiceSentError. Compared to a regular Peppol BIS Billing 3.0 invoice, pay attention to:

• Cadre de Facturation: the Cadre code (e.g. S1) is not placed in ProfileID — that element holds the Peppol process URI. Instead, provide it in an AdditionalDocumentReference with DocumentDescription set to CADRE_DE_FACTURATION.
• Mandatory legal notes: the three mandatory notes (#PMD# payment penalty terms, #PMT# fixed EUR 40 recovery fee, #AAB# early payment discount statement) must all be concatenated in a single cbc:Note element, because Peppol rule PEPPOL-EN16931-R002 allows only one Note element.
• Party identifiers: the seller and buyer EndpointID (BT-34, BT-49) must use schemeID="0225" and the seller and buyer SIREN (BT-30, BT-47) must use schemeID="0002". The buyer endpoint must be registered and active in the Annuaire.

The "Peppol BIS Billing 3.0" example below shows a regulated invoice with these elements in place, with English comments that map each element to its EN 16931 business term (BT).

XML Examples