Sign in Open validatorValidator
XSD+SCH Peppol Autoriteit NL (Stichting Simplerinvoicing) · SI-UBL 2.0.3.13 (NLCIUS 1.0.3)

Netherlands SI-UBL 2.0 Invoice (NLCIUS)

Dutch e-invoice (SI-UBL 2.0, NLCIUS)

A Dutch e-invoice in SI-UBL 2.0, checked against the UBL 2.1 schema and the NLCIUS rules: EN 16931 with the Dutch BR-NL rules.

Validate with this schema Try it with the example

About

NLCIUS is the Dutch core invoice usage specification of EN 16931, and SI-UBL 2.0 its UBL form. Suppliers of the Dutch central government must invoice electronically, mostly through Peppol. Its specification identifier (BT-24) is urn:cen.eu:en16931:2017#compliant#urn:fdc:nen.nl:nlcius:v1.0.

The Dutch rules (BR-NL-*) apply to suppliers in the Netherlands: a KVK or OIN number for the seller, a buyer reference or order reference, a full Dutch address, the allowed payment means and invoice type codes, and fields the specification advises against (warnings).

E-invoicing in the Netherlands: 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 rules are the SI-UBL 2.0 validation artefacts 2.0.3.13 (release of 21 May 2026, in effect since 17 August 2026), which include the EN 16931 rules 1.3.16, in one set.
  • The example is from the SI-UBL test documents of Peppol Autoriteit NL (MIT).

Files

14 files · 2.7 MB · Download all (.zip)
  • maindoc/UBL-Invoice-2.1.xsd main
    58.8 KB View Download
  • common/UBL-CommonAggregateComponents-2.1.xsd
    2.3 MB View Download
  • common/UBL-CommonBasicComponents-2.1.xsd
    214.7 KB View Download
  • common/UBL-CommonExtensionComponents-2.1.xsd
    9.3 KB View Download
  • common/UBL-QualifiedDataTypes-2.1.xsd
    3.5 KB View Download
  • common/UBL-UnqualifiedDataTypes-2.1.xsd
    26.7 KB View Download
  • common/UBL-ExtensionContentDataType-2.1.xsd
    4.2 KB View Download
  • common/CCTS_CCT_SchemaModule-2.1.xsd
    44.2 KB View Download
  • common/UBL-CommonSignatureComponents-2.1.xsd
    5.4 KB View Download
  • common/UBL-SignatureAggregateComponents-2.1.xsd
    7.6 KB View Download
  • common/UBL-SignatureBasicComponents-2.1.xsd
    4.1 KB View Download
  • common/UBL-xmldsig-core-schema-2.1.xsd
    10.5 KB View Download
  • common/UBL-XAdESv132-2.1.xsd
    21.2 KB View Download
  • common/UBL-XAdESv141-2.1.xsd
    1.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

nl-si-ubl-invoice.xml · 16.8 KB · passes the schema and the rules

View Open in validator

In CI and from code

The same schema by its name, nl-si-ubl-invoice, through the API.

npx @xmlvalid/cli validate "**/*.xml" --schema nl-si-ubl-invoice
- uses: xmlvalid/validate-action@v1
  with:
    files: "**/*.xml"
    schema: nl-si-ubl-invoice
    api-key: ${{ secrets.XMLVALID_API_KEY }}
curl https://xmlvalid.com/api/v1/validations \
  -H "Authorization: Bearer $XMLVALID_API_KEY" \
  -F document=@nl-si-ubl-invoice.xml \
  -F schema=nl-si-ubl-invoice

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