Netherlands SI-UBL 2.0 G-account Invoice
Dutch e-invoice with a G-account payment (SI-UBL 2.0)
A Dutch invoice that sends part of the amount to a blocked G-account, checked against the UBL 2.1 schema and the SI-UBL G-account rules.
About
The G-account extension of NLCIUS adds a second set of payment details, for invoices where part of the amount goes to a blocked G-account (G-rekening). Apart from that, the invoice follows NLCIUS. Its identifier is urn:cen.eu:en16931:2017#compliant#urn:fdc:nen.nl:nlcius:v1.0#conformant#urn:fdc:nen.nl:gaccount:v1.0.
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 G-account validation artefacts 1.0.2.13, with the NLCIUS rules and the EN 16931 rules 1.3.16 adapted for two payment means.
- 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
-
common/UBL-CommonAggregateComponents-2.1.xsd
-
common/UBL-CommonBasicComponents-2.1.xsd
-
common/UBL-CommonExtensionComponents-2.1.xsd
-
common/UBL-QualifiedDataTypes-2.1.xsd
-
common/UBL-UnqualifiedDataTypes-2.1.xsd
-
common/UBL-ExtensionContentDataType-2.1.xsd
-
common/CCTS_CCT_SchemaModule-2.1.xsd
-
common/UBL-CommonSignatureComponents-2.1.xsd
-
common/UBL-SignatureAggregateComponents-2.1.xsd
-
common/UBL-SignatureBasicComponents-2.1.xsd
-
common/UBL-xmldsig-core-schema-2.1.xsd
-
common/UBL-XAdESv132-2.1.xsd
-
common/UBL-XAdESv141-2.1.xsd
The validator loads all of these with their folder structure, so includes and imports resolve as published.
Business rules
Schematron · run in this orderThe 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-gaccount.xml · 5.3 KB · passes the schema and the rules
In CI and from code
The same schema by its name, nl-si-ubl-gaccount, through the API.
npx @xmlvalid/cli validate "**/*.xml" --schema nl-si-ubl-gaccount
- uses: xmlvalid/validate-action@v1
with:
files: "**/*.xml"
schema: nl-si-ubl-gaccount
api-key: ${{ secrets.XMLVALID_API_KEY }}
curl https://xmlvalid.com/api/v1/validations \
-H "Authorization: Bearer $XMLVALID_API_KEY" \
-F document=@nl-si-ubl-gaccount.xml \
-F schema=nl-si-ubl-gaccount
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