Validation

How the corpus was validated

Every test invoice was checked with the official validation artefacts of each format it claims: the XML schemas, the CEN EN 16931 schematron and the schematron of the national or network profile. XSD validation ran on a Java 21 runtime (Eclipse Temurin); the schematron rules ran as compiled XSLT with Saxon-HE 12.5. The artefacts were downloaded from their publishers and used unchanged. They are not redistributed here.

Are the validators live?

A run with zero findings proves little unless the same setup also rejects broken input. Deliberately broken copies of the test invoices were rejected as expected: the scheme VIN instead of AKG fails the CEN rule BR-CL-07; two line object identifiers on one line fail the XSD and the Peppol rule R100; two invoice notes on a cross-border Peppol invoice fail the Peppol rule R002.

Not yet run

The KoSIT validator application, the official FNFE and FeRD validators, Mustangproject, Peppol BIS 3.0.21, delivery through Peppol access points, and import into accounting and procurement systems. Results will be added here as they come in.

Reference checker

The format validators above do not know VINvoice. The reference checker reads an invoice (CII or UBL), applies the reading rules and reports where a vehicle line departs from the convention. It takes grammars, labels and the statutory flag from registry.json, so it follows the registry without code changes. It never rejects an invoice: an error means only that the line does not conform to VINvoice. The checker is a single Python file without dependencies, licensed under Apache-2.0 (checker/vehicle_check.py) . A regression test runs it on every test invoice and compares the result with the expected findings.

Schematron

The same rules are published as ISO Schematron, vinvoice.sch, generated from the registry. It runs on CII and UBL invoices in any XSLT 2.0 Schematron processor, next to the EN 16931 and national rules. Rule identifiers match the checker. The VIN check digit (V-05), the six-months-or-6,000-km test of V-08, the registration-number comparison (V-18) and the reader notes on level 0 and attached lines (V-19, V-20) stay with the checker. On the test corpus both report the same errors and warnings; continuous integration checks this on every change.