NLCIUS (SI-UBL 2.0)
Netherlands · SI-UBL 2.0, 34 BR-NL rulesNLCIUS is the Dutch CIUS on EN 16931 UBL — also known as SI-UBL 2.0 (Simplerinvoicing), maintained by the Dutch Peppol Authority (peppolautoriteit-nl). It adds 34 Netherlands-specific business rules (BR-NL-*) on top of the shared EN 16931/Peppol core.
Part of CrateAPI's format coverage — see all formats.
What it is
NLCIUS validates against the current SI-UBL 2.0.3.13 rule set: we run the official phive-rules-simplerinvoicing 4.5.3 XSLT as the primary source, cross-checked against the peppolautoriteit-nl schematron as a second source, and test against the official test-set including its deliberately-invalid BR-NL-9 fixture. CrateAPI generates and validates this XML; a Dutch seller needs a valid KVK or OIN identifier (BR-NL-1), supplied via the invoice's legal-entity-ID field.
Where it's mandatory
The Netherlands requires SI-UBL/NLCIUS-conformant invoices for supplying Dutch central government (EU directive 2014/55/EU) and it's the standard profile for Peppol-based exchange in the country. We don't have a verified mandate-tracker entry for the Netherlands yet, so check peppolautoriteit-nl directly for current requirements by sector rather than a date from us.
What we don't do. CrateAPI doesn't transmit invoices to the Peppol network — we generate and validate the NLCIUS XML; sending it runs over your own Peppol Access Point.
Try it
curl -X POST "https://api.crateapi.com/v1/generate/ubl?profile=nlcius" \ -H "X-API-Key: YOUR_KEY" -H "Content-Type: application/json" \ -d @invoice.json -o invoice.xml
Relevant endpoints
| Endpoint | Notes |
|---|---|
POST /v1/generate/ubl?profile=nlcius | 34 Netherlands-specific BR-NL-* rules on top of the shared EN 16931/Peppol core. |
POST /v1/validate/ubl?profile=nlciusfree | Free, no API key — same free-forever validation as every other profile. |
Convert and render aren't extended to this profile yet — generate and validate are live today, convert/render are next.
Samples & docs
Read the full API reference for exact parameters, or try the format with your own file in the free validator.
FAQ
What rules does NLCIUS add on top of EN 16931?
34 Netherlands-specific business rules (BR-NL-*) — for example a Dutch seller must carry a valid KVK or OIN identifier (BR-NL-1), and corrective invoices need a reference to the original (BR-NL-9).
Which schematron does CrateAPI validate against?
The current official SI-UBL 2.0.3.13 rule set — primary source phive-rules-simplerinvoicing 4.5.3 (compiled XSLT), cross-checked against the peppolautoriteit-nl schematron as a second source, tested with the official test-set including its BR-NL-9 error fixture.
Does CrateAPI submit invoices to Dutch government or the Peppol network?
No — we generate and validate the NLCIUS XML; transmission runs over your own Peppol Access Point.