BR-DE-17
Mit dem Element "Invoice type code" (BT-3) sollen ausschließlich folgende Codes aus der Codeliste UNTDID 1001 übermittelt werden: 326 (Partial invoice), 380 (Commercial invoice), 384 (Corrected invoice), 389 (Self-billed invoice) und 381 (Credit note),875 (Partial construction invoice), 876 (Partial final construction invoice), 877 (Final construction invoice).
What does this rule mean?
The invoice type code (BT-3) used is not allowed for XRechnung.
XRechnung permits only certain codes (e.g. 326 partial, 380 invoice, 384 corrected, 389 self-billed, 381 credit note, 875/876/877).
- BT-3
- Invoice type code (UNTDID 1001)
Official rule message (standard)
Mit dem Element "Invoice type code" (BT-3) sollen ausschließlich folgende Codes aus der Codeliste UNTDID 1001 übermittelt werden: 326 (Partial invoice), 380 (Commercial invoice), 384 (Corrected invoice), 389 (Self-billed invoice) und 381 (Credit note),875 (Partial construction invoice), 876 (Partial final construction invoice), 877 (Final construction invoice).
Official rule message from the standard.
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) = ('326', '380', '384', '389', '381', '875', '876', '877')How to fix it
A missing or incorrect business entry only you can supply. Add or correct it, then re-check.
Use a permitted invoice type code, 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.