BR-DE-17: Invoice type code outside the XRechnung codes

Severity: warning · Syntax: CII, UBL

Official message

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 this means

BR-DE-17 is a should-rule (severity warning). Invoice type code (BT-3) should use only these UNTDID 1001 codes: 326, 380, 384, 389, 381, 875, 876 and 877. The UBL assertion compares InvoiceTypeCode or CreditNoteTypeCode with that set, named supportedInvAndCNTypeCodes in the stylesheet.

Typical cause

Another 1001 code was exported that exists in EN 16931 but is not in this XRechnung list.

How to fix it

Use a code from the list, 380 for an ordinary invoice. The rule warns; in the Schematron file it is not fatal.

UBL

<cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>

CII

<ram:TypeCode>380</ram:TypeCode>

Business term

Invoice type code (BT-3)

Related rules

Context and assertion

UBL /ubl:Invoice | /cn:CreditNote

CII /rsm:CrossIndustryInvoice

UBL

normalize-space(cbc:InvoiceTypeCode) = $supportedInvAndCNTypeCodes or normalize-space(cbc:CreditNoteTypeCode) = $supportedInvAndCNTypeCodes

CII

normalize-space(rsm:ExchangedDocument/ram:TypeCode) = ('326', '380', '384', '389', '381', '875', '876', '877')

Check a file now, free of charge

curl -F "file=@rechnung.xml" https://checkxrechnung.com/v1/validate

Questions

What does BR-DE-17 actually check?

How do I fix BR-DE-17?

Use a code from the list, 380 for an ordinary invoice. The rule warns; in the Schematron file it is not fatal.

If BR-DE-17 passes, is the invoice legally compliant?

No. This page helps you read this one Schematron assertion. A pass is not a statement about tax law, portal acceptance, or bank overlays.