BR-03: what it means and how to fix it
An invoice must have an issue date.
| Rule | BR-03 |
|---|---|
| Standard | EN 16931-1, the European standard for electronic invoices |
| Severity | Error (the invoice is not conformant) |
| Concerns | BT-2: Invoice issue date |
How to fix it
Add the issue date (CII: format 102, YYYYMMDD; UBL: YYYY-MM-DD).
Where the field is in the XML
| Term | CII (XRechnung-CII, ZUGFeRD, Factur-X) | UBL (XRechnung-UBL, Peppol) |
|---|---|---|
| BT-2 Invoice issue date | rsm:ExchangedDocument/ram:IssueDateTime/udt:DateTimeString[@format='102'] | cbc:IssueDate |
From your code
curl -H "Authorization: Bearer $API_KEY" -H "Content-Type: application/xml" \
--data-binary @invoice.xml "https://agent-data-tools.revmesh2074.workers.dev/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-03 mean?
An invoice must have an issue date. It is a rule of EN 16931-1, the European standard for electronic invoices.
How do I fix BR-03?
Add the issue date (CII: format 102, YYYYMMDD; UBL: YYYY-MM-DD).
Is BR-03 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.
Rule numbers are those of EN 16931-1; the explanation is ours. Not tax or legal advice.