Skip to content

Warning: worth checking

BR-DE-17: Use an invoice type code XRechnung expects

In short

BR-DE-17 means the invoice type code (BT-3) is not one XRechnung expects. Fix it by using 380 for a normal invoice, 381 for a credit note, 384 for a corrected invoice, 389 for a self-billed invoice or 326 for a partial invoice.

On this page

What it means

In an XRechnung the invoice type code (BT-3) should be one of these codes: 326 for a partial invoice, 380 for a commercial invoice, 384 for a corrected invoice, 389 for a self-billed invoice, 381 for a credit note, and 875, 876 or 877 for a partial, partial final or final construction invoice.

Why it matters

This is a warning, so the invoice is still accepted. It is worth fixing, because German recipients use this information to process the invoice automatically, and a portal or buyer may ask you to correct it.

How to fix it

Choose the document type in your invoicing software rather than typing a code; most invoices are 380. Codes such as 386 (prepayment invoice) or 393 (factored invoice) are valid in EN 16931 but not expected here, so use 380 or 326 and describe the special case in a note. In the XML it is cbc:InvoiceTypeCode (UBL) or ram:TypeCode (CII).

The rule as published

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).

Business terms: BT-3

Where this rule applies

Rule set Version
XRechnung 3.0 (UBL) 3.0.2
XRechnung 3.0 (UBL credit note) 3.0.2
XRechnung 3.0 (CII) 3.0.2
Rule text from phive-rules 4.6.4.

Check your file

Drop your e-invoice to see whether BR-DE-17 still fails, and which other rules do.