EN 16931 core rules
BR-CL-01: Invoice type code (BT-3) must be a code from the UNTDID 1001 list
What this rule requires
Invoice type code (BT-3) must be a code from the UNTDID 1001 list.
ExampleEN 16931 (UBL)
An invoice built like a valid one, except for this:
<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2" xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2" xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">
<cbc:CustomizationID>urn:cen.eu:en16931:2017</cbc:CustomizationID>
<cbc:ID>INV-1001</cbc:ID>
<cbc:IssueDate>2026-01-15</cbc:IssueDate>
<cbc:InvoiceTypeCode>999</cbc:InvoiceTypeCode>
<cbc:DocumentCurrencyCode>EUR</cbc:DocumentCurrencyCode>
<cbc:BuyerReference>04011000-12345-67</cbc:BuyerReference>
</Invoice>The validator says: Invoice type code (BT-3) carries 999, which is not a value this document type allows.
How to fix it
Replace the value in Invoice type code with one this document type allows.
Frequently asked questions
- What does BR-CL-01 mean?
- Invoice type code (BT-3) must be a code from the UNTDID 1001 list. The rule runs under EN 16931 (UBL), Peppol BIS 3.0, and XRechnung 3.0 (UBL).
- How do I fix BR-CL-01?
- Replace the value in Invoice type code with one this document type allows. In UBL the element is /Invoice/cbc:InvoiceTypeCode.
Runs under these profiles
- EN 16931 (UBL)
- Peppol BIS 3.0
- XRechnung 3.0 (UBL)
Element path
- Invoice type code (BT-3)UBL /
Invoice/ cbc:InvoiceTypeCodeCII / CrossIndustryInvoice/ ExchangedDocument/ TypeCodeRead from what WorkAlio's CII parser accepts — there is no CII writer yet, so this path is not independently verified the way the UBL path is.