SI-V20-INV-R000Not marked as an SI-UBL 2.0 invoice
Also in:Nederlands
What it means
An SI-UBL 2.0 invoice must say so in its specification identifier (CustomizationID). Without it, receivers and validators don't know which Dutch rules apply.
Typical causes
- The export template still writes the old SI-UBL 1.2 identifier.
- The invoice is really a Peppol BIS invoice, but was checked as SI-UBL 2.0.
How to fix it
- Set the CustomizationID to urn:cen.eu:en16931:2017#compliant#urn:fdc:nen.nl:nlcius:v1.0.
- If you send over Peppol, you can also use the Peppol BIS Billing 3.0 identifier and check it as Peppol BIS.
- Export the invoice again.
Check your invoice for SI-V20-INV-R000
Open the free validator with SI-V20-INV-R000 already explained: paste or upload your XML and the finding, if any, is highlighted with its exact line.
Check my invoice3 free validations a month without an account. Invoice contents are never stored.
What the rule says (technical)
An SI-UBL 2.0 invoice or credit note MUST carry a specification identifier (BT-24) starting with urn:cen.eu:en16931:2017#compliant#urn:fdc:nen.nl:nlcius:v1.0.
Set the CustomizationID to urn:cen.eu:en16931:2017#compliant#urn:fdc:nen.nl:nlcius:v1.0, or send the invoice as Peppol BIS Billing 3.0 if the receiver expects that.
More errors with a worked fix
Related rules
- BR-01Invoice specification is missingSame field: BT-24
- PEPPOL-EN16931-R004Select the Peppol billing specificationSame field: BT-24
- BR-DE-21Document profile does not identify XRechnungSame field: BT-24
- IV-SYN-01Invoice file cannot be read
- IV-SYN-02Invoice format is not supported
- IV-SYN-03Number or date format is incorrect
- IV-SYN-04Invoice profile contains too little detail
- BR-CL-24Attachment type isn't allowed