xmlvalid
Sign in Open validator
XSD+SCH FNFE-MPE and FeRD · 1.09.2

Factur-X / ZUGFeRD EXTENDED

The Factur-X and ZUGFeRD profile with more data than EN 16931, for industries that need it.

Validate with this schema Try it with the example

About

EXTENDED adds fields that EN 16931 leaves out, such as more party roles, delivery details per line and sub-lines. It is a superset of the EN 16931 profile.

Two layers are checked: the profile schema, then the profile's Schematron rules with their code lists.

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

Good to know

  • In the validator you can drop the PDF itself: its XML attachment is opened and the profile picked from its specification identifier. So do the API and the command-line client. Rules run only when the document matches the schema.
  • The schemas, rules, code lists and example come from the akretion/factur-x library, which ships the official files unchanged.

Files

4 files · 39.3 KB
  • extended/Factur-X_EXTENDED.xsd main
    1.6 KB View Download
  • extended/Factur-X_1.09_EXTENDED_urn_un_unece_uncefact_data_standard_QualifiedDataType_100.xsd
    5.1 KB View Download
  • extended/Factur-X_1.09.2_EXTENDED_urn_un_unece_uncefact_data_standard_ReusableAggregateBusinessInformationEntity_100.xsd
    29.3 KB View Download
  • extended/Factur-X_1.09_EXTENDED_urn_un_unece_uncefact_data_standard_UnqualifiedDataType_100.xsd
    3.3 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

factur-x-extended.xml · 66 KB · passes the schema and the rules

View Open in validator

In CI and from code

The same schema by its name, factur-x-extended, through the API.

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

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