EN16931 1.3.16 · UBL / CII · Severity: ERROR
An Invoice shall have an Invoice type code (BT-3)
The document must state its UNTDID 1001 document type code (such as 380 for a commercial invoice or 381 for a credit note).
- Rule ID & Severity
BR-04· ERROR- Standard & Scope
- EN16931 1.3.16 · UBL / CII
- XPath Condition
exists(cbc:InvoiceTypeCode | cbc:CreditNoteTypeCode)- Target XML Path
cbc:InvoiceTypeCode
Find the source field
cbc:InvoiceTypeCode
Match namespace URI and element name, not a particular prefix spelling. The validator reports the full expanded-name source path when the published rule supplies a location.
Common causes
- InvoiceTypeCode was omitted during UBL generation.
- A text label like "INVOICE" was used instead of UNTDID 1001 code 380.
Invalid and corrected fragments
<!-- InvoiceTypeCode missing -->
<cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>
Supply a valid UNTDID 1001 code (e.g., 380 for commercial invoice, 381 for credit note, 384 for corrected invoice).
Open BR-04 in en16931-validator →
Verify the whole document
These are fragments, not complete invoices. The exact rule is exercised by synthetic mutation tests against the stated package. Correcting one field does not prove conformance; run the full selected validator again. Published messages and severity remain authoritative.
Explanation record: 2026-10-14 · Local WebAssembly / SaxonJS validation. No invoice-derived report is published as a search page.