BR-01: what it means and how to fix it
An invoice must have a specification identifier.
| Rule | BR-01 |
|---|---|
| Standard | EN 16931-1, the European standard for electronic invoices |
| Severity | Error (the invoice is not conformant) |
| Concerns | BT-24: Specification identifier |
How to fix it
Add the identifier of the standard the file follows, for example urn:cen.eu:en16931:2017 or the XRechnung identifier.
Where the field is in the XML
| Term | CII (XRechnung-CII, ZUGFeRD, Factur-X) | UBL (XRechnung-UBL, Peppol) |
|---|---|---|
| BT-24 Specification identifier | rsm:ExchangedDocumentContext/ram:GuidelineSpecifiedDocumentContextParameter/ram:ID | cbc:CustomizationID |
From your code
curl -H "Authorization: Bearer $API_KEY" -H "Content-Type: application/xml" \
--data-binary @invoice.xml "https://tools.funwords.eu/einvoice/validate"The answer lists every broken rule with its number, the field, a message with the figures from your file and the fix. E-invoice API: validate, convert to JSON, and create XRechnung or ZUGFeRD XML from JSON.
Questions
What does BR-01 mean?
An invoice must have a specification identifier. It is a rule of EN 16931-1, the European standard for electronic invoices.
How do I fix BR-01?
Add the identifier of the standard the file follows, for example urn:cen.eu:en16931:2017 or the XRechnung identifier.
Is BR-01 an error or a warning?
An error: a validator reports the invoice as not conformant, and a recipient that validates incoming e-invoices can reject it.
Related rules
- BR-DE-21: The specification identifier should be the XRechnung identifier.
Rule numbers are those of EN 16931-1; the explanation is ours. Not tax or legal advice.