xmlvalid
Sign in Open validator
XSD+SCH AFNOR and FNFE-MPE · XP Z12-012 1.4, rules 1.4.0.04

France e-invoice (CII)

French e-invoice, EN 16931 profile (CII, XP Z12-012)

An invoice for the French e-invoicing reform in CII syntax, checked against the CII D22B schema, the EN 16931 rules and the French rules (BR-FR-*) published by FNFE-MPE.

Validate with this schema Try it with the example

About

France's e-invoicing reform makes electronic invoices compulsory between French businesses: every company has had to be able to receive them since 1 September 2026, and large and mid-sized companies issue them from that date, through an approved platform (plateforme agréée). The formats are UBL, CII and Factur-X, under the AFNOR standard XP Z12-012.

On top of EN 16931, the French rules (BR-FR-*) check what the reform needs: SIREN and SIRET identifiers, the business process (BT-23, such as S1 or B1), invoice numbers and dates in the expected format, the electronic addresses of both parties, and VAT details. FNFE-MPE publishes them as Schematron; this profile runs them in their "fatal" form, which applies from 1 October 2026.

E-invoicing in France: the rules in short and how to check an invoice →

Good to know

  • Rules run only when the document matches the schema. Documents over 50 MB are checked against the schema only.
  • The EN 16931 rules are release 1.3.16, the one the French rules are published with. Invoices with data beyond EN 16931 (multi-vendor invoices, sub-lines) use the EXTENDED-CTC-FR profile.
  • The schema is the UN/CEFACT CII D22B with uncoupled code lists, as FNFE-MPE names it for CII invoices; any invoice that passes the D16B subset of EN 16931 passes it too.
  • The example is use case 1 of the FNFE-MPE examples for XP Z12-012 (Apache License 2.0).

Files

4 files · 334.7 KB
  • CrossIndustryInvoice_100pD22B.xsd main
    1.9 KB View Download
  • CrossIndustryInvoice_100pD22B_urn_un_unece_uncefact_data_standard_QualifiedDataType_100.xsd
    40.4 KB View Download
  • CrossIndustryInvoice_100pD22B_urn_un_unece_uncefact_data_standard_ReusableAggregateBusinessInformationEntity_100.xsd
    287 KB View Download
  • CrossIndustryInvoice_100pD22B_urn_un_unece_uncefact_data_standard_UnqualifiedDataType_100.xsd
    5.5 KB View Download

The validator loads all of these with their folder structure, so includes and imports resolve as published.

Business rules

Schematron · run in this order

The rules run after the schema check, only when the document matches the schema, and in your browser like the schema check (with SaxonJS by Saxonica). Each finding names its rule, such as BR-CO-15, and the line it points at; each rule has a page with what it checks.

Example document

fr-uc1-invoice-cii.xml · 21.3 KB · passes the schema and the rules

View Open in validator

In CI and from code

The same schema by its name, france-ctc-cii, through the API.

npx @xmlvalid/cli validate "**/*.xml" --schema france-ctc-cii
- uses: xmlvalid/validate-action@v1
  with:
    files: "**/*.xml"
    schema: france-ctc-cii
    api-key: ${{ secrets.XMLVALID_API_KEY }}
curl https://xmlvalid.com/api/v1/validations \
  -H "Authorization: Bearer $XMLVALID_API_KEY" \
  -F document={{ $schema->example ?? 'document.xml' }} -F schema=france-ctc-cii

Free accounts get 100 API validations a month. On Pro, a URL monitor can check a published document against this schema every hour and email you when it breaks. More CI setups