Skip to content

BR-DE-17: Invoice type code (BT-3) is not intended for XRechnung

Official message

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

XRechnung (CII) · Warning · Message language: German · Version: xrechnung-3.0.2-validator-configuration-2026-08-31

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

XRechnung (UBL) · Warning · Message language: German · Version: xrechnung-3.0.2-validator-configuration-2026-08-31
Severity
Warning Note: this does not make the invoice invalid, but it should be checked.
Applies to
XRechnung (CII), XRechnung (UBL)
Affected fields
BT-3

What does this mean?

In XRechnung the invoice type code (BT-3) should be one of the codes 326, 380, 384, 389, 381, 875, 876 or 877 from UNTDID 1001. The invoice uses a different code. The message is a warning.

Typical causes

Another code from UNTDID 1001 was selected, e.g. 386 (prepayment invoice) or 393 (factored invoice).
The code was taken over from another system that uses other invoice types.

How to fix the error

Set the invoice type code to one of the intended values: 380 (commercial invoice), 326 (partial invoice), 384 (corrected invoice), 389 (self-billed invoice), 381 (credit note), 875 (partial construction invoice), 876 (partial final construction invoice) or 877 (final construction invoice).
CII: rsm:ExchangedDocument/ram:TypeCode, UBL: cbc:InvoiceTypeCode or cbc:CreditNoteTypeCode.
Generate and validate the invoice again.

In E-Rechnungsfreund

In the invoice form, section "Rechnungsdetails" (invoice details), select one of these codes in the field "Art-Code (BT-3)".

Example

Wrong

<rsm:ExchangedDocument>
  <ram:ID>RE-2026-001</ram:ID>
  <ram:TypeCode>386</ram:TypeCode>
  ...
</rsm:ExchangedDocument>

Correct

<rsm:ExchangedDocument>
  <ram:ID>RE-2026-001</ram:ID>
  <ram:TypeCode>380</ram:TypeCode>
  ...
</rsm:ExchangedDocument>
For developers: test expression per syntax

XRechnung (CII) (CII)

Context: /rsm:CrossIndustryInvoice

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

XRechnung (UBL) (UBL)

Context: /ubl:Invoice | /cn:CreditNote

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

Related validation rules

  • BR-DE-1: Payment instructions (BG-16) are missing
  • BR-DE-10: Deliver to city (BT-77) is missing
  • BR-DE-11: Deliver to post code (BT-78) is missing
  • BR-DE-14: VAT category rate (BT-119) is missing in the VAT breakdown
  • BR-DE-15: Buyer reference (BT-10) is missing
  • BR-DE-16: Seller VAT ID, tax number or tax representative is missing

Frequently asked questions

Is the invoice invalid because of this warning?

The rule is classified as a warning, not as an error. Whether the recipient still accepts the invoice is up to the recipient; using the intended codes avoids queries.

Last updated:
Explanation of the validation rule, not legal or tax advice.