DE-R-017
The element "Invoice type code" (BT-3) should only contain the following values from code list UNTDID 1001: 326 (Partial invoice), 380 (Commercial invoice), 384 (Corrected invoice), 389 (Self-billed invoice), 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)
The element "Invoice type code" (BT-3) should only contain the following values from code list UNTDID 1001: 326 (Partial invoice), 380 (Commercial invoice), 384 (Corrected invoice), 389 (Self-billed invoice), 381 (Credit note), 875 (Partial construction invoice), 876 (Partial final construction invoice), 877 (Final construction invoice).
Where the rule applies
Syntax: UBL
Affected element (XPath):
(/ubl-invoice:Invoice | /ubl-creditnote:CreditNote)[$supplierCountryIsDE and $customerCountryIsDE]
Technical test
The rule passes when this Schematron expression holds true:
cbc:InvoiceTypeCode = $supportedInvAndCNTypeCodes or cbc:CreditNoteTypeCode = $supportedInvAndCNTypeCodesHow 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.