BR-04: what it means and how to fix it
An invoice must have an invoice type code.
| Rule | BR-04 |
|---|---|
| Standard | EN 16931-1, the European standard for electronic invoices |
| Severity | Error (the invoice is not conformant) |
| Concerns | BT-3: Invoice type code |
How to fix it
Add the type code: 380 for an invoice, 381 for a credit note, 384 for a corrected invoice.
Where the field is in the XML
| Term | CII (XRechnung-CII, ZUGFeRD, Factur-X) | UBL (XRechnung-UBL, Peppol) |
|---|---|---|
| BT-3 Invoice type code | rsm:ExchangedDocument/ram:TypeCode | cbc:InvoiceTypeCode |
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-04 mean?
An invoice must have an invoice type code. It is a rule of EN 16931-1, the European standard for electronic invoices.
How do I fix BR-04?
Add the type code: 380 for an invoice, 381 for a credit note, 384 for a corrected invoice.
Is BR-04 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-17: The invoice type code should be one of 326, 380, 384, 389, 381, 875, 876 or 877.
Rule numbers are those of EN 16931-1; the explanation is ours. Not tax or legal advice.