BR-04
An Invoice shall have an Invoice type code (BT-3).
What does this rule mean?
The invoice is missing the invoice type code (BT-3).
The type code (e.g. 380 invoice, 384 corrected invoice) tells the receiver what kind of document this is.
- BT-3
- Invoice type code (UNTDID 1001)
Official rule message (standard)
An Invoice shall have an Invoice type code (BT-3).
Where the rule applies
Syntax: CII · UBL
The same rule, expressed twice: UBL and CII name the same fields with different paths. Running a CII file against the UBL rules is why you get errors that mean nothing.
UBL
/ubl:Invoice | /cn:CreditNote
CII
/rsm:CrossIndustryInvoice
Technical test
The rule passes when this Schematron expression holds true:
normalize-space(rsm:ExchangedDocument/ram:TypeCode) != ''How to fix it
A missing or incorrect business entry only you can supply. Add or correct it, then re-check.
Add the invoice type code (UNTDID 1001), usually 380.
Correct the affected entry in your XML, then re-check the invoice. Validation runs locally in your browser — your file never leaves your machine.
Check an e-invoice here
Drop an XML or ZUGFeRD PDF file here. Validation runs locally in your browser against EN 16931 — your file never leaves your machine.