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

France EXTENDED-CTC-FR (CII)

French e-invoice, EXTENDED-CTC-FR profile (CII, XP Z12-012)

An invoice in the French EXTENDED-CTC-FR profile in CII syntax, checked against the CII D22B schema, the EXTENDED-CTC-FR 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.

EXTENDED-CTC-FR is the French extension of EN 16931 for invoices the standard cannot carry: multi-vendor invoices (several sellers on one invoice, as on marketplaces), invoice sub-lines and other added data. FNFE-MPE publishes its rules as a version of the EN 16931 rules that allows these additions; on top of them run the same French rules (BR-FR-*) as for the EN 16931 profile, 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 schema is the UN/CEFACT CII D22B with uncoupled code lists, as FNFE-MPE names it for CII invoices.
  • The EXTENDED-CTC-FR rules replace the EN 16931 rules for this profile; FNFE-MPE derives them from EN 16931 release 1.3.16 and publishes them under the EUPL.
  • The example is use case 13 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-uc13-invoice-extended-cii.xml · 30.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-extended-cii, through the API.

npx @xmlvalid/cli validate "**/*.xml" --schema france-ctc-extended-cii
- uses: xmlvalid/validate-action@v1
  with:
    files: "**/*.xml"
    schema: france-ctc-extended-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-extended-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